Cannot coonect to server

Nothing relevant there

Please, stop serviio and follow these to turn on debug (http://wiki.serviio.org/doku.php?id=detail_logging):

1.- Stop serviio
2.- Go to "C:\Program Files\Serviio\config"
3.- Edit "log4j.xml" file, and change:
Where it puts:

  Code:

<category name="org.serviio">
   <priority value="INFO"/>
</category>

change INFO to DEBUG:

  Code:

<category name="org.serviio">
   <priority value="DEBUG"/>
</category>

4.- Start serviio

And let it run untill it fails. Then upload logs again.

.

Is this enough? that's what I did.

This time I deleted the logs, closed Serviio, edited the file; ran Serviio again, it failed, yet hasn't generated new logs.

Now they have

You did it!, it's running in debug mode.

What is see there, serviio is working as usual. Did your server stopped working (the "cannot connect to" you noticed)?

Let serviio run in debug mode at least until you catch the issues again. In that moment, take all files in logdir (serviio.log, serviio.log.1, etc..) and zip them (or rar or whatever you use) and upload it (the forum down not accept some files....).

Courage you almost get it!
.

It hasn't worked for a while now, the exact message is "Cannot connect to the server, it doesn't seem to be running..."

It hasn't worked for a while now, the exact message is "Cannot connect to the server, it doesn't seem to be running..."

It doesn't run at all

You got them!, but one bad news.... I can't see errors! (perhaps some developer can check it please!).

I would think that the program process is been killed (by windows?).

You are getting error from Mediabrowser, isn't it?. It is been launched from the same computer as server (serviio)?
Another question, is a laptop or so (which might suspend from time to time, or close the lid, or ...)..

.

It's a PC, it does tend to re-boot itself from time to time

[atc98092]

Well, I looked at all 6 log files in the rar archive. All I can say from all of that is that Serviio is running. For whatever reason, all 6 of those files only reference checking your media against the database to see if it's already there. The initial startup lines are missing, as well as any attempt to play anything.

The Derby log file isn't necessary for what we're looking for here. And there's been so much back and forth I've had to go back to the first post to remember what's happening.

Smegsie: please make the following change in the log4j.xml file. On line 16, change the 500KB to 5000KB. This way the log files will be larger before Serviio renames and starts a new file. Save the file, and then stop the Serviio service. While stopped, remove all the log files in the /log folder. Then restart the Serviio process and use Serviio a little bit. Finally, shut Serviio down and zip up the log file(s) again and post them back here. We're just missing too much important information in the logs you provided. After you've done that you can switch detailed logging back off so you don't end up with a ton of huge log files.

Serviio has been "on" all night but hasn't generated any logs.

[atc98092]

If you aren't using Serviio, there's nothing to write to the log. If you stop the Serviio service and remove the current log, then restart the service, the log will contain all of the startup task results. But until you actually use Serviio for something, the normal log won't write anything. The debug log would likely have something, but I can't say what that something might be.

That's the issue, Serviio won't start at all at the moment, constantly receiving the same message.

[atc98092]

That's the issue, Serviio won't start at all at the moment, constantly receiving the same message.

If it won't start, the log will contain information relating to the startup attempt. That's what we need to see. We need a log that shows the startup sequence.

Re-booted and it actually started, first time in days, log attached

The Rar is over 500kB and won't upload

[atc98092]

You can remove data from the back, or split the file into smaller chunks and upload them in separate posts. But we really need to see that load info.

Each log file is 5001kB