first crash
От | Thomas T. Thai |
---|---|
Тема | first crash |
Дата | |
Msg-id | Pine.NEB.4.44.0303061251380.4205-100000@ns01.minnesota.com обсуждение исходный текст |
Ответы |
Re: first crash
|
Список | pgsql-general |
I had my first production crash today. PostgreSQL v7.3 NetBSD/Alpha 1.6 Postmaster was started a few months ago. Things went fine for months. Then I started noticing psql.core dumps when exiting from psql. On a fresh startup of postmaster, psql doesn't core dump on exit. Today postmaster crashed without a core dump. When I tried to start postmaster up again it gave me some strange error about using ipcrm to remove stale shared memory block. The main postmaster disappeared from 'ps' but a 4 others remain... Once I removed those stale connections, and started up postmaster again, things are back to normal and psql didn't core dump upon exit (\q). Is there anything I can do to help track down this issue? --- $ ps axj | grep postmaster pgsql 22589 1 16910 a36100 0 S ?? 0:09.87 postmaster: pgsql testdb [local] idle pgsql 22593 1 16910 a36100 0 S ?? 0:09.70 postmaster: pgsql testdb [local] idle pgsql 22596 1 16910 a36100 0 S ?? 0:09.77 postmaster: pgsql testdb [local] idle pgsql 22604 1 16910 a36100 0 S ?? 0:10.43 postmaster: pgsql testdb [local] idle pgsql 22607 1 16910 a36100 0 S ?? 0:10.14 postmaster: pgsql testdb [local] idle pgsql 3266 3028 3265 916d80 2 R+ p3 0:00.00 grep postmaster (sh) $ pg_ctl start -D /var/pgsql/data-7.3 pg_ctl: Another postmaster may be running. Trying to start postmaster anyway. Found a pre-existing shared memory block (key 5432001, id 327680) still in use. If you're sure there are no old backends still running, remove the shared memory block with ipcrm(1), or just delete "/var/pgsql/data-7.3/postmaster.pid". pg_ctl: cannot start postmaster Examine the log output. $ kill -HUP 22589 22593 22596 22604 22607 $ ps axj | grep postmaster ---
В списке pgsql-general по дате отправления: