Cannot see NAS on network after rebooting OMV5

sandman8319 · Nov 7th 2019

Hi Guys,

I have been able to successfully install OMV 5 on a RasPi 4 with Plex running in docker. However when I reboot OMV, i see two things
1. The rebooting dialog does not go away and instead I see a black bar at the top that says "Software Failure. Click Left mouse button. Failure to authenticate"
I just refresh the browser at that point and it will show me the login screen, after which I can successfully login and get back into the OMV GUI.
2. I cannot see the NAS on my network in windows 10 anymore.
I have to stop the docker service. Then go to shared folders-> edit -> reference the shared folders paths -> save. Then restart docker service. After which, I can see the NAS on my network once more.

Are others seeing this too ? Is there something I can do to resolve these errors ?

votdev · Nov 7th 2019

Does this help to see your SMB/CIFS shares again?

Code

# systemctl restart wsdd.service

sandman8319 · Nov 8th 2019

Thanks. That worked!!!
However I noticed something else on reboot
In OMV-Extras -> Portainer -> It says "No Portainer container found"

Then, I have to remove docker, reinstall docker and after that I see portainer running once again .

Erinox · Dec 7th 2020

Hi.

I have the same problem that I can not see OMV on my network after it's running for some time.

If I log in and put "systemctl restart wsdd.service" it's appearing again.

Everything else is running fine and I can still access everything with Cloud Commander but it only shows up in Windows 10 if I restart the rsdd.service every now and then. Any idea why the service apparently gets killed after a while?

macom · Dec 7th 2020

Check

journalctl -u wsdd.service if any errors are logged

and

systemctl status wsdd.service if it is enabeld (automatically started at boot)

votdev · Dec 7th 2020

Is the wsdd service stopped or is it reported as running when the shares disappear in Windows? I'm wondering because systemd should restart it automatically on failure.

Erinox · Dec 8th 2020

I think it does restart when it stops:

Code

Dec 07 12:46:37 openmediavault.local systemd[1]: Stopping Web Services Dynamic Discovery host daemon...
Dec 07 12:46:38 openmediavault.local systemd[1]: wsdd.service: Succeeded.
Dec 07 12:46:38 openmediavault.local systemd[1]: Stopped Web Services Dynamic Discovery host daemon.
Dec 07 12:46:38 openmediavault.local systemd[1]: Started Web Services Dynamic Discovery host daemon.
Dec 07 12:46:38 openmediavault.local wsdd.py[25341]: WARNING: no interface given, using all interfaces

Code

root@openmediavault:~# systemctl status wsdd.service
● wsdd.service - Web Services Dynamic Discovery host daemon
   Loaded: loaded (/lib/systemd/system/wsdd.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2020-12-07 12:46:38 CET; 23h ago
 Main PID: 25341 (python3)
    Tasks: 1 (limit: 4915)
   Memory: 10.9M
   CGroup: /system.slice/wsdd.service
           └─25341 python3 /usr/sbin/wsdd.py --shortlog --workgroup=WORKGROUP

Dec 07 12:46:38 openmediavault.local systemd[1]: Started Web Services Dynamic Discovery host daemon.
Dec 07 12:46:38 openmediavault.local wsdd.py[25341]: WARNING: no interface given, using all interfaces

Display More

It was gone again just now. When I try to navigate to //openmediavault.local in the file explorer it sends me to the browser log-in page of OMV 5. After restarting the service I can see and access the shares in the network. If I try to access the shares by opening //openmediavault directly it disappears again and sends me to the web-login again. After doing that I have to restart it again to work but it's only working for some time before it disappears again. Pretty strange.

Erinox · Dec 20th 2020

I have updated OMV a few times since my post and right now it's working again. Not sure if something was changed in OMV in the meantime?

Cannot see NAS on network after rebooting OMV5

Participate now!

Tags