postgresql 8 abort with signal 10
Alexandre Biancalana
biancalana at gmail.com
Fri May 6 11:15:25 PDT 2005
Hi list,
I'm running postgresql 8.0.1 on FreeBSD 4.11-STABLE, the machine is
and AMD Sempron 2.2, 1GB Ram..
I use postgresql as database for dspam, an spam classification
program. This database have and moderated use, on averange 20
simultaneous conections executing relative big queries using "in"
clausule.
Watching postgresql logs I see the following messages ocurs a lot of
times in a day:
May 3 06:58:44 e-filter postgres[250]: [21-1] LOG: server process
(PID 59608) was terminated by signal 10
May 3 06:58:44 e-filter postgres[250]: [22-1] LOG: terminating any
other active server processes
May 3 06:58:44 e-filter postgres[59605]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:44 e-filter postgres[59605]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:44 e-filter postgres[59605]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:44 e-filter postgres[59605]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:44 e-filter postgres[59607]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:44 e-filter postgres[59607]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:44 e-filter postgres[59607]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:44 e-filter postgres[59607]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:44 e-filter postgres[59606]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:44 e-filter postgres[59606]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:44 e-filter postgres[59606]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:44 e-filter postgres[59606]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:44 e-filter postgres[59626]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:44 e-filter postgres[59626]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:44 e-filter postgres[59626]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:44 e-filter postgres[59626]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:44 e-filter postgres[59628]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:44 e-filter postgres[59629]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:44 e-filter postgres[59629]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:44 e-filter postgres[59629]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:44 e-filter postgres[59629]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:44 e-filter postgres[59628]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:44 e-filter postgres[59628]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:44 e-filter postgres[59628]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:44 e-filter postgres[59609]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:44 e-filter postgres[59609]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:44 e-filter postgres[59609]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:44 e-filter postgres[59609]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:44 e-filter postgres[59627]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:44 e-filter postgres[59627]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:44 e-filter postgres[59627]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:44 e-filter postgres[59627]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:45 e-filter postgres[69093]: [23-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:45 e-filter postgres[69093]: [23-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:45 e-filter postgres[69093]: [23-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:45 e-filter postgres[69093]: [23-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:45 e-filter postgres[59620]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:46 e-filter postgres[59620]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:46 e-filter postgres[59620]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:46 e-filter postgres[59620]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:46 e-filter postgres[59619]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:46 e-filter postgres[59619]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:46 e-filter postgres[59619]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:46 e-filter postgres[59619]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:46 e-filter postgres[59624]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:46 e-filter postgres[59624]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:46 e-filter postgres[59624]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:46 e-filter postgres[59624]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:46 e-filter postgres[59623]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:46 e-filter postgres[59623]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:46 e-filter postgres[59623]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:46 e-filter postgres[59623]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:46 e-filter postgres[59625]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:46 e-filter postgres[59625]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:46 e-filter postgres[59625]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:46 e-filter postgres[59625]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:46 e-filter postgres[59622]: [21-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:46 e-filter postgres[59622]: [21-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 06:58:46 e-filter postgres[59622]: [21-3] process exited
abnormally and possibly corrupted shared memory.
May 3 06:58:46 e-filter postgres[59622]: [21-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 06:58:46 e-filter postgres[59621]: [22-1] WARNING: terminating
connection because of crash of another server process
May 3 06:58:49 e-filter postgres[250]: [23-1] LOG: all server
processes terminated; reinitializing
May 3 06:58:51 e-filter postgres[13478]: [24-1] LOG: database system
was interrupted at 2005-05-03 06:58:16 EST
May 3 06:58:51 e-filter postgres[13478]: [25-1] LOG: checkpoint
record is at 14/99F69378
May 3 06:58:51 e-filter postgres[13478]: [26-1] LOG: redo record is
at 14/99F69378; undo record is at 0/0; shutdown FALSE
May 3 06:58:51 e-filter postgres[13478]: [27-1] LOG: next
transaction ID: 3639687; next OID: 388415
May 3 06:58:51 e-filter postgres[13478]: [28-1] LOG: database system
was not properly shut down; automatic recovery in progress
May 3 06:58:51 e-filter postgres[13478]: [29-1] LOG: redo starts at
14/99F693B4
May 3 06:58:53 e-filter postgres[13478]: [30-1] LOG: record with
zero length at 14/9AE223F0
May 3 06:58:53 e-filter postgres[13478]: [31-1] LOG: redo done at 14/9AE223C8
May 3 06:58:54 e-filter postgres[13484]: [24-1] FATAL: the database
system is starting up
May 3 06:58:54 e-filter postgres[13485]: [24-1] FATAL: the database
system is starting up
May 3 06:58:55 e-filter postgres[13488]: [24-1] FATAL: the database
system is starting up
May 3 06:58:57 e-filter postgres[13478]: [32-1] LOG: database system is ready
and some time latter its ocur again:
May 3 09:59:38 e-filter postgres[250]: [24-1] LOG: server process
(PID 34743) was terminated by signal 10
May 3 09:59:38 e-filter postgres[250]: [25-1] LOG: terminating any
other active server processes
May 3 09:59:38 e-filter postgres[35215]: [24-1] WARNING: terminating
connection because of crash of another server process
May 3 09:59:38 e-filter postgres[35215]: [24-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 09:59:38 e-filter postgres[35215]: [24-3] process exited
abnormally and possibly corrupted shared memory.
May 3 09:59:38 e-filter postgres[35215]: [24-4] HINT: In a moment
you should be able to reconnect to the database and repeat your
command.
May 3 09:59:38 e-filter postgres[34744]: [24-1] WARNING: terminating
connection because of crash of another server process
May 3 09:59:38 e-filter postgres[34744]: [24-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
May 3 09:59:38 e-filter postgres[33592]: [24-1] WARNING: terminating
connection because of crash of another server process
May 3 09:59:38 e-filter postgres[34744]: [24-3] process exited
abnormally and possibly corrupted shared memory.
This is my postgresql.conf
max_connections = 70
superuser_reserved_connections = 2
shared_buffers = 32768
work_mem = 10240
maintenance_work_mem = 51200
fsync = true
checkpoint_segments = 8
effective_cache_size = 100000
log_destination = 'syslog'
silent_mode = true
lc_messages = 'C'
lc_monetary = 'C'
lc_numeric = 'C'
lc_time = 'C'
and the shared memory configuration:
kern.ipc.shmmax: 700000000
kern.ipc.shmmin: 1
kern.ipc.shmmni: 192
kern.ipc.shmseg: 256
kern.ipc.shmall: 700000000
I already asked this in postgresql-general list and no solutions was
reach, the people from there say that is not a postgresql problem,
that should be and hardware or SO problem.....
Any ideas ? Any thoughts ?
Best Regards,
Alexandre
More information about the freebsd-questions
mailing list