Thank you for your reply.
> Andrea Cerrito <[EMAIL PROTECTED]> wrote:
> >
> > I have a server farm with pop3 / smtp / ftp services running on
> Linux and
> > served by tcpserver. My monitoring software is Mon, and sometimes I'm
> > receiving alarms about these services: they are always false alarms.
>
> Two possibilities: tcpserver is accepting the connections as a backlog
> because you're hitting your concurrency limits,
No.
False alarms happens even during low traffic, as show by logs.
2001-06-12 13:27:03.855642500 tcpserver: status: 1/50
2001-06-12 13:27:03.856118500 tcpserver: pid 17372 from 10.10.32.135
2001-06-12 13:27:11.326985500 tcpserver: ok 17372 pop3.frontend.int:ip:10025
:ip::4563
2001-06-12 13:27:11.334100500 tcpserver: end 17372 status 256
2001-06-12 13:27:11.334181500 tcpserver: status: 0/50
As you can see, from 13:27:03 tcpserver spawn at 13:27:11, far away from
timeout for monitoring (5 secs).
A normal session is like:
2001-06-12 13:28:15.451685500 tcpserver: status: 1/50
2001-06-12 13:28:15.452134500 tcpserver: pid 17378 from 10.10.32.135
2001-06-12 13:28:15.452904500 tcpserver: ok 17378 pop3.frontend.int:ip:10025
:ip::4585
2001-06-12 13:28:15.460697500 tcpserver: end 17378 status 0
2001-06-12 13:28:15.460778500 tcpserver: status: 0/50
> or the DNS lookups which
> tcpserver does are timing out sometimes.
Nope, because the host making monitoring is in /etc/hosts and tcpserver
isn't relying on dns. This is my run:
exec /usr/local/bin/tcpserver -v -c 50 -H -P -R -l pop3.frontend.int -x
/coda/qmail/vpopmail/relay/tcp.smtp.cdb -u $QMAILUID -g $QMAILGID ip port
/coda/qmail/bin/qmail-smtpd 2>&1
I thought it can be the tcp.smtp.cdb on coda, but these errors happens even
for pop3, not relying on a cdb on coda.
Other ideas?
---
Cordiali saluti / Best regards
Andrea Cerrito
^^^^^^^^^^^^^^
Net.Admin @ Centro MultiMediale di Terni S.p.A.
P.zzale Bosco 3A
05100 Terni IT
Tel. +39 744 5441330
Fax. +39 744 5441372
