Re: Bug#101177: postgresql: Postgres died, won't restart -- another
От | Oliver Elphick |
---|---|
Тема | Re: Bug#101177: postgresql: Postgres died, won't restart -- another |
Дата | |
Msg-id | 200111051618.fA5GIwYT005814@linda.lfix.co.uk обсуждение исходный текст |
Ответы |
Re: Bug#101177: postgresql: Postgres died, won't restart -- another
(Tom Lane <tgl@sss.pgh.pa.us>)
|
Список | pgsql-hackers |
Can anyone tell me what exit code 11 means on a backend failure? I can't find any definition of backend exit codes. Is there any documentation of these? ------- Forwarded Message Subject: Bug#101177: postgresql: Postgres died, won't restart -- another case From: Ken Harris <kbh7@cornell.edu> Date: Fri, 02 Nov 2001 15:40:58 -0500 (20:40 GMT) To: Debian Bug Tracking System <101177@bugs.debian.org> Package: postgresql Version: 7.1.3-4 I'm seeing something similar here. Postgres died while a program was dumping data into it, and I can't restart it. I'm getting /usr/lib/postgresql/bin/postmaster: Startup proc 10178 exited with status 11 - abort in /var/log/postgres.log (11 = segfault?). It was asked if 7.1.3-4 cures this; I'm already using 7.1.3-4. It was said Postgres creates a 16-20MB file on startup; I have 1.0GB free. (Is this startup file size dependent on the database size?) -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux picea 2.4.12 #2 Thu Nov 1 13:01:34 EST 2001 i686 Locale: LANG=C, LC_CTYPE= ------- End of Forwarded Message ------- Forwarded Message Date: Mon, 05 Nov 2001 10:44:46 -0500 From: Ken Harris <kbh7@cornell.edu> To: Oliver Elphick <olly@lfix.co.uk> Subject: Re: Bug#101177: postgresql: Postgres died, won't restart -- another ca se >No. Your problem does not sound like lack of disk space (I recently had >that and that gives an exit status of 512). > Ok, good. (Or, darn, I don't get to ask my boss for a bigger disk. :-) >Is there anything in the logs? If not, set debug_level = 2 in >/etc/postgresql/postgresql.conf and try again. > The line I quoted above ("exited with status 11") was the only thing that showed up in the log. With debug_level=2, I see: invoking IpcMemoryCreate(size=2211840) FindExec: found "/usr/lib/postgresql/bin/postmaster" using argv[0] /usr/lib/postgresql/bin/postmaster: reaping dead processes... /usr/lib/postgresql/bin/postmaster: Startup proc 14219 exited with status 11 - abort (Doesn't look terribly helpful, I'm afraid.) This database isn't mission-critical, by any means, and I'm working on a program (JDBC) to create it from my raw data, so it gets re-created from scratch all the time. I'm curious to know why Postgres died, though, and I'll be glad to run any sort of diagnostics you can think of. Thanks, - - Ken ------- End of Forwarded Message -- Oliver Elphick Oliver.Elphick@lfix.co.uk Isle of Wight http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C "No man can serve two masters; for either he will hate the one, and love the other; or else he will hold tothe one, and despise the other. Ye cannot serve God and mammon." Matthew 6:24
В списке pgsql-hackers по дате отправления: