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.
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.
I disagree. There can be many reasons why using a later version of a system or an application is not possible. Just as an example, I manage a number of UNIX servers running a range of very old OSes - Solaris 8, AIX 4 and others. I think the oldest operating system we have is a version of MPE/iX. That is part of how we make money. Apart from that, your tone seems to suggest that your mission is not to help and support, but to put somebody down and make them feel stupid; not very commendable, I think. /jan ________________________________________ From: samba-bounces at lists.samba.org [samba-bounces at lists.samba.org] on behalf of Jonathan Buzzard [jonathan at buzzard.me.uk] Sent: 06 March 2013 13:02 To: Joseph, Matthew (EXP) Cc: samba at lists.samba.org Subject: 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
On 03/06/2013 09:46 AM, Jonathan Buzzard wrote:> 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... > Actually it is helpful given the limited and insufficient information > you provided. > > The basic problem is you are looking for a magic fix that likely does > not exist because you want to keep running an OS that is many revisions > out of date and has numerous serious security holes and a whole slew of > known problems as a consequence. > > Where simply keeping your system properly patched has a good chance of > eliminating the problem, which would have known had you been reading the > release and security bulletins for RHEL5 over the last four years. > > There is simply too many NFS and Samba issues in RHEL5.3 for it to be > remotely reasonable to expect any help trying to debug a setup still > running at that level. > > Consequently a sensible course of action is to upgrade to something > recent that does not have a whole bunch of known problems and serious > security holes and if the problem still exists then come back with a > more detail explanation of your setup.Jonathan, you are not being helpful here. We all understood you really want Joseph to upgrade, and we all acknowledge that is good practice, but Joseph seem to have constraints he cannot overcome right now. So please stop hammering on this point. If you do not have anything useful to say for his current situation then just ignore this thread and carry on. Simo.
Sven Tegethoff
2013-Mar-06 15:15 UTC
[Samba] EXTERNAL: Re: SAMBA bringing NFS server to a halt
On 06.03.2013 15:46, Jonathan Buzzard wrote:> Consequently a sensible course of action is to upgrade to something > recentI think everybody got your point by now. best regards, Sven
Hey Metthew, I think you might have a chance. Did you try clearing binary data stored by samba? There's a whole bunch of stuff in tdb files in potentially more than one place (on Debian it's under /var/lib/samba). Parts are temporary data and safe to remove. Thereof cached data, connection data and I think file locking information too. Some other files contain credentials and perhaps ID mapping data you better preserve (was it secrets.tdb?). In my experience, things can become corrupted and samba fails in some way. You can always backup that stuff and try after 6 PM. Andreas On 06.03.13 12:33, 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. > > 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.-- Andreas Gaiser Berlin