Date: Tue, 22 Aug 2000 11:53:36 +0100 (GMT Daylight Time) From: Rick <wylee@sabrecross.com> To: freebsd-security@freebsd.org Subject: 3.5 and 4.0 with sendmail 8.9.3 Message-ID: <Pine.WNT.4.05.10008221124060.170-100000@lan.imbris.com>
next in thread | raw e-mail | index | archive | help
Fun problem? Wanna get a machine to reach max load and never return to normal? Watch sendmail processes explode faster that you can refresh PS? Try this? Here is what we have: tested two machines: Alpha 500a running 4.0 and I386 running 3.5, only common attributes: BT-958 SCSI card and etherlink III 10/100 cards. Which BTW the BT958 goes into mailbox busy, 192 commands, scsi clear both machines, problem is confirmed with the BL driver. Doesn't happen with an Adaptec. Note 3 versions of firmware for Busslogics was tried on 3 seperate cards. All reacted the same. Mail is on one central server and aliase file along with password updates are passed from another machine, via nfs, at various times during the day. 9/10 times not a problem all works as planned. when we fail: aliase.db file is not rebuilt and set to 0 bytes. Aliase file is correct at proper value and number of bytes. Error message is aliase file is locked and can't run new aliases. Now of coarse sendmail looking at the aliase file goes off the deep end and attempts to do local delivery and can't. The only way so far to clear this problem is to shutdown now and do a control D to bring back up in multi user. Forget reading the console port. It scrolls faster than a 2K page running at DS3 speed. Nothing different in the logs, either. Killing sendmail doesn't work. No locks can be found and until this occurs system swears the file is locked. Not just locked in shared mode, but in executive mode. Now we have tried a simple copy, a mv and various other ideas and the problem is persistant on the regular aliase file. Today by varying the sequence the newliase command went off into space, lost somewhere in the great memory void. The system did not attempt to rebuild but the file did not say it was locked. Killed out of processes ok. But could not rebuild aliase file. Again single user mode back to multi and you can clear, go about your business. I stress the fact this is a random error. It may happen once in a 3 day period or once every few hours. Any help would be appreciated. Rick McGee Network Engineer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.WNT.4.05.10008221124060.170-100000>