smbd version 3.0.25b-0.4E.5 Our server was functioning very well for several months. Our SAN crapped out and the LUN the server was using was gone. Everything is back up except SAMBA is acting crazy. I am looking at the logs and I am getting /var/log/samba/winbindd.log winbindd: Exceeding 200 client connections, no idle connection found and ads_krb5_mk_req: krb5_get_credentials failed for e05r5s-dc02$@ENT.DS.GSA.GOV(Server not found in Kerberos database) this on is strange because I get this in the log /var/log/samba/wb-ENT.log error getting user info for sid S-1-5-21-1482476501-413027322-682003330-143384 but when I do this wbinfo -s S-1-5-21-1482476501-413027322-682003330-143394 ENT+(User Name) (edited out user name) /var/log/samba/winbindd-dc-connect.log [2008/05/29 12:12:11, 1] libsmb/clientgen.c:cli_rpc_pipe_close(387) cli_rpc_pipe_close: cli_close failed on pipe \NETLOGON, fnum 0x800b to machine s06b-fin-dc02.finance.int. Error was SUCCESS - 0 /var/log/samba/wb-FINANCE.log <=[2008/05/29 12:25:27, 0] lib/util_tdb.c:tdb_log(662) tdb(/var/cache/samba/netsamlogon_cache.tdb): tdb_rec_read bad magic 0xd9fee666 at offset=27920 If I look at ps ax I get about 20 winbind entries When we try to access the only share on the box everything seems to hang... we can't even do and ls -al Then I restart winbind and everything frees up. It seems as if winbind is hanging Anyone know whet might be going on and how to resolve it? -- Jason
Jason Greene wrote:> smbd version 3.0.25b-0.4E.5 > > Our server was functioning very well for several months. Our SAN crapped > out and the LUN the server was using was gone. Everything is back up except > SAMBA is acting crazy. > > I am looking at the logs and I am getting > > /var/log/samba/winbindd.log > winbindd: Exceeding 200 client connections, no idle connection found > and > ads_krb5_mk_req: krb5_get_credentials failed for > e05r5s-dc02$@ENT.DS.GSA.GOV(Server not found in Kerberos database) > > > > this on is strange because I get this in the log > /var/log/samba/wb-ENT.log > error getting user info for sid > S-1-5-21-1482476501-413027322-682003330-143384 > > but when I do this > > wbinfo -s S-1-5-21-1482476501-413027322-682003330-143394 > ENT+(User Name) (edited out user name) > > > /var/log/samba/winbindd-dc-connect.log > [2008/05/29 12:12:11, 1] libsmb/clientgen.c:cli_rpc_pipe_close(387) > cli_rpc_pipe_close: cli_close failed on pipe \NETLOGON, fnum 0x800b to > machine s06b-fin-dc02.finance.int. Error was SUCCESS - 0 > > /var/log/samba/wb-FINANCE.log <=> [2008/05/29 12:25:27, 0] lib/util_tdb.c:tdb_log(662) > tdb(/var/cache/samba/netsamlogon_cache.tdb): tdb_rec_read bad magic > 0xd9fee666 at offset=27920 > > > If I look at ps ax I get about 20 winbind entries > > When we try to access the only share on the box everything seems to hang... > we can't even do and ls -al > Then I restart winbind and everything frees up. > > It seems as if winbind is hanging > > Anyone know whet might be going on and how to resolve it? > > > > > >Anything interesting in 'netstat -s'? This sounds a bit like something I was seeing with a corrupted E1000 nic module... It was timing out just about every connection. Could you post a section of your logs output while this is happening?
Jason Greene wrote:> I take it back... winbind is taking 99% of the CPU again > > On Thu, May 29, 2008 at 1:34 PM, Jason Greene <jason@the-greenes.net > <mailto:jason@the-greenes.net>> wrote: > > I reinstalled Samba and that cleared up the issue. Thanks for the > response. > > Jason > >Could you provide your logs for us?