Plexamp Raspberry Pi 4.3 bug?

Context:

  • I tried to upgrade from 4.2 to 4.3 via odinb’s (awesome) script, this didn’t work for some reason.
  • I decided to do a fresh install. I got things working again but I’m puzzled and concerned with a couple of error messages, see below

Question: Is this an issue or will this be an issue? Can/should I address this?

pi@raspberrypi:~ $ systemctl --user enable plexamp.service && systemctl --user start plexamp.service
Created symlink /home/pi/.config/systemd/user/basic.target.wants/plexamp.service → /home/pi/.config/systemd/user/plexamp.service.
Failed to start plexamp.service: Unit network-online.target not found.

pi@raspberrypi:~ $ node /home/pi/plexamp/js/index.js
Starting Plexamp 4.3.0
DEVICE: No provider for source 13f113a4cb0031f535745b2c7ee8783fafcXXXXX

pi@raspberrypi:~ $ systemctl --user restart plexamp.service && systemctl --user status plexamp.service
Failed to restart plexamp.service: Unit network-online.target not found.

systemctl --user status plexamp.service does tell me that the service is active but also shows the same ‘DEVICE: no provider’ error…

● plexamp.service - Plexamp
Loaded: loaded (/home/pi/.config/systemd/user/plexamp.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2022-09-18 10:17:07 CEST; 1h 18min ago
Main PID: 640 (node)
Tasks: 39 (limit: 1830)
CPU: 7min 38.581s
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/plexamp.service
└─640 /usr/bin/node /home/pi/plexamp/js/index.js

Sep 18 10:17:07 raspberrypi systemd[601]: Started Plexamp.
Sep 18 10:17:10 raspberrypi node[640]: Starting Plexamp 4.3.0
Sep 18 10:17:10 raspberrypi node[640]: DEVICE: No provider for source 13f113a4cb0031f535745b2c7XXXXX>
~

you can generally ignore “DEVICE: No provider for source …” and other messages that appear after manually starting Plexamp

and regarding the network-online.target error, latest installer from @odinb1 addresses this with updates to the systemd service

1 Like

Correct! Just re-run the installer, choose your user, cleanup for upgrade and run the upgrade. Should be fixed after that!

OK, many thanks!!

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.