On Tue, Dec 09, 2014 at 03:39:29PM -0500, James B. Byrne wrote:
> Dec 9 15:12:08 inet08 postfix/smtp[3670]: fatal: shared lock
> active/0A7EC60D8A: Resource temporarily unavailable
> [...]
> Dec 9 15:12:08 inet08 postfix/smtp[3758]: fatal: shared lock
> active/8DD5060F81: Resource temporarily unavailable
> [...]
> Dec 9 15:12:09 inet08 postfix/qmgr[3198]: warning: transport relay failure --
> see a previous warning/fatal/panic logfile record for the problem description
> [...]
> Dec 9 15:12:09 inet08 postfix/master[3195]: warning: process
> /usr/libexec/postfix/smtp pid 3670 exit status 1
> Dec 9 15:12:09 inet08 postfix/qmgr[3198]: warning: private/smtp socket:
> malformed response
> [...]
> Dec 9 15:12:09 inet08 postfix/qmgr[3198]: warning: transport smtp failure --
> see a previous warning/fatal/panic logfile record for the problem description
> Dec 9 15:12:09 inet08 postfix/master[3195]: warning: process
> /usr/libexec/postfix/smtp pid 3758 exit status 1
>
> The transport mapping error is deliberate on our part. ABMDIRECT.com does not
> go anywhere. That said, perhaps we should set it to something else.
>
> The issue I am concerned about is this:
>
> Dec 9 15:12:09 inet08 postfix/qmgr[3198]: warning: private/relay socket:
> malformed response
>
> I do not know what this means and I cannot find any obvious way how to find
> out. A postfix -vv check shows this and find no errors:
The errors are right there. The smtp delivery agent fails because
you've run out of kernel resources,
> Any idea on how I can nail down what process is generating the malformed
> socket error?
The ones that are exiting with an error.
--
Viktor.
