Minimserver in Docker Container Keeps Writing To Disk

[braunsch]

(30-08-2022 12:57)simoncn Wrote:  Which control point(s) do you use?

I am using either the Linn or the Lumin app on an iPad (I want to use OpenHome).
BubbleUPnP gets good reviews, but unfortunately is Android only.

Am I right that all your suggestions with indexing and tags still rely on browsing my library through the ‘Folders’ view?

In particular Lumin, the app with the best user interface, has fixed buttons for Songs, Albums, Artists, Composers… which are directly visible (no navigation through a hierarchy necessary). If I tap, e.g., on ‘Artists’, I see a tile for each artist, with all the songs for that artist behind the tile, regardless of folder. There is no way to narrow down by other tags (like the ones you suggested): If the same song has copies in three different folders on the server it will show up three times.

(30-08-2022 12:57)simoncn Wrote:  Regarding the problem with disk activity preventing the NAS from sleeping, I have done some testing on my Synology NAS and I can confirm that the solution is to add the -XX:-UsePerfData option when launching Java. To do this in a Docker container, you need to create a file /opt/minimserver/etc/minimstart.conf in the container with the contents

javaopts = -XX:-UsePerfData

You can use a Docker terminal window to create this file. After doing this, you need to stop and restart the MinimServer container.

Since I have so many containers I ran a variety of tests:

• Create the container with or without the “--no-healthcheck” and "--log-driver none" parameters, as suggested by bubbleguuum above
• Start the container with or without the “javaopts = -XX:-UsePerfData” parameter in a minimstart.conf file, as suggested by you.
  

Of the possible four combinations, only one yielded the desired results: Adding “--no-healthcheck” and "--log-driver none" to the container creation AND starting the container with the “javaopts = -XX:-UsePerfData” line in the minimstart.conf file.

Only with both these options chosen, the NAS went to sleep after the expected time.

My command to create the container was
sudo docker run -it --no-healthcheck --log-driver none --network host --name HiRes-Stereo minimworld/minimserver:latest

Would it be possible to add these three settings (switch off healthcheck, log driver and performance data recording) to the next version of the Docker container image?

I appreciate your engagement in this discussion and helping me find a solution that works!

[stefano_mbp]

Lumïn app has its own db that is populated and maintained when you load/update the library from Minimserver.
The four buttons use the internal app db and not Minimserver browsing by folders view, if you use them you’ll not be able to browse by tags.

[simoncn]

In my Synology test environment, the only thing I needed to change to get the disks to spin down was adding the -XX:-UsePerfData option on the java command.

The MinimServer Docker image is used on other platforms as well as Synology. This option might not be needed for these other platforms and could possibly impact performance. (I haven't been able to find a clear description of what performance impact setting this option might have.) I think the current arrangement of enabling the user to set this option if required is a reasonable solution for this issue.

[MarcGPV]

(01-09-2022 21:32)simoncn Wrote:  In my Synology test environment, the only thing I needed to change to get the disks to spin down was adding the -XX:-UsePerfData option on the java command.

The MinimServer Docker image is used on other platforms as well as Synology. This option might not be needed for these other platforms and could possibly impact performance. (I haven't been able to find a clear description of what performance impact setting this option might have.) I think the current arrangement of enabling the user to set this option if required is a reasonable solution for this issue.

Sorry for this question from a dummy in Docker & Containers, but how to add this additional option?
Can this be done in the GUI of the Synology Container Manager app?
I am struggling with the same phenomenon that my NAS (DS224+) does not go into (deep) sleep, despite no user-activity whatsoever during several hours. But when deleting the container again the NAS goes into standby/sleep as set up in the control panel.
Thanks!

[simoncn]

To run the container instance of MinimServer with this option, do the following:

1) Open a Terminal window for the container. In the Synology Docker package, you can do this by double-clicking the container, selecting Terminal, clicking Create and selecting bash. I don't currently have a NAS that can run the Synology Container Manager package, so I can't confirm whether the procedure is the same for this.

2) In the Terminal window, run this command:
echo "javaopts = -XX:-UsePerfData" >/opt/minimserver/etc/minimstart.conf

3) Stop and restart the container

4) Check the MinimServer log to make sure this option was used when starting Java. You should see the following lines at the start of the log:
MinimServer 2.2 update 245, Copyright © 2012-2023 Simon Nash. All rights reserved.
OpenJDK Runtime Environment (build 14.0.1+7)
OpenJDK 64-Bit Server VM (build 14.0.1+7, mixed mode, sharing)
Java runtime options: -XX:-UsePerfData
Platform default charset is UTF-8
System platform is linux-x64

[MarcGPV]

Thanks SimonCN for the info and help.
But actually I did not explain my problem correctly (sorry, my mistake...):
I migrated from my old Synology NAS (DSM 6.x) to a new one (DS224+, running under DSM 7.2).
On the new NAS I had MinimServer already running as native Synology app, not containerized, and this works well: the NAS goes into sleep after the defined time of non-activity.
I'm now also using BubbleUpnp-server to emulate OpenHome-protocol to reach my network-players via the Lumin-app, but BubbleUpnp can only run in a container under DSM 7.x. This is also working nicely, but now my NAS stays always "on", even if no activity whatsoever.
So, in my observation, it looks like BubbleUpnpserver (or it's collaboration with Minimserver?) is causing the read/write NAS-activity every 30 seconds.
I added the -XX:-UsePerfData option on the java command for BubbleUpnp via a slight change on your recommended instruction but it does not give any different behaviour, and nothing visible in the BubbleUpnp-log neither.
I guess I need to reach out to the BubbleUpnp-community, unless somebody following this thread has experienced the same... and found a solution...?

[simoncn]

If you stop the BubbleUPnP container, does this fix the problem with disk activity? If so, this shows the problem is caused by the BubbleUPnP container.

[MarcGPV]

(15-11-2023 11:21)simoncn Wrote:  If you stop the BubbleUPnP container, does this fix the problem with disk activity? If so, this shows the problem is caused by the BubbleUPnP container.

Yes indeed, the NAS goes asleep (after the defined interval) if I stop the BubbleUpnp container.

[simbun]

(15-11-2023 13:29)MarcGPV Wrote:  Yes indeed, the NAS goes asleep (after the defined interval) if I stop the BubbleUpnp container.

Have you tried disabling 'Log to file'?

[MarcGPV]

(15-11-2023 13:47)simbun Wrote:  

(15-11-2023 13:29)MarcGPV Wrote:  Yes indeed, the NAS goes asleep (after the defined interval) if I stop the BubbleUpnp container.

Have you tried disabling 'Log to file'?

Yep, I had done that already (and did it again after each new build of the container).
I also ran the following command in a terminal window (inspired by the advice above):
echo "javaopts = -XX:-UsePerfData" >/opt/bubbleupnpserver/bubbleupnpstart.conf
The instruction did not give an error-message in the Terminal window, and nothing particular in the log-file of the container (AFAICS...), but so far no changed behaviour... but I need to allow the NAS again to stay idle for a period now.
I'm also trying to define environment variables for the healthcheck and log-driver variables (export into JSON-file, change manually via notepad, and import again) but I'm not good in that... and so far no difference...