Re: SpamAssassin Causing Server Startup Failure
On Fri, 2003-01-10 at 18:44, David Bishop wrote: On Friday 10 January 2003 10:11 am, Adrian 'Dagurashibanipal' von Bidder wrote: For some, this is near impossible - I'm in Zurich, my server is in Bern... Then I don't understand how you would expect staying in runlevel 1 would work at all: init 1 doesn't start up network services. That's true, too. How *do* you troubleshoot boot problems? So far, I didn't have to. Back in the SuSE days I once killed libc. That was a trip to Bern and a long evening. I only had a RHat CD at hand, so I installed RH over the existing SuSE (I learned... never do this!). The next bigger case was the complete reinstallation of the system. This was done remote with installing Debian onto another partition and then booting into that, again without problems. (Christian: yes. the nullmodem cable approach would server, too, I guess). cheers -- vbi -- this email is protected by a digital signature: http://fortytwo.ch/gpg signature.asc Description: This is a digitally signed message part
RE: SpamAssassin Causing Server Startup Failure
On Fri, 2003-01-10 at 04:30, Dale W Hodge wrote: Hum... A similar thing happened to me today. The load got so high it brought my system to it's knees. I ended up forcing a reboot to fix it. I reset the config with -L (perform local tests only) -m10 (limit children to max of 10) -S (Stop check as soon as spam threshold is reached to improve performance). So far the load has dropped to near normal levels. I'm thinking the root problem is a network connectivity problem. I know it normally does some lookups and tries to connect to several spam databases. I've been having some network issues, so I suspect that's the problem here. Now this is funny - I had apparently exactly the same problem today, with up to now running sa 2.43 without any problems. I think it was a razor problem in my case, causing sa to eat all memory (which lead to a whole lot of processes being killed on the server - thank god ssh was not one of these) -- vbi -- featured product: vim - http://vim.org signature.asc Description: This is a digitally signed message part
Re: SpamAssassin Causing Server Startup Failure
Hi, server I can try this in. Unfortunately, I don't quite know how to force a Debian server to stay in runlevel 1 during the boot process. I cannot really help you with your Spamassissin problems but if you do not want to process any startup scripts at all then from lilo use : linux init=/bin/sh Then you will get a shell with / mounted read only. To make changes do : mount -o remount / You do not have to include the rw flags, for me it seems to mount it rw by merely specifying the remount option. When you are finished do : mount -o remount,ro / and unmount any other filesystems you may have mounted. Then reboot. I don't know how proper this method is but it stops Debian from going to runlevel 2 first (which it seems to do) and also does not bring up any network interfaces. Cheers, Fred. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SpamAssassin Causing Server Startup Failure
On Fri, 2003-01-10 at 12:58, Fred Clausen wrote: Hi, server I can try this in. Unfortunately, I don't quite know how to force a Debian server to stay in runlevel 1 during the boot process. I cannot really help you with your Spamassissin problems but if you do not want to process any startup scripts at all then from lilo use : linux init=/bin/sh For some, this is near impossible - I'm in Zurich, my server is in Bern... cheers -- vbi -- featured link: http://fortytwo.ch/gpg/subkeys signature.asc Description: This is a digitally signed message part
Re: SpamAssassin Causing Server Startup Failure
On Friday 10 January 2003 10:11 am, Adrian 'Dagurashibanipal' von Bidder wrote: On Fri, 2003-01-10 at 12:58, Fred Clausen wrote: Hi, server I can try this in. Unfortunately, I don't quite know how to force a Debian server to stay in runlevel 1 during the boot process. I cannot really help you with your Spamassissin problems but if you do not want to process any startup scripts at all then from lilo use : linux init=/bin/sh For some, this is near impossible - I'm in Zurich, my server is in Bern... Then I don't understand how you would expect staying in runlevel 1 would work at all: init 1 doesn't start up network services. A solution for you would be to create your own custom runlevel (like, say, grabbing 4), and having it startup ssh and nothing else. Then, if you are having a problem like this, you can, well, I dunno. How *do* you troubleshoot boot problems? -- Yousa steala precious from meesa! - Jar-Jaromir D.A.Bishop -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SpamAssassin Causing Server Startup Failure
- Original Message - From: David Bishop [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, January 10, 2003 6:44 PM Subject: Re: SpamAssassin Causing Server Startup Failure For some, this is near impossible - I'm in Zurich, my server is in Bern... Then I don't understand how you would expect staying in runlevel 1 would work at all: init 1 doesn't start up network services. A solution for you would be to create your own custom runlevel (like, say, grabbing 4), and having it startup ssh and nothing else. Then, if you are having a problem like this, you can, well, I dunno. How *do* you troubleshoot boot problems? What about connecting a com port with another server and using serial console? I've made very positive experience with that. For example than you could unmount an mount the root partition! So you could troubleshoot boot problems too! You only need a null modem cable and somthing like minicom on the other end. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SpamAssassin Causing Server Startup Failure
- Original Message - ... When 'initd' got to spamassassin, the server just hung and would not continue the boot process. I waited for almost five minutes but it didn't time out or continue. ... I have not yet tried to simply turn off spamd in /etc/defaults/spamassassin but have one non-critical server I can try this in. Setting ENABLE=0 in /etc/default/spamassassin does allow the boot process to finish. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: SpamAssassin Causing Server Startup Failure
non-critical server I can try this in. Unfortunately, I don't quite know how to force a Debian server to stay in runlevel 1 during the boot process. from the lilo prompt: 'linux (or whatever image name here) single' -- D.A.Bishop -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: SpamAssassin Causing Server Startup Failure
-Original Message- From: Gene Grimm [mailto:[EMAIL PROTECTED]] During the past couple of days I have noticed log entries showing that spamassassin's daemon refused connections from spamc on our two mail servers. Today, our local mail server was so bogged down I was forced to reset it. When 'initd' got to spamassassin, the server just hung and would not continue the boot process. I waited for almost five minutes but it didn't time out or continue. I was forced to mount the drive in another system without local mail services (only nullmailer) and disable the /etc/rcX.d/S19spamassassin links for spamd. Just as a precaution, I disabled spamassassin on the remote server as well. I have not yet tried to simply turn off spamd in /etc/defaults/spamassassin but have one non-critical server I can try this in. Unfortunately, I don't quite know how to force a Debian server to stay in runlevel 1 during the boot process. If anyone knows why this was happening and/or how to fix it, I would be most appreciative. Hum... A similar thing happened to me today. The load got so high it brought my system to it's knees. I ended up forcing a reboot to fix it. I reset the config with -L (perform local tests only) -m10 (limit children to max of 10) -S (Stop check as soon as spam threshold is reached to improve performance). So far the load has dropped to near normal levels. I'm thinking the root problem is a network connectivity problem. I know it normally does some lookups and tries to connect to several spam databases. I've been having some network issues, so I suspect that's the problem here. Hope this helps some. --dwh --- Dale W Hodge - [EMAIL PROTECTED] Vice Chairman Secretary - [EMAIL PROTECTED] Air Capital Linux User's Group (ACLUG) --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
