On Mon, Sep 08, 2008 at 10:35:40PM +0530, Devdas Bhagat wrote:
> The last error messages I get are these:
> Sep 8 13:54:37 jaundiced-outlook postfix/smtp[7998]: warning: problem
> talking to service private/scache: Connection timed out
> Sep 8 13:54:37 jaundiced-outlook postfix/smtp[20375]: warning: problem
> talking to service private/scache: Connection timed out
> Sep 8 13:54:37 jaundiced-outlook postfix/smtp[7960]: warning: problem
> talking to service private/scache: Connection timed out
> Sep 8 13:54:37 jaundiced-outlook postfix/smtp[17618]: warning: problem
> talking to service private/scache: Connection timed out
> <snip about 600 similar lines about this problem>
Master daemon freezes and is unable to spawn any new processes.
> Sep 8 14:10:56 jaundiced-outlook postfix/master[11125]: fatal: watchdog
> timeout
After a 1000s delay, master bails out, so the problem started 16 minutes
and 40 seconds before 14:10:56, i.e at 13:53:16.
> Sep 8 14:10:56 jaundiced-outlook postfix/qmgr[13568]: fatal: watchdog timeout
The queue manager was also frozen. What happened at ~13:53 ???
The master received no events for 1000 seconds, do you have a 60 second
wakeup timer for pickup in the master.cf? Or a 300s timer for qmgr?
Perhaps the O/S incorrectly reports a full qmgr FIFO as being ready,
and then master blocks trying to write a wakekup trigger (one byte)
to the fifo? But that still leaves the question as to why qmgr is
frozen open...
This looks like an O/S resource issue...
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[EMAIL PROTECTED]>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
