PANIC: assert failed at nsswitch/winbindd.c

[Pavel Rochnyack]

Does this interesting for anybody or not ?

PR> I have setup 3.0.20pre1 on my network (os is freebsd 5.1) joining
PR> domain on w2k3.

PR> Samba work fine, but I have repeats messages in winbindd log (log.winbindd):

PR> [2005/06/22 22:01:21, 0] nsswitch/winbindd.c:request_ok(532)
PR>   PANIC: assert failed at nsswitch/winbindd.c(532)
PR> [2005/06/22 22:01:21, 0] nsswitch/winbindd.c:setup_async_write(443)
PR>   PANIC: assert failed at nsswitch/winbindd.c(443)

PR> After some patching ( I have added output of checked variables) I have:

PR> [2005/06/22 22:04:44, 0] nsswitch/winbindd.c:request_ok(531)
PR>   state->response.result=2
PR> [2005/06/22 22:04:44, 0] nsswitch/winbindd.c:request_ok(532)
PR>   PANIC: assert failed at nsswitch/winbindd.c(532)
PR> [2005/06/22 22:04:44, 0] nsswitch/winbindd.c:setup_async_write(442)
PR>   setup_async_write: event->flags= 2
PR> [2005/06/22 22:04:44, 0] nsswitch/winbindd.c:setup_async_write(443)
PR>   PANIC: assert failed at nsswitch/winbindd.c(443)

PR> As I found in code, state->response.result expected WINBINDD_PENDING
PR> but received WINBINDD_OK and event->flags expected to be unsetted but
PR> EVENT_FD_WRITE already set before event->flags=EVENT_FD_WRITE in
PR> setup_async_write().

PR> I don`t think what it is dangerous but it could be, check it please !?





-- 
Best regards,
 Pavel                            mailto:rpv at muma.tusur.ru