Re: [Samba] Runaway samba processes
Hi, Phil Chambers wrote: We have Samba 2.2.5 running on AIX 4.3.3. The server is a very heavy duty server, and has 3 main shares, which are very large. The problem is that after a few days of running, the server suddenly stops killing off newly spawned smbd processes. They do not die, even when the original smbd process is killed. They will respond to a kill -9, but killing off the main PID does not kill the runaway children. (Instead, their PPID goes to 1 ) I'm curious to see if this is in any way related to a problem we have. Are the ruaway processes using cpu or are they completely idle? We have a problem with smbd getting into a loop and consuming cpu. We do also see processes which do not get closed down, but it is just odd processes and I think they will kill with just a -TERM. This is happening on a huge server with gigabytes of real memory. It can handle thousands of these dead proocesses before slowing down - and then it's not the memory, but the huge process list. They do consume memory and CPU, however, so it may be related. What is the procedure for logging a bug with the Samba developers? Thanks, Robert -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Runaway samba processes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 16 Oct 2002, Robert Euston wrote: Hi - Thanks for the reply - Unfortunately we are running a 24 hour service, so a stop and start is not a good option for us. I'm looking at downgrading to an earlier version to see if that alleviates the problem. I think that this is looking like a bug in the samba code. Robert, Can you please retest using 2.2.6rc4 ? If this does not correct your problem, please send me more information such as client OS, version of server OS, smb.conf, etc Any specifics about your environment that might be a data point for tracking it down. cheers, jerry - Hewlett-Packard - http://www.hp.com SAMBA Team-- http://www.samba.org GnuPG Key http://www.plainjoe.org/gpg_public.asc ISBN 0-672-32269-2SAMS Teach Yourself Samba in 24 Hours 2ed I never saved anything for the swim back. Ethan Hawk in Gattaca -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://quantumlab.net/pine_privacy_guard/ iD8DBQE9rXLzIR7qMdg1EfYRAiA6AKCZdwznsZ3wpV9jM7gUOjUZwThVQQCcC/MH OTqkD+EUh1e8yW1CbfZA4UQ= =2A2O -END PGP SIGNATURE- -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Runaway samba processes
Hi, I need some help! We have Samba 2.2.5 running on AIX 4.3.3. The server is a very heavy duty server, and has 3 main shares, which are very large. The problem is that after a few days of running, the server suddenly stops killing off newly spawned smbd processes. They do not die, even when the original smbd process is killed. They will respond to a kill -9, but killing off the main PID does not kill the runaway children. (Instead, their PPID goes to 1 ) Killing off all the smbd processes with kill -9, and restarting the daemon fixes the problem. This really isn't acceptable. The only thing I can see in the log is that there is rogue machine doing connects with a bad userid/password pair. This is occuring in the log every second or so. The problem here is that we are running at a high debug level, and the log is overwritten within minutes due to this problem. At the moment I am running a test to see if I can reliably reproduce the problem by replicating the rogue login attempts on a test box. There's another test in the pipeline to save a log file large enough to record when it starts so we have more of an idea whats going on, as the logs written after the processes start running away aren't much help. Thoughts : It could be that samba isn't closing the socket properly. This fits, if the process is waiting for the socket to close, but it stays open (deadlocked condition?). Why this might be, I can only guess. I've proved that it works again on the same machine after killing off the runaways, so it does not appear to be an environment issue. It might be a problem with AIX and Samba under certain conditions. A Memory leak maybe? In any case, I would be grateful for some ideas/help. Thanks, Robert -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Runaway samba processes
On Tue, 15 Oct 2002 16:28:42 +0100 Robert Euston [EMAIL PROTECTED] wrote: Hi, I need some help! We have Samba 2.2.5 running on AIX 4.3.3. The server is a very heavy duty server, and has 3 main shares, which are very large. The problem is that after a few days of running, the server suddenly stops killing off newly spawned smbd processes. They do not die, even when the original smbd process is killed. They will respond to a kill -9, but killing off the main PID does not kill the runaway children. (Instead, their PPID goes to 1 ) Killing off all the smbd processes with kill -9, and restarting the daemon fixes the problem. This really isn't acceptable. The only thing I can see in the log is that there is rogue machine doing connects with a bad userid/password pair. This is occuring in the log every second or so. The problem here is that we are running at a high debug level, and the log is overwritten within minutes due to this problem. At the moment I am running a test to see if I can reliably reproduce the problem by replicating the rogue login attempts on a test box. There's another test in the pipeline to save a log file large enough to record when it starts so we have more of an idea whats going on, as the logs written after the processes start running away aren't much help. Thoughts : It could be that samba isn't closing the socket properly. This fits, if the process is waiting for the socket to close, but it stays open (deadlocked condition?). Why this might be, I can only guess. I've proved that it works again on the same machine after killing off the runaways, so it does not appear to be an environment issue. It might be a problem with AIX and Samba under certain conditions. A Memory leak maybe? I'm curious to see if this is in any way related to a problem we have. Are the ruaway processes using cpu or are they completely idle? We have a problem with smbd getting into a loop and consuming cpu. We do also see processes which do not get closed down, but it is just odd processes and I think they will kill with just a -TERM. Phil. --- Phil Chambers ([EMAIL PROTECTED]) University of Exeter -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
