From: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Problems Restarting PostgreSQL Daemon |
Date: | 2008-07-22 13:21:51 |
Message-ID: | Pine.LNX.4.64.0807220614440.1929@salmo.appl-ecosys.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
My server is rebooted infrequently, usually after a kernel upgrade and
on very rare occasions when something causes it to hang. After rebooting I
always have serious issues getting postgresql running again, even though the
startup script is part of the boot sequence. Yesterday was one of those
highly unusual hangs, and I cannot restart the service. I'd like to
understand why.
When I run the Slackware script, '/etc/rc.d/rc.postgresql start' (script
attached), I'm shown a process ID and told the daemon is already running.
For example:
Starting PostgreSQL
15342
PostgreSQL daemon already running
However, there is no process ID 15342, and no postgres running. I manually
removed /tmp/.s.PGSQL.5432 and its log file. Also -- apparently in error --
the .pid file. Makes no difference.
Perhaps there's an error in the script that I'm not seeing (I didn't write
it). Regardless, if I learn why there's a problem I can fix the script and
avoid this delay and hassle restarting postgres after the daemon's been shut
down.
TIA,
Rich
--
Richard B. Shepard, Ph.D. | Integrity Credibility
Applied Ecosystem Services, Inc. | Innovation
<http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863
Attachment | Content-Type | Size |
---|---|---|
rc.postgresql | text/plain | 2.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2008-07-22 13:28:42 | Re: Is it possible to do some damage to database with SELECT query? |
Previous Message | Brandon Metcalf | 2008-07-22 13:04:35 | Re: ER diagram software |