Re: pop3 dying
mick <[EMAIL PROTECTED]> wrote: >Should I add: > | /var/qmail/bin/splogger pop3 3 & > >On Sat, 17 Feb 2001, Peter van Dijk wrote: > >> On Sat, Feb 17, 2001 at 04:02:58PM +, mick wrote: >> > grep for pop3 on mail.log and daemon.log for pop3 (digital unix) returns >> > nothing. >> > this is how it is called: >> > >> > /usr/local/bin/tcpserver 0 pop3 /var/qmail/bin/qmail-popup >> > my.domain.com / >> > bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir & >> >> This startup doesn't specify any logging. I recommend multilog over splogger because syslog is inefficient, insecure, and unreliable. -Dave
Re: pop3 dying
Yep still working great. And found this right out of the tcpserver man page: -climit Do not handle more than limit simultaneous connections. If there are limit simultaneous copies of program running, defer acceptance of a new connection until one copy finishes. limit must be a positive integer. Default: 40. Thanks again. On Sat, 17 Feb 2001, mick wrote: > Ok, tried changing this: > /usr/local/bin/tcpserver 0 pop3 /var/qmail/bin/qmail-popup > my.domain.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir & > > to this: > /usr/local/bin/tcpserver -c 200 0 pop3 /var/qmail/bin/qmail-popup > my.domain.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir & > > See what that does. > > > On Sat, 17 Feb 2001, Charles Cazabon wrote: > > > mick <[EMAIL PROTECTED]> wrote: > > > concurency limit is set to 120, does that mean its limited to 120 pop3 > > > sesions? > > > > Yes, if that's the number you are supplying as the -c option to the > > tcpserver instance launching qmail-pop3d. Double or quadruple it and see > > if your problems stop. You could also enable the logging from tcpserver for > > that. > > > > Charles > > -- > > --- > > Charles Cazabon<[EMAIL PROTECTED]> > > GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ > > Any opinions expressed are just that -- my opinions. > > --- > > > > > > * > Mick Dobra > Systems Administrator > MTCO Communications > 1-800-859-6826 > * > > * Mick Dobra Systems Administrator MTCO Communications 1-800-859-6826 *
Re: pop3 dying
Seems to have worked so far! I'll keep my fingers crossed. Thank you greatly for your help. On Sat, 17 Feb 2001, mick wrote: > Ok, tried changing this: > /usr/local/bin/tcpserver 0 pop3 /var/qmail/bin/qmail-popup > my.domain.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir & > > to this: > /usr/local/bin/tcpserver -c 200 0 pop3 /var/qmail/bin/qmail-popup > my.domain.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir & > > See what that does. > > > On Sat, 17 Feb 2001, Charles Cazabon wrote: > > > mick <[EMAIL PROTECTED]> wrote: > > > concurency limit is set to 120, does that mean its limited to 120 pop3 > > > sesions? > > > > Yes, if that's the number you are supplying as the -c option to the > > tcpserver instance launching qmail-pop3d. Double or quadruple it and see > > if your problems stop. You could also enable the logging from tcpserver for > > that. > > > > Charles > > -- > > --- > > Charles Cazabon<[EMAIL PROTECTED]> > > GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ > > Any opinions expressed are just that -- my opinions. > > --- > > > > > > * > Mick Dobra > Systems Administrator > MTCO Communications > 1-800-859-6826 > * > > * Mick Dobra Systems Administrator MTCO Communications 1-800-859-6826 *
Re: pop3 dying
Ok, tried changing this: /usr/local/bin/tcpserver 0 pop3 /var/qmail/bin/qmail-popup my.domain.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir & to this: /usr/local/bin/tcpserver -c 200 0 pop3 /var/qmail/bin/qmail-popup my.domain.com /bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir & See what that does. On Sat, 17 Feb 2001, Charles Cazabon wrote: > mick <[EMAIL PROTECTED]> wrote: > > concurency limit is set to 120, does that mean its limited to 120 pop3 > > sesions? > > Yes, if that's the number you are supplying as the -c option to the > tcpserver instance launching qmail-pop3d. Double or quadruple it and see > if your problems stop. You could also enable the logging from tcpserver for > that. > > Charles > -- > --- > Charles Cazabon<[EMAIL PROTECTED]> > GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ > Any opinions expressed are just that -- my opinions. > --- > > * Mick Dobra Systems Administrator MTCO Communications 1-800-859-6826 *
Re: pop3 dying
mick <[EMAIL PROTECTED]> wrote: > concurency limit is set to 120, does that mean its limited to 120 pop3 > sesions? Yes, if that's the number you are supplying as the -c option to the tcpserver instance launching qmail-pop3d. Double or quadruple it and see if your problems stop. You could also enable the logging from tcpserver for that. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: pop3 dying
Should I add: | /var/qmail/bin/splogger pop3 3 & On Sat, 17 Feb 2001, Peter van Dijk wrote: > On Sat, Feb 17, 2001 at 04:02:58PM +, mick wrote: > > grep for pop3 on mail.log and daemon.log for pop3 (digital unix) returns > > nothing. > > this is how it is called: > > > > /usr/local/bin/tcpserver 0 pop3 /var/qmail/bin/qmail-popup > > my.domain.com / > > bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir & > > This startup doesn't specify any logging. > > Greetz, Peter. > > * Mick Dobra Systems Administrator MTCO Communications 1-800-859-6826 *
Re: pop3 dying
On Sat, Feb 17, 2001 at 04:02:58PM +, mick wrote: > grep for pop3 on mail.log and daemon.log for pop3 (digital unix) returns > nothing. > this is how it is called: > > /usr/local/bin/tcpserver 0 pop3 /var/qmail/bin/qmail-popup > my.domain.com / > bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir & This startup doesn't specify any logging. Greetz, Peter.
Re: pop3 dying
concurency limit is set to 120, does that mean its limited to 120 pop3 sesions? On Sat, 17 Feb 2001, Peter van Dijk wrote: > On Sat, Feb 17, 2001 at 10:40:20PM +0100, Peter van Dijk wrote: > > On Sat, Feb 17, 2001 at 03:41:45PM +, mick wrote: > > > Can't see anything obvious > > > This is a busy server so the logs a flying pretty fast, connetions just > > > time out and I can't see any obvious failure messages in the logs. > > > Any suggestions for what I should grep for? > > > > Well, I suppose there's no log of any pop3 activity after it dies. > > What are the last few lines logged about pop3? > > Hmm, is your pop3 perhaps reaching the concurrency limit set in > tcpserver? Or, if running from inetd (which is a bad idea), is the > ratelimiting holding it back? > > Greetz, Peter. > > * Mick Dobra Systems Administrator MTCO Communications 1-800-859-6826 *
Re: pop3 dying
grep for pop3 on mail.log and daemon.log for pop3 (digital unix) returns nothing. this is how it is called: /usr/local/bin/tcpserver 0 pop3 /var/qmail/bin/qmail-popup my.domain.com / bin/checkpassword /var/qmail/bin/qmail-pop3d Maildir & On Sat, 17 Feb 2001, Peter van Dijk wrote: > On Sat, Feb 17, 2001 at 03:41:45PM +, mick wrote: > > Can't see anything obvious > > This is a busy server so the logs a flying pretty fast, connetions just > > time out and I can't see any obvious failure messages in the logs. > > Any suggestions for what I should grep for? > > Well, I suppose there's no log of any pop3 activity after it dies. > What are the last few lines logged about pop3? > > Greetz, Peter. > > * Mick Dobra Systems Administrator MTCO Communications 1-800-859-6826 *
Re: pop3 dying
On Sat, Feb 17, 2001 at 10:40:20PM +0100, Peter van Dijk wrote: > On Sat, Feb 17, 2001 at 03:41:45PM +, mick wrote: > > Can't see anything obvious > > This is a busy server so the logs a flying pretty fast, connetions just > > time out and I can't see any obvious failure messages in the logs. > > Any suggestions for what I should grep for? > > Well, I suppose there's no log of any pop3 activity after it dies. > What are the last few lines logged about pop3? Hmm, is your pop3 perhaps reaching the concurrency limit set in tcpserver? Or, if running from inetd (which is a bad idea), is the ratelimiting holding it back? Greetz, Peter.
Re: pop3 dying
On Sat, Feb 17, 2001 at 03:41:45PM +, mick wrote: > Can't see anything obvious > This is a busy server so the logs a flying pretty fast, connetions just > time out and I can't see any obvious failure messages in the logs. > Any suggestions for what I should grep for? Well, I suppose there's no log of any pop3 activity after it dies. What are the last few lines logged about pop3? Greetz, Peter.
Re: pop3 dying
Can't see anything obvious This is a busy server so the logs a flying pretty fast, connetions just time out and I can't see any obvious failure messages in the logs. Any suggestions for what I should grep for? On Sat, 17 Feb 2001, Peter van Dijk wrote: > On Sat, Feb 17, 2001 at 03:28:38PM +, mick wrote: > > I've got a qmail system in which pop3 dies after about 30 minutes of use. > > The system load average in low, can't see any obvious run away process, > > the rest of the system works fine (sshd, smtp, http, ftp). killing all > > qmail process's and restarting gets it to work for about another 30 > > minutes > > Any suggestions as to where to start looking? > > What do the logs say? > > Greetz, Peter. > > * Mick Dobra Systems Administrator MTCO Communications 1-800-859-6826 *
Re: pop3 dying
On Sat, Feb 17, 2001 at 03:28:38PM +, mick wrote: > I've got a qmail system in which pop3 dies after about 30 minutes of use. > The system load average in low, can't see any obvious run away process, > the rest of the system works fine (sshd, smtp, http, ftp). killing all > qmail process's and restarting gets it to work for about another 30 > minutes > Any suggestions as to where to start looking? What do the logs say? Greetz, Peter.
pop3 dying
I've got a qmail system in which pop3 dies after about 30 minutes of use. The system load average in low, can't see any obvious run away process, the rest of the system works fine (sshd, smtp, http, ftp). killing all qmail process's and restarting gets it to work for about another 30 minutes Any suggestions as to where to start looking? * Mick Dobra Systems Administrator MTCO Communications 1-800-859-6826 *
