Nagios Support Forum

To Nagios XI Tech Support Specialist:
Anybody working today. I posted a reply back. I still need some help. Our network monitor is down.

The wiki does not seem to help. Is there anything else I can try?

[root@fldmon ~]# psql nagiosxi nagiosxi
psql: FATAL: database is not accepting commands to avoid wraparound data loss in database "postgres"
HINT: Stop the postmaster and use a standalone backend to vacuum database "postgres".
You have new mail in /var/spool/mail/root
[root@fldmon ~]# VACUUM;
-bash: VACUUM: command not found
[root@fldmon ~]# psql nagiosxi nagiosxi
psql: FATAL: database is not accepting commands to avoid wraparound data loss in database "postgres"
HINT: Stop the postmaster and use a standalone backend to vacuum database "postgres".
[root@fldmon ~]# VACUUM;
-bash: VACUUM: command not found
[root@fldmon ~]# VACUUM ANALYZE;
-bash: VACUUM: command not found
[root@fldmon ~]# VACUUM FULL;
-bash: VACUUM: command not found
[root@fldmon ~]# \q
-bash: q: command not found
[root@fldmon ~]# psql postgres postgres
psql: FATAL: database is not accepting commands to avoid wraparound data loss in database "postgres"
HINT: Stop the postmaster and use a standalone backend to vacuum database "postgres".
[root@fldmon ~]# VACUUM;
-bash: VACUUM: command not found
[root@fldmon ~]# VACUUM ANALYZE;
-bash: VACUUM: command not found
[root@fldmon ~]# VACUUM FULL;
-bash: VACUUM: command not found
[root@fldmon ~]# \q
-bash: q: command not found
[root@fldmon ~]# VACUUM FULL;
-bash: VACUUM: command not found
You have new mail in /var/spool/mail/root
[root@fldmon ~]# VACUM FULL;
-bash: VACUM: command not found
[root@fldmon ~]#

uhiadmin wrote:The wiki does not seem to help. Is there anything else I can try?

[root@fldmon ~]# psql nagiosxi nagiosxi
psql: FATAL: database is not accepting commands to avoid wraparound data loss in database "postgres"
HINT: Stop the postmaster and use a standalone backend to vacuum database "postgres".

Your other commands are failing because of this. You need to follow the directions it is giving you here. Stop the postmaster and use the standalone backend.
Something like this:

GldRush98's suggestions are correct, make sure you follow the commands list and read the text in between them on the Wiki page and it should work like a charm. I followed the wiki page and am unable to reproduce your errors.

Entering Ex mode. Type "visual" to go to Normal mode.
:exit
[wanadmin@fldmon etc]$ cd ..
[wanadmin@fldmon /]$ cd ..
[wanadmin@fldmon /]$ cd ..
[wanadmin@fldmon /]$ /etc/init.d/postgresql stop
Stopping postgresql service: [FAILED]
rm: cannot remove `/var/run/postmaster.5432.pid': Permission denied
rm: cannot remove `/var/lock/subsys/postgresql': Permission denied
[wanadmin@fldmon /]$ su postgres
Password:

[wanadmin@fldmon /]$ touch /tmp/fix.sql
[wanadmin@fldmon /]$ echo "VACUUM FULL;" > /tmp/fix.sql
[wanadmin@fldmon /]$ postgres -D /var/lib/pgsql/data postgres < /tmp/fix.sql
postgres cannot access the server configuration file "/var/lib/pgsql/data/postgresql.conf": Permission denied
[wanadmin@fldmon /]$ postgres -D /var/lib/pgsql/data nagiosxi < /tmp/fix.sql
postgres cannot access the server configuration file "/var/lib/pgsql/data/postgresql.conf": Permission denied
[wanadmin@fldmon /]$ /etc/init.d/postgresql restart
Stopping postgresql service: [FAILED]
rm: cannot remove `/var/run/postmaster.5432.pid': Permission denied
rm: cannot remove `/var/lock/subsys/postgresql': Permission denied
touch: cannot touch `/var/lib/pgsql/pgstartup.log': Permission denied
[wanadmin@fldmon /]$

Last login: Mon Dec 24 18:01:51 2012
[root@fldmon ~]# /etc/init.d/postgresql stop
Stopping postgresql service: [ OK ]
[root@fldmon ~]# su postgres
bash-3.2$ touch /tmp/fix.sql
touch: cannot touch `/tmp/fix.sql': Permission denied
bash-3.2$
You have new mail in /var/spool/mail/root
bash-3.2$
bash-3.2$ postgres -D /var/lib/pgsql/data postgres < /tmp/fix.sql
WARNING: database "postgres" must be vacuumed within 1000000 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 1000000 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".

PostgreSQL stand-alone backend 8.1.23
backend> WARNING: database "postgres" must be vacuumed within 999999 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999998 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999997 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999996 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999995 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999994 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999993 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999992 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999991 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999990 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999989 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999988 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999987 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999986 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999985 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999984 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999983 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999982 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999981 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999980 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999979 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999978 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999977 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999976 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999975 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999974 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999973 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999972 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999971 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999970 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999969 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999968 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999967 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999966 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999965 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999964 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999963 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999962 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999961 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999960 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999959 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999958 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999957 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999956 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999955 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999954 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999953 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999952 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999951 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999950 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999949 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999948 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999947 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "postgres" must be vacuumed within 999946 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "postgres".
WARNING: database "nagiosxi" must be vacuumed within 999945 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "nagiosxi".
WARNING: database "nagiosxi" must be vacuumed within 999946 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "nagiosxi".
WARNING: database "nagiosxi" must be vacuumed within 999945 transactions
HINT: To avoid a database shutdown, execute a full-database VACUUM in "nagiosxi".
backend> bash-3.2$ echo "VACUUM FULL;" > /tmp/fix.sql
bash: /tmp/fix.sql: Permission denied
bash-3.2$ exit
exit
You have new mail in /var/spool/mail/root
[root@fldmon ~]# su postgres
bash-3.2$ exit
exit
[root@fldmon ~]# touch /tmp/fix.sql
[root@fldmon ~]# echo "VACUUM FULL;" > /tmp/fix.sql
[root@fldmon ~]# postgres -D /var/lib/pgsql/data postgres < /tmp/fix.sql
"root" execution of the PostgreSQL server is not permitted.
The server must be started under an unprivileged user ID to prevent
possible system security compromise. See the documentation for
more information on how to properly start the server.
[root@fldmon ~]# postgres -D /var/lib/pgsql/data nagiosxi < /tmp/fix.sql
"root" execution of the PostgreSQL server is not permitted.
The server must be started under an unprivileged user ID to prevent
possible system security compromise. See the documentation for
more information on how to properly start the server.
[root@fldmon ~]# /etc/init.d/postgresql restart
Stopping postgresql service: [FAILED]
Starting postgresql service: [ OK ]
[root@fldmon ~]# service httpd restart
Stopping httpd: [ OK ]
Starting httpd: [ OK ]
[root@fldmon ~]#

Send me a PM when you can do a remote session and I will assist you in fixing this...

Please call me to make arrangements...thx.

Hi scottwilkerson,
What is your schedule look like for the weekend or weekdays? I am off today but will be back in the office on Sunday 9-6 and Monday 2:30-11:00p. My point of contact or alternate Jesse Tomchak who can also assist me is down below:

[redacted contact info]

Have you tried running the vacuum as the postres user?

http://support.nagios.com/wiki/index.ph ... .22_in_log