Panic or segfault in Samba

[Elbarbudo]

Binary package hint: samba

I get the following message in the root mailbox :
---------------------------------------------------------------------------------------------
The Samba 'panic action' script, /usr/share/samba/panic-action,
was called for PID 25264 (/usr/sbin/smbd).

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
-------------------------------------------------------------------------------------------------
I did install samba-dbg but there is no debugging information in the message

Ubuntu Lucid Lynx (Ubuntu 10.04.1 LTS)

patrice@grosbill:~$ apt-cache policy samba
samba:
  Installé : 2:3.4.7~dfsg-1ubuntu3.2
  Candidat : 2:3.4.7~dfsg-1ubuntu3.2
 Table de version :
 *** 2:3.4.7~dfsg-1ubuntu3.2 0
        500 http://fr.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
        500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
        100 /var/lib/dpkg/status
     2:3.4.7~dfsg-1ubuntu3 0
        500 http://fr.archive.ubuntu.com/ubuntu/ lucid/main Packages
patrice@grosbill:~$ apt-cache policy samba-dbg
samba-dbg:
  Installé : 2:3.4.7~dfsg-1ubuntu3.2
  Candidat : 2:3.4.7~dfsg-1ubuntu3.2
 Table de version :
 *** 2:3.4.7~dfsg-1ubuntu3.2 0
        500 http://fr.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
        500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages
        100 /var/lib/dpkg/status
     2:3.4.7~dfsg-1ubuntu3 0
        500 http://fr.archive.ubuntu.com/ubuntu/ lucid/main Packages
patrice@grosbill:~$
---
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427.1)
NonfreeKernelModules: nvidia
Package: samba 2:3.4.7~dfsg-1ubuntu3.2
PackageArchitecture: i386
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7
SambaServerRegression: Yes
Tags: lucid
Uname: Linux 2.6.32-25-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[C de-Avillez (hggdh2)]

Thank you for opening this bug and helping make Ubuntu better. Unfortunately, there is nothing we can do until we actually know what happened.

You can try to add more data here by running ´apport-collect 657972', which will attach a series of logs to this bug.

[Elbarbudo (patricearnal)]

apport information

[Elbarbudo (patricearnal)]

apport information

[Elbarbudo (patricearnal)]

That is THE problem :
1- I just noticed a delay when connecting my Win XP PC to the samba share. (maybe , no sure)
2- the connection was OK after that

At the end of the day I checked my mailbox and found the "panic" message, with NO backtrace.

Nothing in syslog.....

What can I do now to get more info?

[muzak24h (cmatt77)]

I don't know if this log helps but I get this too. 10.04 upgraded
to 10.10 (also have 3 multiple keyring sign-ons at startup)
-----------------------------------------------------------

Date: Thu, 09 Dec 2010 19:27:56 -0500
To: root
Subject: Panic or segfault in Samba
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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

This means there was a problem with the program, such as a segfault.
However, the executable could not be found for process 2655.
It may have died unexpectedly, or you may not have permission to debug
the process.
Date: Thu, 09 Dec 2010 19:29:11 -0500
To: root
Subject: Panic or segfault in Samba
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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

This means there was a problem with the program, such as a segfault.
However, the executable could not be found for process 2666.
It may have died unexpectedly, or you may not have permission to debug
the process.
Date: Thu, 09 Dec 2010 22:30:46 -0500
To: root
Subject: Panic or segfault in Samba
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

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

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]
0x00007fcd5282fdee in waitpid () from /lib/libc.so.6
#0 0x00007fcd5282fdee in waitpid () from /lib/libc.so.6
#1 0x00007fcd527c7a79 in ?? () from /lib/libc.so.6
#2 0x00007fcd55704884 in smb_panic ()
#3 0x00007fcd556f415d in ?? ()
#4 <signal handler called>
#5 0x00007fcd52808e52 in ?? () from /lib/libc.so.6
#6 0x00007fcd556da71e in rep_strlcpy ()
#7 0x00007fcd55711284 in connections_fetch_entry ()
#8 0x00007fcd5548e666 in yield_connection ()
#9 0x00007fcd554fc496 in close_cnum ()
#10 0x00007fcd55495d1c in conn_close_all ()
#11 0x00007fcd559ffaf5 in ?? ()
#12 0x00007fcd559ffd1e in exit_server_cleanly ()
#13 0x00007fcd554f8570 in ?? ()
#14 0x00007fcd55715f1a in tevent_common_check_signal ()
#15 0x00007fcd55714094 in run_events ()
#16 0x00007fcd554fa5f0 in smbd_process ()
#17 0x00007fcd559fffbe in ?? ()
#18 0x00007fcd55714212 in run_events ()
#19 0x00007fcd557144c1 in ?? ()
#20 0x00007fcd557148a0 in _tevent_loop_once ()
#21 0x00007fcd55a00ca3 in main ()
A debugging session is active.

 Inferior 1 [process 2674] will b...

