Re: [Samba] EXTERNAL: Re: SAMBA bringing NFS server to a halt
Hey Simo, I modified the entries you listed below and started running a few instances of SVN on the shares and it seems to be holding steady. I'm going to continue testing during the day to see how it does. Looking back on the issue I never noticed the date in which the files were accessed. The Samba clients would be done with a file but the server never clicked in that it should release the files. Like I said I'm going to continue the testing on this to make sure it stays consistent with the current results. Thank you very much for the suggestion. Matt -Original Message- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of Simo Sent: Wednesday, March 06, 2013 9:47 AM To: samba@lists.samba.org Subject: Re: [Samba] EXTERNAL: Re: SAMBA bringing NFS server to a halt On 03/06/2013 08:28 AM, Joseph, Matthew (EXP) wrote: > Hello JAB, > > Thank you for taking the time to respond to this in a very helpful manner... > If the SAMBA community does not care about helping someone with a "wildly out > of date server" then they should state that before letting someone join the > mailing list. Do not ascribe to the whole community the shortcomings of an individuals the volunteers 'his' opinion please. > This is a production server on a closed LAN which we don't have the option of > upgrading it to RHEL 5.9 or greater in the near future. > > So with that being said, anyone have any experience with what I am dealing > with? Unless you have 15000 servers connected the fact you have that many processes indicates a serious issue with the server or at least one of the clients. Samba creates just 1 single process per client and all its requests are served by that process. If you are seeing multiple processes it means the client is opening multiple connections. That is wrong and indicate there is probably a bug with either server processes crashing, becoming unresponsive or both, or the client misbehaving.. You may want to consider trying playing with the following parameters on your samba server: - deadtime - max connections - keepalive - reset on zero vc You may also want to prevent samba from dumping core if that is activated as it could put pressure on disks and the kernel if too many processes core all at once. HTH, Simo. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] EXTERNAL: Re: SAMBA bringing NFS server to a halt
Hello JAB, You need to understand that installing patches and upgrading servers is not a simple task when it comes to my situation. My first step is to try to figure out if it's a OS fault or if it can be fixed with modifying configurations of the OS or in this case Samba (or my configuration of Samba). You are making a lot of assumptions which is fine if that is what you choose to believe. It is a completely closed LAN with multiple layers of security so let's leave it at that. If the solution is to install patches then it is something I will look into but again that is a long process that I would prefer not to go into if it is not needed for this situation. -Original Message- From: Jonathan Buzzard [mailto:jonat...@buzzard.me.uk] Sent: Wednesday, March 06, 2013 10:12 AM To: Joseph, Matthew (EXP) Cc: samba@lists.samba.org Subject: RE: EXTERNAL: Re: [Samba] SAMBA bringing NFS server to a halt On Wed, 2013-03-06 at 08:28 -0500, Joseph, Matthew (EXP) wrote: > Hello JAB, > > Thank you for taking the time to respond to this in a very helpful > manner... If the SAMBA community does not care about helping someone > with a "wildly out of date server" then they should state that before > letting someone join the mailing list. Given you are running RHEL, you should have been over the last four years been reading the security bulletins for RHEL and responding to them appropriately. It should be apparent to any sensible person that the first step would be to check that my distribution does not have fixes for the problems that I am seeing. (hint I am 99% certain it does). > > This is a production server on a closed LAN which we don't have the > option of upgrading it to RHEL 5.9 or greater in the near future. > No lan is that closed. That you have no procedure for upgrading the OS on your server which suffers from a number of remote root security holes that require nothing more than a connection to your network is very bad practice. > So with that being said, anyone have any experience with what I am > dealing with? Read your distro release and security notes. I am 99% certain that this is a known problem that can be fixed by upgrading. JAB. -- Jonathan A. Buzzard Email: jonathan (at) buzzard.me.uk Fife, United Kingdom. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] EXTERNAL: Re: SAMBA bringing NFS server to a halt
My apologizes Simo, I did not intend with that comment to put down the Samba community as a whole I was just trying to point out a fault with a certain user. I will try fooling around with those options that you listed below and see if any of them remedy my issue. Thanks for taking the time and effort on this issue. Matt -Original Message- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of Simo Sent: Wednesday, March 06, 2013 9:47 AM To: samba@lists.samba.org Subject: Re: [Samba] EXTERNAL: Re: SAMBA bringing NFS server to a halt On 03/06/2013 08:28 AM, Joseph, Matthew (EXP) wrote: > Hello JAB, > > Thank you for taking the time to respond to this in a very helpful manner... > If the SAMBA community does not care about helping someone with a "wildly out > of date server" then they should state that before letting someone join the > mailing list. Do not ascribe to the whole community the shortcomings of an individuals the volunteers 'his' opinion please. > This is a production server on a closed LAN which we don't have the option of > upgrading it to RHEL 5.9 or greater in the near future. > > So with that being said, anyone have any experience with what I am dealing > with? Unless you have 15000 servers connected the fact you have that many processes indicates a serious issue with the server or at least one of the clients. Samba creates just 1 single process per client and all its requests are served by that process. If you are seeing multiple processes it means the client is opening multiple connections. That is wrong and indicate there is probably a bug with either server processes crashing, becoming unresponsive or both, or the client misbehaving.. You may want to consider trying playing with the following parameters on your samba server: - deadtime - max connections - keepalive - reset on zero vc You may also want to prevent samba from dumping core if that is activated as it could put pressure on disks and the kernel if too many processes core all at once. HTH, Simo. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] EXTERNAL: Re: SAMBA bringing NFS server to a halt
Hello JAB, Thank you for taking the time to respond to this in a very helpful manner... If the SAMBA community does not care about helping someone with a "wildly out of date server" then they should state that before letting someone join the mailing list. This is a production server on a closed LAN which we don't have the option of upgrading it to RHEL 5.9 or greater in the near future. So with that being said, anyone have any experience with what I am dealing with? Thanks -Original Message- From: Jonathan Buzzard [mailto:jonat...@buzzard.me.uk] Sent: Wednesday, March 06, 2013 9:03 AM To: Joseph, Matthew (EXP) Cc: samba@lists.samba.org Subject: EXTERNAL: Re: [Samba] SAMBA bringing NFS server to a halt On Wed, 2013-03-06 at 06:33 -0500, Joseph, Matthew (EXP) wrote: > Hello, > > We have a Red Hat 5.3 SAMBA 3.0.33-3.7 Server that shares a few directories > to 4 other servers. > The other servers are Red Hat 5.3 and one Solaris 10 server. > Stop right there. Nobody here could care less about someone running a wildly out of date server. There are numerous NFS and Samba fixes in RHEL 5.9 over 5.3 some of which are critical bugs, performance issues and others are ones that make your box open to remote root compromises. Upgrade to RHEL 5.9 and get back if you still have a problem. JAB. -- Jonathan A. Buzzard Email: jonathan (at) buzzard.me.uk Fife, United Kingdom. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] SAMBA bringing NFS server to a halt
Hello, We have a Red Hat 5.3 SAMBA 3.0.33-3.7 Server that shares a few directories to 4 other servers. The other servers are Red Hat 5.3 and one Solaris 10 server. I configured SAMBA to do the following for each share; Force User: User1 Force Group: Group1 Create Mask: 02770 Security Mask: 02770 Directory Mask: 02770 Directory Security Mask: 02770 Inherit Permissions: Yes Inherit ACLS: Yes Inherit Owner: Yes Guest Okay: Yes When the other servers mount the SAMBA shares they work fine until someone starts using SVN or Eclipse. This brings the SAMBA server to basically a halt. Looking at the processes I see about 15000 instances of SMB running. I try running top to see a list of processes but it takes about 10 minutes for it to start and then it will hang when it tries to do its first refresh. Looking at the logs I don't see anything that really stands out on why it is slowing down. Is there something I'm doing wrong in this configuration? Thanks. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] SAMBA Slow down on clients?
Hello, I have a Red Hat 5.3 NFS server that I started using Samba version 3.0.33-3.7 on it for network file sharing. I use to use the basic file sharing with no issues other than permissions so I wanted to use Samba for easy permission management. This server is sharing 4 different mount points. I switched over my 4 clients to mount the Samba mount points. After I did this one server (which runs svn) started to slow down to a near halt (ps -ef would take 5+ minutes to print). The other 3 servers are running a bit slower but nothing compared to the other server. I ran top and the system resources are fine. The NFS server is also having no issues at all. I reverted back to the original way I was sharing files and now everything is working fine again. Has anyone had any issues with Samba like this? Any suggestions? Thanks. Matt -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
