At 09:14 AM 23/09/2002 +0200, Roel Rozendaal wrote:
in fact they are dying: otherwise the PID would have stayed the same for
those messages;
Sorry; I should have included more of the messages. They are in fact repeating:
Sep 23 15:44:03 mag dbmail/pop3d[203]: Maximum # of connections reached,
committing suicide...
Sep 23 15:44:04 mag dbmail/pop3d[201]: Maximum # of connections reached,
committing suicide...
Sep 23 15:44:04 mag dbmail/pop3d[252]: Maximum # of connections reached,
committing suicide...
Sep 23 15:44:05 mag dbmail/pop3d[250]: Maximum # of connections reached,
committing suicide...
Sep 23 15:44:05 mag dbmail/pop3d[204]: Maximum # of connections reached,
committing suicide...
Sep 23 15:44:05 mag dbmail/pop3d[203]: Maximum # of connections reached,
committing suicide...
Sep 23 15:44:06 mag dbmail/pop3d[201]: Maximum # of connections reached,
committing suicide...
Sep 23 15:44:08 mag dbmail/pop3d[250]: Maximum # of connections reached,
committing suicide...
Sep 23 15:44:08 mag dbmail/pop3d[252]: Maximum # of connections reached,
committing suicide...
Sep 23 15:44:09 mag dbmail/pop3d[204]: Maximum # of connections reached,
committing suicide...
however there seems to be a problem as you normally don't
get a lot of those suicides. What is your current POP3D_CHILD_MAX_CONNECTS
POP3D_CHILD_MAX_CONNECTS=10000
value in the config table? Is it the newly created process that dies
immediately? Could happen - when all your childs have had the same number of
connections (on average) that they all die and restart in a short timespan.
What seems to be happening is that after a large number of connects, almost
certainly enough to expire all default processes and then some, we get a
lot of failed suicides, then eventually, PostgreSQL connections fail
because the max connections is exceeded. I am not at
all sure of the sequence of events, but this seems right.
Bye for now,
Philip
regards roel
----- Original Message -----
From: "Philip Warner" <[EMAIL PROTECTED]>
To: <dbmail@dbmail.org>
Sent: Sunday, September 22, 2002 10:42 AM
Subject: [Dbmail] Failed suicide?
>
> We are getting a large number of these sorts of messages:
>
> Sep 22 16:29:28 mag dbmail/pop3d[2063]: Maximum # of connections reached,
> committing suicide...
> Sep 22 16:29:30 mag dbmail/pop3d[2079]: Maximum # of connections reached,
> committing suicide...
> Sep 22 16:29:31 mag dbmail/pop3d[2064]: Maximum # of connections reached,
> committing suicide...
>
> Ordinarily thus would be fine, but they seem to be repeated - so the
> processes do not seem to be dying (assuming the number in [] is the pid).
>
> Has anybody else seen this?
>
> Or should we hunt for causes locally?
>
> The server is running FreeBSD 4.5, and dbmail is from (slightly old) CVS.
>
>
>
> ----------------------------------------------------------------
> Philip Warner | __---_____
> Albatross Consulting Pty. Ltd. |----/ - \
> (A.B.N. 75 008 659 498) | /(@) ______---_
> Tel: (+61) 0500 83 82 81 | _________ \
> Fax: (+61) 0500 83 82 82 | ___________ |
> Http://www.rhyme.com.au | / \|
> | --________--
> PGP key available upon request, | /
> and from pgp5.ai.mit.edu:11371 |/
>
> _______________________________________________
> Dbmail mailing list
> Dbmail@dbmail.org
> https://mailman.fastxs.nl/mailman/listinfo/dbmail
>
_______________________________________________
Dbmail mailing list
Dbmail@dbmail.org
https://mailman.fastxs.nl/mailman/listinfo/dbmail
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
