The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 1783 (/usr/sbin/winbindd).

[Theodotos Andreou]

Binary package hint: samba

Guys I receive this message occasionally when I restart my Ubuntu Server:

-----------------------
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 1783 (/usr/sbin/winbindd).

This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred. The Samba log
files may contain additional information about the problem.

If the problem persists, you are encouraged to first install the
samba-dbg package, which contains the debugging symbols for the Samba
binaries. Then submit the provided information as a bug report to
Ubuntu by visiting this link:
https://launchpad.net/ubuntu/+source/samba/+filebug

[Thread debugging using libthread_db enabled]
0x00007ffe722c9f7e in waitpid () from /lib/libc.so.6
#0 0x00007ffe722c9f7e in waitpid () from /lib/libc.so.6
#1 0x00007ffe722617e9 in ?? () from /lib/libc.so.6
#2 0x00007ffe7470a264 in smb_panic ()
#3 0x00007ffe746f984d in ?? ()
#4 <signal handler called>
#5 0x00007ffe747ec204 in rpc_pipe_np_smb_conn ()
#6 0x00007ffe747e5048 in rpccli_set_timeout ()
#7 0x00007ffe7467f3b1 in winbindd_lookup_names ()
#8 0x00007ffe7467f53f in ?? ()
#9 0x00007ffe74680948 in ?? ()
#10 0x00007ffe74680ef7 in ?? ()
#11 0x00007ffe7466ab9a in ?? ()
#12 0x00007ffe7465e773 in winbindd_lookup_sid_by_name ()
#13 0x00007ffe7468b751 in winbindd_dual_lookupname ()
#14 0x00007ffe746891e8 in ?? ()
#15 0x00007ffe746896cf in ?? ()
#16 0x00007ffe74656ba0 in main ()
A debugging session is active.

 Inferior 1 [process 1783] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]
-----------------------

This is 64 bit Ubuntu Server 10.04.02 LTS that runs as a guest on VMWare VShere. No VMWare Tools installed.

Any idea what this message is all about? Should I worry? Everything seems to work fine after I receive it. Let me know if you need any further information.

[James Page (james-page)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Please could you install the samba-dbg package and try to capture a full backtrace; this should help capture more information next time this issue occurs.

You can find for information on how todo this here: https://wiki.ubuntu.com/DebuggingProgramCrash

Thanks

[Theodotos Andreou (theodotos)]

Do I need to create a winbind-dbg using the procedure describing in the above link? It looks like samba-dbg has some files relevant to winbind:

# dpkg -L samba-dbg | grep -i winbind
/usr/lib/debug/lib/libnss_winbind.so.2
/usr/lib/debug/lib/security/pam_winbind.so
/usr/lib/debug/usr/sbin/winbindd

The debug report is longer now:

-------
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 1653 (/usr/sbin/winbindd).

This means there was a problem with the program, such as a segfault.
Below is a backtrace for this process generated with gdb, which shows
the state of the program at the time the error occurred. The Samba log
files may contain additional information about the problem.

If the problem persists, you are encouraged to first install the
samba-dbg package, which contains the debugging symbols for the Samba
binaries. Then submit the provided information as a bug report to
Ubuntu by visiting this link:
https://launchpad.net/ubuntu/+source/samba/+filebug

[Thread debugging using libthread_db enabled]
0x00007f90352c7f7e in waitpid () from /lib/libc.so.6
#0 0x00007f90352c7f7e in waitpid () from /lib/libc.so.6
#1 0x00007f903525f7e9 in ?? () from /lib/libc.so.6
#2 0x00007f9037708264 in smb_panic (why=<value optimized out>)
    at lib/util.c:1486
#3 0x00007f90376f784d in fault_report (sig=11) at lib/fault.c:52
#4 sig_fault (sig=11) at lib/fault.c:75
#5 <signal handler called>
#6 rpc_pipe_np_smb_conn (p=0x0) at rpc_client/rpc_transport_np.c:402
#7 0x00007f90377e3048 in rpccli_set_timeout (rpc_cli=0x0, timeout=35000)
    at rpc_client/cli_pipe.c:2956
#8 0x00007f903767d3b1 in winbindd_lookup_names (mem_ctx=0x7f903802fce0,
    domain=<value optimized out>, num_names=<value optimized out>,
    names=<value optimized out>, domains=0x0, sids=0x7fff54ac6918,
    types=0x7fff54ac6910) at winbindd/winbindd_rpc.c:1287
#9 0x00007f903767d53f in msrpc_name_to_sid (domain=0x7f9038084af0,
    mem_ctx=0x7f903802fce0, original_cmd=<value optimized out>,
    domain_name=0x7fff54ac6f28 "LIM", name=<value optimized out>,
    sid=0x7fff54ac6b70, type=0x7fff54ac6bbc) at winbindd/winbindd_rpc.c:311
#10 0x00007f903767e948 in name_to_sid (domain=0x0, mem_ctx=0x88b8,
    orig_cmd=WINBINDD_INTERFACE_VERSION,
    domain_name=0x7fff54ac6908 "\200\264\005\070\220\177", name=0x0,
    sid=0x7fff54ac6918, type=0x7fff54ac6bbc)
    at winbindd/winbindd_reconnect.c:94
#11 0x00007f903767eef7 in name_to_sid (domain=0x0, mem_ctx=0x88b8,
    orig_cmd=WINBINDD_INTERFACE_VERSION,
    domain_name=0x7fff54ac6908 "\200\264\005\070\220\177", name=0x0,
    sid=0x7fff54ac6918, type=0x7fff54ac6bbc) at winbindd/winbindd_ads.c:413
#12 0x00007f9037668b9a in name_to_sid (domain=0x7f9038084af0,
    mem_ctx=<value optimized out>, orig_cmd=<value optimized out>,
    domain_name=0x7fff54ac6f28 "LIM", name=0x7fff54ac7028 "theodotos.andreou",
    sid=0x7fff54ac6b70, type=0x7fff54ac6bbc) at winbindd/winbindd_cache.c:1655
#13 0x00007f903765c773 in winbindd_lookup_sid_by_name (mem_ctx=0x0,
    orig_cmd=<value optimized out>, domain=0x0,
    domain_name=0x7fff54ac6908 "\200\264\005\070\220\177", name=0x0,
    sid=0x7fff54ac6918, type=0x7fff54ac6...

[gmoore777 (guy-moore)]

FYI:
I have reported this exact same backtrace (at least the last 3 calls) here
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/667269?comments=all

for us, winbind is dead, black screen on Console, no longer can ssh into machine using
Active Directory credentials.
I must kill any winbind processes running, then restart it.
It's happening more frequently, (hourly) on 25% or more of our 80
64-bit LucidLinux machines, integrated with ActiveDirectory(winbind).

I am desperate to get this bug fixed.

[James Page (james-page)]

Thanks for the updated backtrace.

This looks very similar to bug 736757.

Please could you try out the version of samba in lucid proposed (see bug 736757 for more details on how todo this); this update might resolve your issue.

Thanks

[Theodotos Andreou (theodotos)]

After I updated to the lucid-proposed version the problem is resolved. I restarted the daemons several times and I didn't get any crashes yet. Nice work guys!

[James Page (james-page)]

Marking as duplicate of bug 736757 after feedback on lucid -proposed package indicated that issue was resolved.

[gmoore777 (guy-moore)]

It's been 36 hours, and have not got the "rpc_pipe_np_smb_conn" crash on any of the 3 machines that I installed the 2:3.4.7~dfsg-1ubuntu3.6 package.
Will still be monitoring this, and may even install it on a few more machines, today.
Any date on when this proposed version will be generally available? Thank you.