Re: postgresql 8 abort with signal 10

oops... you were writing about signal 10 not signal 11. my bad - sorry

On 5/3/05, Vlad <marchenko(at)gmail(dot)com> wrote:
> Alexandre,
>
> I saw reports (and observed the problem myself) that all sort of
> different softwares suffering from signal 11 under FreeBSD (more often
> seen on 5-STABLE). So far the collection is: Apache 1.3 (myself),
> Mysql (recent descussion on freebsd-stable list) and now postgresql...
> The hardware is not the point of failure here. Try to post this into
> freebsd-stable - perhaps additional problem report will help them find
> the cause.
>
> p.s. here is the last one I see in my apache error log:
> [Wed Mar 9 17:50:45 2005] [notice] child pid 95642 exit signal
> Segmentation fault (11)
>
> On 5/3/05, Alexandre Biancalana <biancalana(at)gmail(dot)com> wrote:
> > 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 10
> > 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 = 81920
> > 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 have some configuration error that could result in this kind of problem ?
> >
> > Any ideas ? Any thoughts ?
> >
> > Best Regards,
> > Alexandre
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 4: Don't 'kill -9' the postmaster
> >
>
> --
>
> Vlad
>

--

Vlad