Date: Tue, 11 Dec 2001 23:08:50 +0300 From: Smirnov Konstantin <sam@rmp.ru> To: Josh Paetzel <friar_josh@webwarrior.net>, freebsd-net@freebsd.org Subject: Re[2]: Help! Server unexpectedly stops respond... Message-ID: <553702363.20011211230850@rmp.ru> In-Reply-To: <20011211111358.E397@twincat.vladsempire.net> References: <305430238.20011211185144@rmp.ru> <20011211111358.E397@twincat.vladsempire.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello Josh, Tuesday, December 11, 2001, 2:13:58 PM, you wrote: JP> This could be a lot of things, but without more info, it's hard to JP> make any judgements at all. I will ask on question, though: What is JP> MAXUSERS set to in your kernel? Of course, I've should mention it in previous letter. Yes, I know that FreeBSD has a very low default MAXUSERS value (32, in 4.1.1.) So (3 months ago) I increased it to 256 ;). But it was not a reason Firstly I deduced that problems happen because of I've rebuilt kernel (1st of November). But when I built a "almost-generic" kernel (it means GENERIC config-file with 2 CPUs support and ipfw enabled), subject remains... Some backround: We use IBM NetFinity 3500 (without RAID-controller), 2xPIII 700, 512 Mb, 20GB SCSI (of which 1028MB is swap), Intel Pro 10/100B/100+ Ethernet OS: FreeBSD 4.1.1 ;) Installed services: Apache-1.3.20 with php-4.0.6, MySQL-3.23.45, BIND-9.1.3, Postfix, Qpopper-4.0, latest thttpd. 2 days ago I put into crontab a shell script that appends top+netstat shot to text file, so it's possible to see server status by the last minute before crash. But I saw nothing. Really nothing! Maybe, server can't fork any more, or something like that?? Maybe it would be more informative to post to you any config files? Thank you for help, John. Best regards, Samius -------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?553702363.20011211230850>