Serviio

My Synology NAS does not hibernate after upgrading to 1.0. It seems like Serviio is reading online repositories every one minute instead of using the feed expiry interval set in the console.



Any ideas???

It always checked every minute. No change there from 0.6.

My Synology has never hibernated while running Serviio. I did try symlinking the log folder to a ramdisk but it didn't seem to help so maybe it's some kind of Java issue.

My Synology used to hibernate with Serviio 0.6.2. It stopped after upgrading to 1.0. I am still trying to figure out what changed.

Well, after upgrading my Synology DS212+ to the latest Serviio version (very bad idea), it also doesn't hibernate...

After some fiddling around, there is a command on the Synology to debug hibernation issues:

syno_hibernate_debug_tool --enable 1

then

cd /var/log

tail -f messages

So I've found out that ever 30s, the Serviio server checks this file on the disk:

[/volume1/homes/serviio/.java/.userPrefs/.user.lock.serviio] opened by pid 10290 [u:(/volume1/@appstore/java7/jre/bi), comm:(java)]

(it repeats this endlessly every 30s...)

I think this is the reason why the NAS doesn't hibernate.

Stoping Serviio, the message stops, and the NAS hibernates.

Any solutions?

Zip, we would really appreciate if you could comment on syncmaster's findings.

OK, this is caused by Java preferences subsystem - out of my hands. Apparently you can change the syncing interval form 30 seconds to some very high number using this system property:



e.g.:

1. the value is in milliseconds right ?
2. Where does the parameter go ? serviio java options file ?

Nice detective work syncmaster - I'll take a look at incorporating this fix into the package. Can you guys confirm it works? Add that parameter to the variable JAVA_OPTS in /volume1/@appstore/Serviio/bin/serviio.sh

Just restarted my server with the parameter added. Will update shortly.

seconds

Ok, just added the parameter with value 9999999.

Let's see how it goes.

I'll be back in an hour or two .

Ok.

Adding the parameter and starting Serviio, after a while the NAS does hibernate. So at least starting on boot does allow to hibernate.

When using it the NAS does wake up and Serviio works, it seems, fine.

So I've stop using it, and now I'm waiting that the NAS hibernates again.

But at least it looks promising, and probably the issue is solved.

Confirming that my ds212+ hibernates after adding the java option.

Thanks syncmaster for identifying what was causing this

Thanks Petr for the quick response.

x2 for me.

Adding the Java option allows the NAS to hibernate.

Problem solved.

off-topic:

I'll have to check if with the Crashplan package for the Synology, that when running, the NAS also doesn't hibernate, if the issue is the same...

What sort of default do you think I should add to the package? 12 hours? 24 hours?
That debugging will be useful for diagnosing why CrashPlan prevents hibernation too.

well, I have the library scan 12h (720m).

Regarding the preferences scan, if Serviio doesn't use it, I think 24h, would be fine. It would mean one wake up/day.

Hi all,

sorry, I am a Linux newbie so my question is: In wich file (and where) I have to insert the code?

Thanks a lot!

Regards,
Fleetship1

If you have a Synology - don't worry, I'll update the package today with a new version incorporating that setting.

Done.