I do have a problem putting things down. Yesterday I wrote a post about updating to the latest version of GroundWork Monitor Open Source and the problem I had with resolving three service checks, local_mysql_database_nopw, local_process_gw_feeders, and local_process_snmptt. Today I fixed them and here’s what I did:
- To resolve the local_mysql_database_nopw alert I went to Nagios resource macro, USER6, and made its value null. This service check uses the value of USER6 as the mysql password. The mysql password is not set in the vmware appliance version so the correct answer is null.
- To resolve the local_process_gw_feeders alert I
fixed the nagios2collage_eventlog.pl so that it would find the included files. Then I ran the perl file in the background. My final fix was to modify the run script in feeder-nagios-status folder to start up the eventlog.pl when the service is started. I think this is right placechanged the service check parameters to allow 1 to 3 processes to be running. The eventlog process is a Pro feature.
- To resolve the local_process_snmptt alert I installed net-snmp and snmptt. Then I modified the parameters for this service check for this host so that it was happy with 2 to 3 services running.
The GroundWork server has been running for a couple of hours without alerts. Yea!