On 26 September 2012 18:15, Caleb O'Connell <ca...@privacyassociation.org> wrote: > Thanks for that info. I'll see if I can get some info to send along to the > developers. Whats the best place to send that info?
Well, the Samba4 HOWTO still says the samba-technical list, so I suppose there :) > Michael Wood wrote: > >> Hi >> >> On 26 September 2012 17:18, Caleb O'Connell >> <ca...@privacyassociation.org> wrote: >>> I have no idea why, occasionally one of my samba4 servers won't respond >>> to my RSAT tools on windows 7. I check the server and when I do a ps >>> -aux I see many lines just like the following: >>> >>> >>> root 28073 0.0 0.0 2132 52 ? S 00:11 0:00 >>> /bin/sleep 999999999 >> [...] >> >> This indicates that Samba has crashed and has called "sleep 999999999" >> as the panic action. >> >> This is to allow you to attach a debugger to the parent process and >> get a stack trace (assuming you compiled with ./configure.developer). >> >> You should be able to do something like this: >> >> Use "ps axl" to get the parent process ID (PPID) of one of the sleep >> processes. (e.g. 12345) >> >> Then: >> >> # gdb /usr/local/samba/sbin/samba >> (gdb) attach 12345 >> (gdb) bt full >> >> That might tell the Samba developers what caused the crash. >> >>> I usually just reboot that server and it's all good again. >>> >>> I'm using samba4 beta6 I believe on this machine. >> >> Run /usr/local/samba/sbin/samba --version to get the exact version. -- Michael Wood <esiot...@gmail.com> -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba