Summary: | samba 3.0.21b stops working - many smbd processes | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Hans-Christian Armingeon <mog.johnny> |
Component: | [OLD] Server | Assignee: | Gentoo's SAMBA Team <samba> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | CC: | vapier |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Hans-Christian Armingeon
2006-02-18 03:27:24 UTC
I don't have an amd64 system to test it, but I think it could be related to winbind (this used to be a core bug with external protocol libraries, as kerberos): try to either 1) upgrade to samba-3.0.21c 2) remove (temporarily) the winbind flag Use the quickpkg tool (portage package) to save your system binary package, so you don't have to recompile to revert the tests. Hi, thank you for your reply. What does removing the winbind flag? What is winbind for? I usually had the stable amd64 3.0.14 samba. Johnny "euse -i winbind": winbind (net-fs/samba): Enables support for the winbind auth daemon In short, the WINS protocol daemon for client network browsing: you have a server, usually a primary domain controller, that keeps the anagrafic registry of the active clients in the lan at every moment. Every system can be automatically the WINS server: maintainig it on the PDC gives the administrator more control on the net. Infact, only one daemon is authoritative: there is a (trasparent) election between the systems in the lan based on various things, such as protocols supported, os version, and so on... well, I merged samba 3.0.21c # emerge -pv samba [ebuild R ] net-fs/samba-3.0.21c +acl -async -automount +cups -doc +examples -kerberos -ldap -ldapsam -libclamav -mysql -oav +pam -postgres -python -quotas +readline (-selinux) +swat +syslog -winbind -xml -xml2 0 kB But I am having the same behaviour. revdep-rebuild didn't find any broken libs. I think, that something is broken, that samba depends on. Johnny I don't like the idea to do an "emerge --ask --buildpkg --deep --verbose samba" without inspection of the many internal details changed since 3.0.14 (hence the shift of versions to 3.0.20). This has to do with oplocks, either in the smbd daemon or the kernel: I think the backup procedure causes a timeout in the samba lock queue. So: 1) (if you can) upgrade and check the kernel configuration: the latest stable for you is gentoo-sources-2.6.15-r5 2) From "man smb.conf", I'd try to check the behaviours of these conf options: "blocking locks" "kernel oplocks": I won't touch this, I'm mentioning it just for background reference "level2 oplocks" "oplocks" "use sendfile" "write cache size": only if the zombies eat excessive memory I have similar problems on two gentoo file-servers. Both are amd64. It seems to me that smbd processes stay alive even when client has already disconnected. just updated from samba-3.0.21c-r1 to samba-3.0.22 #emerge -pv samba [ebuild R ] net-fs/samba-3.0.22 -acl -async -automount -cups -doc -examples -kerberos -ldap -ldapsam -libclamav -mysql -oav +pam -postgres -python -quotas +readline (-selinux) -swat -syslog -winbind -xml -xml2 0 kB In samba-3.0.23a the wins internals have changed. Could you try it? get back to us |