Everyone's access dies once memory is full, which doesn't take long in 64mRam/128mSwap. The samba process running away is owned by root, while the users samba processes have just quietly stopped working but still exist. The samba processes are outnumbering users in the extreme. ~13 active users this morning and 67 samba processes were running. Only two people had locked files. The extra samba processes are all owned by root. I haven't done the strace because of our charging/billing structure.
The file not found error appears every once in a while under normal conditions, but there are several in a row before the madness begins. We had experimented with a daily recycle of samba via cron in hopes of introducing stability, but this did not help. There is no pattern for when this is occuring time wise, so we never know when it will hit. It can go weeks without a problem, then 1 - 3 hits in two days. Frustrating, to say the least. "Nature and nature's laws lay hid in night: God said, 'Let Newton Be!' and all was light." - Alexander Pope "It did not last; the Devil howling 'Ho! Let Einstein Be!' restored the status quo." - John Collings Squire "God Rolled his dice, to Einstein's great dismay: 'Let Feynman Be!' and all was clear as day." - Jagdish Mehra Gordon W. Wolfe, Ph. D. VM Technical Services, The Boeing Company > ---------- > From: Daniel Jarboe > Reply To: Linux on 390 Port > Sent: Tuesday, April 27, 2004 1:09 PM > To: [EMAIL PROTECTED] > Subject: Re: Samba process runaway > > > out of control and eating up CPU, meanwhile, customers access to the > samba > > shares dies. When it happens, there appears to be waaaay too many > samba > > processes spawned, yet only one of them is going bezerk according to > > "top". > > The parent smbd forks one smbd for each connection. So each client > (including WINS servers in the domain) should get a smbd. Are there > more smbd's than that? smbstatus will show you how many connected users > there are at any time, assuming your connections.tdb file is ok. > > Everyone's access dies, or just the one that belongs to the looping > smbd? > > You might want to attach strace or ltrace or gdb to the pid that's using > all your CPU to get a handle on where it's stuck. > > > I've had level 3 samba logging turned on, but I'm not capturing > > anything that I can identify as the cause. I see some oplock > messages, > > but those come in during good & bad times. The other thing I notice > is > > there is typically a file or directory not found error in the log, > too, > > prior to the bad behavior, although I don't see how that could be a > cause. > > Which file not found? Is this same message present in good times and > bad, or only in bad? > > ~ Daniel > > > > > > > > > > ----------------------------------------------------------------------- > > This message is the property of Time Inc. or its affiliates. It may be > legally privileged and/or confidential and is intended only for the use > of the addressee(s). No addressee should forward, print, copy, or > otherwise reproduce this message in any manner that would allow it to be > viewed by any individual not originally listed as a recipient. If the > reader of this message is not the intended recipient, you are hereby > notified that any unauthorized disclosure, dissemination, distribution, > copying or the taking of any action in reliance on the information > herein is strictly prohibited. If you have received this communication > in error, please immediately notify the sender and delete this message. > Thank you. > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > > ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
