Ben Tisdall
2007-Aug-09 20:11 UTC
[Samba] Samba 3.0.25b: smbd 99% CPU utilisation with opened MS Word doc
Hi I'm trying to upgrade from Samba 3.0.23c on FC4 to 3.0.25b from Samba sources. Everything appears to function correctly until an MS word document is opened from a share - the file opens but the smbd process in question rockets to 99%+ CPU, stays there & needs kill -9'ing to stop it. This happens reliably. I have an appropriate strace & a level 7 log but can't see anything obviously wrong & would appreciate some guidance as to what to look for. In the meantime here's my testparm output - this is the same config that works fine on the previous version. Thanks! [global] workgroup = REDRESSTRUST netbios aliases = JERRY interfaces = eth0 passdb backend = ldapsam:ldap://192.168.0.3:1389 passwd program = /usr/sbin/smbldap-passwd %u passwd chat = *New*Password* %n\n*Re-enter*new*password* %n\n *Password*changed* username map = /etc/samba/users.conf log level = 1 syslog = 0 name resolve order = wins bcast hosts time server = Yes printcap name = /etc/printers.conf show add printer wizard = No add user script = /usr/sbin/smbldap-useradd -m %u delete user script = /usr/sbin/smbldap-userdel "%u" add group script = /usr/sbin/smbldap-groupadd -p "%g" delete group script = /usr/sbin/smbldap-groupdel "%g" add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g" delete user from group script = /usr/sbin/smbldap-groupmod -x "%u" "%g" set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u" add machine script = /usr/sbin/smbldap-useradd -w "%u" logon script = login.bat logon drive = P: domain logons = Yes preferred master = Yes wins support = Yes ldap admin dn = uid=admin,dc=redress,dc=org ldap delete dn = Yes ldap group suffix = ou=groups ldap idmap suffix = ou=idmap ldap machine suffix = ou=computers ldap passwd sync = Yes ldap suffix = dc=redress,dc=org ldap ssl = no ldap user suffix = ou=users hide files = /desktop.ini/ map archive = No include = /etc/samba/shares.conf [homes] comment = Home Directories valid users = %S read only = No browseable = No [printers] comment = SMB Print Spool path = /var/spool/samba guest ok = Yes printable = Yes use client driver = Yes browseable = No [netlogon] comment = Network Logon Service path = /mnt/share/netlog valid users = root, @users write list = root [itadmin] path = /mnt/share/redressdata/itadmin valid users = root, xxxxx read only = No create mask = 00 force create mode = 0660 directory mask = 00 force directory mode = 0770 [Quickbooks] comment = "FINANCE read/write" path = /mnt/share/redressdata/quickbooks valid users = root, @finance read only = No create mask = 0660 force create mode = 0660 directory mask = 0770 force directory mode = 0770 [WebForms] path = /var/www/html/_docs_ valid users = xxx,xxx,xxx read only = No create mask = 00 force create mode = 0664 -- Ben Tisdall RedCircle IT Ltd, London NW1. www.redcircleit.com ben@redcircleit.com +44 (0)20 7387 0351 +44 (0)7932 745803
Eric J. Feldhusen
2007-Aug-10 13:38 UTC
[Samba] Samba 3.0.25b: smbd 99% CPU utilisation with opened MS Word doc
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ben Tisdall wrote:> Hi I'm trying to upgrade from Samba 3.0.23c on FC4 to 3.0.25b from Samba > sources. > > Everything appears to function correctly until an MS word document is > opened from a share - the file opens but the smbd process in question > rockets to 99%+ CPU, stays there & needs kill -9'ing to stop it. This > happens reliably.We're running RHEL 4.x with the latest RHEL samba packages of 3.0.10.x.x, and we've seen something similar on a couple of servers, but it's a very rare occurrence. Would you be able to send me a document that you know triggers the problem, along with what version of MS Word you're using to open it? - -- Eric Feldhusen Network Administrator http://www.remc1.org eric@remc1.org PO Box 270 (906) 482-4520 x239 809 Hecla St (906) 482-5031 fax Hancock, MI 49930 (906) 370 6202 mobile -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGvGot7yU9EEFrWcwRAixOAJ45La8blvq6j4xQyi+9WGpnRr0UTQCeMiCl Qp0RYw/V8zD8tShCfOl7orI=rNFw -----END PGP SIGNATURE-----