Re: postgreslog - panic message
От | Richard Huxton |
---|---|
Тема | Re: postgreslog - panic message |
Дата | |
Msg-id | 44758147.2010404@archonet.com обсуждение исходный текст |
Ответ на | postgreslog - panic message ("surabhi.ahuja" <surabhi.ahuja@iiitb.ac.in>) |
Ответы |
Re: postgreslog - panic message
|
Список | pgsql-general |
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 6 > > i 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
В списке pgsql-general по дате отправления: