Latest updates break my pi players

Feb 19, 2024 Last reply: 2 years ago 15 Replies

I've been using the OS Pi OS Lite Dec 11th 2023 since it came out. It was fine.



Today after installing it I did the usual: sudo apt update sudo apt upgrade



I got an absolute torrent of updates/upgrades and now my MediaPlayer system does not function at all. It should have a web server for setting etc. and a player that should be vissible from open home apps but nothing.



It looks as though neither components is even starting.



Once added in to the builds are these updates permanent or do they sometimes cause issues and get pulled?



Thanks.



Bob.



A bit like what happened to me upgrading TO that release. (Dec 11th 2023)

Before I break MY system, will a *fresh* install plus full updates work?

Sorry to reply to myself.

As neither the web server or the player start up I started to think about Java, I think both are Java apps.

In the past I used java 11 with the command:

sudo apt install openjdk-11-jdk

That has stopped working, it gives the error:

The following packages have unmet dependencies: ca-certificates-java : Breaks: openjdk-11-jre-headless (<

11.0.19+7~1~) but 11.0.17+8-2 is to be installed E: Unable to correct problems, you have held broken packages.

So I found another install command. sudo apt install default-jdk

Which installed Java 17 with error but is it a good replacement?

Does this look like it might be the issue?

Thanks.

Bob.

First try starting the program from a terminal window (edit the main menu entry to find the command name if you don't know it), there will often be a very obvious error displayed.

Failing that in a terminal do a tail -f /var/log/syslog Then start the program again.

jdk-11 is end of life

Yes, there should be very little hasn't been updated to work with that.

You need to tell us, see above.

---druck

Right, I'm hoping that a putty window is sufficient but certainly no error when the manual start command is issued.

sudo /home/pi/mediaplayer/run.sh

pi@LinnPi-base1:~/mediaplayer/scripts/systemd $ tail -f /var/log/syslog tail: cannot open '/var/log/syslog' for reading: No such file or directory tail: no files remaining

There is a file mediaplayer.log but I cannot see a way to get this public so you can have a look.

Still nothing unfortunately.

Oh right.

Brain got ahead of fingers there. There was NO error.

Oh dear. I would not be surprised if MediaPlayer has not been updated.

Thanks.

Bob.

Again.

My player builds are done in blocks, the idea is that it helps a little with testing if you don't have to go back to the start every time. After each block is added, I save back the SD card.

Block01 working operating system with updates. Block02 Block01 + working Samba. Block03 Block02 + mpd + java block04 Block03 + media Player

So as Java looks a strong possibility I cleaned an SD card and installed Block02 from January build. All fine.

Tried to install mpd. No it's not having any of it.

E: Failed to fetch

formatting link
404 Not Found [IP: 93.93.128.193 80] E: Unable to fetch some archives, maybe run apt-get update or try with --fix-sing?

So changes have been made and things are really broken for me now.

Fortunately, I still have the working blocks from january although on block 04 is of any use apparently.

Bob.

Okay, if anyone would be interested enough to look at the mediaplayer log that would be great, thanks.

it's now at..

formatting link
had to change the type to txt from log which the web server didn't like and I've no idea why that pie thought it was summer time.

Thanks.

Bob.

FFS you've got one infested with systemd's journald and no rsyslog installed - in which case god help you.

---druck

You shouldn't need to run a mediaplayer as root, it is not a good thing to do.

---druck

From your log:

2024-02-19 16:05:39,769 [main] ERROR [org.rpi.mpdplayer.TCPConnector] java.net.ConnectException: Connection refused 2024-02-19 16:05:39,770 [Thread-0] ERROR [org.rpi.mpdplayer.TCPConnector] java.net.ConnectException: Connection refused 2024-02-19 16:05:39,774 [main] ERROR [org.rpi.mpdplayer.TCPConnector] java.net.ConnectException: Connection refused

Is there something wrong with networking on your Pi? Can you ping google.com?

It looks like you've configured this URL:

[org.rpi.config.Config] 'pins_service_url' : 'http://192.168.1.205:8088/PinServiceManager1/webapi/broadcast' I don't know what it does, but can you ping that IP (192.168.1.205)?

Theo

I don't think so.

Yes, no problem.

Neither do I. Pins is something I keep seeing mentioned in the Linn control app but I've never understood what it is, I've ignored it for years.

No, there is nothing there.

I manage IP addresses from the router and IPs:

02 to 99 are managed for various fixed devices. from 240 upwards is for NAS boxes and printers.

From 100 to 239 is not managed and is just for things which temporarily get plugged in with random allocation. So I've no idea what gave rise to the 202 address.

Do you think I should try to find where that is configured and remove it? Or, try and stop the usage of it.

Thanks.

Bob.

In the log, why is FATAL being used like INFO?

It makes me wonder what level of support this app gets, if the answer is very little, is it worth the effort?

There are very good media players for the rPi like mpv. What does this app give you?

I've no idea. :-)

I think that is the answer yes.

It's as near a perfect match for my needs as I'll get.

Plays music from MinimServer UPnP server. Also radio streams indexed from a play list on MinimServer. In essence that's it but the extra bonus is that it's an openhome player.

For my main hifi system I use a Linn streamer which has it's own apps which work with any openhome players so the same control point for all my players.

I did look briefly at volumio but the control point (when I looked) was quite basic, it was mostly text rather than graphical.

Bob.

Fair enough, I never got into the home streaming idea. I just have NAS and play music and video on the rPi, like I would on a normal PC.

Just in case anyone is interested in how this worked out. I'm not fully conversant with it but in general...

The author wrote the application to work on several platforms and in order to make that work he set the PATH required dynamically. Unfortunately, Java 17 stopped his method of doing that working. That's what he told me.

So he gave me a fix just for the pi.

In two files, run.sh and run_systemd.sh I had to add the single line:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$SCRIPTPATH/mediaplayer_lib/ohNet/linux/armv6hf

That fixed the problem for me.

Thanks for all the suggestions.

Cheers,

Bob.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required