I've started playing with OpenNMS to monitor our network. I've noticed that periodically it will complain of a SMTP outage. Looking at my ASSP log, I see:
May-29-13 10:44:07 [Worker_2] 192.168.0.7 IP 192.168.0.7 matches acceptAllMail - with 192.168.0.0/24 May-29-13 10:44:07 [Worker_2] Connected: session:7FFD54D890D0 192.168.0.7:40840 > 192.168.0.2:25 > 127.0.0.1:125 May-29-13 10:44:07 [Worker_2] 192.168.0.7 info: sending EHLO instead of HELO to 127.0.0.1 May-29-13 10:44:07 [Worker_2] Disconnected: session:7FFD54D890D0 192.168.0.7 - processing time 0 seconds May-29-13 10:44:07 [Worker_3] 192.168.0.7 IP 192.168.0.7 matches acceptAllMail - with 192.168.0.0/24 May-29-13 10:44:07 [Worker_3] Connected: session:7FFD4C2B83D8 192.168.0.7:40841 > 192.168.0.2:25 > 127.0.0.1:125 May-29-13 10:44:07 [Worker_3] 192.168.0.7 info: sending EHLO instead of HELO to 127.0.0.1 May-29-13 10:44:07 [Worker_3] Disconnected: session:7FFD4C2B83D8 192.168.0.7 - processing time 0 seconds OpenNMS reports an outage at this time. A little later: May-29-13 10:44:38 [Worker_3] 192.168.0.7 IP 192.168.0.7 matches acceptAllMail - with 192.168.0.0/24 May-29-13 10:44:38 [Worker_3] Connected: session:D83D950 192.168.0.7:40871 > 192.168.0.2:25 > 127.0.0.1:125 May-29-13 10:44:38 [Worker_3] 192.168.0.7 info: sending EHLO instead of HELO to 127.0.0.1 May-29-13 10:44:38 [Worker_3] Disconnected: session:D83D950 192.168.0.7 - processing time 0 seconds OpenNMS reports service restored. Similarly, I see this for the next failure: May-29-13 10:49:38 [Worker_1] 192.168.0.7 IP 192.168.0.7 matches acceptAllMail - with 192.168.0.0/24 May-29-13 10:49:38 [Worker_1] Connected: session:7FFD5DB7C510 192.168.0.7:40974 > 192.168.0.2:25 > 127.0.0.1:125 May-29-13 10:49:38 [Worker_1] 192.168.0.7 info: sending EHLO instead of HELO to 127.0.0.1 May-29-13 10:49:38 [Worker_1] Disconnected: session:7FFD5DB7C510 192.168.0.7 - processing time 0 seconds May-29-13 10:49:38 [Worker_2] 192.168.0.7 IP 192.168.0.7 matches acceptAllMail - with 192.168.0.0/24 May-29-13 10:49:38 [Worker_2] Connected: session:7FFD54341188 192.168.0.7:40975 > 192.168.0.2:25 > 127.0.0.1:125 May-29-13 10:49:38 [Worker_2] 192.168.0.7 info: sending EHLO instead of HELO to 127.0.0.1 May-29-13 10:49:38 [Worker_2] Disconnected: session:7FFD54341188 192.168.0.7 - processing time 0 seconds May-29-13 10:50:02 [Worker_1] 192.168.0.7 IP 192.168.0.7 matches acceptAllMail - with 192.168.0.0/24 May-29-13 10:50:02 [Worker_1] Connected: session:7FFD5DD90CC0 192.168.0.7:60492 > 192.168.0.3:25 > 127.0.0.1:125 May-29-13 10:50:02 [Worker_1] 192.168.0.7 info: sending EHLO instead of HELO to 127.0.0.1 May-29-13 10:50:02 [Worker_1] Disconnected: session:7FFD5DD90CC0 192.168.0.7 - processing time 0 seconds May-29-13 10:50:09 [Worker_1] 192.168.0.7 IP 192.168.0.7 matches acceptAllMail - with 192.168.0.0/24 May-29-13 10:50:09 [Worker_1] Connected: session:7FFD5D8F9690 192.168.0.7:40995 > 192.168.0.2:25 > 127.0.0.1:125 May-29-13 10:50:09 [Worker_1] 192.168.0.7 info: sending EHLO instead of HELO to 127.0.0.1 May-29-13 10:50:09 [Worker_1] Disconnected: session:7FFD5D8F9690 192.168.0.7 - processing time 0 seconds May-29-13 10:50:09 [Worker_2] 192.168.0.7 IP 192.168.0.7 matches acceptAllMail - with 192.168.0.0/24 May-29-13 10:50:09 [Worker_2] Connected: session:7FFD5557F238 192.168.0.7:40996 > 192.168.0.2:25 > 127.0.0.1:125 May-29-13 10:50:09 [Worker_2] 192.168.0.7 info: sending EHLO instead of HELO to 127.0.0.1 May-29-13 10:50:09 [Worker_2] Disconnected: session:7FFD5557F238 192.168.0.7 - processing time 0 seconds May-29-13 10:50:39 [Worker_1] 192.168.0.7 IP 192.168.0.7 matches acceptAllMail - with 192.168.0.0/24 May-29-13 10:50:39 [Worker_1] Connected: session:7FFD5C134960 192.168.0.7:40997 > 192.168.0.2:25 > 127.0.0.1:125 May-29-13 10:50:39 [Worker_1] 192.168.0.7 info: sending EHLO instead of HELO to 127.0.0.1 May-29-13 10:50:39 [Worker_1] Disconnected: session:7FFD5C134960 192.168.0.7 - processing time 0 seconds May-29-13 10:50:39 [Worker_2] 192.168.0.7 IP 192.168.0.7 matches acceptAllMail - with 192.168.0.0/24 May-29-13 10:50:39 [Worker_2] Connected: session:C0818D8 192.168.0.7:40998 > 192.168.0.2:25 > 127.0.0.1:125 May-29-13 10:50:40 [Worker_2] 192.168.0.7 info: sending EHLO instead of HELO to 127.0.0.1 May-29-13 10:50:40 [Worker_2] Disconnected: session:C0818D8 192.168.0.7 - processing time 1 seconds And then restores with: May-29-13 10:51:10 [Worker_1] 192.168.0.7 IP 192.168.0.7 matches acceptAllMail - with 192.168.0.0/24 May-29-13 10:51:10 [Worker_1] Connected: session:7FFD5DA788F0 192.168.0.7:40999 > 192.168.0.2:25 > 127.0.0.1:125 May-29-13 10:51:10 [Worker_1] 192.168.0.7 info: sending EHLO instead of HELO to 127.0.0.1 May-29-13 10:51:10 [Worker_1] Disconnected: session:7FFD5DA788F0 192.168.0.7 - processing time 0 seconds May-29-13 10:51:10 [Worker_1] 192.168.0.7 IP 192.168.0.7 matches acceptAllMail - with 192.168.0.0/24 May-29-13 10:51:10 [Worker_1] Connected: session:7FFD5D728628 192.168.0.7:41000 > 192.168.0.2:25 > 127.0.0.1:125 May-29-13 10:51:10 [Worker_1] 192.168.0.7 info: sending EHLO instead of HELO to 127.0.0.1 May-29-13 10:51:10 [Worker_1] Disconnected: session:7FFD5D728628 192.168.0.7 - processing time 0 seconds Something I noticed going through this - when the outage occurs, it appears two different worker processes are being engaged - and the restoral occurs when only one is used. This server does have multiple IP's, and ASSP listens on them all. Is it a problem having a remote connection attempt to talk to ASSP on multiple IP's simultaneously? -- Daniel ------------------------------------------------------------------------------ Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET Get 100% visibility into your production application - at no cost. Code-level diagnostics for performance bottlenecks with <2% overhead Download for free and get started troubleshooting in minutes. http://p.sf.net/sfu/appdyn_d2d_ap1 _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
