SMB will not start

Xeljawn · Apr 12th 2024

I've been struggling with one problem after another after installing updates this morning. All that was updated were docker packages, but afterward I first couldn't get into my web admin (since resolved), and now I can't get Samba to start. Help would be much appreciated.

On attempting to apply configuration changes through the web admin, I get:

Code

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color samba 2>&1' with exit code '1': debian:
...
----------
          ID: start_samba_service
    Function: service.running
        Name: smbd
      Result: False
     Comment: Job for smbd.service failed because the control process exited with error code.
              See "systemctl status smbd.service" and "journalctl -xe" for details.
     Started: 11:29:40.272881
    Duration: 218.568 ms

Display More

When I run "systemctl status smbd.service" followed by "journalctl -xe" in the shell, I get:

Code

root@nas:~# 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 Fri 2024-04-12 11:29:40 EDT; 1min 47s ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 9366 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=>
Process: 9373 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMBDOPTIONS (code=exite>
Main PID: 9373 (code=exited, status=1/FAILURE)
CPU: 101ms


Apr 12 11:29:40 nas systemd[1]: Starting Samba SMB Daemon...
Apr 12 11:29:40 nas systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Apr 12 11:29:40 nas systemd[1]: smbd.service: Failed with result 'exit-code'.
Apr 12 11:29:40 nas systemd[1]: Failed to start Samba SMB Daemon.


root@nas:~# journalctl -xe
Apr 12 11:30:01 nas CRON[9468]: pam_unix(cron:session): session opened for user root(uid=0) by (uid>
Apr 12 11:30:01 nas CRON[9469]: pam_unix(cron:session): session opened for user root(uid=0) by (uid>
Apr 12 11:30:01 nas CRON[9470]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/sy>
Apr 12 11:30:01 nas CRON[9471]: (root) CMD (/usr/sbin/omv-mkrrdgraph >/dev/null 2>&1)
Apr 12 11:30:01 nas CRON[9468]: pam_unix(cron:session): session closed for user root
Apr 12 11:30:07 nas CRON[9469]: pam_unix(cron:session): session closed for user root
Apr 12 11:30:28 nas monit[1139]: Cannot connect to [127.0.0.1]:25 -- Connection refused
Apr 12 11:30:28 nas monit[1139]: Cannot open a connection to the mailserver 127.0.0.1:25 -- Operati>
Apr 12 11:30:28 nas monit[1139]: Mail: Delivery failed -- no mail server is available
Apr 12 11:30:28 nas monit[1139]: Alert handler failed, retry scheduled for next cycle
Apr 12 11:30:58 nas monit[1139]: Cannot connect to [127.0.0.1]:25 -- Connection refused
Apr 12 11:30:58 nas monit[1139]: Cannot open a connection to the mailserver 127.0.0.1:25 -- Operati>
Apr 12 11:30:58 nas monit[1139]: Mail: Delivery failed -- no mail server is available
Apr 12 11:30:58 nas monit[1139]: Alert handler failed, retry scheduled for next cycle
Apr 12 11:31:10 nas systemd[1]: Started Run anacron jobs.
░░ Subject: A start job for unit anacron.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit anacron.service has finished successfully.
░░
░░ The job identifier is 3412.
Apr 12 11:31:10 nas anacron[10129]: Anacron 2.3 started on 2024-04-12
Apr 12 11:31:10 nas anacron[10129]: Normal exit (0 jobs run)
Apr 12 11:31:10 nas systemd[1]: anacron.service: Succeeded.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit anacron.service has successfully entered the 'dead' state.
Apr 12 11:31:28 nas monit[1139]: Cannot connect to [127.0.0.1]:25 -- Connection refused
Apr 12 11:31:28 nas monit[1139]: Cannot open a connection to the mailserver 127.0.0.1:25 -- Operati>
Apr 12 11:31:28 nas monit[1139]: Mail: Delivery failed -- no mail server is available
Apr 12 11:31:28 nas monit[1139]: Alert handler failed, retry scheduled for next cycle

Display More

Please help me get my shares back up and running. Thanks!

Xeljawn · Apr 12th 2024

I should add that a bunch of permissions got messed up somehow by the docker updates install, so fixing some of the stuff I was able to fix myself involved reclaiming root ownership of a bunch of different files. I suspect there may be more permissions to fix somewhere. I just don't know where.

Xeljawn · Apr 12th 2024

UPDATE: I got Samba working again. My myriad problems were caused by ownership of many directories and files being updated after updating docker packages (through the OMV admin). That's never happened before. I don't think all my issues are resolved yet, but setting root:root as the owner of nearly everything on the boot drive resolved the Samba issue for me.
One thing that wasn't fully resolved was the 502 error when trying to login to the admin. To fix that, I once again had to run:

mkdir /run/php
chown www-data:www-data /run/php
chmod 755 /run/php
omv-salt deploy run phpfpm
Any reason why that fix doesn't seem to stick?

eipiplusone · Apr 17th 2024

I had the same problem after recent docker upgrade.

How did you fix it? Thanks.

Xeljawn · Apr 17th 2024

I found that ownership of nearly everything on my boot drive had been updated to the wrong user and group. I fixed most of my issues by resetting the ownership of most folders recursively on my boot drive to root:root. Just be careful not to reset ownership of everything under /srv/ where your non-boot filesystems are mapped.

ex: chown -R root:root /etc/

chente · Apr 17th 2024

Quote from Xeljawn

I fixed most of my issues by resetting the ownership of most folders recursively on my boot drive to root:root.

ummm... Is it possible that this will give you problems in the future? I would use omv-regen to move the configuration to a clean system.

chente · Apr 17th 2024

And I would also make sure to replicate the permissions of the files that omv-regen copies to the new system before regenerating. You have the list of files here. https://github.com/xhente/omv-…ster/omv-regen.sh#L69-L75

Xeljawn · Apr 17th 2024

Quote from chente

ummm... Is it possible that this will give you problems in the future? I would use omv-regen to move the configuration to a clean system.

IS it possible this will give me problems in the future? How would running omv-regen help here?

Soma · Apr 17th 2024

Quote from Xeljawn

I found that ownership of nearly everything on my boot drive had been updated to the wrong user and group. I fixed most of my issues by resetting the ownership of most folders recursively on my boot drive to root:root.

ex: chown -R root:root /etc/

Please, don't advertise this anywhere and to noone.

This is BS.

Your system is FUBAR and you need to do a fresh install to fix that.

chente · Apr 17th 2024

Quote from Xeljawn

IS it possible this will give me problems in the future?

I would not trust a system in which the permissions and/or owners have been completely modified.

Quote from Xeljawn

How would running omv-regen help here?

omv-regen moves your OMV configuration to a new, freshly installed system. Files and directories will have the appropriate permissions.

You just have to compare and make sure that the permissions of that small list of files that omv-regen copies are correct, the list that I gave you before.

andrzejls · Apr 17th 2024

Quote from Soma

Please, don't advertise this anywhere and to noone.
This is BS.

Your system is FUBAR and you need to do a fresh install to fix that.

Could not have said it better myself.

chente · Apr 17th 2024

This is the list of files that you should check if the permissions and owners are correct. It is the only thing that omv-regen copies to the new system by default.

/etc/passwd

/etc/shadow

/etc/group

/etc/subuid

/etc/subgid

/var/lib/samba/private/passdb.tdb

/etc/default/openmediavault

If you have openmediavault-kvm installed, these two folders and all their content will also be copied. In that case the topic would be more complicated, that content can be extensive.

/etc/libvirt

/var/lib/libvirt

If you add an optional folder to the backup, that folder will also be copied to the new system. In that case, you must also check the permissions of the files included in that folder.

Soma · Apr 17th 2024

Quote from chente

etc/shadow

At least this one I'm certain that it doesn't have root:root ownership

As for permissions, who knows...

chente · Apr 17th 2024

Quote from Soma

Please, don't advertise this anywhere and to noone.
This is BS.

Your system is FUBAR and you need to do a fresh install to fix that.

I didn't mean to say it that way because over time I learned that it creates problems for me with some users... let's say... a little sensitive

But yes, that is exactly the situation in this case.

Soma · Apr 17th 2024

Quote from chente

because over time I learned that it creates problems for me with some users... let's say... a little sensitive

That's why i'm not a Moderator,

donh · Apr 17th 2024

Try testparm. It will tell you if there is a problem with /etc/samba/smb.conf.

Xeljawn · Apr 20th 2024

Quote from Soma

Please, don't advertise this anywhere and to noone.
This is BS.

Your system is FUBAR and you need to do a fresh install to fix that.

This is not a usage of FUBAR I'm familiar with, given the system's been running fine for a few days now.
If it were truly FUBAR and I needed a fresh install, I don't think I'd install the same system that f'd it up in the first place.

SMB will not start

Participate now!

Similar Threads

After upgrade 6to7: no access to RPi through hostname

Solution to slow boot time (systemd-networkd-wait-online.service)

Basics for Firewall Hardening

Can't login to workbench omv6

SMB GURUS PLEASE HELP (Is anyone actually getting 10GB speeds on OMV?)

SMB share is available but OMV says it's not enabled

Tags