Post Reply 
Integrity check failed ....
02-07-2022, 11:21
Post: #1
Integrity check failed ....
First: thanks, Simon, for sorting the license issue.

I now have a further problem in that after a reboot of my Raspberry Pi4 MinimServer didn't appear on the tray (it was set on installation to start on boot) so I started it from the apps menu, whereupon the icon appeared, but turned red. Going to the web config page I found status: "Failed", with a red "Integrity check failed for file minimserver.config; select a profile and relaunch." I have only the one, default, profile, which I selected and relaunched, but to no avail.

I've read through the long thread from Feb 2021 where mightyoakbob had a similar problem, but could see nothing that might be relevant to my situation.

What might be relevant is:
1. I've had problems recently with the RPi4,which seem to have been caused by a faulty SSD enclosure (I run the Pi from a USB SSD drive). As part of the troubleshooting process I cloned the drive contents to another SSD in an enclosure I knew was sound. Having found the problem was with the enclosure, I'm now back on the original drive but in a new enclosure. I'm wondering if there's a possibility that moving back and forth between the two drives (with supposedly identical contents?) has somehow confused MinimServer?
2. I've just installed MPD and upmpdcli on the Pi and have been tweaking config files for them. I don't see how/why this should affect MS, but they are all part of the audio software ecology.
Find all posts by this user
Quote this message in a reply
02-07-2022, 12:19 (This post was last modified: 02-07-2022 12:20 by simoncn.)
Post: #2
RE: Integrity check failed ....
This usually means you have manually edited the minimserver.config file. You can manually edit .profile files but not the .config file.

You should be able to recover from this by deleting the minimserver.config and minimserver.config.save files, then relaunching MinimServer. When MinimServer is running, you can apply configuration settings either from the Properties dialog or by importing a .profile file.
Find all posts by this user
Quote this message in a reply
02-07-2022, 15:11 (This post was last modified: 02-07-2022 15:20 by nickc.)
Post: #3
RE: Integrity check failed ....
(02-07-2022 12:19)simoncn Wrote:  This usually means you have manually edited the minimserver.config file. You can manually edit .profile files but not the .config file.

You should be able to recover from this by deleting the minimserver.config and minimserver.config.save files, then relaunching MinimServer. When MinimServer is running, you can apply configuration settings either from the Properties dialog or by importing a .profile file.

Thank you - that sorted it. I had to reactivate my license again, but now everything is as it should be.

Aha! No sooner had I posted that reply, than a pop-up appeared on my desktop (not of the RPi4, but the linux desktop running MinimWatch) saying " MinimStreamer has been disabled because your updates license has expired. Etc" . Yet I had just checked the license status before replying just now and it showed the full license as active. And on the actual RPi desktop (which I'm monitoring via VNC), the MS icon remains green. I suspect it will turn red again, though, if I restart the RPi (which I don't want to do right now). I'm wondering if there is some kind of conflict between MinimWatch on my linux desktop (which may be looking for the instance of MS that was on the other drive?) and the actual instance of MS running on the Rpi. Is that possible?
Find all posts by this user
Quote this message in a reply
02-07-2022, 22:24
Post: #4
RE: Integrity check failed ....
Your license for updates and MinimStreamer does not expire until 28th July. If you open the MinimServer configuration web page (select Configure from MinimWatch) and select the License tab, what does this say?
Find all posts by this user
Quote this message in a reply
03-07-2022, 08:04
Post: #5
RE: Integrity check failed ....
(02-07-2022 22:24)simoncn Wrote:  Your license for updates and MinimStreamer does not expire until 28th July. If you open the MinimServer configuration web page (select Configure from MinimWatch) and select the License tab, what does this say?

I've still not restarted the RPi4, which I leave running continuously much of the time. It is still showing a green MS icon and the Configure > License page shows the correct information as you state it above.

But when I booted up my linux desktop pc this morning I got the same message I reported yesterday about MinimStreamer being disabled due to updates license expiry. Yet accessing the Configuration > License page via the MinimWatch icon on that desktop, I get the same, correct status report:

"Your MinimServer license type is Full, with no expiry date.
Your MinimStreamer license expires on 28 July 2022 at 12:06:08 BST.
Your license includes updates until 28 July 2022 at 12:06:08 BST.
You are using 2 of 3 license activations (click here for details) "

Weird!

Without rebooting the RPi, I've restarted MS from the Pi desktop (via VNC) and it stays green.

Now I've rebooted the Rpi and see no MS icon in the top tray (even though, as I reported in my OP, it is set to launch at boot). Launching it from the menu, the icon appears, but is grey. I've waited a minute or two (there are only a few test files in the music folder) but it hasn't changed so far.
Find all posts by this user
Quote this message in a reply
04-07-2022, 07:40 (This post was last modified: 04-07-2022 07:41 by simoncn.)
Post: #6
RE: Integrity check failed ....
As I understand it, your Linux desktop is running MinimWatch and your RPi4 is running MinimServer. This means the messages you see on your Linux desktop about MinimStreamer being disabled are coming from MinimServer running on your RPi4.

You have confirmed that MinimServer on the RPi4 has the correct expiry date (shown on the License tab). What is the system date on this machine? If it is set to a date later than the expiry date, your will get the "MinimStreamer is disabled" message.

