Services have stopped

General Discussion
1

good night everyone, guys I need a little help, currently 2 services have stopped working, below the logs

 nmbd.service - Samba NMB Daemon
│      Loaded: loaded (/lib/systemd/system/nmbd.service; disabled; vendor
│ preset: enabled)
│      Active: failed (Result: exit-code) since Sat 2023-03-11 21:07:03 GMT; 1
│ day 14h ago
│        Docs: man:nmbd(8)
│              man:samba(7)
│              man:smb.conf(5)
│     Process: 1059 ExecStart=/usr/sbin/nmbd --foreground --no-process-group
│ $NMBDOPTIONS (code=exited, status=1/FAILURE)
│    Main PID: 1059 (code=exited, status=1/FAILURE)
│         CPU: 182ms
│
│ Mar 11 21:07:02 DietPi systemd[1]: Starting Samba NMB Daemon...
│ Mar 11 21:07:03 DietPi nmbd[1059]: invalid permissions on directory
│ '/var/log/samba/cores': has 0777 should be 0700
│ Mar 11 21:07:03 DietPi nmbd[1059]: Failed to create /var/log/samba/cores for
│ user 0 with mode 0700

 ● smbd.service - Samba SMB Daemon                                            │
│      Loaded: loaded (/lib/systemd/system/smbd.service; disabled; vendor      │
│ preset: enabled)                                                             │
│      Active: failed (Result: exit-code) since Sat 2023-03-11 21:07:03 GMT; 1 │
│ day 14h ago                                                                  │
│        Docs: man:smbd(8)                                                     │
│              man:samba(7)                                                    │
│              man:smb.conf(5)                                                 │
│    Main PID: 1063 (code=exited, status=1/FAILURE)                            │
│         CPU: 183ms                                                           │
│                                                                              │
│ Mar 11 21:07:03 DietPi systemd[1]: Starting Samba SMB Daemon...              │
│ Mar 11 21:07:03 DietPi systemd[1]: smbd.service: Main process exited,        │
│ code=exited, status=1/FAILURE                                                │
│ Mar 11 21:07:03 DietPi systemd[1]: smbd.service: Failed with result          │
│ 'exit-code'.                                                                 │
│ Mar 11 21:07:03 DietPi systemd[1]: Failed to start Samba SMB Daemon.         │
│
2

‘/var/log/samba/cores’: has 0777 should be 0700

Create that directory in /var/log/samba/cores chown it to root:root and then chmod to 700
If it is there…make sure ownership and permissions are correct

If NMBD can’t start SMBD fails also

3

You could reboot your system and check the whole log to get some more information

journalctl -u nmbd
journalctl -u smbd
4

Sorry, I understand very little, could you give me the written code so I can paste it via ssh, to create the directory with code 0700

/var/log/samba/colors

5

/var/log/samba/cores 0700

this way

6

to change

chmod 700 -R /var/log/samba/cores
reboot

to check logs as it might not fix your issue. The incorret file system permission should not have such effect. Let’s see

journalctl -u nmbd
journalctl -u smbd
7 
Journal begins at Wed 2023-03-15 20:44:31 GMT, ends at Wed 2023-03-15 20:45:35 GMT. --
Mar 15 20:44:39 DietPi systemd[1]: Starting Samba NMB Daemon...
Mar 15 20:44:40 DietPi nmbd[818]: invalid permissions on directory '/var/log/samba/cores': has 0777 should be 0700
Mar 15 20:44:40 DietPi nmbd[818]: Failed to create /var/log/samba/cores for user 0 with mode 0700
Mar 15 20:44:40 DietPi nmbd[818]: Unable to setup corepath for nmbd: File exists
Mar 15 20:44:40 DietPi systemd[1]: nmbd.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 20:44:40 DietPi systemd[1]: nmbd.service: Failed with result 'exit-code'.
Mar 15 20:44:40 DietPi systemd[1]: Failed to start Samba NMB Daemon.
Mar 15 20:45:32 DietPi systemd[1]: Starting Samba NMB Daemon...
Mar 15 20:45:32 DietPi nmbd[1890]: invalid permissions on directory '/var/log/samba/cores': has 0777 should be 0700
Mar 15 20:45:32 DietPi nmbd[1890]: Failed to create /var/log/samba/cores for user 0 with mode 0700
Mar 15 20:45:32 DietPi nmbd[1890]: Unable to setup corepath for nmbd: File exists
Mar 15 20:45:32 DietPi systemd[1]: nmbd.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 20:45:32 DietPi systemd[1]: nmbd.service: Failed with result 'exit-code'.
Mar 15 20:45:32 DietPi systemd[1]: Failed to start Samba NMB Daemon.

