Event short description: no_event_detected
This event is generated everytime when no machine-ok notification is received from the source machine.
This indicates there is something that is failing and if it was notified in the past it remains in the same state).
It also may indicate there is some problem with some checker that got stuck, causing the machine-ok notification to be delayed.
When all checkers reports ok-status, a machine-ok notification is generated. The period where this notification is received depends on the number of checkers, the checking period and the number of parallel checkers to run on each run, but in general, it is received every 5 minutes.
In the case this machine-ok notification isn’t received at the server, a no_event_detected event is generated directly from the central server, to warn the panel operator that something is happening in the source machine.
To resolve this issue, please review all checkers at your server. Click on the panel general view, then click on Actions button at the top right and then click on “show machine checkers”.
According to the error, you have the following solutions:
- You should see which checker may be in fault state. If so, please review the error and solve it to get the checker back to ok state.
- If all checkers show an ok status, check if the last status of every checker is up to date and recent. To do so, click on the header’s column to arrange by date. You should see which checker is lagging behind. If this is the case, restart the agent. To do so, click on the Actions button and then click on “Restart agent”.
- You could also consider disabling the checker temporally or permanently according to your needs or particular setup.
Increasing no-event-limit at the central server
Another solution that is available, though not recommended because it afects all agents, is to increase the period considered after which a no_event_detect event is generated when no machine-ok notification is received.
To do so, follow the following steps:
- Connect to the central server where you are running Core-Admin Server (through ssh or a console).
- Now edit the file /etc/core-admin/server/server.conf
- Go down through the file and edit the xml node <checkers no-event-limit-period=”3600″> to have the requested value. By default it is configured 3600 seconds (1 hour) which is reasonable value before which we should have received a machine-ok notification.
- After updating the value, restart turbulence. In debian systems this is done like:
>> /etc/init.d/turbulence restart