On Mon, 21 Jun 2004, Etienne Goyer wrote:Jun 21 14:26:54 frontend1 master[12195]: process 2270 exited, status 75
Jun 21 14:26:54 frontend1 master[12195]: service pop3s pid 2270 in BUSY state: terminated abnormally
This happen with both pop3s and imaps.
This is more of a concern. It indicates the process is exiting with an abnormal error code. EX_TEMPFAIL, which isn't tremendouly useful. Is it always the same user, same mailbox, etc?
We don't get to see the user/mailbox. Here is more context :
Jun 22 14:42:28 frontend1 imaps[8300]: accepted connection
Jun 22 14:42:28 frontend1 imaps[8300]: imaps failed: somehost [1.2.3.4]
Jun 22 14:42:28 frontend1 master[12195]: process 8300 exited, status 75
Jun 22 14:42:28 frontend1 master[12195]: service imaps pid 8300 in BUSY state: terminated abnormally
Same, with pop3s :
Jun 22 14:41:58 frontend1 pop3s[8705]: pop3s failed: somehost [1.2.3.4]
Jun 22 14:41:58 frontend1 pop3s[8705]: Fatal error: tls_start_servertls() failed
Jun 22 14:41:58 frontend1 master[12195]: process 8705 exited, status 75
Jun 22 14:41:58 frontend1 master[12195]: service pop3s pid 8705 in BUSY state: terminated abnormally
It happen only with imaps/pop3s, could it be related to TLS or somesuch?
signature.asc
Description: OpenPGP digital signature