Permission issue. No perms to apply changes

Geert · 20. Februar 2022

Hello,

So yesterday I was messing around with SMB/CIFS because for some reason, I do not have access to docker files, thus no access to modifying contents in there to mod servers etc.

I've changed ownership of it to my admin user instead of 'root' and that seemed to work, I thought so. After a reboot, the perms were gone. Now I have a way bigger issue. None of my accounts have permission to change anything about my server. Is I try to apply changes, I'm met by this error:

"Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color samba 2>&1' with exit code '1': debian: ---------- ID: configure_samba_global Function: file.managed Name: /etc/samba/smb.conf Result: True Comment: File /etc/samba/smb.conf updated Started: 12:44:41.515963 Duration: 82.788 ms

Continues here: https://pastebin.com/D6GK8VjS

Extra details are:

https://pastebin.com/Dm6SfJ6B

I've been trying all day to resolve this issue but I can't seem to get anything to work.

Does anyone know how to solve this? I have some pretty valuable data on this server and I can't access any of it atm

Kind regards

Zoki · 20. Februar 2022

The messages contains this: See "systemctl status smbd.service" and "journalctl -xe"

Geert · 21. Februar 2022

Journalctl -xe

gave the following output: https://pastebin.com/nkprAqh8

Systemctl status smbd.service:

● smbd.service - Samba SMB Daemon

Loaded: loaded (/lib/systemd/system/smbd.service; disabled; vendor preset: enabled)

Active: failed (Result: exit-code) since Mon 2022-02-21 16:41:55 CET; 11min ago

Docs: man:smbd(8)

man:samba(7)

man:smb.conf(5)

Process: 7551 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS)

Process: 7579 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exited, status=1/FAILURE)

Main PID: 7579 (code=exited, status=1/FAILURE)

Feb 21 16:41:52 HomeServer systemd[1]: Starting Samba SMB Daemon...

Feb 21 16:41:55 HomeServer systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE

Feb 21 16:41:55 HomeServer systemd[1]: smbd.service: Failed with result 'exit-code'.

Feb 21 16:41:55 HomeServer systemd[1]: Failed to start Samba SMB Daemon.

Code

sudo journalctl -u smbd.service

gave me similar results,

XML: Output

Feb 21 16:28:59 HomeServer systemd[1]: Starting Samba SMB Daemon...
Feb 21 16:29:15 HomeServer systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Feb 21 16:29:15 HomeServer systemd[1]: smbd.service: Failed with result 'exit-code'.
Feb 21 16:29:15 HomeServer systemd[1]: Failed to start Samba SMB Daemon.
Feb 21 16:30:11 HomeServer systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
Feb 21 16:30:11 HomeServer systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
Feb 21 16:30:13 HomeServer systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
Feb 21 16:30:13 HomeServer systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
Feb 21 16:30:58 HomeServer systemd[1]: Starting Samba SMB Daemon...
Feb 21 16:30:58 HomeServer systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Feb 21 16:30:58 HomeServer systemd[1]: smbd.service: Failed with result 'exit-code'.
Feb 21 16:30:58 HomeServer systemd[1]: Failed to start Samba SMB Daemon.
Feb 21 16:30:58 HomeServer systemd[1]: Starting Samba SMB Daemon...
Feb 21 16:30:59 HomeServer systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Feb 21 16:30:59 HomeServer systemd[1]: smbd.service: Failed with result 'exit-code'.
Feb 21 16:30:59 HomeServer systemd[1]: Failed to start Samba SMB Daemon.
Feb 21 16:30:59 HomeServer systemd[1]: Starting Samba SMB Daemon...
Feb 21 16:30:59 HomeServer systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Feb 21 16:30:59 HomeServer systemd[1]: smbd.service: Failed with result 'exit-code'.
Feb 21 16:30:59 HomeServer systemd[1]: Failed to start Samba SMB Daemon.
Feb 21 16:41:52 HomeServer systemd[1]: Starting Samba SMB Daemon...
Feb 21 16:41:55 HomeServer systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Feb 21 16:41:55 HomeServer systemd[1]: smbd.service: Failed with result 'exit-code'.
Feb 21 16:41:55 HomeServer systemd[1]: Failed to start Samba SMB Daemon.
Feb 21 17:08:14 HomeServer systemd[1]: Starting Samba SMB Daemon...
Feb 21 17:08:15 HomeServer systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Feb 21 17:08:15 HomeServer systemd[1]: smbd.service: Failed with result 'exit-code'.
Feb 21 17:08:15 HomeServer systemd[1]: Failed to start Samba SMB Daemon.

Alles anzeigen

These indeed do point out there is something wrong with Samba SMB Deamon

Zoki · 21. Februar 2022

Not much of a hint.

Try testparm /etc/samba/smb.conf or to start the service maually with systemctl start smbd.service

