[Roi Danton]

Hello,

I have trouble with the recordings list when starting my Kodi box. It is just empty. I need to restart Kodi, then it appears - most of the times.

My setup: yaVDR newest version based on Ubuntu trusty (VDR 2.2.0, vdr-plugin-vnsiserver 2:1.5.2+git20171022-17-63d8151-0yavdr0~trusty), Kodi 17.3 on LibreELEC 8.0.2 x86_64, VDR VNSI Client 2.6.23.1.

The hard drive for the recordings goes into sleep after some time and I think that this might be related with the problem. I noticed the following log lines on LibreELEC:

Code:

22:11:07.296 T:139790364763904   ERROR: AddOnLog: VDR VNSI Client: Login - failed to read greeting from server
22:11:08.298 T:139790364763904  NOTICE: AddOnLog: VDR VNSI Client: Logged in at '1512033057+3600' to 'VDR-Network-Streaming-Interface (VNSI) Server' Version: '1.5.2' with protocol version '12'
22:11:17.146 T:139791981602560   ERROR: AddOnLog: VDR VNSI Client: ReadResult - request timed out after 10 seconds
22:11:17.146 T:139791981602560   ERROR: AddOnLog: VDR VNSI Client: SupportChannelScan - Can't get response packed
22:11:30.003 T:139790624212736   ERROR: AddOnLog: VDR VNSI Client: ReadResult - request timed out after 10 seconds
22:11:30.003 T:139790624212736   ERROR: AddOnLog: VDR VNSI Client: GetRecordingsList - Can't get response packed
22:11:30.003 T:139790624212736   ERROR: PVR - GetRecordings - addon 'VDR-Network-Streaming-Interface (VNSI) Server:172.27.0.20:34890' returned an error: unknown error

I already changed the timeout of the VNSI Client from 3 to 10 seconds (which should be enough time for the hard drive to wake up) but it did not help. Should I even put the timeout to more than 10 seconds?

Any more ideas?

On the VDR I noticed this:

Code:

Nov 29 22:51:07 yavdr vdr: [32376] VNSI: Requesting clients to reload recordings list

If I cannot solve this issue on the client side, is it possible to send this request to the clients after they connect. Lets say 30 seconds after they connect?

Cheers,
Roi

[FernetMenta]

please pastebin complete debug log

[Roi Danton]

Client, server, both? Do you have a small hint how to set this up, what settings do I need to adjust? ;-) Thank you!

[Schreibwaise]

I already changed the timeout of the VNSI Client from 3 to 10 seconds (which should be enough time for the hard drive to wake up) but it did not help. Should I even put the timeout to more than 10 seconds?

Yes, please try. My NAS sometimes takes substantially longer to wake up its drives. I only use it for my music library and kodi always was patiently enough to wait for it. But chances are timeouts for NFS mounts are longer than for local drives.

[Schreibwaise]

Client, server, both? Do you have a small hint how to set this up, what settings do I need to adjust? ;-) Thank you!

 Just go to settings->system->logging and enable the debug log. You will find the logfile in the temp directory of your userdata folder. More info here

[bogey]

I have the same issue.
Here is the debug log
https://pastebin.com/D72tWEJ9

Edit:
I have 4 some older disks with snapraid on vdr server, so waking up all drives takes some time.
Could the max timeout be increased?

Code:

$ time ls /data
video
real 0m17.250s
user 0m0.002s
sys 0m0.001s

[FernetMenta]

VDR is master of recordings and keeps a list of those. vnsiserver is just a client that can read this list. If this list changes, VDR fires an event and vnsiserver notifies Kodi about this event. Kodi will read recordings again.
VDR 2.2.x was buggy in this regard. First thing I would try is VDR 2.3.8 with latest version of vnsiserver.

[bogey]

As a workaround I increased the timeout to 20 second in vnsi settings.xml file directly as in UI max is 15.
Now it is ok.