Greetings-
I have sort of fallen out of the loop with major milestones in the Samba
project... I was really up on Samba back in the 3.0.x days.
Used to be, a Samba PDC would only run smbd and nmbd tasks. Now I see winbindd
tasks as well. I peeked in its log and it does not seem too happy.
[2010/08/18 09:20:14, 0] winbindd/winbindd.c:1252(main)
winbindd version 3.4.7 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2010/08/18 09:20:14, 0]
winbindd/winbindd_cache.c:2578(initialize_winbindd_cache)
initialize_winbindd_cache: clearing cache and re-creating with version number
1
[2010/08/18 09:20:59, 1] lib/util_tdb.c:521(tdb_wrap_log)
tdb(/var/run/samba/mutex.tdb): tdb_lock failed on list 127 ltype=1
(Interrupted system call)
[2010/08/18 09:20:59, 0] lib/util_tdb.c:69(tdb_chainlock_with_timeout_internal)
tdb_chainlock_with_timeout_internal: alarm (40) timed out for key LDSLNX01 in
tdb /var/run/samba/mutex.tdb
[2010/08/18 09:20:59, 1] lib/server_mutex.c:71(grab_named_mutex)
Could not get the lock for LDSLNX01
[2010/08/18 09:20:59, 0] winbindd/winbindd_cm.c:782(cm_prepare_connection)
cm_prepare_connection: mutex grab failed for LDSLNX01
[2010/08/18 09:22:02, 0] libsmb/namequery.c:75(saf_store)
saf_store: refusing to store 0 length domain or servername!
[2010/08/18 09:22:02, 1] winbindd/winbindd_cm.c:977(cm_prepare_connection)
failed tcon_X with NT_STATUS_END_OF_FILE
[2010/08/18 09:23:04, 0] libsmb/namequery.c:75(saf_store)
saf_store: refusing to store 0 length domain or servername!
[2010/08/18 09:23:04, 1] winbindd/winbindd_cm.c:977(cm_prepare_connection)
failed tcon_X with NT_STATUS_END_OF_FILE
[2010/08/18 09:24:14, 1] lib/util_tdb.c:521(tdb_wrap_log)
tdb(/var/run/samba/mutex.tdb): tdb_lock failed on list 127 ltype=1
(Interrupted system call)
[2010/08/18 09:24:14, 0] lib/util_tdb.c:69(tdb_chainlock_with_timeout_internal)
tdb_chainlock_with_timeout_internal: alarm (40) timed out for key LDSLNX01 in
tdb /var/run/samba/mutex.tdb
[2010/08/18 09:24:14, 1] lib/server_mutex.c:71(grab_named_mutex)
Could not get the lock for LDSLNX01
[2010/08/18 09:24:14, 0] winbindd/winbindd_cm.c:782(cm_prepare_connection)
cm_prepare_connection: mutex grab failed for LDSLNX01
[2010/08/18 09:24:57, 1] lib/util_tdb.c:521(tdb_wrap_log)
tdb(/var/run/samba/mutex.tdb): tdb_lock failed on list 127 ltype=1
(Interrupted system call)
[2010/08/18 09:24:57, 0] lib/util_tdb.c:69(tdb_chainlock_with_timeout_internal)
tdb_chainlock_with_timeout_internal: alarm (40) timed out for key LDSLNX01 in
tdb /var/run/samba/mutex.tdb
[2010/08/18 09:24:57, 1] lib/server_mutex.c:71(grab_named_mutex)
Could not get the lock for LDSLNX01
[2010/08/18 09:24:57, 0] winbindd/winbindd_cm.c:782(cm_prepare_connection)
cm_prepare_connection: mutex grab failed for LDSLNX01
[2010/08/18 09:25:47, 0] libsmb/namequery.c:75(saf_store)
saf_store: refusing to store 0 length domain or servername!
[2010/08/18 09:25:47, 1]
rpc_client/cli_pipe.c:949(cli_pipe_validate_current_pdu)
cli_pipe_validate_current_pdu: RPC fault code DCERPC_FAULT_OP_RNG_ERROR
received from host LDSLNX01!
[2010/08/18 09:25:47, 0]
winbindd/winbindd_dual.c:186(async_request_timeout_handler)
async_request_timeout_handler: child pid 1166 is not responding. Closing
connection to it.
[2010/08/18 09:25:47, 1] winbindd/winbindd_util.c:303(trustdom_recv)
Could not receive trustdoms
Specifically:
Could not get the lock for LDSLNX01
failed tcon_X with NT_STATUS_END_OF_FILE
Could not receive trustdoms
Is this normal? Does this mean that by upgrading all the way from Samba 3.0.14a
on Debian to 3.3.2 on Ubuntu 9.04, and now with the jump to 3.4.7 on Ubuntu
10.04, is there some setup steps that never
got done?
Our environment is Samba PDC with a mix of Linux and Window workstations. No
Windows servers, no AD, etc...
TIA!
Sincerely,
--
Michael Lueck
Lueck Data Systems
http://www.lueckdatasystems.com/