Which version of Raspbian or Raspberry Pi OS are you running on the RPi4? There is a known issue with the latest version of Raspberry Pi OS (bullseye) that could prevent MinimServer from starting at boot. I am working on a fix for this. The could explain the grey icon but is not related to the "MinimStreamer is disabled" message.
Find all posts by this user
Quote this message in a reply
04-07-2022, 08:53 (This post was last modified: 04-07-2022 08:55 by nickc.)
Post: #7
RE: Integrity check failed ....
(04-07-2022 07:40)simoncn Wrote:  As I understand it, your Linux desktop is running MinimWatch and your RPi4 is running MinimServer. This means the messages you see on your Linux desktop about MinimStreamer being disabled are coming from MinimServer running on your RPi4.

You have confirmed that MinimServer on the RPi4 has the correct expiry date (shown on the License tab). What is the system date on this machine? If it is set to a date later than the expiry date, your will get the "MinimStreamer is disabled" message.

Which version of Raspbian or Raspberry Pi OS are you running on the RPi4? There is a known issue with the latest version of Raspberry Pi OS (bullseye) that could prevent MinimServer from starting at boot. I am working on a fix for this. The could explain the grey icon but is not related to the "MinimStreamer is disabled" message.

Thanks for that.
To take your last question first: I am running an up to date version of 'Bullseye', so as you suggest, that probably explains MS not starting from boot.

The date on the RPi4 is correct:
Code:
nick@RPi4:~ $ timedatectl
               Local time: Mon 2022-07-04 08:04:16 BST
           Universal time: Mon 2022-07-04 07:04:16 UTC
                 RTC time: n/a
                Time zone: Europe/London (BST, +0100)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no
(The time and zone are incorrect, though, as I'm in France! But that's never been an issue before.)

I rebooted the RPi4 last night and, rather to my surprise, when I launched MS from the menu (again it didn't auto-launch) it immediately displayed a green icon. I left it running all night and it's still green and Configure > License shows correct information. However, when I first opened Configure it defaulted as usual to the Status tab and beneath the line:
"Media server status for MinimServer[RPi4.2]: Running"
there was a line in red font saying MinimServer full license is incorrect. I can't quote exactly as after clicking the License tab and seeing all was as it should be, I returned to the Status tab to find the red message had disappeared.

All this I was observing on the RPi4 desktop itself, viewed via VNC on my Linux desktop, as you correctly stated. Oddly though, when I booted up my Linux desktop this morning I saw that the MinimWatch icon for MS in the RPi immediately displayed red! So I have MinimWatch on my Linux desktop saying something's wrong and MS itself on the RPi4 saying everything's OK! (And I've just restarted MS from it's drop-down menu on the icon on the RPi4 desktop, and it's restarted smoothly and stays green.)
Find all posts by this user
Quote this message in a reply
04-07-2022, 10:24
Post: #8
RE: Integrity check failed ....
(04-07-2022 08:53)nickc Wrote:  (The time and zone are incorrect, though, as I'm in France! But that's never been an issue before.)

The "MinimStreamer is disabled" problem would not be caused by an incorrect time or timezone, only an incorrect date (except on the expiry date itself).

As this problem seems to have gone away now (but see below), it will have to remain unsolved unless it happens again.

Quote:Oddly though, when I booted up my Linux desktop this morning I saw that the MinimWatch icon for MS in the RPi immediately displayed red!

Saying the icon is red isn't enough information for me to understand and help solve the problem. If this happens, please note down and post the error mesage that accompanies the red icon.
Find all posts by this user
Quote this message in a reply
04-07-2022, 14:33
Post: #9
RE: Integrity check failed ....
Thanks. Happy to report both icons - MinimWatch on Linux desktop and MinimServer on RPi4 desktop now showing green and MS working as normal.

"If this happens, please note down and post the error message that accompanies the red icon. " Will do. Once again, thanks for your help.
Find all posts by this user
Quote this message in a reply
05-07-2022, 15:02
Post: #10
RE: Integrity check failed ....
(04-07-2022 14:33)nickc Wrote:  Thanks. Happy to report both icons - MinimWatch on Linux desktop and MinimServer on RPi4 desktop now showing green and MS working as normal.

"If this happens, please note down and post the error message that accompanies the red icon. " Will do. Once again, thanks for your help.

It happened again this morning.

The RPi4 with MS had been running all night and when I booted up my Linux desktop I could see (via VNC) that MS was running correctly on the Pi and the MinimWatch icon on the Linux desktop was also green. But I needed to restart the RPi4, whereupon the MinimWatch icon on the Linux desktop disappeared and similarly on the RPi4 there was no icon. I realised this must be due to the issue you're trying to fix, so I launched MS from the menus on the RPi4, whereupon the MinimWatch icon on my Linux desktop went red, with a pop-up message:

"MinimServer[RPi4]: Integrity check failed for file minimserver.config; select a profile and relaunch"

Yet, to my surprise, on the RPi4 desktop MS launched to a green icon and the Configure > License web pages showed everything correctly.

This is the situation I still have: MinimWatch on my Linux desktop showing red and failed integrity check, while MS itself on my RPi4 desktop showing it running as it should.
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 1 Guest(s)