Your message dated Tue, 15 Nov 2022 11:51:29 +0300
with message-id <[email protected]>
and subject line Re: Bug#822453: samba: Samba segfaults, calling 'panic action'
script.
has caused the Debian Bug report #822453,
regarding samba: Samba segfaults, calling 'panic action' script.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
822453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822453
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba
Version: 2:4.2.10+dfsg-0+deb8u2
Severity: normal
Dear Maintainer,
* What led up to the situation?
Started occuring shortly after dist upgrade from Debian 7 to Debian 8.
* What exactly did you do (or not do) that was effective (or
ineffective)?
Installed gdb and samba-dbg as instructed by the emails generated
by samba when it segfaulted.
* What was the outcome of this action?
The following debug was generated (hopefully it's meaningful):
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
0xb7706d40 in __kernel_vsyscall ()
#0 0xb7706d40 in __kernel_vsyscall ()
#1 0xb6a0dab3 in __waitpid_nocancel () at ../sysdeps/unix/syscall-template.S:81
#2 0xb699502e in do_system (line=line@entry=0xb93b0b20
"/usr/share/samba/panic-action 1650") at ../sysdeps/posix/system.c:148
#3 0xb6995400 in __libc_system (line=line@entry=0xb93b0b20
"/usr/share/samba/panic-action 1650") at ../sysdeps/posix/system.c:184
#4 0xb76edbfb in system (line=0xb93b0b20 "/usr/share/samba/panic-action 1650")
at pt-system.c:28
#5 0xb6f85688 in smb_panic_s3 (why=0xb756f214 "smb1srv_tcon_disconnect_all
failed") at ../source3/lib/util.c:801
#6 0xb76c871b in smb_panic (why=0xb756f214 "smb1srv_tcon_disconnect_all
failed") at ../lib/util/fault.c:166
#7 0xb744b1f9 in exit_server_common (how=(unknown: 4294966784),
how@entry=SERVER_EXIT_NORMAL, reason=0x0, reason@entry=0xb7556062 "failed to
receive smb request") at ../source3/smbd/server_exit.c:243
#8 0xb744b5ee in smbd_exit_server_cleanly (explanation=0xb7556062 "failed to
receive smb request") at ../source3/smbd/server_exit.c:266
#9 0xb6f29b42 in exit_server_cleanly (reason=0xb7556062 "failed to receive smb
request") at ../source3/lib/smbd_shim.c:131
#10 0xb741791f in smbd_server_connection_read_handler (xconn=0xb93abaf0,
fd=<optimized out>) at ../source3/smbd/process.c:2522
#11 0xb6fa8170 in run_events_poll (ev=0xb93949a0, pollrtn=1, pfds=0xb93a4680,
num_pfds=5) at ../source3/lib/events.c:257
#12 0xb6fa83ca in s3_event_loop_once (ev=0xb93949a0, location=0xb75589d8
"../source3/smbd/process.c:3997") at ../source3/lib/events.c:326
#13 0xb6b083d8 in _tevent_loop_once () from
/usr/lib/i386-linux-gnu/libtevent.so.0
#14 0xb6b0858a in tevent_common_loop_wait () from
/usr/lib/i386-linux-gnu/libtevent.so.0
#15 0xb6b08611 in _tevent_loop_wait () from
/usr/lib/i386-linux-gnu/libtevent.so.0
#16 0xb7418cfd in smbd_process (ev_ctx=0xb93949a0, msg_ctx=0xb9394a20,
sock_fd=39, interactive=false) at ../source3/smbd/process.c:3997
#17 0xb7733da5 in smbd_accept_connection (ev=0xb93949a0, fde=0xb93be3e0,
flags=1, private_data=0xb93be398) at ../source3/smbd/server.c:627
#18 0xb6fa8170 in run_events_poll (ev=0xb93949a0, pollrtn=1, pfds=0xb93a4680,
num_pfds=6) at ../source3/lib/events.c:257
#19 0xb6fa83ca in s3_event_loop_once (ev=0xb93949a0, location=0xb77366a3
"../source3/smbd/server.c:985") at ../source3/lib/events.c:326
#20 0xb6b083d8 in _tevent_loop_once () from
/usr/lib/i386-linux-gnu/libtevent.so.0
#21 0xb6b0858a in tevent_common_loop_wait () from
/usr/lib/i386-linux-gnu/libtevent.so.0
#22 0xb6b08611 in _tevent_loop_wait () from
/usr/lib/i386-linux-gnu/libtevent.so.0
#23 0xb772ff53 in smbd_parent_loop (parent=<optimized out>, ev_ctx=<optimized
out>) at ../source3/smbd/server.c:985
#24 main (argc=2, argv=0xbff59a94) at ../source3/smbd/server.c:1626
A debugging session is active.
Inferior 1 [process 1650] will be detached.
Quit anyway? (y or n) [answered Y; input not from terminal]
* What outcome did you expect instead?
-- System Information:
Debian Release: 8.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.16.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages samba depends on:
ii adduser 3.113+nmu3
ii dpkg 1.17.26
ii libbsd0 0.7.0-2
ii libc6 2.19-18+deb8u4
ii libhdb9-heimdal [heimdal-hdb-api-8] 1.6~rc2+dfsg-9
ii libldb1 2:1.1.20-0+deb8u1
ii libpam-modules 1.1.8-3.1+deb8u1+b1
ii libpam-runtime 1.1.8-3.1+deb8u1
ii libpopt0 1.16-10
ii libpython2.7 2.7.9-2
ii libtalloc2 2.1.2-0+deb8u1
ii libtdb1 1.3.6-0+deb8u1
ii libtevent0 0.9.25-0+deb8u1
ii lsb-base 4.1+Debian13+nmu1
ii multiarch-support 2.19-18+deb8u4
ii procps 2:3.3.9-9
ii python 2.7.9-1
ii python-dnspython 1.12.0-1
ii python-ntdb 1.0-5
ii python-samba 2:4.2.10+dfsg-0+deb8u2
pn python2.7:any <none>
ii samba-common 2:4.2.10+dfsg-0+deb8u2
ii samba-common-bin 2:4.2.10+dfsg-0+deb8u2
ii samba-dsdb-modules 2:4.2.10+dfsg-0+deb8u2
ii samba-libs 2:4.2.10+dfsg-0+deb8u2
ii tdb-tools 1.3.6-0+deb8u1
ii update-inetd 4.43
Versions of packages samba recommends:
ii attr 1:2.4.47-2
ii logrotate 3.8.7-1+b1
ii samba-vfs-modules 2:4.2.10+dfsg-0+deb8u2
Versions of packages samba suggests:
pn bind9 <none>
pn bind9utils <none>
pn ctdb <none>
pn ldb-tools <none>
ii ntp 1:4.2.6.p5+dfsg-7+deb8u1
pn smbldap-tools <none>
pn winbind <none>
-- debconf information:
samba-common/title:
samba/run_mode: daemons
--- End Message ---
--- Begin Message ---
Version: 2:4.13.0+dfsg-1
On Sun, 24 Apr 2016 12:32:51 -0400 Jehster <[email protected]> wrote:
Version: 2:4.2.10+dfsg-0+deb8u2
Started occuring shortly after dist upgrade from Debian 7 to Debian 8.
The following debug was generated (hopefully it's meaningful):
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
0xb7706d40 in __kernel_vsyscall ()
#0 0xb7706d40 in __kernel_vsyscall ()
#1 0xb6a0dab3 in __waitpid_nocancel () at ../sysdeps/unix/syscall-template.S:81
#2 0xb699502e in do_system (line=line@entry=0xb93b0b20
"/usr/share/samba/panic-action 1650") at ../sysdeps/posix/system.c:148
#3 0xb6995400 in __libc_system (line=line@entry=0xb93b0b20
"/usr/share/samba/panic-action 1650") at ../sysdeps/posix/system.c:184
#4 0xb76edbfb in system (line=0xb93b0b20 "/usr/share/samba/panic-action 1650")
at pt-system.c:28
#5 0xb6f85688 in smb_panic_s3 (why=0xb756f214 "smb1srv_tcon_disconnect_all
failed") at ../source3/lib/util.c:801
#6 0xb76c871b in smb_panic (why=0xb756f214 "smb1srv_tcon_disconnect_all
failed") at ../lib/util/fault.c:166
#7 0xb744b1f9 in exit_server_common (how=(unknown: 4294966784),
how@entry=SERVER_EXIT_NORMAL, reason=0x0, reason@entry=0xb7556062 "failed to receive
smb request") at ../source3/smbd/server_exit.c:243
#8 0xb744b5ee in smbd_exit_server_cleanly (explanation=0xb7556062 "failed to
receive smb request") at ../source3/smbd/server_exit.c:266
#9 0xb6f29b42 in exit_server_cleanly (reason=0xb7556062 "failed to receive smb
request") at ../source3/lib/smbd_shim.c:131
Let's close this one after 6 years of inactivity, with
an arbitrary version (from bullseye). Unfortunately it's
unrealistic to track these old stack traces after numerous
new releases and numerous fixes for various crashes.
If an issue still exist, a new trace is needed, for current
samba version.
Thanks,
/mjt
--- End Message ---
