Postgres 7.0.3 Dying - Mailing list pgsql-admin

From Andre Schubert
Subject Postgres 7.0.3 Dying
Date
Msg-id 3B0A1116.B72E31FF@geyer.kabeljournal.de
Whole thread Raw
Responses Re: Postgres 7.0.3 Dying
List pgsql-admin
Hi all,

I have a problem with my Postgres Server.
The last time the servers terminates itself and the following entries in
the log files are written, but i don't no what they say.
I'am running Postgres 7.0.3
On RedHat Immunix 6.2

*********************************************************************
Log-Entries( Debug-Level 2 )

/usr/bin/postmaster: BackendStartup: pid 20840 user nw_manager db
db_netzwerkmanagement socket 5
010517.09:39:35.133 [20840] read_pg_options: verbose=2,query=2,syslog=0
FindExec: found "/usr/bin/postgres" using argv[0]
010517.09:39:35.134 [20840] started: host=213.68.241.40 user=nw_manager
database=db_netzwerkmanagement
010517.09:39:35.134 [20840] InitPostgres
010517.09:39:35.142 [20840] reset_client_encoding()..
/usr/bin/postmaster: reaping dead processes...
/usr/bin/postmaster: CleanupProc: pid 20839 exited with status 0
010517.09:39:35.142 [20840] reset_client_encoding() done.
010517.09:39:35.143 [20840] StartTransactionCommand
010517.09:39:35.143 [20840] query: select getdatabaseencoding()
out of dynamic memory in yy_create_buffer()
/usr/bin/postmaster: reaping dead processes...
/usr/bin/postmaster: CleanupProc: pid 20840 exited with status 512
Server process (pid 20840) exited with status 512 at Thu May 17 09:39:35
2001
Terminating any active server processes...
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 20606
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 20497
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 15454
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 15453
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 15057
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 5976
010517.09:39:35.179 [15454] NOTICE:  Message from PostgreSQL backend:
The Postmaster has informed me that some other backend died
abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am going to terminate
your database system connection and exit.
Please reconnect to the database system and repeat your query.
010517.09:39:35.186 [15453] NOTICE:  Message from PostgreSQL backend:
The Postmaster has informed me that some other backend died
abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am going to terminate
your database system connection and exit.
Please reconnect to the database system and repeat your query.
010517.09:39:35.194 [15057] NOTICE:  Message from PostgreSQL backend:
The Postmaster has informed me that some other backend died
abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am going to terminate
your database system connection and exit.
Please reconnect to the database system and repeat your query.
/usr/bin/postmaster: reaping dead processes...
/usr/bin/postmaster: CleanupProc: pid 15454 exited with status 256
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 20606
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 20497
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 15453
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 15057
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 5976
/usr/bin/postmaster: CleanupProc: pid 15453 exited with status 256
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 20606
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 20497
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 15057
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 5976
/usr/bin/postmaster: CleanupProc: pid 15057 exited with status 256
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 20606
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 20497
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 5976
010517.09:39:35.204 [20497] NOTICE:  Message from PostgreSQL backend:
The Postmaster has informed me that some other backend died
abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am going to terminate
your database system connection and exit.
Please reconnect to the database system and repeat your query.
010517.09:39:35.215 [20606] NOTICE:  Message from PostgreSQL backend:
The Postmaster has informed me that some other backend died
abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am going to terminate
your database system connection and exit.
Please reconnect to the database system and repeat your query.
010517.09:39:35.226  [5976] NOTICE:  Message from PostgreSQL backend:
The Postmaster has informed me that some other backend died
abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am going to terminate
your database system connection and exit.
Please reconnect to the database system and repeat your query.
/usr/bin/postmaster: reaping dead processes...
/usr/bin/postmaster: CleanupProc: pid 20606 exited with status 256
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 20497
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 5976
/usr/bin/postmaster: CleanupProc: pid 20497 exited with status 256
/usr/bin/postmaster: CleanupProc: sending SIGUSR1 to process 5976
/usr/bin/postmaster: CleanupProc: pid 5976 exited with status 256
Server processes were terminated at Thu May 17 09:39:35 2001
Reinitializing shared memory and semaphores
010517.09:39:35.229  [5434] shmem_exit(0)
010517.09:39:35.232  [5434] IpcMemoryCreate: shmget failed (Das
Argument ist ungültig) key=5432101, size=17627136, permission=600
This type of error is usually caused by an improper
shared memory or System V IPC semaphore configuration.
For more information, see the FAQ and platform-specific
FAQ's in the source directory pgsql/doc or on our
web site at http://www.postgresql.org.
010517.09:39:35.232  [5434] FATAL 1:  ShmemCreate: cannot create region
010517.09:39:35.232  [5434] proc_exit(0)
010517.09:39:35.232  [5434] shmem_exit(0)
010517.09:39:35.298  [5434] exit(0)
postmaster successfully started up.
FindExec: found "/usr/bin/postgres" using argv[0]
010517.09:53:36.224 [20963] DEBUG:  Data Base System is starting up at
Thu
May 17 09:53:36 2001
010517.09:53:36.239 [20963] DEBUG:  Data Base System was interrupted
being
in production at Fri May 11 11:07:50 2001
010517.09:53:36.250 [20963] DEBUG:  Data Base System is in production
state



pgsql-admin by date:

Previous
From: Dronamraju Rajesh
Date:
Subject: Re: cannot connect using terminal nor pgaccess
Next
From: Tomasz Misterka
Date:
Subject: user delete problem