[opensuse] Samba en TW
Just updated TW with the latest packages (zypper dup ---no-rec) only to find that Samba is not working anymore, see below: systemctl start smb.service Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for details. pws1:~ # systemctl status smb.service ● smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2018-10-19 22:09:58 CEST; 6s ago Process: 8913 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=255) Process: 8912 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) Main PID: 8913 (code=exited, status=255) Oct 19 22:09:57 pws1 systemd[1]: Starting Samba SMB Daemon... Oct 19 22:09:58 pws1 smbd[8913]: [2018/10/19 22:09:58.212377, 0] ../source3/auth/auth_util.c:1382(make_new_session_info_> Oct 19 22:09:58 pws1 smbd[8913]: create_local_token failed: NT_STATUS_ACCESS_DENIED Oct 19 22:09:58 pws1 smbd[8913]: [2018/10/19 22:09:58.242258, 0] ../source3/smbd/server.c:2000(main) Oct 19 22:09:58 pws1 smbd[8913]: ERROR: failed to setup guest info. Oct 19 22:09:58 pws1 systemd[1]: smb.service: Main process exited, code=exited, status=255/n/a Oct 19 22:09:58 pws1 systemd[1]: smb.service: Failed with result 'exit-code'. Oct 19 22:09:58 pws1 systemd[1]: Failed to start Samba SMB Daemon. Same smb.conf used under Leap 15 was working correctly. One of those rare moments that TW is not so stable anymore? Regards, Frans. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Freitag, 19. Oktober 2018, 22:17:11 CEST schrieb Frans de Boer:
Just updated TW with the latest packages (zypper dup ---no-rec) only to find that Samba is not working anymore, see below:
systemctl start smb.service Job for smb.service failed because the control process exited with error code. See "systemctl status smb.service" and "journalctl -xe" for details. pws1:~ # systemctl status smb.service ● smb.service - Samba SMB Daemon Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2018-10-19 22:09:58 CEST; 6s ago Process: 8913 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=255) Process: 8912 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS) Main PID: 8913 (code=exited, status=255)
Oct 19 22:09:57 pws1 systemd[1]: Starting Samba SMB Daemon... Oct 19 22:09:58 pws1 smbd[8913]: [2018/10/19 22:09:58.212377, 0] ../source3/auth/auth_util.c:1382(make_new_session_info_> Oct 19 22:09:58 pws1 smbd[8913]: create_local_token failed: NT_STATUS_ACCESS_DENIED Oct 19 22:09:58 pws1 smbd[8913]: [2018/10/19 22:09:58.242258, 0] ../source3/smbd/server.c:2000(main) Oct 19 22:09:58 pws1 smbd[8913]: ERROR: failed to setup guest info. Oct 19 22:09:58 pws1 systemd[1]: smb.service: Main process exited, code=exited, status=255/n/a Oct 19 22:09:58 pws1 systemd[1]: smb.service: Failed with result 'exit-code'. Oct 19 22:09:58 pws1 systemd[1]: Failed to start Samba SMB Daemon.
Same smb.conf used under Leap 15 was working correctly.
One of those rare moments that TW is not so stable anymore?
Regards, Frans.
I experienced the same issue last weekend. Some online research indicated that this could be some conflict between the smb and winbind services. As I don't have much energy to spend on this (and the machine in question does not rely on winbind anyhow) my workaround was to disable the winbind service. However, this is only a workaround, so I guess it would be appreciated if you could find the time to create a bug report. /Andreas -- Time flies like an arrow. Fruit flies like a banana. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Andreas Mahel -
Frans de Boer