-- Journal begins at Wed 2023-03-15 20:44:31 GMT, ends at Wed 2023-03-15 20:45:35 GMT. --
Mar 15 20:44:40 DietPi systemd[1]: Starting Samba SMB Daemon...
Mar 15 20:44:40 DietPi systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Mar 15 20:44:40 DietPi systemd[1]: smbd.service: Failed with result 'exit-code'.
Mar 15 20:44:40 DietPi systemd[1]: Failed to start Samba SMB Daemon.
root@DietPi:~#
8

AHH my fault. There was an incorrect command above. Correct above. Please try following

chmod 700 -R /var/log/samba/cores
reboot

journalctl -u nmbd
journalctl -u smbd
9

make sure you run that chmod command as sudo

10 
root@DietPi:~# journalctl -u nmbd
-- Journal begins at Thu 2023-03-16 16:50:25 GMT, ends at Thu 2023-03-16 16:50:54 GMT. --
Mar 16 16:50:32 DietPi systemd[1]: Starting Samba NMB Daemon...
Mar 16 16:50:33 DietPi systemd[1]: nmbd.service: Main process exited, code=exited, status=1/FAILURE
Mar 16 16:50:33 DietPi systemd[1]: nmbd.service: Failed with result 'exit-code'.
Mar 16 16:50:33 DietPi systemd[1]: Failed to start Samba NMB Daemon.

root@DietPi:~# journalctl -u smbd
-- Journal begins at Thu 2023-03-16 16:50:25 GMT, ends at Thu 2023-03-16 16:50:54 GMT. --
Mar 16 16:50:33 DietPi systemd[1]: Starting Samba SMB Daemon...
Mar 16 16:50:33 DietPi systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Mar 16 16:50:33 DietPi systemd[1]: smbd.service: Failed with result 'exit-code'.
Mar 16 16:50:33 DietPi systemd[1]: Failed to start Samba SMB Daemon.
root@DietPi:~#
11

hmm it simply fails without letting us know why. Let’s start the process manually

systemctl stop nmbd.service
/usr/sbin/nmbd --foreground --no-process-group
12

I did the process, nothing changed, what’s the next step

13

you could share the output if you try to start the process manually.

14

journalctl -u nmbd
journalctl -u smbd

the output would be this same code

15

this one I’m referring to Services have stopped - #11 by Joulinar

16

I’m going to do a new dietpi installation from scratch

17

good morning, I did the dietpi from scratch, now new inactive services have appeared

 dietpi-vpn.service - VPN Client (DietPi)
│      Loaded: loaded (/etc/systemd/system/dietpi-vpn.service; disabled;
│ vendor preset: enabled)
│     Drop-In: /etc/systemd/system/dietpi-vpn.service.d
│              └─dietpi-services_edit.conf
│      Active: failed (Result: exit-code) since Mon 2023-03-20 13:49:34 GMT;
│ 2s ago
│     Process: 1810 ExecStart=/usr/sbin/openvpn --suppress-timestamps --nobind
│ --config /etc/openvpn/client.ovpn (code=exited, status=203/EXEC)
│    Main PID: 1810 (code=exited, status=203/EXEC)
│         CPU: 28ms
│
│ Mar 20 13:49:34 DietPi systemd[1]: Starting VPN Client (DietPi)...
│ Mar 20 13:49:34 DietPi systemd[1810]: dietpi-vpn.service: Failed to locate
│ executable /usr/sbin/openvpn: No such file or directory
│ Mar 20 13:49:34 DietPi systemd[1810]: dietpi-vpn.service: Failed at step
│ EXEC spawning /usr/sbin/openvpn: No such file or directory
│ Mar 20 13:49:34 DietPi systemd[1]: dietpi-vpn.service: Main process exited,
│
18

the service is inactive by default and will only become active if you configure the VPN client using dietpi-vpn