mysterious segfault

[kzmk]

Binary package hint: postgresql-8.3

root@denes:/var/log# lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
root@denes:/var/log# cat syslog | grep postgres
Mar 4 10:15:32 denes kernel: [475978.179783] postgres[31631]: segfault at 97b4adf8 ip b7ab20f8 sp bff98620 error 4 in libcrypto.so.0.9.8[b7a06000+133000]
root@denes:/var/log# dpkg -l | grep postgres
ii postgresql-8.3 8.3.7-0ubuntu8.10.1 object-relational SQL database, version 8.3
ii postgresql-8.3-plsh 1.3-1 PL/sh procedural language for PostgreSQL 8.3
ii postgresql-8.3-slony1 1.2.14-1ubuntu1 replication system for PostgreSQL
ii postgresql-client-8.3 8.3.7-0ubuntu8.10.1 front-end programs for PostgreSQL 8.3
ii postgresql-client-common 90 manager for multiple PostgreSQL client versi
ii postgresql-common 90 PostgreSQL database-cluster manager
ii pure-ftpd-postgresql 1.0.21-11.2ubuntu1 Pure-FTPd FTP server with PostgreSQL user au

postgreslog:
2010-03-04 10:15:32 CET LOG: server process (PID 31631) was terminated by signal 11: Segmentation fault
2010-03-04 10:15:32 CET LOG: terminating any other active server processes
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:32 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:32 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:32 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:32 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET WARNING: terminating connection because of crash of another server process
2010-03-04 10:15:32 CET DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2010-03-04 10:15:32 CET HINT: In a moment you should be able to reconnect to the database and repeat your command.
2010-03-04 10:15:32 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:32 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:33 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:33 CET LOG: all server processes terminated; reinitializing
2010-03-04 10:15:33 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:33 CET LOG: database system was interrupted; last known up at 2010-03-04 10:13:24 CET
2010-03-04 10:15:33 CET LOG: database system was not properly shut down; automatic recovery in progress
2010-03-04 10:15:33 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:33 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:33 CET LOG: redo starts at 2/BD7D2224
2010-03-04 10:15:33 CET LOG: record with zero length at 2/BD8278A4
2010-03-04 10:15:33 CET LOG: redo done at 2/BD827834
2010-03-04 10:15:33 CET LOG: last completed transaction was at log time 2010-03-04 10:15:32.400461+01
2010-03-04 10:15:33 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:33 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:33 CET LOG: autovacuum launcher started
2010-03-04 10:15:33 CET FATAL: the database system is in recovery mode
2010-03-04 10:15:33 CET LOG: database system is ready to accept connections
2010-03-04 10:15:43 CET NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=5720
2010-03-04 10:15:43 CET NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=7483
2010-03-04 10:15:43 CET NOTICE: Slony-I: cleanup stale sl_nodelock entry for pid=7488