[Samba] Re: Performance and disconnect troubles on winbind after
samba upgrade
Fabiano Felix
fabianof.martins at cetelem.com.br
Mon Jul 28 13:03:28 GMT 2008
Hello,
Somebody have any trouble like this? I'm lost because I didn't found any
report near to mine, and it's getting worse.
Any help will be appreciated.
Best regards,
Fabiano Felix
On Wed, 2008-07-23 at 11:55 -0300, Fabiano Felix wrote:
> Hello,
>
> We have a RHEL4 x64 running for 3 years, which is a samba member server
> integrated with a AD domain without any problems (we was using
> samba-3.0.10-1.4E.6).
>
> Last Saturday we performed an entire server update, applying all RHN
> available patches. Everything is running fine, except for winbind
> service which has a strange behavior: often we are receiving some errors
> at logs, and the users/groups resolution is taking a long time, which
> affects user experience.
>
> The installed version is samba-3.0.25b-1.el4_6.5, and below we have some
> of these errors:
> "
> Jul 22 11:05:10 lxnserver winbindd[18539]: [2008/07/22 11:05:10, 0]
> libsmb/clientgen.c:cli_receive_smb(111)
> Jul 22 11:05:10 lxnserver winbindd[18539]: Receiving SMB: Server
> stopped responding
> Jul 22 11:05:10 lxnserver winbindd[18539]: [2008/07/22 11:05:10, 0]
> rpc_client/cli_pipe.c:rpc_api_pipe(790)
> Jul 22 11:05:10 lxnserver winbindd[18539]: rpc_api_pipe: Remote
> machine server.mydomain.intra pipe \lsarpc fnum 0x4000returned critical
> error. Error was Call timed out: server did not respond after 10000
> milliseconds
> Jul 22 11:11:03 lxnserver winbindd[18539]: [2008/07/22 11:11:03, 0]
> libsmb/clientgen.c:cli_receive_smb(111)
> Jul 22 11:11:03 lxnserver winbindd[18539]: Receiving SMB: Server
> stopped responding
> Jul 22 11:11:03 lxnserver winbindd[18539]: [2008/07/22 11:11:03, 0]
> rpc_client/cli_pipe.c:rpc_api_pipe(790)
> Jul 22 11:11:03 lxnserver winbindd[18539]: rpc_api_pipe: Remote
> machine server.mydomain.intra pipe \lsarpc fnum 0x400areturned critical
> error. Error was Call timed out: server did not respond after 10000
> milliseconds
> Jul 22 11:12:46 lxnserver winbindd[18539]: [2008/07/22 11:12:46, 0]
> libsmb/clientgen.c:cli_receive_smb(111)
> Jul 22 11:12:46 lxnserver winbindd[18539]: Receiving SMB: Server
> stopped responding
> Jul 22 11:12:46 lxnserver winbindd[18539]: [2008/07/22 11:12:46, 0]
> rpc_client/cli_pipe.c:rpc_api_pipe(790)
> Jul 22 11:12:46 lxnserver winbindd[18539]: rpc_api_pipe: Remote
> machine server.mydomain.intra pipe \lsarpc fnum 0xc001returned critical
> error. Error was Call timed out: server did not respond after 10000
> milliseconds
> Jul 22 11:15:12 lxnserver winbindd[18539]: [2008/07/22 11:15:12, 0]
> libsmb/clientgen.c:cli_receive_smb(111)
> Jul 22 11:15:12 lxnserver winbindd[18539]: Receiving SMB: Server
> stopped responding
> Jul 22 11:15:12 lxnserver winbindd[18539]: [2008/07/22 11:15:12, 0]
> rpc_client/cli_pipe.c:rpc_api_pipe(790)
> Jul 22 11:15:12 lxnserver winbindd[18539]: rpc_api_pipe: Remote
> machine server.mydomain.intra pipe \lsarpc fnum 0x4000returned critical
> error. Error was Call timed out: server did not respond after 10000
> milliseconds
> Jul 22 11:20:11 lxnserver winbindd[18539]: [2008/07/22 11:20:11, 0]
> libsmb/clientgen.c:cli_receive_smb(111)
> Jul 22 11:20:11 lxnserver winbindd[18539]: Receiving SMB: Server
> stopped responding
> Jul 22 11:20:11 lxnserver winbindd[18539]: [2008/07/22 11:20:11, 0]
> rpc_client/cli_pipe.c:rpc_api_pipe(790)
> Jul 22 11:20:11 lxnserver winbindd[18539]: rpc_api_pipe: Remote
> machine server.mydomain.intra pipe \lsarpc fnum 0x4006returned critical
> error. Error was Call timed out: server did not respond after 10000
> milliseconds
> Jul 22 11:25:11 lxnserver winbindd[18539]: [2008/07/22 11:25:11, 0]
> libsmb/clientgen.c:cli_receive_smb(111)
> Jul 22 11:25:11 lxnserver winbindd[18539]: Receiving SMB: Server
> stopped responding
> Jul 22 11:25:11 lxnserver winbindd[18539]: [2008/07/22 11:25:11, 0]
> rpc_client/cli_pipe.c:rpc_api_pipe(790)
> Jul 22 11:25:11 lxnserver winbindd[18539]: rpc_api_pipe: Remote
> machine server.mydomain.intra pipe \lsarpc fnum 0x4002returned critical
> error. Error was Call timed out: server did not respond after 10000
> milliseconds
> "
>
> Note that it is occurring in a short time, and the server is taking
> slow. My smb.conf global session:
> "
> [global]
> username map = /etc/samba/smbusers
> map to guest = Bad User
> passdb backend = tdbsam
> printcap name = cups
> printcap cache time = 750
> cups options = raw
> printing = cups
> workgroup = MYINTERNALDOMAIN
> security = ads
> realm = myinternaldomain.local.intra
> domain logons = no
> domain master = no
> wins support = no
> time server = yes
>
> wins server = Y.Y.Y.Y Z.Z.Z.Z
>
> log level = 0
> log file = /var/log/samba/%m.log
>
> ldap admin dn =
> cn=samba-admin,ou=Admin,dc=idmap,dc=myinternal,dc=com,dc=br
> ldap idmap suffix = ou=Idmap
> ldap suffix = dc=idmap,dc=myinternal,dc=com,dc=br
> idmap backend = ldap:ldap://localhost
> idmap uid = 15000-55000
> idmap gid = 15000-55000
> template shell = /bin/bash
> winbind use default domain = yes
> template homedir = /home/%U
> winbind enum groups = yes
> winbind enum users = yes
> winbind cache time = 1800
> winbind offline logon = true
> acl compatibility = auto
> "
>
> We use Openldap as a backend for winbind IDMAPs, have someone some kind
> of trouble like this?
>
> Best regards,
>
> Fabiano Felix
More information about the samba
mailing list