Snmp not enabled after kill -HUP of event demon

Document ID : KB000004823
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

We updated the Autosys configuration file with these attributes

SnmpManagerHosts=<host name of the snmp trap manager>

SnmpCommunity=public

Then we executed a 'kill -HUP <event demon PID>, which reloads the configuration file but keeps the scheduler running.

The end result is  - we still do not get SNMP traps generated for job failures.

Environment:
CA WAAE 11.3 SP1, CA WAAE 11.3.5, CA WAAE 11.3.6 on Linux/Unix
Cause:

The SnmpManagerHosts attribute cannot be activated by a kill -HUP signal

The following attributes can be activated with kill -HUP <event_demon_pid>

CrossPlatformScheduling 

GlobalPendMachDelay 

GlobalPendMachStatus 

GlobalPendMachInterval 

AggregatorStatistics 

EnableIPCaching 

ISDBGACTIV 

LOGROLLOVER 

NotifyMethod 

NotifySMTPHost 

UnicenterEvents 

ServiceDeskUser 

ServiceDeskCust 

ServiceDeskURL 

DCAUser 

DCAURL 

UseSMTPAuthentication 

NotifySMTPUser 

NotifySMTPFromAddress 

SetJobAttributeEnvironmentals 

 

Note: The scheduler and application server also refresh the internal components responsible for managing real resources. 

Resolution:

You have to restart the scheduler with 'unisrvcntr restart waae_sched.$AUTOSERV'