Opsview_notifyd memory leak

Symptoms Copied

• You have an Opsview version below 6.11.5

• opsview-notifydmemory usage grows significantly over time

• Your Unix Memory check the graph on your orchestrator may look like this:

  

Cause: Memory leak Copied

Known issue: OP-45287 (Fixed in 6.11.5)

There is a known memory leak issue with opsview_notifyd, one of the processes used by the Service Desk Connector module.

Two workarounds exist: * scheduled restart the opsview-servicedeskconnector component * disable the Service Desk Connector module

Solution: Scheduled restart of the opsview-servicedeskconnector component Copied

If you use the Service Desk Connector, you should use this solution.

1. Log in to the orchestrator as root.
2. Add the below entry to the root user crontab using crontab -e:

0 12 * * * /opt/opsview/watchdog/bin/opsview-monit restart opsview-servicedeskconnector

This will restart the opsview-servicedeskconnector component at 12:00 every day. Feel free to adjust the frequency and timing of this restart to meet your own system’s needs.

Solution: Disable the Service Desk Connector module Copied

If you do not use the Service Desk Connector, you may want to disable the module completely. Follow the steps to disable the Service Desk Connector module.