Serviio prevents NAS from sleeping??

Hello guys -
Fairly new to the NAS game with Serviio - and running into a problem for which I could not find a solution:

I am running Serviio on a Synology NAS in Docker, with the Docker image that can be found here: https://hub.docker.com/r/soerentsch/serviio
Installation, all, was fairly straightforward (after I managed to de-cypher how to map the relevant folders and create the mounting points.

The only problem I have is: Apparently, Serviio is constantly accessing my disks - because as soon as I start the Docker container with Serviio, my hard drives will not go to sleep anymore.
Googling and searching this forum did not reveal any enlightening insights - hence the question here:

Has anyone successfully managed to set parameters (or do anything else) to have Serviio not constantly access the disks?

[atc98092]

First, I'll say that I've never used a NAS, so I am unfamiliar with their operation. Serviio itself must be running constantly to be able to be available at any time for a player's request. One of Serviio's tasks is to monitor for new files. Depending on the operating system, that might require periodically accessing the drives to query for new files. I have no idea if any of my hard drives go to sleep on my Windows Serviio PCs.

Serviio itself must be running constantly to be able to be available at any time for a player's request. One of Serviio's tasks is to monitor for new files. Depending on the operating system, that might require periodically accessing the drives to query for new files. I have no idea if any of my hard drives go to sleep on my Windows Serviio PCs.

The program itself can stay up and running in the computer’s (NAS’s) memory, without accessing any files.

When setting up a media source for Serviio you can specify if you want to use a “poller” to have Serviio search for new files or file changes. The instructions say: “Normally Serviio uses the operating system event based file changes notifications. This might not work well in certain situations (like for remote drives or mounted file systems). You can use the poller mechanism where Serviio manages the changes to files itself”.
This “poller” certainly would need to access disks - but I’m not using it (default setting).

I have multiple servers running on my NAS - because I have different needs for the streaming of my music:

- Serviio to send my multichannel high-resolution (.dsf) files to a multichannel-capable renderer,
- Minimserver to stream my 2-channel .dsf files (I can stream them directly to my Marantz receiver, without need for an external renderer),
- OwnTone for the large chunk of my music (mp3 and aac files). It’s an iTunes server which I can access using iTunes Remote and listen to my music on a wider variety of devices using Apple AirPlay 2.

Both Minimserver and OwnTone are running in the RAM of the NAS, listening to play or stream requests - and are not accessing any disks while just waiting for commands. They get into action if they either get a playback request, or (Minimserver) if they get a notification of updated files in the monitored folders. Other than that, the disks stop and the server goes to sleep, waiting for commands.

Serviio, too, should just be waiting for commands and not access disks while being idle.

[atc98092]

Yes, I am aware of the Poller switch. I'm just not certain how Serviio is interacting with the OS your NAS is running. I don't know if it's still necessary to access the drives itself. Of course, it's always possible the activity you saw is just the database updating itself for metadata retrieval, although with your file types (.dsf) you might not have that option selected. I know there's online metadata available for music, but I don't know if you're using that function.

I just looked at my Serviio log, and I see gaps in disk access that are hours long. Of course, without having debug logging enabled, there is a lot of activity that isn't logged, so that might not be a valid check.

act98092, thank you for your reply!

Is there anyone out here (incl. zip) who can tell me how to find out reliably which files keep being accessed?

[atc98092]

Zip is really the only person that can likely know the answer.

Serviio is not a bad platform to work on, after a month of use I would still prefer an analogue of this platform, such as Plex or Stremio. Well here, as they say, a matter of taste, and more precisely the tasks that you have set yourself and expect from these services. In any case, I have the leading Plex. The quality of service and queries that are in front of me on this service meet my requirements. In my spare time I earn my dough at 1houseofpokies bonuses casino and I recommend to try it out and make sure in quality of service).

[Meelis]

act98092, thank you for your reply!

Is there anyone out here (incl. zip) who can tell me how to find out reliably which files keep being accessed?

The Docker is the reason why NAS won't go to sleep. And this is the reason why i dont like to use Docker.

https://kb.synology.com/en-us/DSM/tutorial/What_stops_my_Synology_NAS_from_entering_System_Hibernation

And from google i found this. That is the reason why Docker won't let go NAS to sleep. The healthcheck holding it active all the time. I need to try it by myself as well now.

In the end, I managed to wrestle Synology into looking at the problem - and indeed, the health check was the problem, on both my trouble containers: * Our developers took another look, and determined that the container(s) both contain a setting called healthcheck, which requires it to report it’s status back to a config.v2.json file every 5 seconds.*
Ok, it was 30 seconds, not 5 - but after re-creating a container using the ‘docker run’ command with the parameter ‘–no-healthcheck’, all the ‘WRITE’ activity disappeared.
Interestingly, I got a gazillion of ‘READ’ entries in my debug log now - but after a day or so, the NAS properly went to sleep (I guess that might have to do with caching).