Nagios Support Forum

Posted: **Tue Aug 14, 2018 4:00 pm**

HELP!
for some reason postgresql has crashed on my Prod and secondary servers!
i am getting this error

psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

I tried to use the db repair script, tried a restore nothing is working! We have no active monitoring until this is resolved!
i really need some help fellas!

Posted: **Tue Aug 14, 2018 4:45 pm**

The error message suggest that the servers hard drive has filled up and the Postgress database cannot write temporary files.
To check the space of the server you can run this command

Code: Select all

df -h

If it shows that the drive is full, you can use the following commands to see what is taking up the space.

Find largest 10 directories by size command:

Code: Select all

find / -type d -print0 | xargs -0 du | sort -n | tail -10 | cut -f2 | xargs -I{} du -sh {}

Find the largest 10 files by size command:

Code: Select all

find / -type f -print0 | xargs -0 du | sort -n | tail -10 | cut -f2 | xargs -I{} du -sh {}

Try to free up some space on the server.

Files that can be deleted on Nagios system to free up space.

Generic Files
For generic Centos and Redhat installs, most log files are stored in the following folder and it's subfolders.

Code: Select all

/var/log

Most files in that folder are setup to automatically be compressed and deleted by the logrotate application. It allows automatic rotation, compression, removal of log files.
But if the server is totally out of space, the files that end in a date code can be deleted to free up space.

Some files in that folder do not get rotated and over time, could grow very large.
The MYSQL and Mariadb log files for example, do not get rotated on some systems.
If you do not need to keep then, they can be truncated.
The MYSQL log file is typically located here

Code: Select all

/var/log/mysqld.log

The Mariadb log file is typically located here

Code: Select all

/var/log/mariadb/mariadb.log

To truncate those files, you would just need to pipe null into the file.

Code: Select all

> /var/log/mysqld.log
> /var/log/mariadb/mariadb.log

If the image is a Nagios supplied VM, you can increase the drive space by following this article.
https://support.nagios.com/kb/article/n ... e-266.html

Posted: **Tue Aug 14, 2018 4:48 pm**

Code: Select all

Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_lkensherlockp-lv_root
                       58G   23G   32G  42% /
tmpfs                  12G     0   12G   0% /dev/shm
/dev/sda1             477M  162M  291M  36% /boot
/dev/mapper/vg_lkensherlockp-lv_home
                       65G   14G   48G  23% /home
isilon.healthone.org:/ifs/data/monitoring/sherlock
                      300G   41G  260G  14% /scratch

Posted: **Tue Aug 14, 2018 4:51 pm**

Hello, @benhank. What is the output of this command?

Code: Select all

service postgresql restart

Make sure that your Nagios server hasn't run out of space.

Please run through the Postgres vacuum steps in this tutorial:
https://support.nagios.com/kb/article.php?id=25

If the problem is still present after the vacuuming please send in your system profile.
To send us your system profile. Login to the Nagios XI GUI using a web browser.
Click the "Admin" > "System Profile" Menu
Click the "Download Profile" button
Save the profile.zip file and upload it to a cloud storage of your choice. You can share a link with me in a personal message.
After you upload the profile please post something in this thread to bring it up in the support queue.

Posted: **Tue Aug 14, 2018 4:56 pm**

It could be that the inodes are full, run this to see if that is the issue.

Code: Select all

df -i

If that is OK, then check this log file for any errors and post them here.

Code: Select all

/var/lib/pgsql/data/pg_log/postgresql-Tue.log

Posted: **Tue Aug 14, 2018 5:03 pm**

Code: Select all

Stopping postgresql service:                               [FAILED]
Starting postgresql service:                               [FAILED]

ive cleaned out a few large files but it still wont start

Posted: **Tue Aug 14, 2018 5:10 pm**

So far all of my log files are in the kb range

Posted: **Tue Aug 14, 2018 5:26 pm**

Code: Select all

 echo "vacuum;vacuum analyze;vacuum full;"|psql nagiosxi postgres
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/tmp/.s.PGSQL.5432"?

Posted: **Tue Aug 14, 2018 5:28 pm**

my iptables are turned off too

Posted: **Tue Aug 14, 2018 6:02 pm**

ok here is the shocking twist:
this issue has happened simultaneously on two seperatee servers at the same time.
i have backups of my postgresqldb,
how do i uninstall and then reinstall postgresql, and then restore the correct permissions so I can reimport the postgresql db?
Mysql is working fine, i think this may be (unless you guys say otherwise) the best and fastest way to get this working again.

Nagios Support Forum

URGENT Postgresql server unalaiable Production server down!

URGENT Postgresql server unalaiable Production server down!

Re: URGENT Postgresql server unalaiable Production server do

Re: URGENT Postgresql server unalaiable Production server do

Re: URGENT Postgresql server unalaiable Production server do

Re: URGENT Postgresql server unalaiable Production server do

Re: URGENT Postgresql server unalaiable Production server do

Re: URGENT Postgresql server unalaiable Production server do

Re: URGENT Postgresql server unalaiable Production server do

Re: URGENT Postgresql server unalaiable Production server do

Re: URGENT Postgresql server unalaiable Production server do