Symptoms
- You have an Opsview version between 6.4 and 6.6.6
opsview-freshnesschecker
memory usage grows significantly over time- Your
Unix Memory
check graph on your orchestrator may look like this:
Cause: Memory leak
Known issue: OP-47878
There is a known memory leak issue with the opsview-freshnesschecker
process used by the opsview-freshnesschecker
component.
Solution: Scheduled restart of the opsview-freshnesschecker
component
- Log in to the orchestrator as
root
. - Add the below entry to the
root
user crontab usingcrontab -e
:
0 12 * * * /opt/opsview/watchdog/bin/opsview-monit restart opsview-freshnesschecker
This will restart the opsview-freshnesschecker
component at 12:00 every day. Feel free to adjust the frequency and timing of this restart to meet your own system’s needs.
Comments
0 comments
Please sign in to leave a comment.