Have to Restart Nagios VM Periodically

[easy2kent]

The log is pretty much identical to the last time it was run.

Code: Select all

The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale en_US.UTF-8.
The default database encoding has accordingly been set to UTF8.

fixing permissions on existing directory /var/lib/pgsql/data ... ok
creating directory /var/lib/pgsql/data/global ... ok
creating directory /var/lib/pgsql/data/pg_xlog ... ok
creating directory /var/lib/pgsql/data/pg_xlog/archive_status ... ok
creating directory /var/lib/pgsql/data/pg_clog ... ok
creating directory /var/lib/pgsql/data/pg_subtrans ... ok
creating directory /var/lib/pgsql/data/pg_twophase ... ok
creating directory /var/lib/pgsql/data/pg_multixact/members ... ok
creating directory /var/lib/pgsql/data/pg_multixact/offsets ... ok
creating directory /var/lib/pgsql/data/base ... ok
creating directory /var/lib/pgsql/data/base/1 ... ok
creating directory /var/lib/pgsql/data/pg_tblspc ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 1000
creating configuration files ... ok
creating template1 database in /var/lib/pgsql/data/base/1 ... ok
initializing pg_authid ... ok
enabling unlimited row size for system tables ... ok
initializing dependencies ... ok
creating system views ... ok
loading pg_description ... ok
creating conversions ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok

Success. You can now start the database server using:

    /usr/bin/postmaster -D /var/lib/pgsql/data
or
    /usr/bin/pg_ctl -D /var/lib/pgsql/data -l logfile start

FATAL:  lock file "postmaster.pid" already exists
HINT:  Is another postmaster (PID 5478) running in data directory "/var/lib/pgsql/data"?
LOG:  logger shutting down
LOG:  logger shutting down
LOG:  logger shutting down
LOG:  logger shutting down
LOG:  logger shutting down

It runs perfectly fine for about a week. It is almost clock work now that it needs to be restarted every week. I have started keeping track of when I have restarted Nagios. I have had to reset the virtual machine on: Mar. 28, Apr. 4, Apr. 10, Apr. 17, and Apr. 24. Nagios will be running fine until something happens and causes it to crash but do not know what it is. Is there a way to start fresh without losing performance data? I thought maybe an update would solve this problem but there have been a couple of updates to Nagios and it is still happening.

It almost points to postgresql locking up every week causing the virtual machine to pretty much crash, but I am no Nagios expert or anything just an observation because something has to be happening to cause this. Postgresql does not start when the virtual machine is reset either, it has to be manually started after the virtual machine is up.

Thanks for all your help,
Kent

[scottwilkerson]

It almost points to postgresql locking up every week causing the virtual machine to pretty much crash, but I am no Nagios expert or anything just an observation because something has to be happening to cause this. Postgresql does not start when the virtual machine is reset either, it has to be manually started after the virtual machine is up.

I would tend to agree, something is definitely funky with postgresql on this machine.

Is there a way to start fresh without losing performance data?

Yes, if you follow our backup procedure and restore on a new machine you should preserve performance data unless you switch architecture (32 to 64 bit)
http://library.nagios.com/library/produ ... -nagios-xi

[easy2kent]

Migrating the virtual machine to a new one with updated version and restoring from a backup seemed to do the trick as it has been a couple of weeks and no issues. The process was simple and painless. Thanks for all of your help.

Kent

[abrist]

No problem. Cheers.

[lmiltchev]

I'm glad your issue has been resolved!