GroupWise SNMP stops working when snmpd is restarted

  • 7006087
  • 24-May-2010
  • 27-Apr-2012


Novell GroupWise 8
Novell Open Enterprise Server 2 (OES 2) Linux
SuSE Linux Enterprise Server 10


Every day the SNMP that GroupWise uses stops responding to queries.
In order to get SNMP to respond again, a restart of the GroupWise Agents is required.



Disable the SNMP logging, or at least turn it down so it will restart less often.  This can be done by editing the net-snmp file located in the /etc/sysconfig/ directory.  The logging level is set to 'd' or 7 (Debug) by default.  This can be turned down as far as desired if a frequent restart of the agents is not possible.  This can be set to 0 or completely off in order to prevent interference with the monitoring of the GroupWise Agents or to avoid GroupWise Agent restarts.  However, it is not recommended ever turning any form of logging completely of, so setting it to a number from 1-6 may be enough to provide sufficient results and prevent the SNMP daemon from restarting too often.

See Additional Information section for background information on what's going on.


Reported to Engineering

Additional Information

When the net-snmp daemon is restarted to rotate it's log file,GroupWise will stop sending SNMP traps or responding to SNMP queries until the GW service(s) are restarted.

By default, on SLES, the snmpd logs will be rotated when they reach +1MB.  By turning the logging level down or off, this prevents the SNMP daemon from restarting or restarting less often, and will require less restarts of the GroupWise Agents until this defect is resolved.