| From: | Gary Stainburn <gary(dot)stainburn(at)ringways(dot)co(dot)uk> |
|---|---|
| To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Postgresql not accessible, recovering |
| Date: | 2013-11-19 11:08:18 |
| Message-ID: | 201311191108.18620.gary.stainburn@ringways.co.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi folks.
My Bacula system has stopped working because it cannot access the Postgresql
server.
I have tried restarting the server using
systemctl restart postgresql
and
pg_ctl start (from postgres user)
I get nothing appearing on-screen using either method but the server is still
unaccessible.
Doing a 'ps ax' found the following output. Can anyone help on what I need to
do next as Google only returns posts relating to replication which I don't
use.
-bash-4.2$ ps ax|grep post
29370 pts/0 S 0:00 su - postgres
29446 pts/0 S 0:00 /usr/bin/postgres
29447 ? Ss 0:00 postgres: logger process
29448 ? Ds 0:07 postgres: startup process recovering
000000010000000C000000FD
29653 ? Ss 0:00
gvim /etc/systemd/system/multi-user.target.wants/postgresql.service
29746 pts/0 S+ 0:00 grep --color=auto post
-bash-4.2$
I'm using:
[root(at)lou clients]# uname -a
Linux lou.ringways.co.uk 3.6.10-2.fc17.x86_64 #1 SMP Tue Dec 11 18:07:34 UTC
2012 x86_64 x86_64 x86_64 GNU/Linux
[root(at)lou clients]# rpm -qa|grep postgr
postgresql-9.1.7-1.fc17.x86_64
postgresql-server-9.1.7-1.fc17.x86_64
postgresql-libs-9.1.7-1.fc17.x86_64
Gary
--
Gary Stainburn
Group I.T. Manager
Ringways Garages
http://www.ringways.co.uk
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karl Hafner | 2013-11-19 11:14:44 | Re: MultiXactId Error in Autovacuum |
| Previous Message | Albe Laurenz | 2013-11-19 10:00:18 | Re: MultiXactId Error in Autovacuum |