search for: writev_state

Displaying 2 results from an estimated 2 matches for "writev_state".

2019 Aug 22
3
Winbind timeouts/hangs(?)
....c:432 [2019/08/22 14:34:14.809450] [30.000098] -> TEVENT_REQ_DONE (2 0)) [struct req_write_state] ../nsswitch/wb_reqtrans.c:158 [2019/08/22 14:33:44.809353] ../nsswitch/wb_reqtrans.c:194 [2019/08/22 14:33:44.809377] [0.000024] -> TEVENT_REQ_DONE (2 0)) [struct writev_state] ../lib/async_req/async_sock.c:263 [2019/08/22 14:33:44.809353] ../lib/async_req/async_sock.c:412 [2019/08/22 14:33:44.809376] [0.000023] -> TEVENT_REQ_DONE (2 0)) [struct resp_read_state] ../nsswitch/wb_reqtrans.c:222 [2019/08/22 14:33:44.809378] ../nsswitch/wb_reqtrans.c:275 [...
2019 Aug 22
0
Winbind timeouts/hangs(?)
...4:14.809450] [30.000098] > -> TEVENT_REQ_DONE (2 0)) > ???????????? [struct req_write_state] ../nsswitch/wb_reqtrans.c:158 > [2019/08/22 14:33:44.809353] ../nsswitch/wb_reqtrans.c:194 [2019/08/22 > 14:33:44.809377] [0.000024] -> TEVENT_REQ_DONE (2 0)) > ????????????? [struct writev_state] ../lib/async_req/async_sock.c:263 > [2019/08/22 14:33:44.809353] ../lib/async_req/async_sock.c:412 > [2019/08/22 14:33:44.809376] [0.000023] -> TEVENT_REQ_DONE (2 0)) > ???????????? [struct resp_read_state] ../nsswitch/wb_reqtrans.c:222 > [2019/08/22 14:33:44.809378] ../nsswitch/...