Minimsever update won't run

[NPZwar]

Greetings to all. I am experiencing the same problem.

Yesterday, MinimServer suddenly stopped working on my QNAP NAS. It wouldn't start at all. A look at the error log suggested a Java issue (MinimServer expected a newer Java version), so I first tried reinstalling Java, but there was no newer Java version within QNAP. For a variety of reasons, I run only "certified" programs on the NAS, so I couldn't just install an "outside" Java pack. After some digging, I realized the native install might have been broken or incompatible because of a recent update.
To get things running again, I set up MinimServer inside a container. I really knew nothing about containers and since yesterday, I know a lot more (though not nearly enough.). Anyway, that has done the trick so for, MinimServer has launched properly and started indexing as expected.

Good new is: it is currently running.

Now I'm not sure whether running it in a docker container makes any real difference? Pros and cons? I don't notice any performance issues yet, but of course, I have not been able to listen to a lot of music yet. For now at least it is back up and working.

Question: can I try out whether it's running now without the container as well? Now that I have it run in the container, not sure whether I should try to run it "native" again.

[Klaus57]

Just for your information: In my environment - QNAP (including Container Version) - update 261 works without any problems now.

[NPZwar]

(11-09-2025 08:51)Klaus57 Wrote:  Just for your information: In my environment - QNAP (including Container Version) - update 261 works without any problems now.

Can confirm. In my setup 261 works within the container. As I said, I created the container yesterday after all else failed.

[simoncn]

MinimServer update 261 fixes the startup problem (Java version mismatch) for all environments, both inside and outside containers.

[NPZwar]

That is ace support!

Well, if anything, I have yesterday now learned hard and fast how to setup docker containers on my NAS and what else they might be useful for. So it's wasn't all bad. :-)

[MarekMalinie]

(10-09-2025 18:34)simoncn Wrote:  To recover from the problem on QNAP, do the following:

1) In QNAP QTS App Center, remove MinimServer
2) In QNAP QTS App Center, install MinimServer

I still have a message
Unexpected exception java.lang.IndexOutOfBoundsException: Index: 1, Size: 1

How can I restore the previous version of Minim Server 259?
Or what else should I do?
I am asking for urgent help

[gbrist]

I'm also having similar problems on my Synology DS118. Keep getting:
Unexpected exception java.lang.IndexOutOfBoundsException: Index 1 out of bounds for length 1
Using MinimServer 2.2 update 261
Synology is at: DSM 7.2.2-72806 Update 4
Been using Minimserver for a long time..first time with this sort of problem.
Tried suggestions in this article and also completely uninstalled and reinstalled Minimserver. Also restarted NAS etc etc
I can however use Asset ok. I used to use Asset before I purchased Minimserver...so I just re activated it)..just fyi..
Hopefully there is a fix please?
Thanks
Steve

[simoncn]

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.

[simoncn]

(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.

[steamfan]

(10-09-2025 18:43)simoncn Wrote:  

(10-09-2025 17:58)steamfan Wrote:  But one question remains: how do I update my MinimServer installations in the Container Manager?

1) In the container, delete the entire contents of the folder /opt/minimserver/libext. Don't remove the folder itself.
2) Stop the container and restart it

I haven't tried this yet. Please let me know whether it worked.

I'm not sure if I understand you correctly. Do you mean that I should open a terminal window within Container Manager for the running MinimServer container? If so, this is not possible because the MinimServer container crashed yesterday after the update to version 260 and now crashes some seconds after it has been started. So I have no access to the folder /opt/minimserver/libext

I will try to export the settings of the MinimServer container and import it into a new container.