Serviio

This is the last one

Great! Now, is that a particular title that you attempted to play but had issues? Without some more specific place to look, that's a lot of data. The startup section looks normal.

no particular file, just is either not connecting to the server; or does and then drops off part way through soemthing

How about one title you tried, so I can search for anything to do with that title?

Try Happy Gilmore, but generally nothing works

Hi, any update?

Guys?

Sorry, I've had my hands full so far this weekend. Babysitting the grandkids, yard work, and other life things getting in the way. I'll see if I can look it over tonight.

I know you don't want to hear this, but the log is still incomplete. First I had to figure out the order of the files, then merge them into a single file for easier analysis. Doing that, I found a more than 2 hour gap in the log. The time stamp jumps from 17:50:36 to 20:02:02. So no idea if anything vital is missing.

There are only four lines with Happy Gilmore, and they were only checking to see if the file was already contained in the DB. In fact, there are no playback command lines anywhere in the log. There are some early lines (up to about line #430) that show Serviio discovering several players, but after that there is nothing found that shows any player activity. And there's a total of 96,565 lines all together. The log just abruptly ends while it's still checking your shared folders for new files. There's no Serviio shutdown information, and nothing to show any connectivity to your players, other than the early lines.

I can see that you changed the log file size in the log4j.xml file, but we need to go larger to make it easier to examine. It's kind of painful to put them together. But I have to admit that I don't know the max file size that can be attached to a post, so maybe we have to stick with the 5 MB file size for now.

Hate to ask it again, but we need to try again with the logs. Stop Serviio, delete all log files, and ensure debug logging is enabled. Start Serviio, go to a player and begin playback. Let it play for a bit, then stop the video. If you are still encountering the disconnect message, try to wait for that to happen. Then stop the Serviio service and zip up all the log files you now have in the Logs folder and post them here again. We don't need the Derby log. Once I'm comfortable that there's something of value, and it myself or other users can't find an issue, we'll ask Zip to look it over. He can spot things that I would never recognize.

after a few reboots I managed to get it working again but only for a few of minutes, played The 100 S03E02 for a couple of minutes, then tried The 100 S03E03 at this one it stopped and disconnected probably less than a minute

OK. No time for me to get on it tonight. I'll see if I can find some time tomorrow or Tuesday.

no problem, much appreciatted

OK, put the files in order and started looking. I found the delivering for 100 S03E03 on line 95544, using the generic profile. From the device name, I assume that it is the Samsung UE55K5600. Have you tried using the Samsung J Series or M Series profile? Can't say if ti would make any difference, but it never hurts.

Found this error on line 95572:

Then it looks like it tries to reconnect, but the error keeps occurring.

Before we go any further, I suggest installing the new version that Zip just published today: 1.9.2. I don't think this was specifically addressed, but you never know what might be improved.

Beyond that, I have to ask Zip to review this info. Once you get deep into the debug information, I really don't know what I'm looking at. Hopefilly by listing the line numbers in the log he can save time looking it over. I have uploaded the assembled log so it's all one file in time sequence.

The Samsung is the smart tv we use, however Serviio will not connect to any of the other devices in the house that we use.

You will have to explain in laymens terms what you mean about the zip

Zip is a person, and the developer of Serviio. He released a new version of Serviio yesterday (1.9.2). I suggest you install the update and see if the problem still occurs. If it does, Zip will need to read those logs, as I've reached the limits of my knowledge in that area.

downloaded latest version, re-booted to be sure; Serviio came on briefly but dropped off before I could open a file, so no logs other the the usual serviio.log and the derby log.