Assume the following situation:
You changed something on a service and the performance data format has changed as well. PNP4Nagios graphs that belong to the changed service will not be changed automatically. You have to remove the old XML file that belongs to the changed service and then re-start your OMD site completely like this:
OMD[mysite]:~$ rm var/pnp4nagios/perfdata/webserver35/Apache_127.0.0.1_80_Status.xml
OMD[mysite]:~$ omd restart
In a few minutes the XML file should be re-generated and graphs belonging to new performance data counters should appear. If NOT, I’m afraid that you have to remove all RRD-files that belong to the service (you can recognize it on the file name) and to hope that they will be re-created properly. In this case all the server statistic will be lost (you have been warned!).
OMD provides some very useful commands to manage sites. Execute “omd help” as root to see all possible commands.
I’ve updated the check and built a new package. The package can be downloaded from Check_MK exchange site here. The new version has the number 1.4.
There are two changes regarding the agent’s side: the plugin call logic and the caching of results.
Today I’ve uploaded a new version of checks for Fortigate devices. The new version is 2.2 and can be downloaded from the exchange site of the Check_MK project. These are new features:
- added a check to monitor the synchronization status of Fortigate high availability clusters (HA cluster)
- added a check to monitor the number of current VPN SSL connections
- added perf-o-meters for some checks
- minor changes
The checks have worked under CMK 1.2.4p2 and 1.2.4.p3, but might work with other versions of Check_MK. The Fortigate devices the checks work successfully with are: Fortigate 60C/60D/90D/300C