On Thu, 21 Oct 2010, Adrian Klaver wrote:
The missing piece of information seems to be the system board failure. My
guess is that caused corruption. See if you can connect by doing:
psql -h localhost -d aesi
Adrian,
[rshep...@salmo ~]$ psql -h localhost -d aesi
psql: could not connect to server: Connection refused
Is the server running on host "localhost" and accepting
TCP/IP connections on port 5432?
Let's try something different:
[rshep...@salmo ~]$ su - postgres
Password:
postg...@salmo:~$ postgres -D /var/lib/pgsql/data &
[1] 17910
postg...@salmo:~$ FATAL: bogus data in lock file "postmaster.pid": ""
So, I rm postmaster.pid and run again as user postgres and ... it works!
Now that it's working again, can I assume the problem is with the
rc.postgresql init script not running as root rather than as user postgres?
If that's the case, I need to learn how to effectively su to user postgres
during the boot process so postgresql starts as it should.
Suggestions, anyone?
And thanks to all of you for helping me climb out of the hole in which I
was stuck.
Now I need to re-read how to properly and cleanly upgrade postgres and
move from 8.3.3 to 8.4.5. (I've just posted a question on the CMS MadeSimple
forum asking if there's an issue with 9.0. If not, that's to what I'll
upgrade.)
Much grasses,
Rich
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
