Threaded Mode | Linear Mode

simoncn

A fix is available now. To install the fix, exit MinimServer and then relaunch it. MinimStreamer should update automatically from version 2.1.5 to version 2.1.6.

The logs that were posted (many thanks) show that the problem was caused by an internal test version of 2.1.5 being accidentally published via the updates server instead of the correct final release version. The new version 2.1.6 contains the correct final release code.

simoncn

(Today 11:57)Klaus57 Wrote: Unfortunately, I cannot confirm this; even after a restart, there is no change in the error behavior.

Do you have MinimStreamer 2.1.5 or 2.1.6 installed? The MinimServer log should show this.

You need to exit MinimServer completely and then relaunch it. A restart from the minim icon is not sufficient. Also, you need to have autoUpdate enabled (the default setting).

Klaus57

Sorry Simon, my reply crossed with yours. I had responded to Marnix Morsink—suggesting a "NAS restart"—but that action didn't help. I haven't yet installed the latest update that was provided.

Lex

I did the update, but problem still present.
current version that has the issue is 276.

Klaus57

I can now confirm that everything is working again; I did have to completely reinstall one Docker instance, but it wasn't much trouble.

simoncn

(Today 12:32)Lex Wrote: I did the update, but problem still present.
current version that has the issue is 276.

The problem isn't caused by MinimServer update 276. It is caused by MinimStreamer 2.1.5.

To fix it, MinimStreamer needs to be updated to 2.1.6. This happens automatically when MinimServer is relaunched with .autoUpdate set to true.

Lex

OK, that may be true. But minimstreamer 2.1.6 then still has the issue for me.

Lex

The loop is running wild. Minimwatch is not responding anymore. Is there a way to stop the Minimserver service from my NAS?

Klaus57

If it’s a native app installation, there will likely be some form of "App Station" on the NAS; I would stop the MS [application] there.
If it’s a Docker installation, there will surely be some kind of "Container Station"—you should stop the MS container there as well.
In my view, the only remaining option is to uninstall and reinstall.
As I mentioned in my previous post, I encountered this same issue with a container instance (it was stuck in an infinite loop in the log file); I stopped the container, deleted it, and reinstalled it—that solved the problem.
However, Simon might have a more suitable solution, so I would suggest waiting for his input.

Stake

No problems with 276 on my QNAP.