Parameters Setting Lost After Agent Restart
When using the PATROL Agent versions prior to 3.6.00, parameter poll times that are set using the PATROL KM for Event Management are not retained upon agent restart.
Explanation | Solution |
|---|---|
The allowsendparamonly variable exists in %PATROL_HOME%\common\patrol.d\patrol.conf file and is set to true. | Remove the allowsendparamonly variable. For instructions, see Removing the allowsendparamonly Variable. If this variable exists and is set to True, then state change events for applications and instances are not generated. This reduces network traffic, but it also prevents the PATROL KM for Event Management from detecting when parameters become active after an agent restart. Thus, the PATROL KM or Event Management threshold and poll time settings are not applied. |
etc/patrol.d/patrol.conf does not exist. | If patrol.conf file doesn't exist then all the agent variables get set to TRUE. To resolve this problem, obtain a copy of the file patrol.conf and remove the allowsendparamonly variable, if it exists, as described in Removing the allowsendparamonly Variable. To obtain the patrol.conf file, copy it from another computer or contact BMC Software Support. |
Removing the allowsendparamonly Variable
- Move patrol.conf from %PATROL_HOME%\common\patrol.d to a secure location.
- Using the PACFG (PATROL Agent Configuration) utility, specify that secured location.
- Using Notepad (with word wrap disabled) or Wordpad, open patrol.conf.
Underneath the [AGENT] stanza, remove the following line:
{{allowsendparamonly=true}}- Save and close the file.
- Reinitialize the agent.