Re: postmaster dies (was Re: Very disappointing performance)
От | secret |
---|---|
Тема | Re: postmaster dies (was Re: Very disappointing performance) |
Дата | |
Msg-id | 36ED56CA.71BC3F1D@kearneydev.com обсуждение исходный текст |
Ответ на | Re: postmaster dies (was Re: Very disappointing performance) (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
Tom Lane wrote: > secret <secret@kearneydev.com> writes: > >>>> PostgreSQL is also crashing 1-2 times a day on me, although I have a > >>>> handy perl script to keep it alive now <grin>... > > > basically the server randomly dies with a: > > ERROR: postmaster: StreamConnection: accept: Invalid argument > > pmdie 3 > > (then signals all children to drop dead) > > Hmm. That shouldn't happen, especially not randomly; if the accept > works the first time then it should work forever after, since the > arguments being passed in never change. > > The error is coming from StreamConnection() in > pgsql/src/backend/libpq/pqcomm.c. Could you maybe add some debugging > code to the routine to see what the server_fd and port arguments are > when accept() fails? I think just changing the first elog() to > > elog(ERROR, > "postmaster: StreamConnection: accept: %m\nserver_fd = %d, port = %p", > server_fd, port); > > would do for starters. This would let us eliminate the possibility that > the routine is getting passed bad arguments. > > An alternative possibility is to run the postmaster under truss so you > can see what arguments are passed to the kernel on every kernel call, > but that'd generate a pretty verbose logfile. > > regards, tom lane Done. I'll install the new binaries at the end of the day when no one is using the database and give you a copy of the logs when it dies again. Thank you for the help on this, it's very much appreciated. David Secret MIS Director Kearney Development Co., Inc.
В списке pgsql-hackers по дате отправления: