Groundwork Support Forum

[tkube]

Hello from Germany,

First: please excuse my awful english.

I just installed groundwork-monitor-os-4.5-M1.31.i586.rpm and got the following problem:
A first test (commit to the deliverd nagios.cfg) shows me, that the Status Viewer does not match the Output from Nagios. Nagios shows, that localhost and the four services are in pending state, in Status Viewer they are in up state. I added a new service check_local_disk ../var:
Status Viewer immediately get this service into o.k, Nagios into pending state.
This is the output from ps -ef|grep nagios:
root 11109 11104 0 17:10 pts/2 00:00:00 supervise feeder-nagios-status
root 11110 11104 0 17:10 pts/2 00:00:00 supervise feeder-nagios-status/log
root 11111 11104 0 17:10 pts/2 00:00:00 supervise feeder-nagios-log
root 11112 11104 0 17:10 pts/2 00:00:00 supervise feeder-nagios-log/log
nagios 11113 11109 0 17:10 ? 00:00:01 /usr/local/groundwork/bin/perl --? /usr/local/groundwork/feeder/nagios2db_status.pl
nagios 11114 11110 0 17:10 ? 00:00:00 /usr/local/groundwork/bin/dumblog main/log
nagios 11116 11112 0 17:10 ? 00:00:02 /usr/local/groundwork/bin/dumblog -c main/log
nagios 14471 1 0 17:43 ? 00:00:00 /usr/local/groundwork/bin/nsca -s -c /usr/local/groundwork/etc/nsca.cfg
nagios 14497 1 0 17:43 ? 00:00:00 /usr/local/groundwork/nagios/bin/nagios -d /usr/local/groundwork/nagios/etc/nagios.cfg
root 14737 11111 11 17:46 ? 00:00:00 [nagios2db_event] <defunct>
root 14739 11642 0 17:46 pts/4 00:00:00 grep nagios

As you see, the process nagios2db_status.pl is running, but i think, that the defunct process is the problem!?

My environment:

SuSE 10.0, 64bit
MySQL 5.0
Grouindwork Monitor 4.5 Milestone 1

Regards,

Thomas Kube
Germany, Hamburg

[Peter_Loh]

Hi Thomas,
This build does not support 64 bit machines. We do not think there will be problems, but we have not fully tested on SUSE 10 yet. Sorry.
Regards,
Peter

[Peter_Loh]

Aside from the 64 bit issue, there is another bug you should be aware of. In this build there is a delay between the Nagios commit and the Status Viewer status. After you commit a change to Nagios, please run the following script: "/usr/local/groundwork/feeder/nagios2db_hostgroupcheck.pl". This script will force synchronization between Nagios and Status Viewer. This will be fixed in the next release.

The defunct process should not be there, but let me explain. There is another feeder script, "/usr/local/groundwork/feeder/nagios2db_eventlog.pl", that will read the Nagios event log and load it into the mysql database. This has been disabled by default because Status Viewer does not show an event list. Our professional product has an event console application. If you need this for any reason, you can edit the feeder configuration file, /usr/local/groundwork/nagios/etc/nagiosfeeder.cfg, and turn on the event_enable flag.

Regards,
Peter

[tkube]

Hello Peter,

i installed Groundwork on a 32bit PC ( SuSE 10 ) -> same problem. Running /usr/local/groundwork/feeder/nagios2db_hostgroupcheck.pl after commit has no effect.
Perhaps a SuSE 10 "Bug"? Has anyone installed Groundwork on SuSE 10?
_________________
Thomas Kube
Hamburg, Germany

[Peter_Loh]

Hi Thomas, Please try renaming the host, committing to Nagios, then running the nagios2db_hostgroupcheck.pl script again.
Sorry about the bug. This will be fixed in our next release, which should be available late next week.
Peter

[Guest]

Hi Peter,

i renamed the host (localhost) to nagios-host. In Configuration->Hosts it looks fine, but now i have two hosts in Status Viewer:localhost and nagios-host.

This is what i get when i run the perl program:
linux:/usr/local/groundwork # /usr/local/groundwork/feeder/nagios2db_hostgroupcheck.pl
DBD::mysql::st execute failed: Cannot delete or update a parent row: a foreign key constraint fails at /usr/local/groundwork/feeder/nagios2db_hostgroupcheck.pl line 466.
DBD::mysql::st execute failed: Cannot delete or update a parent row: a foreign key constraint fails at /usr/local/groundwork/feeder/nagios2db_hostgroupcheck.pl line 472.
DBD::mysql::st execute failed: Cannot delete or update a parent row: a foreign key constraint fails at /usr/local/groundwork/feeder/nagios2db_hostgroupcheck.pl line 478.
linux:/usr/local/groundwork #

In the database SV are two hosts (wrong):
mysql> select HostName from Host;
+-------------+
| HostName |
+-------------+
| localhost |
| nagios-host |
+-------------+

but in monarch (right) only one:
mysql> select name from hosts;
+-------------+
| name |
+-------------+
| nagios-host |
+-------------+
1 row in set (0.00 sec)

Any idea?

Thomas

[Peter_Loh]

Thomas,
I think it is best to reset the database. The original database SQL for sv is in /usr/local/groundwork/databases/load/sv.sql. Please try the following:
mysql
drop database sv;
create database sv;
exit
cat /usr/local/groundwork/databases/load/sv.sql | mysql sv

Run the hostgroupcheck again to synch. Please let me know if this works.
Peter