Serviio

Hi,

Serviio 1.10.1 (pro) is running in a VM guest of a Hyper-V server. it works so far, and has worked before, after i "upgraded" my server to a newer CPU.

ISnce then it stops playback on all of my devices after around 15 minutes

enablewd logging and found tons of

2020-10-07 13:29:53,827 WARN [RendererManager] Error while retrieving renderer description from http://127.0.0.1:9085/dev2/desc.xml: connect timed out
2020-10-07 13:29:54,178 WARN [RendererManager] Error while retrieving renderer description from http://127.0.0.1:9085/dev2/desc.xml: connect timed out
2020-10-07 13:29:54,178 WARN [RendererManager] Error while retrieving renderer description from http://127.0.0.1:9085/dev2/desc.xml: connect timed out

but no real cause why it stops playing.

Any advice ?

would there be any difference to serviio 2.x ? actually i won't need the pro features anymore (although mediaplayer is nice...

You might first check to see if your virtual network card is going to sleep. You didn't say what OS you're using, but Serviio has always had issues with Windows Server OS.

But it's also a little puzzling why it's using the loopback interface (127.0.0.1). I would expect that to be your network IP address. Certainly sounds like something amiss with your VM.

i'm using Windows Server 2019 Hyperv and Win10 as client OS. no chnage in this setup, except "upgrading" the server from an atomic plant Dell Poweredge720 12cores to a Intel i3 9th generation 4 cores.

AND, what i forogt to mention, i moved the videos from the local powerewdge to a synology nas drive as well... will check if playback of a "local file" also fails... will report back.

But what is this RendererManager doing ? who's listening o this port, netstat didn't report any listening process...

aha, so here weg go...

it's actually somehow related with the Synology NAS.

Is there a way to track why the stream seems to stop after 15 mins ?

network monitor or procmon from sysinternals come to my mind, anything else builtin ?

Thx !

and the RendererManager is still also an black box for me...

Zip would have to respond to this now. You're getting into the depths of the functionality that is way over my head.

perhaps the filesystem gives the wrong file size when Serviio scans the files. Can you see the file size / duration of the file when browsed in Serviio?

thx, but looks to be some sort of networking issue...

17:58:42,0647966 ServiioService.exe 5336 ReadFile \\nas.olwe.local\6tb\videoArchiv\(T)Raumschiff Surprise - Periode 1\20190101-1247 Komödie, D 2003-ProSieben-201901-0112-47-01-1.mkv NETWORK ERROR Offset: 17.825.792, Length: 4.096, I/O Flags: Non-cached, Paging I/O, Synchronous Paging I/O, Priority: Normal
17:58:42,0649338 ServiioService.exe 5336 ReadFile \\nas.olwe.local\6tb\videoArchiv\(T)Raumschiff Surprise - Periode 1\20190101-1247 Komödie, D 2003-ProSieben-201901-0112-47-01-1.mkv NETWORK ERROR Offset: 17.821.696, Length: 65.536, Priority: Normal
17:58:42,0651915 ServiioService.exe 5336 CloseFile \\nas.olwe.local\6tb\videoArchiv\(T)Raumschiff Surprise - Periode 1\20190101-1247 Komödie, D 2003-ProSieben-201901-0112-47-01-1.mkv SUCCESS
17:59:16,2893863 ServiioService.exe 5336 CreateFile \\nas.olwe.local\6tb\videoArchiv\(T)Raumschiff Surprise - Periode 1\20190101-1247 Komödie, D 2003-ProSieben-201901-0112-47-01-1.mkv LOGON FAILURE Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a

Seems to be a problem in SMB protocol between Windows10 and the Synology NAS...