Minimsever update won't run

[steamfan]

The export-import approach did not work. i got error messages while importing. It was faster to set up a new container from scratch.
So now my MinimServers are up and running again

[Nick P]

(11-09-2025 13:47)simoncn Wrote:  There is a fix for this IndexOutOfBoundsException error in MinimServer update 262, just released. You can install this update from the MinimServer configuration web page.

All working again.

Thank you Simon.

[MarekMalinie]

It's green

[MarekMalinie]

All working again.

Thank you Simon.

Best Regards
Marek

[simoncn]

(11-09-2025 15:53)steamfan Wrote:  The export-import approach did not work. i got error messages while importing. It was faster to set up a new container from scratch.
So now my MinimServers are up and running again

Thanks for letting me know. I hadn't realised that you can't start a shell in the container unless the container is running with its designated application.

[simoncn]

For all who have been affected by the java.lang.IndexOutOfBoundsException bug, check this thread for information about a change in update 260 that might affect you.

If you have questions about this, please post them to the above-referenced thread.

[paulM]

(11-09-2025 14:02)simoncn Wrote:  

(10-09-2025 22:57)paulM Wrote:  I tried this but only got as far as instruction 1). The Minimserver icon then vanished from the AppCentre, so there is now no icon in the AppCentre from which to install it again.

In the App Center left sidebar, select Entertainment. This shows a MinimServer icon with an Install button.

Thanks for the advice Simon, but I've tried it and my QNAP (HS251) does not have an install icon in the Entertainment tab.

[simoncn]

QNAP has a policy of removing App Center icons for third-party packages on "older" versions of QTS. If you are able to update QTS on your HS251 to a newer version, you might be able to see the icon. If not, you need to download MinimServer manually as described in this section.

[simoncn]

(11-09-2025 15:53)steamfan Wrote:  The export-import approach did not work. i got error messages while importing. It was faster to set up a new container from scratch.
So now my MinimServers are up and running again

I have found a possible solution for this. I have made a change to the MinimServer script launched by the container. The updated script checks for a launch error and waits for 5 minutes before exiting. This gives enough time for the user to start a terminal inside the container and either retrieve important data or make changes to fix the problem.

The only problem with my current implementation is that no error message is shown to the user until the 5 minute timeout has expired. There is a message in the container log but the user needs to open the container log to see it. This means the user will think the container is hung (or very slow) unless they open the container log.

Do you know of any way for a container to show a message that pops up in Synology Container Manager with no user action needed? Ideally this would work for other container managers as well.

Edit: I have another idea. As the container has a mounted volume for the host MinimServer shared folder, there could be a setting in a file there to tell the container to wait for a specified time after abnormal exit. The user would see the error, then activate this setting, then restart the container with enough wait time to do whatever recovery/repair is needed.

[gbrist]

Hi Simon.. 263 seems to have solved my issues.. Just FYI I have 4 NAS's. The only one that seemed to be affected with the issue (Unexpected exception java.lang.IndexOutOfBoundsException: Index 1 out of bounds for length 1) was one NAS that had a lot of music files where the disc numbering was non existent.
The other 3 had all disc numbering applied to the music files..
All now running on 263.
Thanks again.