[Chuck Short (zulcss)]

Can you install the samba-dbg package and try to reproduce this?

Thanks
chuck

[DuffManOhYeah (matt-southcott)]

I am not getting this anymore. I think if I remember correctly I opened
another port but it's been a while since I looked into this problem.

On Tue, Feb 1, 2011 at 10:27 AM, Chuck Short <email address hidden>wrote:

> Can you install the samba-dbg package and try to reproduce this?
>
> Thanks
> chuck
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/657972
>
> Title:
> Panic or segfault in Samba
>

--
Matt Southcott

[Elbarbudo (patricearnal)]

Le 01/02/2011 19:27, Chuck Short a écrit :
> Can you install the samba-dbg package and try to reproduce this?
>
> Thanks
> chuck
>
Samba-dbg IS installed :
> patrice@grosbill:~$ dpkg -s samba-dbg
> Package: samba-dbg
> Status: install ok installed
> Priority: extra
> Section: debug
> Installed-Size: 129132
> Maintainer: Ubuntu Core Developers <email address hidden>
> Architecture: i386
> Source: samba
> Version: 2:3.4.7~dfsg-1ubuntu3.3
> Depends: samba (= 2:3.4.7~dfsg-1ubuntu3.3)
> Description: Samba debugging symbols
> Samba is an implementation of the SMB/CIFS protocol for Unix systems,
> providing support for cross-platform file and printer sharing with
> Microsoft Windows, OS X, and other Unix systems.
> .
> This package provides debugging information for the software in the
> Samba suite. Install it to get a better backtrace in the event of a
> crash.
> Homepage: http://www.samba.org
> Original-Maintainer: Debian Samba Maintainers
> <email address hidden>
> patrice@grosbill:~$
But I still get
> The Samba 'panic action' script, /usr/share/samba/panic-action,
> was called for PID 2972 ().
>
> This means there was a problem with the program, such as a segfault.
> However, the executable could not be found for process 2972.
> It may have died unexpectedly, or you may not have permission to debug
> the process.
And absolutely NO debug information.......
> patrice@grosbill:~$ ps -ef | fgrep 2972
> patrice 5440 5351 0 11:47 pts/0 00:00:00 fgrep --color=auto 2972
> patrice@grosbill:~$
> patrice@grosbill:~$ ps -ef | fgrep smb
> root 819 1 0 08:34 ? 00:00:00 smbd -F
> root 867 819 0 08:34 ? 00:00:00 smbd -F
> root 5304 819 0 11:37 ? 00:00:00 smbd -F
> patrice 5442 5351 0 11:48 pts/0 00:00:00 fgrep --color=auto smb
> patrice@grosbill:~$

And now? what can I search for?
What are the permissions to set in order to debug?

[Edson Manners (edson-manners)]

