Server hanging w/qmail 1.03
I am having the following problem on my qmail server ... running the LATEST version of qmail 1.03 Sun E-450 2CPU, 1G RAM The server hangs and is unresponseive to anything but pings load on the server skyrokets to 300+ server is NOT loggin anything, in fact the server is doing nothing (cron can not even run) the only way to resolve this problem is to reboot the box Sun believes we are running out of memory, but that doesn't jive w/sar reports has anyone experienced this or anything like this I will summerize thanks Brian
Re: Server hanging w/qmail 1.03
Brian Estes [EMAIL PROTECTED] wrote: I am having the following problem on my qmail server ... running the LATEST version of qmail 1.03 Sun E-450 2CPU, 1G RAM The server hangs and is unresponseive to anything but pings load on the server skyrokets to 300+ server is NOT loggin anything, in fact the server is doing nothing (cron can not even run) What is your logging configuration for qmail on that box? If you're going to the syslog, that could be your problem. syslog has been known to bring even large boxes to their knees with a busy qmail server. Try multilog or something instead. It could also be that you've got the concurrent remote connection limit or inbound connection limit set too high for your hardware, although that seems unlikely. What are the values of /var/qmail/control/concurrencyremote and your tcpserver limit on SMTP connections? 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: Server hanging w/qmail 1.03
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 17 Aug 2000, at 11:21, Brian Estes wrote: The server hangs and is unresponseive to anything but pings load on the server skyrokets to 300+ server is NOT loggin anything, in fact the server is doing nothing (cron can not even run) Can "top" run? "ps"? What's chewing up on CPU? (Don't tell me it's syslogd :-)) -BEGIN PGP SIGNATURE- Version: PGP 6.0.2 -- QDPGP 2.60 Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBOZv3clMwP8g7qbw/EQIFxACfcXtmnNTNcSehqA/SS3cXeA8CKmUAnjhM TxX6fflvjLHi4OnBE4eS0xAI =06xS -END PGP SIGNATURE- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Server hanging w/qmail 1.03
has anyone experienced this or anything like this not the same... just qmail-smtpd crashed ones with the following message in the logs: --- from /var/log/messages --- Jul 31 05:42:59 joshua -- MARK -- Jul 31 05:52:52 joshua kernel: Oops: Jul 31 05:52:52 joshua kernel: CPU:0 Jul 31 05:52:52 joshua kernel: EIP:0010:[cached_lookup+37/84] Jul 31 05:52:52 joshua kernel: EFLAGS: 00010206 Jul 31 05:52:52 joshua kernel: eax: 1000 ebx: c0f172a0 ecx: edx: c08da6d3 Jul 31 05:52:52 joshua kernel: esi: 000b edi: 000b ebp: c0bd8980 esp: c0999f5c Jul 31 05:52:52 joshua kernel: ds: 0018 es: 0018 ss: 0018 Jul 31 05:52:52 joshua kernel: Process qmail-send (pid: 174, process nr: 14, stackpage=c0999000) Jul 31 05:52:52 joshua kernel: Stack: c01298c5 c0bd8980 c0999f80 000b c0937000 c0937000 0001 bb1c Jul 31 05:52:52 joshua kernel:c0937000 c0937005 0001 0031 c012999d c0937000 0001 Jul 31 05:52:52 joshua kernel:c0998000 bb54 badc c01279d3 08052230 0001 c0998000 bb54 Jul 31 05:52:52 joshua kernel: Call Trace: [lookup_dentry+253/428] [__namei+41/92] [sys_newstat+19/100] [system_call+52/56] Jul 31 05:52:52 joshua kernel: Code: 8b 00 85 c0 74 23 56 53 ff d0 83 c4 08 85 c0 75 18 53 e8 78 Jul 31 06:02:59 joshua -- MARK -- --- cya Joel
Re: Server hanging w/qmail 1.03
Brian Estes [EMAIL PROTECTED] wrote: What is your logging configuration for qmail on that box? If you're going to the syslog, that could be your problem. syslog has been known to bring even large boxes to their knees with a busy qmail server. Try multilog or something instead. tell me more about mulitlog, we are running syslog but during this process nothing is being logged qmail and qmail-smtpd log to stdout; 'splogger' forwards this logging information to syslogd. syslogd will happily suck 100% of the CPU on a busy mail server, preventing useful work from being done. multilog is part of the daemontools package (http://cr.yp.to/daemontools.html); see (http://cr.yp.to/daemontools/multilog.html). It flexible, configurable, and much easier on the system. You really should install the dameontools if you're not already running them. 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. ---