Geert · 21. Februar 2022

"testparm /etc/samba/smb.conf" Gave the following output

XML: Output testparm

rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[Server_Storage]"
Processing section "[DataPool2]"
Processing section "[DATA3]"
Processing section "[Movies]"
Processing section "[Series]"
Processing section "[Config]"
Processing section "[Minecraft]"
Processing section "[DockerPath]"
Loaded services file OK.
Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

# Global parameters
[global]
        disable spoolss = Yes
        dns proxy = No
        load printers = No
        log file = /var/log/samba/log.%m
        logging = syslog
        map to guest = Bad User
        max log size = 1000
        multicast dns register = No
        pam password change = Yes
        panic action = /usr/share/samba/panic-action %d
        passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
        passwd program = /usr/bin/passwd %u
        printcap name = /dev/null
        server string = %h server
        socket options = TCP_NODELAY IPTOS_LOWDELAY
        time server = Yes
        fruit:aapl = yes
        idmap config * : backend = tdb
        aio read size = 16384
        aio write size = 16384
        create mask = 0777
        directory mask = 0777
        printing = bsd
        use sendfile = Yes


[Server_Storage]
        create mask = 0664
        directory mask = 0775
        force create mode = 0664
        force directory mode = 0775
        hide special files = Yes
        inherit acls = Yes
        path = /srv/dev-disk-by-uuid-3f5f245d-855a-4583-ab18-9dcd127d7627/
        read only = No
        valid users = Wout @RootAdmin
        write list = Wout @RootAdmin


[DataPool2]
        create mask = 0664
        directory mask = 0775
        force create mode = 0664
        force directory mode = 0775
        hide special files = Yes
        inherit acls = Yes
        path = /srv/dev-disk-by-uuid-0a19f4ae-45ee-4aeb-a1ec-4bb238942176/
        read only = No
        valid users = Wout @RootAdmin
        write list = Wout @RootAdmin


[DATA3]
        create mask = 0664
        directory mask = 0775
        force create mode = 0664
        force directory mode = 0775
        hide special files = Yes
        inherit acls = Yes
        path = /DATA3/
        read only = No
        valid users = Wout @RootAdmin
        write list = Wout @RootAdmin


[Movies]
        create mask = 0664
        directory mask = 0775
        force create mode = 0664
        force directory mode = 0775
        guest ok = Yes
        guest only = Yes
        hide special files = Yes
        inherit acls = Yes
        path = /srv/dev-disk-by-uuid-0a19f4ae-45ee-4aeb-a1ec-4bb238942176/Movies/
        read only = No


[Series]
        create mask = 0664
        directory mask = 0775
        force create mode = 0664
        force directory mode = 0775
        guest ok = Yes
        guest only = Yes
        hide special files = Yes
        inherit acls = Yes
        path = /srv/dev-disk-by-uuid-0a19f4ae-45ee-4aeb-a1ec-4bb238942176/Series/
        read only = No


[Config]
        create mask = 0664
        directory mask = 0775
        force create mode = 0664
        force directory mode = 0775
        guest ok = Yes
        guest only = Yes
        hide special files = Yes
        inherit acls = Yes
        path = /Config/
        read only = No


[Minecraft]
        create mask = 0664
        directory mask = 0775
        force create mode = 0664
        force directory mode = 0775
        guest ok = Yes
        hide special files = Yes
        inherit acls = Yes
        path = /srv/dev-disk-by-uuid-3f5f245d-855a-4583-ab18-9dcd127d7627/Minecraft/
        read only = No
        write list = Wout @RootAdmin


[DockerPath]
        create mask = 0664
        directory mask = 0775
        ea support = No
        force create mode = 0664
        force directory mode = 0775
        guest ok = Yes
        hide special files = Yes
        inherit acls = Yes
        path = /var/lib/docker/volumes/
        read only = No
        store dos attributes = No
        write list = Wout @RootAdmin

Alles anzeigen

I wasn't able to run "systemctl start smbd.service" duo to an error. Same message as last time

XML: Error message systemctl

root@HomeServer:~# systemctl start smbd.service
Job for smbd.service failed because the control process exited with error code.
See "systemctl status smbd.service" and "journalctl -xe" for details.

Geert · 28. Februar 2022

So, a couple of days of troubleshooting I've finally found the solution myself.

Just getting back to this thread in case other people experience the same problem.

What I have done was first reinstalling samba:

Code

sudo apt-get purge samba samba-common
sudo apt-get install samba

This gave me a problem with the web GUI, this, I have solved by just reinstalling OMV using the following command:

sudo apt-get install --reinstall openmediavault, this does not delete any of your personal data and solved all the problems.

My server is back up and running as before.

Special thanks to Zoki for assisting me with this issue!

Permission issue. No perms to apply changes

geaves 20. Februar 2022

Jetzt mitmachen!