My Vero has been losing connection to my NAS for the past couple of months when left on standby. Rebooting fixes the issue, then it will play fine.
I’ve recently changed to mount my shares using autofs but that didn’t help.
One thing I have noticed is that when I reboot and you see all the command lines scrolling up, there’s a couple of red lines but they’re gone before I can read them, are they logged anywhere?
Has anyone got any recommendation to try. I’m not sure how to create a debug log for this as rebooting fixes the issue.
Providing logs may expose any configuration issues regardless of the network currently working at the time of creation. You should start there.
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
enable debug logging at settings->system->logging
reboot the OSMC device
reproduce the issue
upload the log set either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
Feb 16 15:06:30 osmc systemd[1]: mnt-Movies.automount: Refusing to start, unit to trigger not loaded.
Feb 16 15:06:30 osmc systemd[1]: Failed to set up automount mnt-Movies.automount.
Feb 16 15:06:30 osmc systemd[1]: Reached target Swap.
Feb 16 15:06:30 osmc systemd[1]: Listening on Journal Socket.
Feb 16 15:06:30 osmc systemd[1]: mnt-ShareFolder.automount: Refusing to start, unit to trigger not loaded.
Feb 16 15:06:30 osmc systemd[1]: Failed to set up automount mnt-ShareFolder.automount.
Feb 16 15:06:30 osmc systemd[1]: mnt-KidsMovies.automount: Refusing to start, unit to trigger not loaded.
Feb 16 15:06:30 osmc systemd[1]: Failed to set up automount mnt-KidsMovies.automount.
You appear to have attempted to configure systemd mounts at some point during your journey which are failing? You should remove these failing configs.
Just a FYI. You were seeing these messages in your log:
Feb 16 15:06:30 osmc systemd[1]: mnt-Movies.automount: Refusing to start, unit to trigger not loaded.
Feb 16 15:06:30 osmc systemd[1]: Failed to set up automount mnt-Movies.automount.
because the network didn’t come up until 5 seconds later:
Feb 16 15:06:35 osmc systemd[1]: Reached target Network is Online.
Right, the connection lost again, the log uploader didn’t work so looks like the vero is dropping wifi connection. I copied logs to the SD card, rebooted and did grab-logs -A, was that correct?
Well this gives us the current Kernel Log and the previous Kodi.log. From that I couldn’t see any connection issues. Which means you would now get one from the older Kernel log (before reload) see below for instructions.
One other question, do you have a VPN installed?
7.a) login via SSH and invoke sudo journalctl --list-boots --no-pager
7.b) the lines start with an index id like 0, -1, -2, etc. and contain the date and time when log was started
8. upload the appropriate kernel log using sudo journalctl -k -b <identified index> --no-pager|paste-log
(replace <identified index> with the real index id, see above)
9. also, upload the appropriate full log using sudo journalctl -b <identified index> --no-pager|paste-log
(replace <identified index> with the real index id, see above)
10. provide the returned URLs here
I rectified this by locating the NFS privileges section under Access Control (on the NAS)
and setting the following:
client address: *
Privilege: Read & Write
Root Mapping: Admin (999)
