getaddrinfo failed: Name or service not known error in event_demon.log file
search cancel

getaddrinfo failed: Name or service not known error in event_demon.log file


Article ID: 202434


Updated On:


CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent Autosys Workload Automation



[10/27/2020 00:00:08]      CAUAJM_I_40245 EVENT: ALARM            ALARM: STARTJOBFAIL     JOB: sat_cam_plainid_autostartjob MACHINE: HOSTNAME1233   TEXT: <Owner attribute error. User does not exist in the system>
getaddrinfo failed: Name or service not known



Release : 12.0

Component : CA Workload Automation AE (AutoSys)


In the log file, where the getaddrinfo message failed, the log messages are not formatted. There is no date/time header or a CAUAJM catalog associated with the message. This was happening for STARTJOBFAIL/JOBFAILURE alarms.

Check if the jobs/scheduler config to see if there are some UNIX commands that are being run on STARTJOBFAIL/JOBFAILURE, or as part of SNMP traps. That command is being executed by the scheduler, and redirects UNIX stdout and stderr to the scheduler log file.  It will not be able to intercept those messages in order to format them so they appear in the log just as the UNIX command outputs them.



Its not the scheduler itself that's causing the behavior, but the commands the scheduler is running externally on the alarms, or the SNMP configuration that's causing the error.


In this case, customer had a wrong/invalid SNMP hostname, which was causing the error