Serviio

Hi All

I have been using Serviio since v1.2, so this is not my first rodeo. Tried to upgrade from V1.6.1 to V1.8, but ended up with none of my Samsung devices seeing the Serviio "service" on my LAN. On 1.6.1 both devices worked flawlessly. Although my TV showed up in 1.6 as a Unrecognised Device, it still played the content. But, I wanted to upgrade my serviio to get on the latest version, and now none of the devices that worked previously, is discovering the service.

I ended up canning the "upgraded" 1.8, and re-installing from scratch. Still the problem persists. At least 1.8 shows my TV as the correct Samsung 7351 55"

I am uploading the log.

My system is:

Fedora 21 64bit
ffmpeg version 2.4.11
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)

Samsung Blu-Ray E4500K
Samsung UA55K7351KXXA


Any help would be appreciated? Please?

Your devices are timing out in the lan:

2017-05-26 21:47:42,886 WARN [RendererManager] Error while retrieving renderer description: Read timed out


This is repeated many times.

Yeah but this is not a LAN issue. Sorry to say. I reverted back to 1.6.1 and it showed up IMMEDIATELY. And it is working. My BR player has been working with all version up to and including 1.6.1 flawlessly. So this may be the error message, but I can assure you that is not the root cause. In any case, 1G running to all of it, traceroutes show less than 1ms response time. And all devices are up. There must have been a change in the way that Serviio "discovers" devices, or the way it "adevertises" itself to devices. I am not a coding expert, and not a JAVA expert, I am however a network architect by trade, and I am 99.999% sure the network is not the problem here.

Just to show you, ping and traceroute times for the network:

ping 192.168.2.13
PING 192.168.2.13 (192.168.2.13) 56(84) bytes of data.
64 bytes from 192.168.2.13: icmp_seq=1 ttl=64 time=0.326 ms
64 bytes from 192.168.2.13: icmp_seq=2 ttl=64 time=0.298 ms
64 bytes from 192.168.2.13: icmp_seq=3 ttl=64 time=0.358 ms
64 bytes from 192.168.2.13: icmp_seq=4 ttl=64 time=0.360 ms
64 bytes from 192.168.2.13: icmp_seq=5 ttl=64 time=0.343 ms

traceroute 192.168.2.13
traceroute to 192.168.2.13 (192.168.2.13), 30 hops max, 60 byte packets
1 192.168.2.13 (192.168.2.13) 0.290 ms 0.275 ms 0.362 ms

And I just booted my TV, Serviio shows up in less than 5 seconds after I boot it, so the discovery in 1.6.1 is working 100%, which makes me believe this is not a LAN issue, and that the log entry is a "false" recording of the problem.

Sometimes if I turn my Blu-ray off and on that helps.

Sorry, I'm not a programmer either.

I assume you're using the same Java version for both these versions? I did have a quick look for changes between 1.6.1 and 1.8 around this area and can't find anything that might be causing this. Will have a look again.

could you post detailed log of 1.6.1 and 1.8 when Serviio is starting up? I can't see anything in the code, maybe the logs will reveal something.

Hi zip

Detailed log for 1.8 attached in first post.

Attaching 1.6.1 detailed log as soon as I can generate it, not at home atm.

And yes, to your answer, I installed Oracle Java and used the same JAVA version with exactly the same start-up parameters for both versions. So not sure what is happening.

Will get that log to you a.s.a.p.

@zip

Herewith the log. I use exactly the same Java for both versions. I literally just remove old serviio from /opt/serviio and dump new version in there.

Regards

Thanks, it looks like your TV requests Serviio's DeiceDescription - so it should be ok.

But then I also see a timeout warning in the 1.8 log. I'm thinking these should not be related, but will double check.

Anything else I can try? Anything else you need? Would really like to get this fixed. Thanks for all the trouble so far!

I did try this and it's not related in the code at all, so it was a red herring.

The last option would be to do a Wireshard packet capture using both versions (just the startup of the server, don't stream anything). And tell me the IP of the TV and the server so that I can filter on these.

OK, but busy at work at the moment, but will try this as soon as I have some time, and send the results. Thanks for the trouble!

Fixed in 1.9 see my post http://forum.serviio.org/viewtopic.php?f=6&t=22925#p114998

@zip

So I have found the problem, at bloody last.

Updating on a fresh install of CentOS 7.4, and serviio 1.9, I came across the following (and with hindsight, well DUH), but the problem is the proxy options I am adding to Serviio. It seems Serviio doesn't honour system proxy settings in Linux, so in order to get updates from websites (art, metadata etc) I have to hardcode the settings to the Serviio launch parameters using -Dproxy.... options. However, the -DnonProxyHost=localhost option is not working for local network discovery of devices. So, it seems, that it wants to go through the proxy whilst discovering for local rendering devices, which it shouldn't. And before anyone asks, the proxy for web related stuff is non-negotiable. It simply has to work.

So in short, I need basically for Serviio to use the proxy for any web content it needs to get, and ignore proxy for local network. If anyone has any idea how to tell Java to do that, I would be forever in your debt!

Any ideas?

Regards

Oh and I referenced http://docs.oracle.com/javase/8/docs/technotes/guides/net/proxies.html for my options.

OK so the fix is the following. When adding Proxy commands you also have to add nonProxyHost option, and the syntax MUST BE CORRECT!

so my final proxy parameters look like this:

-Dhttp.proxyHost=HOST_IP -Dhttp.proxyPort=PORT# -Dhttps.proxyHost=HOST_IP -Dhttps.proxyPort=PORT# -Dhttp.nonProxyHosts="192.168.2.*"

Notice the " " at the end. They are also important.

Anyway, 1.9 is now up and running, indexing everything again, and fetching Metadata from the net, and discovering devices quicker on the network.

Cheers

well done, thanks for letting us know