postgreslog - panic message
hi,
i am getting the following error messages:
<2006-05-24 15:28:08 CDT%>LOG: could not bind IPv4 socket: Address already in use
<2006-05-24 15:28:08 CDT%>HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
<2006-05-24 15:28:08 CDT%>WARNING: could not create listen socket for "localhost"
<2006-05-24 15:28:08 CDT%>LOG: database system was shut down at 2006-05-24 15:28:08 CDT
<2006-05-24 16:19:39 CDT%>PANIC: could not locate a valid checkpoint record
<2006-05-24 16:19:39 CDT%>LOG: startup process (PID 6548) was terminated by signal 6
<2006-05-24 16:19:39 CDT%>LOG: aborting startup due to startup process failure
<2006-05-24 16:21:28 CDT%>LOG: database system was shut down at 2006-05-24 16:01:00 CDT
<2006-05-24 16:21:28 CDT%>LOG: record with zero length at 0/AC92BC
<2006-05-24 16:21:28 CDT%>LOG: invalid primary checkpoint record
<2006-05-24 16:21:28 CDT%>LOG: record with zero length at 0/AC9280
<2006-05-24 16:21:28 CDT%>LOG: invalid secondary checkpoint record
<2006-05-24 16:21:28 CDT%>PANIC: could not locate a valid checkpoint record
<2006-05-24 16:21:28 CDT%>LOG: startup process (PID 8428) was terminated by signal 6
i am using postgres 8.0.0
please tell as to what might be going wrong.
thanks,
regards
Surabhi
surabhi.ahuja wrote:
hi,
i am getting the following error messages:<2006-05-24 15:28:08 CDT%>LOG: could not bind IPv4 socket: Address already in use
<2006-05-24 15:28:08 CDT%>HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
<2006-05-24 15:28:08 CDT%>WARNING: could not create listen socket for "localhost"
<2006-05-24 15:28:08 CDT%>LOG: database system was shut down at 2006-05-24 15:28:08 CDT
This is what it says. You've either got:
1. another version of PostgreSQL running on port 5432
2. Something else on port 5432
3. The operating-system hasn't recycled the port after a shutdown (it
can take a few seconds sometimes).
I assume it started up after this?
<2006-05-24 16:19:39 CDT%>PANIC: could not locate a valid checkpoint record
<2006-05-24 16:19:39 CDT%>LOG: startup process (PID 6548) was terminated by signal 6
<2006-05-24 16:19:39 CDT%>LOG: aborting startup due to startup process failure
<2006-05-24 16:21:28 CDT%>LOG: database system was shut down at 2006-05-24 16:01:00 CDT
<2006-05-24 16:21:28 CDT%>LOG: record with zero length at 0/AC92BC
<2006-05-24 16:21:28 CDT%>LOG: invalid primary checkpoint record
<2006-05-24 16:21:28 CDT%>LOG: record with zero length at 0/AC9280
<2006-05-24 16:21:28 CDT%>LOG: invalid secondary checkpoint record
<2006-05-24 16:21:28 CDT%>PANIC: could not locate a valid checkpoint record
<2006-05-24 16:21:28 CDT%>LOG: startup process (PID 8428) was terminated by signal 6i am using postgres 8.0.0
You should be running the latest release of 8.0.8 - there are 8 sets of
bug-fixes between your version and the latest.
please tell as to what might be going wrong.
Either the WAL has been corrupted (have you had a crash? Are your disks
reliable?), PG is reading the wrong file (unlikely) or you've hit a bug
in 8.0.0. Read the release notes for 8.0 and see if any of the changes
could affect you.
http://www.postgresql.org/docs/8.0/static/release.html
--
Richard Huxton
Archonet Ltd
On May 25 11:04, Richard Huxton wrote:
surabhi.ahuja wrote:
hi,
i am getting the following error messages:<2006-05-24 15:28:08 CDT%>LOG: could not bind IPv4 socket: Address
already in use
<2006-05-24 15:28:08 CDT%>HINT: Is another postmaster already running on
port 5432? If not, wait a few seconds and retry.
<2006-05-24 15:28:08 CDT%>WARNING: could not create listen socket for
"localhost"
<2006-05-24 15:28:08 CDT%>LOG: database system was shut down at
2006-05-24 15:28:08 CDTThis is what it says. You've either got:
1. another version of PostgreSQL running on port 5432
2. Something else on port 5432
3. The operating-system hasn't recycled the port after a shutdown (it
can take a few seconds sometimes).
Just for curiosity, shouldn't SO_REUSEADDR (in
backend/libpq/pqcomm.c:342) handle the 3rd possibility in the above
list? Or isn't this behaviour guaranteed by SO_REUSEADDR on every
platform?
Regards.
"surabhi.ahuja" <surabhi.ahuja@iiitb.ac.in> writes:
<2006-05-24 16:21:28 CDT%>LOG: database system was shut down at =
2006-05-24 16:01:00 CDT
<2006-05-24 16:21:28 CDT%>LOG: record with zero length at 0/AC92BC
<2006-05-24 16:21:28 CDT%>LOG: invalid primary checkpoint record
<2006-05-24 16:21:28 CDT%>LOG: record with zero length at 0/AC9280
<2006-05-24 16:21:28 CDT%>LOG: invalid secondary checkpoint record
<2006-05-24 16:21:28 CDT%>PANIC: could not locate a valid checkpoint =
record
<2006-05-24 16:21:28 CDT%>LOG: startup process (PID 8428) was =
terminated by signal 6
Hm, those are remarkably small values of the checkpoint record pointers;
roughly what you'd see immediately after initdb. What's the history of
this installation? If it's not freshly initdb'd, the only thing I can
think is that somebody has restored an old version of pg_control into
the directory tree. Which would be a pretty bad move, but maybe you can
recover with pg_resetxlog.
regards, tom lane
where can i download the rpms for the PostgreSQL version 8.0.8
till now we have been using 8.0.0.
thanks,
regards
Surabhi
surabhi.ahuja wrote:
where can i download the rpms for the PostgreSQL version 8.0.8
till now we have been using 8.0.0.thanks,
regards
Surabhi
you can from here :
http://www.postgresql.org/ftp/binary/v8.0.8/linux/
leonel