samba client freezes

zentralmaschine · 02-06-2007, 11:30 AM

Hi,

We have serious problems with samba on our system and it seems like samba is the cause.

After the freeze, the only thing one can do is to reboot the machine via recovery console.

The setup (wich was not my idea) is as follows:

Client: Suse 9.3:
Server: Suse 9.3: only purpose: Samba-Server

The Client mounts shares consisting of directories full of images. The Client then serves these images trough apache to the web.

Examining /var/log/messages on the CLIENT machine

The log is shattered with:

Code:

kernel: smb_add_request: request [ffff810061ef16c0, mid=1581] timed out!

And directly before the freeze I could see:

Code:

kernel: smbiod_handle_request: smbiod got a request ... and we don't implement oplocks!
kernel: smb_receive_header: long packet: 65636

although the output directly before the freeze varied the last times, it always had something to do with samba.

Examining /var/log/messages on the SERVER machine

Code:

smbd[10623]:   read_socket_data: recv failure for 4. Error = Connection reset by peer

which happens at the same time when smb_add_request time outs take place on the client machine.

Has anybody experienced similar problems? Can anybody see the cause for these freezes.
Does anybody know about performance problems with a webserver accessing files on samba shares?

If you need any more info on the system or more log output, I can provide that.

Thanks in advance!
Niels Hoffmann

jason_dustrose · 02-08-2007, 01:38 AM

First, I would like to have a look at your smb.conf, if you are able to post it.

I like how you are serving these files, that's how we're doing our intranet at the office, and it works pretty well. Of course we have had problems similar to this one, and we discovered that the NIC in the machine kept going in and out, and I've also seen cables be the cause of similar problems (we've got our fare share of issues if you couldn't tell).

I will probably be of more help once I see your smb.conf

zentralmaschine · 02-09-2007, 07:24 AM

Hi Jason,

First of all, thanks for the reply

smb.conf:

Code:

[global]
        workgroup = XYZ
        username map = /etc/samba/smbusers
        map to guest = Bad User
        include = /etc/samba/dhcp.conf
        logon path = \\%L\profiles\.msprofile
        logon home = \\%L\%U\.9xprofile
        logon drive = P:
        add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
        domain logons = No
        domain master = No
        passdb backend = smbpasswd
        security = user

        # this is something i found as a possible problem-solver
        # but does not seem to mak eanything better
        use sendfile = no
        large readwrite = no
        max xmit = 16644

[large]
        comment = 
        inherit acls = No
        path = /srv/images/large
        read only = No

there are four more shares, but with the same options.

Sadly, we don't have control over NIC and cables because the server is a rented one, without physical access.

Regards,
Niels Hoffmann

jason_dustrose · 02-12-2007, 08:54 PM

Code:

        # this is something i found as a possible problem-solver
        # but does not seem to make anything better
        use sendfile = no
        large readwrite = no
        max xmit = 16644

First of all, sorry for taking so long, I've been "under the gun" as far as LQ is concerned

Well hmmm... I have to say that your smb.conf looked alright to me, except for this part above here. I work with Samba day in and day out at the office, and I can honestly say that I have no idea what this is supposed to do, and usually, if that's the case, you don't need it anyway.

Anywho... Do you have control over the software on the Samba box? If you do, I would recommend upgrading your Samba version (if needed), also update your krb libraries, and your smbfs libraries.

Wish I could be of more help at the moment

New2Linux2 · 02-15-2007, 12:22 PM

Another LQ user (xjlittle) pointed out to me that one of the serious bandwidth hogs when it comes to Samba is roaming profiles. This line

Code:

logon path = \\%L\profiles\.msprofile

is the one you want to comment out to disable roaming profiles if they are not needed. I found that my Samba server's reliability increased tenfold just by shutting off that one thing. This was after I replaced the integrated Gb NIC with a PCI Gb NIC and a new Cat5e patch cable to the switch (that helped a little, btw, but not enough).

If you're interested, the problem that I've been having (and all of the stuff xjlittle <John> has helped me with) can be found here:
samba resetting users connections to files

Hopefully, some of what I've gone through will help.