Control: tag -1 + moreinfo unreproducible
On Sat, 26 Feb 2022 09:47:04 +0900 Tomoo Nomura <[email protected]> wrote:
Package: samba
Version: 2:4.13.13+dfsg-1~deb11u3
Severity: important
File: samba-ad-dc
X-Debbugs-Cc: [email protected]
Dear Maintainer,
Samba-ad-dc always failes to run at booting time.
Hereis the status
-----------------------------------------------------------
file@root:~# systemctl status samba-ad-dc.service
● samba-ad-dc.service - Samba AD Daemon
Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Sat 2022-02-26 08:47:07 JST;
22min ago
Docs: man:samba(8)
man:samba(7)
man:smb.conf(5)
Process: 594 ExecStart=/usr/sbin/samba --foreground --no-process-group
$SAMBAOPTIONS (code=exited, status=1/FAILURE)
Main PID: 594 (code=exited, status=1/FAILURE)
Status: "samba: ready to serve connections..."
CPU: 8.923s
2月 26 08:47:01 file samba[915]: #21
/usr/lib/x86_64-linux-gnu/samba/libservice.so.0(server_service_startup+0x96)
[0x7ffa4b11bdf6]
2月 26 08:47:01 file samba[915]: #22 samba: task[kdc] pre-fork
master(+0x596e) [0x55b5019d396e]
2月 26 08:47:01 file samba[915]: #23
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7ffa4abb6d0a]
2月 26 08:47:01 file samba[915]: #24 samba: task[kdc] pre-fork
master(_start+0x2a) [0x55b5019d27ca]
2月 26 08:47:01 file samba[915]: [2022/02/26 08:47:01.974710, 0]
../../lib/util/fault.c:139(smb_panic_default)
2月 26 08:47:01 file samba[915]: smb_panic(): calling panic action
[/usr/share/samba/panic-action 915]
2月 26 08:47:07 file samba[915]: [2022/02/26 08:47:07.595386, 0]
../../lib/util/fault.c:146(smb_panic_default)
2月 26 08:47:07 file samba[915]: smb_panic(): action returned status 0
2月 26 08:47:07 file systemd[1]: samba-ad-dc.service: Failed with result
'exit-code'.
2月 26 08:47:07 file systemd[1]: samba-ad-dc.service: Consumed 8.923s CPU
time.
----------------------------------------------------------------------------
After failed, however, it can restart and work fine.
Hi!
Does this issue still occurs? Does it happen with current version of samba,
say, 4.16 from bullseye-backports?
From your bugreport it is unclear what the problem is. Might it be a startup
ordering issue, like, samba is being started before some other required
service (I dunno which one it can be) or before some filesystem is being
mounted?
It looks like the issue you faced is unique for your setup.
Thanks,
/mjt
