Re: tcpserver delaying connections

2000-08-01 Thread James Raftery

On Tue, Aug 01, 2000 at 08:03:23AM -0500, Ben Beuchler wrote:
 despite the annoying tai64n timestamps on multilog. ;-)

Let's just pass over that :)

 2000-08-01 07:42:33.785679500 tcpserver: ok 61983 :216.243.128.140:25
 :205.188.1
 2000-08-01 07:42:34.432984500 tcpserver: ok 61985
 mail.bitstream.net:216.243.128
 2000-08-01 07:42:34.453643500 tcpserver: ok 61989
 mail.bitstream.net:216.243.128
  
 Note the delay from when it notes the start of a connection (07:41:34)
 to when it actually accepts it and says OK (07:42:25).

I've cut out everything but the 'ok' lines. They look incomplete. Could
you check that's what they actually contain?

 Here is the command line I am using for tcpserver:
   
 exec /usr/local/bin/softlimit -m 200 \
  /usr/local/bin/tcpserver -R -H -c80 -v -x \
  /etc/smtprules/tcp.smtp.cdb -u73 -g1003 0 smtp \
  /var/qmail/bin/qmail-smtpd 21

Are you certain that is the invocation used for the running instance of
tcpserver? The log lines above have TCPLOCALHOST information, which
mean it is looking up your hosts IP address in the DNS. Is the reverse
DNS for your IP allocation healthy?

Regards,

james
-- 
James Raftery (JBR54)  -  Programmer Hostmaster  -  IE TLD Hostmaster
   IE Domain Registry  -  www.domainregistry.ie  -  (+353 1) 706 2375
  "Managing 4000 customer domains with BIND has been a lot like
   herding cats." - Mike Batchelor, on [EMAIL PROTECTED]



Re: tcpserver delaying connections

2000-08-01 Thread Ben Beuchler

On Tue, Aug 01, 2000 at 03:27:44PM +0100, James Raftery wrote:

 On Tue, Aug 01, 2000 at 08:03:23AM -0500, Ben Beuchler wrote:
  despite the annoying tai64n timestamps on multilog. ;-)
 
 Let's just pass over that :)
 
  2000-08-01 07:42:33.785679500 tcpserver: ok 61983 :216.243.128.140:25
  :205.188.1
  2000-08-01 07:42:34.432984500 tcpserver: ok 61985
  mail.bitstream.net:216.243.128
  2000-08-01 07:42:34.453643500 tcpserver: ok 61989
  mail.bitstream.net:216.243.128
   
  Note the delay from when it notes the start of a connection (07:41:34)
  to when it actually accepts it and says OK (07:42:25).
 
 I've cut out everything but the 'ok' lines. They look incomplete. Could
 you check that's what they actually contain?

I apologize, I'm not sure how I managed to truncate those lines.  Here's
the actual goods:

2000-08-01 07:42:33.785679500 tcpserver: ok 61983 :216.243.128.140:25
:205.188.157.37::35254
2000-08-01 07:42:34.432984500 tcpserver: ok 61985
mail.bitstream.net:216.243.128.140:25 :38.202.217.115::1855
2000-08-01 07:42:34.453643500 tcpserver: ok 61989
mail.bitstream.net:216.243.128.140:25 :204.160.241.38::63400
 
  Here is the command line I am using for tcpserver:

  exec /usr/local/bin/softlimit -m 200 \
   /usr/local/bin/tcpserver -R -H -c80 -v -x \
   /etc/smtprules/tcp.smtp.cdb -u73 -g1003 0 smtp \
   /var/qmail/bin/qmail-smtpd 21
 
 Are you certain that is the invocation used for the running instance of
 tcpserver? The log lines above have TCPLOCALHOST information, which
 mean it is looking up your hosts IP address in the DNS. 

Hmmm...  What flag tells it not to look for that?  Anyway, here's the
actual running copy from 'ps awx | grep smtprules':

83699  ??  S  0:58.31 /usr/local/bin/tcpserver -R -H -c80 -v -x
/etc/smtprules/tcp.smtp.cdb -u73 -g1003 0 smtp
/var/qmail/bin/qmail-smtpd

 Is the reverse DNS for your IP allocation healthy?

It appears to be.  If you or anyone else can find a problem with it, I
would be greatful.  But...  Everything appears to be fine.

Thanks,
Ben

-- 
Ben Beuchler [EMAIL PROTECTED]
MAILER-DAEMON (612) 321-9290 x101
Bitstream Underground   www.bitstream.net



Re: tcpserver delaying connections

2000-08-01 Thread James Raftery

On Tue, Aug 01, 2000 at 09:43:50AM -0500, Ben Beuchler wrote:
 Hmmm...  What flag tells it not to look for that?

-l localname
See http://cr.yp.to/ucspi-tcp/tcpserver.html for the full raft of
options.

 It appears to be.  If you or anyone else can find a problem with it, I
 would be greatful.  But...  Everything appears to be fine.

The delegation information your nameservers are announcing for
128.243.216.in-addr.arpa is different to what ARIN have registered for
the netblock. There no reason this would cause tcpserver to pause, but
even so.

Regards,

james
-- 
James Raftery (JBR54)  -  Programmer Hostmaster  -  IE TLD Hostmaster
   IE Domain Registry  -  www.domainregistry.ie  -  (+353 1) 706 2375
  "Managing 4000 customer domains with BIND has been a lot like
   herding cats." - Mike Batchelor, on [EMAIL PROTECTED]



Re: tcpserver delaying connections

2000-08-01 Thread Ben Beuchler

On Tue, Aug 01, 2000 at 05:52:57PM +0100, James Raftery wrote:

 On Tue, Aug 01, 2000 at 09:43:50AM -0500, Ben Beuchler wrote:
  Hmmm...  What flag tells it not to look for that?
 
 -l localname
 See http://cr.yp.to/ucspi-tcp/tcpserver.html for the full raft of
 options.

I will try that, thank-you.
 
  It appears to be.  If you or anyone else can find a problem with it, I
  would be greatful.  But...  Everything appears to be fine.
 
 The delegation information your nameservers are announcing for
 128.243.216.in-addr.arpa is different to what ARIN have registered for
 the netblock. There no reason this would cause tcpserver to pause, but
 even so.

I will look into that.

Thanks!

Ben

-- 
Ben Beuchler [EMAIL PROTECTED]
MAILER-DAEMON (612) 321-9290 x101
Bitstream Underground   www.bitstream.net