MinimServer won't start on Raspberry Pi server since last update

[Bard]

This post is simply to record that MS is failing to start on a Raspberry Pi server, as well as in the contexts mentioned in other recent posts.

Is there a simple way to roll back, with MinimWatch (on the Win 10 PC I use to control things) showing grey?

[simoncn]

For rollback instructions, see this post.

Is the problem just affecting Raspberry Pi for you or does it also happen on other platforms?

[Bard]

(10-12-2017 15:03)simoncn Wrote:  For rollback instructions, see this post.

Is the problem just affecting Raspberry Pi for you or does it also happen on other platforms?

To answer your question, I'm only running MinimServer on a Pi; MinimWatch runs on a Windows 10 PC.

Thanks for the pointer to info about rolling back to an earlier version; I'll try that.

[Bard]

Hello Simon
I followed the instructions to roll back to minimserver-0.8-update-110, but it hasn't fixed the problem: the MinimWatch icon is still grey, and MinimServer still won't launch.

[simoncn]

There is a fix for update 111 available now. Please follow the instructions in this post.

[Tell]

Simon / Bard snap.

I've been on the floor, got the keyboard plugged in and mouse just to check whether self help isn't possible. I was getting the error GDBUS.ERROR.ORG.free.desktop.PolicyKit1.Error.Failed

I followed this one

https://www.raspberrypi.org/forums/viewt...p?t=100118

Didn't sort it but that error went away.

I've also got a Kernal Lacks Cgroups - I don't know whether that has anything to do with it... sure it wasn't there before.

I'll do post #37 now.

[Tell]

OK now working but in your step

2) After you get the startup error, type: remove minimserver-0.8-update-111

It said no package or something, read the other thread and saw people were talking about a 112 release which also didn't work. Thought I might have that instead so changed to

2) After you get the startup error, type: remove minimserver-0.8-update-112

So all fine. Did a reboot of the Raspberry Pi and it all came back again.

Now on another Raspberry Pi that hasn't had the update package executed yet via Minimwatch do I need to do anything special or will it pick up the updated version ?.

Thanks.

[Bard]

After some experimentation I've found that the latest 112 update has made no improvement on my Pi server, but rolling back to 111 with a manual remove (112) and install (111) has restored normality. I don't know whether MS would have found it automatically after removing 112; I didn't wait to find out.

Hope this helps somebody ... !

[simoncn]

The is a small difference between updates 111 and 112 to fix a different problem and this should make no difference to the previous issue with the libstdc++ error when loading the ohNet library.

I think the problem is that you didn't remove update 111 before installing update 112 (see steps 2 and 3 of this post) and this would have left the bad version of the ohNet module on your system.

To fix this problem with update 112 installed, you can do the following:

1) From a command prompt, run minimserver/bin/startc
2) After you get the startup error, type: remove minimserver-0.8-update-112
3) Type: install minimserver-0.8-update-112
4) Type: relaunch
5) After MinimServer restarts successfully, type: exit

You should now be able to run MinimServer normally.