Hi Charles,

Thanks for your answer.

> Renato <[EMAIL PROTECTED]> wrote:
> > 
> > I'm monitoring the behaviour of tcpserver for the pop service ( 
simple 'ps -
> > aux | grep tcpserver | grep pop' and I get, obviously, just one is 
> > running ). Sometimes, supervise tries to restart tcpserver and I see 2 
> > tcpservers. Then the second dies ( port is already bind ). During this 
> > time, pop fails. Looking at the log for the pop service, I can tell 
that 
> > there is no specific moment that it happens. Tcpserver didn't run out 
of 
> > connections ( I have up to 150 concurrent ), sometimes it did with 20 
> > connections, sometimes with 90 concurrents. 
> > 
> > Is this an expected behauvior ?
> 
> No.  tcpserver shouldn't randomly die.
> 
> > Is there a way to tune up supervise ? ( time-out, any other 
parameters ? )
> 
> Perhaps you're running it with memory or other process limits, or its 
hitting
> a system-wide limit?  Without specific information about how you've 
configured
> svscan, tcpserver, etc, log entries, and perhaps strace of the process 
dying,
> we can't help you.
> 
> Charles

First of all, how can I configure svscan ? I just run svscan-
start /var/service and that's all ( I think ). In terms of pop3, here is 
how I start tcpserver in pop.

exec tcpserver -u "$uid" -g "$gid" -c "$concurrency" -v -R -H -t 90 \
    -lmyserver \
     -x /etc/tcpcontrol/pop-3.cdb 0 pop-3 \
     qmail-popup "$hostname" \
     checkvpw \
     qmail-pop3d Maildir/

In terms of logs, I don't have any message ( like system is not able to 
fork... ) just tcpserver common status/concurrency messages.

In terms of kernel I have, by the moment we speak:
proc/sys/fs/inode-max -> 131072
/proc/sys/fs/inode-nr -> 65540 14180
/proc/sys/fs/file-max -> 16384
/proc/sys/fs/file-nr -> 2180    297     16384

/proc/sys/net/ipv4/tcp_syncookies -> 1
/proc/sys/net/ipv4/ip_local_port_range -> 1024 61000
/proc/sys/net/ipv4/tcp_fin_timeout -> 30
/proc/sys/net/ipv4/tcp_keepalive_time -> 1800
/proc/sys/net/ipv4/tcp_window_scaling -> 0
/proc/sys/net/ipv4/tcp_sack -> 0
/proc/sys/net/ipv4/tcp_timestamps -> 0

Number of processes: 360 ( My machine is a Pentium III 800 Mhz, SCSI - 
14Gb, 80% full ).

I think there might be a queue of incoming connections that my system is 
not able to handle. Is it a kernel issue ? 

Thanks again
Renato - Brazil.

Reply via email to