Reboot required after reindex

steve.eckett · 8 July 2018 09:38

For the last month or so my Vero 4k has started playing video in background, which is a stunningly useless feature. More specifically, if I select a new file that has been added to the library, an indicator appears to tell me it is playing, and how far it has progressed, but the screen stays on the menu rather than switching to the movie. A reboot or Kodi restart cures the problem, but I’m sure that should not be necessary. If there a skin or video playback setting that triggers this?
I checked on the Kodi Forums in case it was a more general error but can’t see anything relevant. Has anyone else seen this issue? Software is current 4K OSMC release.

Tom_Doyle · 8 July 2018 09:43

Hi,

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.

So, in summary:

activate the 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.

Tom.

sam_nazarko · 8 July 2018 17:16

Which skin are you using?

Sam

Xanderzdad · 8 July 2018 17:48

I have been experiencing the exact same issue for a few months. I press play and the play icon shows but the film doesn’t actually become visible or audible - but does seem to be playing silently and invisibly in the background… Only a reboot fixes it.

sam_nazarko · 8 July 2018 18:47

Which skin are you using?

Xanderzdad · 8 July 2018 21:32

Hi Sam. I am using Estuary. It all worked fine until 2-3 months ago and I am not aware of changing anything.

Xanderzdad · 8 July 2018 21:36

I’ve just tried switching to the new OSMC skin to see if it makes a difference and now when the error occurs it displays “Buffering…” in the top right corner. But it never actually starts playing. That may give some more insight

ActionA · 8 July 2018 21:37

We need logs in order to have any clue what the issue may possibly be.

Xanderzdad · 8 July 2018 21:43

OK the error is still happening so hopefully this log captured it.

The reference is [https://paste.osmc.tv/epofoqovot]

Tom_Doyle · 8 July 2018 21:45

Hi,

You can have debug logs on all the time and have it not show on the display, until you capture the error. Enable debug logs and set debug level to 1 in advancedsettings.xml:

<loglevel>1</loglevel>

Thanks Tom.

Xanderzdad · 8 July 2018 21:50

Hi Tom

Sorry but my knowledge of Kodi is quite limited. How do I find and edit advancedsettings.xml?

Tom_Doyle · 8 July 2018 22:14

Hi,

Tom.

sam_nazarko · 8 July 2018 23:04

For the short time, you could just enable debug logging via Settings -> Logging and deactivate it after reproducing the problem and uploading the logs.

steve.eckett · 9 July 2018 08:36

I carefully set up logging and read new files into the library but could not trigger the fault. Will leave logging on for a few days. Skin is OSMC default. Build is latest production release plus SMB and VNC.

Xanderzdad · 9 July 2018 09:18

Hi Sam

Assuming I did it correctly then that is what I did for my log file [https://paste.osmc.tv/epofoqovot]. Has it captured my starting and stopping a film, that did not actually play? The buffering message seems related.

Tom_Doyle · 9 July 2018 09:52

Hi,

Did you reboot before uploading logs? If so it looks like debug logs were not enabled.

No settings file to load (special://masterprofile/advancedsettings.xml)

Doesn’t look like the advancedsettings.xml file has been created correctly.

Please issue:

cat /home/osmc/.kodi/userdata/advancedsettings.xml | paste-log

And post the provided link.

Thanks Tom.

Xanderzdad · 9 July 2018 10:30

Hi Tom / Sam

Sorry if my log didn’t work.

Do you mean that I should enable logging as per Sam’s suggestion but then

reboot before uploading logs

Perhaps I am being dim but I thought the link to creating an error log suggested:

Enable Debug logging via OSMC
Reboot
Wait for error to occur
Upload log via OSMC

Should I have rebooted again between steps 3 & 4?
Also should I have enabled all the sub options in the debug log menu?
I must admit the instructions were a little vague to me although that could be because I am definitely a Kodi newbie.

Tom_Doyle · 9 July 2018 10:31

Hi,

No what mean is did you reboot after capturing the issue?

Thanks Tom.

Xanderzdad · 9 July 2018 12:24

No, I didn’t reboot after capturing the issue.

Are you saying I should reboot twice - once when I enable logging and again after the issue occurs but before I submit the log?

Tom_Doyle · 9 July 2018 12:53

Hi,

Sorry was missreading the log, this stands out:

18:58:35.450 T:3846529792    INFO: CNFSFile::Open: Unable to open file : 'volume1/Video/Movies/Lady Bird (2017)1080p BluRay H264 AAC.avi'  error : 'open call failed with "NFS: Lookup of /Movies/Lady Bird (2017)1080p BluRay H264 AAC.avi failed with NFS3ERR_NOENT(-2)"'
18:58:35.450 T:3846529792   ERROR: Open - failed to open source <nfs://192.168.0.136/volume1/Video/Movies/Lady Bird (2017)1080p BluRay H264 AAC.avi>

Can you play that movie locally or on any other device?

Also you should have more luck with fstab mounted shares:

Thanks Tom.