Postgresql 7.1 dying on Debian Woody
Postgresql 7.1 dying on Debian Woody
От:
Johann Spies <jspies@maties.sun.ac.za>
Дата:
I happened yesterday while I was running a script copying about 58000
entries to a table and I can not get it going again. From
/var/log/postgres.log:
--------------------------------------------------
pq_recvbuf: unexpected EOF on client connection
Smart Shutdown request at Thu Jun 28 08:34:56 2001
Server process (pid 12898) exited with status 512 at Thu Jun 28
17:14:09 2001
Terminating any active server processes...
Server processes were terminated at Thu Jun 28 17:14:09 2001
Reinitializing shared memory and semaphores
The Data Base System is starting up
The Data Base System is starting up
The Data Base System is starting up
/usr/lib/postgresql/bin/postmaster: Startup proc 12953 exited with
status 512 - abort
/usr/lib/postgresql/bin/postmaster: Startup proc 13036 exited with
status 512 - abort
/usr/lib/postgresql/bin/postmaster: Startup proc 13098 exited with
status 512 - abort
/usr/lib/postgresql/bin/postmaster: Startup proc 13138 exited with
status 512 - abort
/usr/lib/postgresql/bin/postmaster: Startup proc 13671 exited with
status 512 - abort
/usr/lib/postgresql/bin/postmaster: Startup proc 13859 exited with
status 512 - abort
/usr/lib/postgresql/bin/postmaster: Startup proc 13892 exited with
status 512 - abort
/usr/lib/postgresql/bin/postmaster: Startup proc 14034 exited with
status 512 - abort
-------------------------------------------------
Can somebody tell me how to correct it?
Johann
--
Johann Spies
Informasietegnologie
Universiteit van Stellenbosch
"One thing have I desired of the LORD, that will I seek
after; that I may dwell in the house of the LORD all
the days of my life, to behold the beauty of the LORD,
and to inquire in his temple."
Psalms 27:4
Re: Postgresql 7.1 dying on Debian Woody
От:
Tom Lane <tgl@sss.pgh.pa.us>
Дата:
Johann Spies writes: > I happened yesterday while I was running a script copying about 58000 > entries to a table and I can not get it going again. From > /var/log/postgres.log: > The Data Base System is starting up > /usr/lib/postgresql/bin/postmaster: Startup proc 12953 exited with > status 512 - abort > /usr/lib/postgresql/bin/postmaster: Startup proc 13036 exited with > status 512 - abort Very strange. If the startup process detects a problem, it should write some kind of error message to the log before aborting. Are you getting a core dump file in the $PGDATA directory? One thing I'd suggest immediately is to update to 7.1.2 and see if the behavior changes. regards, tom lane