Date: Thu, 25 Jul 2002 23:25:57 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: mbettinger@championelevators.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Samba Server rebooting --Long Message-ID: <20020725222557.GC20670@happy-idiot-talk.infracaninophi> In-Reply-To: <200207251541.38671.matt@championelevators.com> References: <200207251541.38671.matt@championelevators.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 25, 2002 at 03:41:36PM -0500, Matthew Bettinger wrote: > I am having a rather serious problem here at work with a Samba > server that is rebooting. I can't find any rhyme or reason to this > machine going down. Maybe someone can help. Here is the > information on the server. Ouch. 300 concurrent Samba users on a 450MHz K6-2 with 128Mb ram. I'm thinking you're running into some sort of resource starvation problem here. First of all, this is not a good idea: > makeoptions COPTFLAGS=3D"-O2 -pipe" The maximum recommended optimisation level for compiling the kernel is '-O': anything higher is known to produce incorrect code. Start by recompiling the kernel with COPTFLAGS=3D"-O -pipe", and see if the problem persists. If it does, you need to monitor the system to see if it is running out of resources. Can you correlate crashing with peaks of activity from your users? Can you see if you're running out of mbufs (ie netstat -m) as usage ramps up? Try running top(1) and watch the CPU, swap and memory usage over time. Similarly run 'systat -vm' for a summary of all system activity. This may give you some hints about where your system is running out of steam, and how to tune it to cope better. If it does appear to be a Kernel bug, you should set up your system to produce kernel crash dumps. Read Section 16.1 of the Developers handbook and follow the instructions therein --- http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kernel= debug.html (ie. compile a kernel with debug symbols, set up a dump area by setting the 'dumpdev' and 'dumpdir' commands in /etc/rc.conf --- nb. both of those should point to areas larger than your system RAM in order to get any meaningful results.) If you can then generate a traceback using gdb and post it to freebsd-stable@freebsd.org and/or send-pr(1) you should find some of the kernel developers willing to help you out. Good hunting, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way Tel: +44 1628 476614 Marlow Fax: +44 0870 0522645 Bucks., SL7 1TH UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020725222557.GC20670>