Displaying 3 results from an estimated 3 matches for "tevent_req_finish".
2013 Apr 14
10
[samba4] crash of winbind after "ls -l /usr/local/samba/var/locks/sysvol"
Hi,
I used Samba 4.0.5 in Wheezy. Here is that I have done:
---------------------------------------------------------------
samba-tool domain provision --realm=CHEZMOI.PRIV --domain=CHEZMOI \
--server-role=dc --dns-backend=SAMBA_INTERNAL --adminpass='+toto123'
echo "nameserver 192.168.0.21" > /etc/resolv.conf
samba
ln -s /usr/local/samba/lib/libnss_winbind.so
2014 Mar 13
0
Help with Possible Bug in Samba 4.1.5 on Connection Close
...ot;time.c"
timeval_current(), line 542 in "time.c"
smbXsrv_session_close_loop(subreq = 0x2000cde8), line 243 in
"smbXsrv_session.c"
_tevent_req_notify_callback(req = 0x2000cde8, location =
"../source3/lib/msg_channel.c:234"), line 101 in "tevent_req.c"
tevent_req_finish(req = 0x2000cde8, state = TEVENT_REQ_USER_ERROR,
location = "../source3/lib/msg_channel.c:234"), line 110 in "tevent_req.c"
tevent_req_trigger(ev = 0x2000b2f8, im = 0x200c1528, private_data =
0x2000cde8), line 166 in "tevent_req.c"
tevent_common_loop_immediate(ev = 0...
2018 Dec 03
2
Samba 4.9.3 and the "10 hour problem"
Hmm…
I see that there is a patch in the bugzilla page for that bug. I guess I could try that one… :-)
I notice in the patch that there is a lot of talk about SMB2 - we use SMB3 mostly now. But perhaps there is some code sharing? Or perhaps SMB2 is used when talking to the AD servers? Or the few SMB2-talking clients causes the problem for all of the other users? When testing the “timeout” issue I