Posts: 58
Threads: 7
Joined: May 2023
Reputation:
2
01-30-2024, 12:58 PM
(This post was last modified: 01-31-2024, 01:04 PM by Tim Curtis.
Edit Reason: Improve thread title
)
Hi,
after some time I have updated my Moode installation. Debian wanted to keep back some of the updates, but I forced it to do it anyways.
First I had quite some problems with the Camilla DSP config files not being valid, which after some doctoring I was able to solve (the format seems to have changed quite a bit).
The problem that I have not been able to solve yet is an MPD error, "json.parse unexpected character at line 1 column 1 of the json data". I tried looking in the different normal log files to determine which json file this might be, but to no avail. Where can I find the source of this problem? Btw., this does not stop MPD, after showing the error a few times MPD continues to work without further problems.
And a minor thing: While looking through the logs, I saw the following error: "Error executing camilla_exit_cmd /usr/local/bin/cdspstorevolume". Is there a way to correct that?
Sorry for not being more specific, but I didn't take any notes of the exact state of my installation beforehand...
Cheers, Joe
Posts: 13,431
Threads: 305
Joined: Mar 2018
Reputation:
545
If you mean you disabled the package locks and performed an apt update/upgrade then your installation is broken and can't be fixed. In this broken state volume is probably unsafe so if you play anything it's at your own risk.
The only option is to re-flash with a fresh moOde image and respect the package locks. They are there to prevent these critical packages from being updated.
Btw, moOde has never been apt upgrade safe. The only supported upgrade method is via the in-place update offered in System Config.
Posts: 58
Threads: 7
Joined: May 2023
Reputation:
2
Ah, ok, I didn't know that. Then this means a new install at some time in the future. Nonetheless, can I fix these problems in my installation and if it is possible, how?
Cheers, Joe
Posts: 58
Threads: 7
Joined: May 2023
Reputation:
2
Btw., the MPD error does not show up if I simply restart the MPD daemon, only when I reboot the whole system...
Cheers, Joe
Posts: 1,281
Threads: 24
Joined: Jun 2022
Reputation:
42
(01-30-2024, 01:16 PM)jbaumann Wrote: Ah, ok, I didn't know that. Then this means a new install at some time in the future. Nonetheless, can I fix these problems in my installation and if it is possible, how?
Cheers, Joe
It may require too long to fix your current installation; you are better off a brand new image with the latest 8.3.7
NOTE:
1. read the installation notes
2. read them again, because you may still think they are the same as few years ago, and they are not!
3. use Raspberry Imager, not any other flashing tool such as Balena Etcher and the like.
Posts: 58
Threads: 7
Joined: May 2023
Reputation:
2
Thank you, @ Nutul, I will do that (especially reading the installation notes).
For me that point is that playing around with the installation allows me to better understand the inner working of it. And this is something that I value. I know that doing the whole installation again takes maybe 30min, but where is the fun in that?
Btw., it seems I got rid of the json problem, probably by saving some of the configuration details from the GUI.
Cheers, Joe
Posts: 58
Threads: 7
Joined: May 2023
Reputation:
2
Instead of manually copying the configuration entries, I assume I can use moodeutl -e to generate a moodecfg.ini that contains the necessary information (apart from the camilladsp config), right? Then it would be even simpler than I thought...
Cheers, Joe
Posts: 1,281
Threads: 24
Joined: Jun 2022
Reputation:
42
(01-30-2024, 04:52 PM)jbaumann Wrote: Instead of manually copying the configuration entries, I assume I can use moodeutl -e to generate a moodecfg.ini that contains the necessary information (apart from the camilladsp config), right? Then it would be even simpler than I thought...
Cheers, Joe
Even simpler: you can do a backup, download it, then restore it in the new installation.
See in "m" => Configuration => System down the page.
Posts: 571
Threads: 16
Joined: Apr 2020
Reputation:
23
@ jbaumann that the system didn't allow upgrading of some packages. .. that was already a hint by it self.
Such packages upgrade locks are used to prevent breaking the your system. What exactly happened after a forced upgrade.
moode audio player consists about a large bunch of packages which have a delicate relation to each other and especially the moode audio player software itself.
Posts: 58
Threads: 7
Joined: May 2023
Reputation:
2
@ bitlab I know, I have been working with Debian for the last 25 years or so. And I have reasonable trust in my skills to repair any Debian installation that hasn't been foobar'd. And every time I do this I learn something, so these package locks are not as scary to me.
The main surprise for me was that the Moode update shouldn't be done via command line (i.e., apt), but using the GUI. And this obviously thwarts my normal strategies for repairing a system :-)
The only thing that I would like to understand before I re-install on a new sdcard is what the "json.parse" error means (yes, it is back). The normal sys logs show nothing relevant, the mpd log shows nothing relevant, and I simply would like to know where to look...
TL;DR: I have learned a lot from the botched update. I have, with your help, a very simply strategy for setting up the same system from scratch. I still have a few questions, and the answers would help me understand the system better.
Cheers, Joe
|
