Hallo, musste das Image 2.5 neu flashen, jetzt läuft Samba nicht mehr.
[global]
security = user
server string = dreambox %h
workgroup = WORKGROUP
netbios name = %h
map to guest = Bad User
[Harddisk]
comment = The hard disk drive
path = /media/hdd
read only = no
public =
guest ok = yes
root@dm900:~$ systemctl restart 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.
root@dm900:~$
=================================================================================
root@dm900:~$ systemctl status smb.service
● smb.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smb.service; enabled; vendor preset: ena
Active: failed (Result: exit-code) since Sa 2018-01-27 15:41:33 CET; 1min 3s
Process: 2622 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=1/FA
Main PID: 2622 (code=exited, status=1/FAILURE)
Jan 27 15:41:33 dm900 smbd[2622]: [2018/01/27 15:41:33.684569, 0] ../lib/param
Jan 27 15:41:33 dm900 smbd[2622]: Unknown parameter encountered: "character s
Jan 27 15:41:33 dm900 smbd[2622]: [2018/01/27 15:41:33.685225, 0] ../lib/param
Jan 27 15:41:33 dm900 smbd[2622]: Ignoring unknown parameter "character set"
Jan 27 15:41:33 dm900 smbd[2622]: [2018/01/27 15:41:33.686016, 0] ../lib/param
Jan 27 15:41:33 dm900 smbd[2622]: set_variable_helper(): value is not boolean
Jan 27 15:41:33 dm900 systemd[1]: smb.service: Main process exited, code=exited
Jan 27 15:41:33 dm900 systemd[1]: Failed to start Samba SMB Daemon.
Jan 27 15:41:33 dm900 systemd[1]: smb.service: Unit entered failed state.
Jan 27 15:41:33 dm900 systemd[1]: smb.service: Failed with result 'exit-code'.
lines 1-16/16 (END)
=================================================================================
root@dm900:~$ journalctl -xe
--
-- The start-up result is done.
Jan 27 15:44:02 dm900 systemd[1]: nn2Daemon.service: Main process exited, code=
Jan 27 15:44:02 dm900 systemd[1]: nn2Daemon.service: Unit entered failed state.
Jan 27 15:44:02 dm900 systemd[1]: nn2Daemon.service: Failed with result 'core-d
Jan 27 15:44:07 dm900 systemd[1]: nn2Daemon.service: Service hold-off time over
Jan 27 15:44:07 dm900 systemd[1]: Stopped Newnigma2 eDaemon.
-- Subject: Unit nn2Daemon.service has finished shutting down
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nn2Daemon.service has finished shutting down.
Jan 27 15:44:07 dm900 systemd[1]: Started Newnigma2 eDaemon.
-- Subject: Unit nn2Daemon.service has finished start-up
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nn2Daemon.service has finished starting up.
--
-- The start-up result is done.
Jan 27 15:44:07 dm900 systemd[1]: nn2Daemon.service: Main process exited, code=
Jan 27 15:44:07 dm900 systemd[1]: nn2Daemon.service: Unit entered failed state.
Jan 27 15:44:07 dm900 systemd[1]: nn2Daemon.service: Failed with result 'core-d
Was kann/muss ich tun ?
[global]
security = user
server string = dreambox %h
workgroup = WORKGROUP
netbios name = %h
map to guest = Bad User
[Harddisk]
comment = The hard disk drive
path = /media/hdd
read only = no
public =
guest ok = yes
root@dm900:~$ systemctl restart 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.
root@dm900:~$
=================================================================================
root@dm900:~$ systemctl status smb.service
● smb.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smb.service; enabled; vendor preset: ena
Active: failed (Result: exit-code) since Sa 2018-01-27 15:41:33 CET; 1min 3s
Process: 2622 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=1/FA
Main PID: 2622 (code=exited, status=1/FAILURE)
Jan 27 15:41:33 dm900 smbd[2622]: [2018/01/27 15:41:33.684569, 0] ../lib/param
Jan 27 15:41:33 dm900 smbd[2622]: Unknown parameter encountered: "character s
Jan 27 15:41:33 dm900 smbd[2622]: [2018/01/27 15:41:33.685225, 0] ../lib/param
Jan 27 15:41:33 dm900 smbd[2622]: Ignoring unknown parameter "character set"
Jan 27 15:41:33 dm900 smbd[2622]: [2018/01/27 15:41:33.686016, 0] ../lib/param
Jan 27 15:41:33 dm900 smbd[2622]: set_variable_helper(): value is not boolean
Jan 27 15:41:33 dm900 systemd[1]: smb.service: Main process exited, code=exited
Jan 27 15:41:33 dm900 systemd[1]: Failed to start Samba SMB Daemon.
Jan 27 15:41:33 dm900 systemd[1]: smb.service: Unit entered failed state.
Jan 27 15:41:33 dm900 systemd[1]: smb.service: Failed with result 'exit-code'.
lines 1-16/16 (END)
=================================================================================
root@dm900:~$ journalctl -xe
--
-- The start-up result is done.
Jan 27 15:44:02 dm900 systemd[1]: nn2Daemon.service: Main process exited, code=
Jan 27 15:44:02 dm900 systemd[1]: nn2Daemon.service: Unit entered failed state.
Jan 27 15:44:02 dm900 systemd[1]: nn2Daemon.service: Failed with result 'core-d
Jan 27 15:44:07 dm900 systemd[1]: nn2Daemon.service: Service hold-off time over
Jan 27 15:44:07 dm900 systemd[1]: Stopped Newnigma2 eDaemon.
-- Subject: Unit nn2Daemon.service has finished shutting down
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nn2Daemon.service has finished shutting down.
Jan 27 15:44:07 dm900 systemd[1]: Started Newnigma2 eDaemon.
-- Subject: Unit nn2Daemon.service has finished start-up
-- Defined-By: systemd
-- Support: lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nn2Daemon.service has finished starting up.
--
-- The start-up result is done.
Jan 27 15:44:07 dm900 systemd[1]: nn2Daemon.service: Main process exited, code=
Jan 27 15:44:07 dm900 systemd[1]: nn2Daemon.service: Unit entered failed state.
Jan 27 15:44:07 dm900 systemd[1]: nn2Daemon.service: Failed with result 'core-d
Was kann/muss ich tun ?