Your message dated Mon, 14 Nov 2022 16:22:02 +0300 with message-id <[email protected]> and subject line Re: Bug#932716: samba: smbd gets killed by systemd on magic script invocation has caused the Debian Bug report #932716, regarding samba: smbd gets killed by systemd on magic script invocation 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.) -- 932716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932716 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: samba Version: 2:4.5.16+dfsg-1+deb9u2 Severity: normal Dear Maintainer, * What led up to the situation? Samba was configured to use a magic script and the magic script was executed. * What exactly did you do (or not do) that was effective (or ineffective)? Tried different settings in the systemd unit (Type forking, simple, notify) and ultimately started smbd manually without systemd. * What was the outcome of this action? When smbd was run manually, the magic script was executed normally and everything worked as expected. When smbd was started via systemd, systemd killed the smbd process. The log reported the following: Jun 26 14:18:19 vast01 systemd[1]: smbd.service: State 'stop-sigterm' timed out. Killing. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Killing process 30152 (smbd) with signal SIGKILL. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Killing process 12712 (smbd) with signal SIGKILL. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Killing process 13890 (smbd) with signal SIGKILL. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Killing process 30153 (smbd-notifyd) with signal SIGKILL. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Killing process 30154 (cleanupd) with signal SIGKILL. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Killing process 30156 (lpqd) with signal SIGKILL. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Main process exited, code=killed, status=9/KILL Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Unit entered failed state. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Failed with result 'timeout' * What outcome did you expect instead? smbd should not get killed by systemd. Since this is my first bug report, I may have missed something. If you need further information, please let me know. Best regards, Alex -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-9-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages samba depends on: ii adduser 3.115 ii dpkg 1.18.25 ii init-system-helpers 1.48 ii libbsd0 0.8.3-1 ii libc6 2.24-11+deb9u4 ii libldb1 2:1.1.27-1+deb9u1 ii libpam-modules 1.1.8-3.6 ii libpam-runtime 1.1.8-3.6 ii libpopt0 1.16-10+b2 ii libpython2.7 2.7.13-2+deb9u3 ii libtalloc2 2.1.8-1 ii libtdb1 1.3.11-2 ii libtevent0 0.9.31-1 ii libwbclient0 2:4.5.16+dfsg-1+deb9u2 ii lsb-base 9.20161125 ii procps 2:3.3.12-3+deb9u1 ii python 2.7.13-2 ii python-dnspython 1.15.0-1+deb9u1 ii python-samba 2:4.5.16+dfsg-1+deb9u2 ii python2.7 2.7.13-2+deb9u3 ii samba-common 2:4.5.16+dfsg-1+deb9u2 ii samba-common-bin 2:4.5.16+dfsg-1+deb9u2 ii samba-libs 2:4.5.16+dfsg-1+deb9u2 ii tdb-tools 1.3.11-2 ii update-inetd 4.44 Versions of packages samba recommends: ii attr 1:2.4.47-2+b2 ii logrotate 3.11.0-0.1 ii samba-dsdb-modules 2:4.5.16+dfsg-1+deb9u2 ii samba-vfs-modules 2:4.5.16+dfsg-1+deb9u2 Versions of packages samba suggests: pn bind9 <none> pn bind9utils <none> pn ctdb <none> pn ldb-tools <none> pn ntp | chrony <none> pn smbldap-tools <none> pn ufw <none> pn winbind <none> -- Configuration Files: /etc/init.d/samba [Errno 2] No such file or directory: '/etc/init.d/samba' /etc/init.d/smbd [Errno 2] No such file or directory: '/etc/init.d/smbd' -- no debconf information root@vast-proj01:~# cat /tmp/reportbug-samba-20190722-12176-n7ckrdjk Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Alexander Zima <[email protected]> To: Debian Bug Tracking System <[email protected]> Subject: samba: smbd gets killed by systemd on magic script invocation Message-ID: <156377966520.12176.3180636668761773776.reportbug@vast-proj01> X-Mailer: reportbug 7.1.7 Date: Mon, 22 Jul 2019 07:14:25 +0000 Package: samba Version: 2:4.5.16+dfsg-1+deb9u2 Severity: normal Dear Maintainer, * What led up to the situation? Samba was configured to use a magic script and the magic script was executed. * What exactly did you do (or not do) that was effective (or ineffective)? Tried different settings in the systemd unit (Type forking, simple, notify) and ultimately started smbd manually without systemd. * What was the outcome of this action? When smbd was run manually, the magic script was executed normally and everything worked as expected. When smbd was started via systemd, systemd killed the smbd process. The log reported the following: Jun 26 14:18:19 vast01 systemd[1]: smbd.service: State 'stop-sigterm' timed out. Killing. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Killing process 30152 (smbd) with signal SIGKILL. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Killing process 12712 (smbd) with signal SIGKILL. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Killing process 13890 (smbd) with signal SIGKILL. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Killing process 30153 (smbd-notifyd) with signal SIGKILL. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Killing process 30154 (cleanupd) with signal SIGKILL. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Killing process 30156 (lpqd) with signal SIGKILL. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Main process exited, code=killed, status=9/KILL Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Unit entered failed state. Jun 26 14:18:19 vast01 systemd[1]: smbd.service: Failed with result 'timeout' * What outcome did you expect instead? smbd should not get killed by systemd. Since this is my first bug report, I may have missed something. If you need further information, please let me know. Best regards, Alex -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-9-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages samba depends on: ii adduser 3.115 ii dpkg 1.18.25 ii init-system-helpers 1.48 ii libbsd0 0.8.3-1 ii libc6 2.24-11+deb9u4 ii libldb1 2:1.1.27-1+deb9u1 ii libpam-modules 1.1.8-3.6 ii libpam-runtime 1.1.8-3.6 ii libpopt0 1.16-10+b2 ii libpython2.7 2.7.13-2+deb9u3 ii libtalloc2 2.1.8-1 ii libtdb1 1.3.11-2 ii libtevent0 0.9.31-1 ii libwbclient0 2:4.5.16+dfsg-1+deb9u2 ii lsb-base 9.20161125 ii procps 2:3.3.12-3+deb9u1 ii python 2.7.13-2 ii python-dnspython 1.15.0-1+deb9u1 ii python-samba 2:4.5.16+dfsg-1+deb9u2 ii python2.7 2.7.13-2+deb9u3 ii samba-common 2:4.5.16+dfsg-1+deb9u2 ii samba-common-bin 2:4.5.16+dfsg-1+deb9u2 ii samba-libs 2:4.5.16+dfsg-1+deb9u2 ii tdb-tools 1.3.11-2 ii update-inetd 4.44 Versions of packages samba recommends: ii attr 1:2.4.47-2+b2 ii logrotate 3.11.0-0.1 ii samba-dsdb-modules 2:4.5.16+dfsg-1+deb9u2 ii samba-vfs-modules 2:4.5.16+dfsg-1+deb9u2 Versions of packages samba suggests: pn bind9 <none> pn bind9utils <none> pn ctdb <none> pn ldb-tools <none> pn ntp | chrony <none> pn smbldap-tools <none> pn ufw <none> pn winbind <none> -- Configuration Files: /etc/init.d/samba [Errno 2] No such file or directory: '/etc/init.d/samba' /etc/init.d/smbd [Errno 2] No such file or directory: '/etc/init.d/smbd' -- no debconf information
--- End Message ---
--- Begin Message ---This seems to be a stalled bug report. I don't know what to do with it besides closing it. If you think this is incorrect and the issue is still happening with current version of samba, please feel free to reopen this bug report or file a new one. Thank you! /mjt
--- End Message ---