I have the same problem:

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

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]
0x00007fd406b8edee in waitpid () from /lib/libc.so.6
#0 0x00007fd406b8edee in waitpid () from /lib/libc.so.6
#1 0x00007fd406b26a79 in ?? () from /lib/libc.so.6
#2 0x00007fd409a639b4 in smb_panic (why=<value optimized out>) at lib/util.c:1471
#3 0x00007fd409a5328d 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 0x00007fd406b67e52 in ?? () from /lib/libc.so.6
#7 0x00007fd409a3981e in rep_strlcpy (d=0x7fff647ecd38 "", s=0x0, bufsize=256) at ../lib/replace/replace.c:69
#8 0x00007fd409a70494 in connections_fetch_entry (mem_ctx=0x0, conn=0x7fd40adb5220, name=0x0) at lib/conn_tdb.c:65
#9 0x00007fd4097ed666 in yield_connection (conn=0x7fd40adb5220, name=0x0) at smbd/connection.c:33
#10 0x00007fd40985b496 in close_cnum (conn=0x7fd40adb5220, vuid=101) at smbd/service.c:1256
#11 0x00007fd4097f4d1c in conn_close_all (sconn=<value optimized out>) at smbd/conn.c:185
#12 0x00007fd409d5ed25 in exit_server_common (how=SERVER_EXIT_NORMAL, reason=0x7fd409d89047 "failed to receive smb request") at smbd/server.c:852
#13 0x00007fd409d5ef4e in exit_server_cleanly (explanation=0x0) at smbd/server.c:931
#14 0x00007fd40985a8ab in smbd_server_connection_read_handler (ev=<value optimized out>, fde=<value optimized out>, flags=<value optimized out>, private_data=<value optimized out>) at smbd/process.c:2115
#15 smbd_server_connection_handler (ev=<value optimized out>, fde=<value optimized out>, flags=<value optimized out>, private_data=<value optimized out>) at smbd/process.c:2137
#16 0x00007fd409a73422 in run_events (ev=0x7fd40acfc430, selrtn=1, read_fds=0x7fff647ed130, write_fds=0x7fff647ed0b0) at lib/events.c:156
#17 0x00007fd4098595f0 in smbd_server_connection_loop_once () at smbd/process.c:840
#18 smbd_process () at smbd/process.c:2451
#19 0x00007fd409d5f1ee in smbd_accept_connection (ev=<value optimized out>, fde=<value optimized out>, flags=<value optimized out>, private_data=<value optimized out>) at smbd/server.c:438
#20 0x00007fd409a73422 in run_events (ev=0x7fd40acfc430, selrtn=1, read_fds=0x7fff647ed440, write_fds=0x7fff647ed3c0) at lib/events.c:156
#21 0x00007fd409a736e1 in s3_event_loop_once (ev=0x7fd40acfc430, location=<value optimized out>) at lib/events.c:219
#22 0x00007fd409a73ac0 in _tevent_loop_once (ev=0x7fd40acfc430, location=0x7fd409f65658 "smbd/server.c:726") at ../lib/tevent/tevent.c:497
#23 0x00007fd409d5fed3 in smbd_parent_loop (argc=<value optimize...

[Matthew Morgan (lytithwyn)]

I'm having this error, too. Most of mine contained a backtrace nearly identical to Edson Manners', but a few had the "executable could not be found" message. I think this might be a duplicate of https://bugs.launchpad.net/ubuntu/+source/samba/+bug/388483

This bug is definitely still around. The upstream samba bug report referenced in the above-mentioned possible duplicate hasn't had any activity since the bug was submitted.

If anyone working on this bug needs any more information at all I'd be glad to submit what I can.

Are all those 0x0 values memory addresses?

[Matthew Morgan (lytithwyn)]

Sorry, I meant to mention that I'm running Lucid Server 64-bit.

[Launchpad Janitor (janitor)]

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]

[t98907 (t98907)]

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

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]
0x00007f8ad5b79dee in waitpid () from /lib/libc.so.6
#0 0x00007f8ad5b79dee in waitpid () from /lib/libc.so.6
#1 0x00007f8ad5b11a79 in ?? () from /lib/libc.so.6
#2 0x00007f8ad8a4e9b4 in smb_panic ()
#3 0x00007f8ad8a3e28d in ?? ()
#4 <signal handler called>
#5 0x00007f8ad5bf75cf in ?? () from /lib/libc.so.6
#6 0x00007f8ad8a2481e in rep_strlcpy ()
#7 0x00007f8ad8a5b494 in connections_fetch_entry ()
#8 0x00007f8ad87d8666 in yield_connection ()
#9 0x00007f8ad8846496 in close_cnum ()
#10 0x00007f8ad87ff2fd in reply_tdis ()
#11 0x00007f8ad8844ff7 in ?? ()
#12 0x00007f8ad8845397 in ?? ()
#13 0x00007f8ad88458ed in ?? ()
#14 0x00007f8ad8a5e422 in run_events ()
#15 0x00007f8ad88445f0 in smbd_process ()
#16 0x00007f8ad8d4a1ee in ?? ()
#17 0x00007f8ad8a5e422 in run_events ()
#18 0x00007f8ad8a5e6e1 in ?? ()
#19 0x00007f8ad8a5eac0 in _tevent_loop_once ()
#20 0x00007f8ad8d4aed3 in main ()
A debugging session is active.

 Inferior 1 [process 11874] will be detached.

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

[t98907 (t98907)]

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

This means there was a problem with the program, such as a segfault.
However, the executable could not be found for process 24005.
It may have died unexpectedly, or you may not have permission to debug
the process.