search for: tevent_req_poll

Displaying 7 results from an estimated 7 matches for "tevent_req_poll".

2015 Jun 16
2
winbind bug - possible overflow
...6475== by 0xA4AC8E4: writev_handler (async_sock.c:514) ==16475== by 0xB5EE30A: ??? (in /usr/lib64/libtevent.so.0.9.21) ==16475== by 0xB5EC7D6: ??? (in /usr/lib64/libtevent.so.0.9.21) ==16475== by 0xB5E8FBC: _tevent_loop_once (in /usr/lib64/libtevent.so.0.9.21) ==16475== by 0xB5EA28E: tevent_req_poll (in /usr/lib64/libtevent.so.0.9.21) ==16475== by 0x5AD310D: tevent_req_poll_ntstatus (tevent_ntstatus.c:106) ==16475== by 0x6EF09AA: dcerpc_binding_handle_call (binding_handle.c:565) ==16475== by 0x69AE98C: dcerpc_lsa_LookupSids_r (ndr_lsa_c.c:3037) ==16475== by 0x69AEC1C: dcerpc_lsa_Lo...
2016 Sep 04
2
samba crashing on start up INTERNAL ERROR: Signal 11
...t_common_loop_timer_delay+0xba) [0x7efe564f862a] #8 /usr/local/samba/lib/libsmbconf.so.0(run_events_poll+0x76) [0x7efe57ca83a9] #9 /usr/local/samba/lib/libsmbconf.so.0(+0x3b9f7) [0x7efe57ca89f7] #10 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x9d) [0x7efe564f3c1d] #11 /usr/lib64/libtevent.so.0(tevent_req_poll+0x1f) [0x7efe564f4fbf] #12 smbd(+0x75ea) [0x55e4354375ea] #13 smbd(main+0xf5a) [0x55e43543a7c5] #14 /lib64/libc.so.6(__libc_start_main+0xf0) [0x7efe56170720] #15 smbd(_start+0x29) [0x55e435435b19] smb_panic(): calling panic action [/bin/sleep 90000] BACKTRACE: 6 stack frames: #0 /usr/local/sam...
2015 Jun 16
0
winbind bug - possible overflow
...E4: writev_handler (async_sock.c:514) > ==16475== by 0xB5EE30A: ??? (in /usr/lib64/libtevent.so.0.9.21) > ==16475== by 0xB5EC7D6: ??? (in /usr/lib64/libtevent.so.0.9.21) > ==16475== by 0xB5E8FBC: _tevent_loop_once (in /usr/lib64/libtevent.so.0.9.21) > ==16475== by 0xB5EA28E: tevent_req_poll (in /usr/lib64/libtevent.so.0.9.21) > ==16475== by 0x5AD310D: tevent_req_poll_ntstatus (tevent_ntstatus.c:106) > ==16475== by 0x6EF09AA: dcerpc_binding_handle_call (binding_handle.c:565) > ==16475== by 0x69AE98C: dcerpc_lsa_LookupSids_r (ndr_lsa_c.c:3037) > ==16475== by 0x69...
2015 Jun 16
2
winbind bug - possible overflow
Hello, I'm facing a bug with winbind. If I request groups for particular domain user, winbind cache gets corrupted. My winbind version is 4.1.12-23.el7_1 (Centos 7.1, x86_64). 1) this is correct UID to SID mapping: wbinfo -U 100152 S-1-5-21-3451901064-902568176-4053310204-180212 2) I request groups info for a user: id -G -n 209459 [reply with 33 groups] 3) I request UID to SID mapping
2018 Dec 27
1
FreeBSD, Libmd5, samba 4.9.4 & "smbclient -L" (using password) -> core dump
...m /usr/local/lib/libtevent.so.0 #17 0x0000000808649f94 in tevent_common_loop_immediate () from /usr/local/lib/libtevent.so.0 #18 0x000000080864c17c in ?? () from /usr/local/lib/libtevent.so.0 #19 0x0000000808648e4e in _tevent_loop_once () from /usr/local/lib/libtevent.so.0 #20 0x000000080864ac0b in tevent_req_poll () from /usr/local/lib/libtevent.so.0 #21 0x00000008052349de in tevent_req_poll_ntstatus (req=req at entry=0x811a84080, ev=ev at entry=0x811a582e0, status=status at entry=0x7fffffffdbf4) at ../lib/util/tevent_ntstatus.c:109 #22 0x0000000801d66efd in cli_session_setup_creds (cli=<optimized ou...
2018 Nov 08
0
Crashes on File Access - Post Solaris Patching
...234 [0x7ffcb1fd079b8]    #11 /usr/lib/samba/private/ sparcv9/libtevent.so.0.9.36' port_event_loop_once+0x374 [0x7ffcb2000d430]    #12 /usr/lib/samba/private/ sparcv9/libtevent.so.0.9.36'_ tevent_loop_once+0xa0 [0x7ffcb200071f8]    #13 /usr/lib/samba/private/ sparcv9/libtevent.so.0.9.36' tevent_req_poll+0x20 [0x7ffcb20008c80]    #14 /usr/lib/samba/sbin/smbd'main+ 0x1404 [0x7ffcb28813378]    #15 /usr/lib/samba/sbin/smbd'_ start+0x64 [0x7ffcb2880b5c4] [2018/11/08 10:12:08.821377,  0] ../source3/lib/dumpcore.c:315( dump_core)   dumping core in /var/samba/log/cores/smbd [2018/11/08 10:12:12.40...
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