SAMBA not starting automatically, ok if started manually

  • I'm trying to get my head around on why SAMBA is not starting automatically.
    The Enabled is of course set to on on the SMB config page.


    After a reboot I see no smb process:


    Code
    root@nas:~# ps aux |grep smbroot      1216  0.0  0.0  12732  2192 pts/0    S+   13:46   0:00 grep smb


    but if I start it manually from the shell

    Code
    root@nas:~# /usr/sbin/smbd -D
    root@nas:~# ps aux |grep smb
    root      1271  1.0  0.1 283160 13908 ?        Ss   13:49   0:00 /usr/sbin/smbd -D
    root      1275  0.0  0.0  12732  2240 pts/0    S+   13:49   0:00 grep smb


    Everything works fine.


    Any tip?


    Thanks

  • Code
    root@nas:~# systemctl status smbd.service
    ● smbd.service - LSB: start Samba SMB/CIFS daemon (smbd)   
       Loaded: loaded (/etc/init.d/smbd)   
       Active: active (exited) since Thu 2017-07-06 13:40:08 BST; 1h 13min ago
    
    
    Jul 06 13:40:08 nas smbd[1133]: Starting SMB/CIFS daemon: smbd.
    Jul 06 13:40:08 nas systemd[1]: Started LSB: start Samba SMB/CIFS daemon (smbd).
  • Try enabling samba logs on the smb/cifs page. Set it back to none when done. Then look at the log for possible clues.


    Do you have this file? /sbin/start-stop-daemon.REAL


    Yes that file is available:


    Code
    root@nas:~# ls -la /sbin/start-stop-daemon.REAL 
    -rwxr-xr-x 1 root root 32392 May  2  2016 /sbin/start-stop-daemon.REAL



    about the log this is the content:

    • Offizieller Beitrag

    According to this link here is how to fix it. https://forum.openmediavault.o…?postID=147109#post147109
    mv /sbin/start-stop-daemon.REAL /sbin/start-stop-daemon


    My best guess is an installation issue caused it and it may be fairly common. If you can see anything in the install logs let us know. If you find it works I want to include it in this link https://forum.openmediavault.o…s-samba-Trouble-shooting/ . I am going into the back country for a few days. So if another moderator could add that to the first post that would be great.


    Thanks

  • According to this link here is how to fix it. https://forum.openmediavault.o…?postID=147109#post147109
    mv /sbin/start-stop-daemon.REAL /sbin/start-stop-daemon


    My best guess is an installation issue caused it and it may be fairly common. If you can see anything in the install logs let us know. If you find it works I want to include it in this link https://forum.openmediavault.o…s-samba-Trouble-shooting/ . I am going into the back country for a few days. So if another moderator could add that to the first post that would be great.


    Thanks

    Unfortunately that didn't resolve.


    Just to clarify this is a fresh OMV 3.0 installation.


    2.x worked perfectly for years...

  • It's a VM on VMWARE and it's a fresh installation from the ISO I have downloaded from the official openmediavault site.


    Having said that I have few users moaning about the lack of samba so had to quick re-build 2.x which worked out of the box at the first attempt.

  • I confirm this issue is still there in the latest v3.x ISO.
    I did a fresh install on a dedicated hardware, then installed omv-extras, then I was setting the shares.


    Dashboard indicators show green status, but I can't connect to shares until I start smbd manually via ssh console.
    Running smbd temporarily fixes samba, until next restart.



    Any suggestions how where to look for the issue and to properly fix it?
    Thank you

    • Offizieller Beitrag

    I confirm this issue is still there in the latest v3.x ISO.
    I did a fresh install on a dedicated hardware, then installed omv-extras, then I was setting the shares.

    I have installed many times from that ISO and haven't had this issue.


    systemctl enable smbd.service should make it start at boot.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


    omv-extras.org plugins source code and issue tracker - github


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • #SOLVED


    $ systemctl enable smbd.service
    $ systemctl start smbd.service
    These commands did nothing for me.


    I checked an output of journalctl -r and noticed smbd[2122]: Warning: Fake start-stop-daemon called, doing nothing. message.


    This message is generated by current start-stop-daemon:

    Bash
    $ cat /sbin/start-stop-daemon
    #!/bin/sh
    echo 1>&2
    echo 'Warning: Fake start-stop-daemon called, doing nothing.' 1>&2
    exit 0


    There is another start-stop-daemon available:

    Bash
    $ ls -l /sbin/start-stop-daemon*
    -rwxr-xr-x 1 root root 94 Sep 8 17:42 /sbin/start-stop-daemon
    -rwxr-xr-x 1 root root 32392 May 2 2016 /sbin/start-stop-daemon.REAL


    So I replaced the REAL start-stop-daemon with the fake one:

    Bash
    mv /sbin/start-stop-daemon /sbin/start-stop-daemon.FAKE
    mv /sbin/start-stop-daemon.REAL /sbin/start-stop-daemon


    It works now. Now I can see smbd successfully starting on boot: server smbd[2651]: STATUS=daemon 'smbd' finished starting up and ready to serve connections (output of journalctl -r).


    Thank you.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!