The Samba 'panic action' script, /usr/share/samba/panic-action, was called for PID 1783 (/usr/sbin/winbindd).
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: samba
Guys I receive this message occasionally when I restart my Ubuntu Server:
-------
The Samba 'panic action' script, /usr/share/
was called for PID 1783 (/usr/sbin/
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:/
[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_
#6 0x00007ffe747e5048 in rpccli_set_timeout ()
#7 0x00007ffe7467f3b1 in winbindd_
#8 0x00007ffe7467f53f in ?? ()
#9 0x00007ffe74680948 in ?? ()
#10 0x00007ffe74680ef7 in ?? ()
#11 0x00007ffe7466ab9a in ?? ()
#12 0x00007ffe7465e773 in winbindd_
#13 0x00007ffe7468b751 in winbindd_
#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.
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/DebuggingPr ogramCrash
Thanks