Hi,
Firstly, a massive thank you to mherger and the LMS community for
keeping this platform up and running. Its brilliant that I can still use
my squeezebox setup so long after logitech ceased support.
I've been running LMS on my Vero4k running OSMC without issue for ages.
Last week I upgraded OSMC to the latest August '21 image and LMS refused
to start. OSMC is built on Debian Buster and is the Vero4k is armhf.
The server.log is not very helpful. This is all it contains:
Code:
--------------------
[21-08-30 09:43:27.5839] main::init (390) Starting Logitech Media Server
(v8.2.1, 1628483320, Mon Aug 9 06:46:12 CEST 2021) perl 5.028001 -
arm-linux-gnueabihf-thread-multi-64int
--------------------
systemctl status logitechmediaserver reports:
Code:
--------------------
osmc@vero4k:~$ systemctl status logitechmediaserver
* logitechmediaserver.service - Logitech Media Server
Loaded: loaded (/lib/systemd/system/logitechmediaserver.service; enabled;
vendor preset: enabled)
Active: failed (Result: signal) since Mon 2021-08-30 09:43:29 BST; 12min ago
Process: 13783 ExecStart=/usr/sbin/squeezeboxserver --prefsdir $PREFSDIR
--logdir $LOGDIR --cachedir $CACHEDIR --ch
Main PID: 13783 (code=killed, signal=ILL)
Aug 30 09:43:23 vero4k systemd[1]: Started Logitech Media Server.
Aug 30 09:43:25 vero4k squeezeboxserver[13783]: dirsFor: Didn't find a match
request: [scprefs]
Aug 30 09:43:27 vero4k squeezeboxserver[13783]: dirsFor: Didn't find a match
request: [videos]
Aug 30 09:43:27 vero4k squeezeboxserver[13783]: dirsFor: Didn't find a match
request: [pictures]
Aug 30 09:43:29 vero4k systemd[1]: logitechmediaserver.service: Main process
exited, code=killed, status=4/ILL
Aug 30 09:43:29 vero4k systemd[1]: logitechmediaserver.service: Failed with
result 'signal'.
--------------------
and journalctl -xe shows:
Code:
--------------------
Aug 30 09:43:23 vero4k systemd[1]: Started Logitech Media Server.
-- Subject: A start job for unit logitechmediaserver.service has finished
successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit logitechmediaserver.service has finished successfully.
--
-- The job identifier is 2096.
Aug 30 09:43:23 vero4k systemd[1]: Reloading.
Aug 30 09:43:24 vero4k systemd[1]: /lib/systemd/system/smbd.service:9:
PIDFile= references path below legacy director
Aug 30 09:43:24 vero4k systemd[1]: /lib/systemd/system/nmbd.service:9:
PIDFile= references path below legacy director
Aug 30 09:43:24 vero4k systemd[1]:
/lib/systemd/system/[email protected]:6: PIDFile= references path below
legacy
Aug 30 09:43:24 vero4k sudo[13668]: pam_unix(sudo:session): session closed
for user root
Aug 30 09:43:25 vero4k squeezeboxserver[13783]: dirsFor: Didn't find a match
request: [scprefs]
Aug 30 09:43:27 vero4k squeezeboxserver[13783]: dirsFor: Didn't find a match
request: [videos]
Aug 30 09:43:27 vero4k squeezeboxserver[13783]: dirsFor: Didn't find a match
request: [pictures]
Aug 30 09:43:29 vero4k systemd[1]: logitechmediaserver.service: Main process
exited, code=killed, status=4/ILL
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit logitechmediaserver.service has
exited.
--
-- The process' exit code is 'killed' and its exit status is 4.
Aug 30 09:43:29 vero4k systemd[1]: logitechmediaserver.service: Failed with
result 'signal'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit logitechmediaserver.service has entered the 'failed' state with
result 'signal'.
--------------------
Are there any other log locations I should be looking at to get an
indication as to what is going on?
At first I was thinking it was because the version of perl had increased
to 5.28.1 I've seen posts about, I think it was, Synology users who's
LMS broke when the NAS updated to 5.28. But I've also seen reference on
this forum of someone running 'LMS on Debian Bullseye with perl 5.32.1'
(https://forums.slimdevices.com/showthread.php?115024-debian-11-bullseye-issues&p=1031429&viewfull=1#post1031429)
successfully. So is there a problem with perl 5.28 or should LMS work
okay on it?
If anyone is able to assist it would be massively appreciated. I've
spent many hours over many evenings trying to get this sorted out. I've
tried perlbrew to build an older install of perl, but then found out
this was for my user only and not system wide. I've tried various
docker containers, starting with the offical LMS Community one, but they
all fail with an illegal instruction. Most recently I've reinstalled my
vero4k from scratch followed by a native install of LMS but that hasn't
helped either.
Any ideas anybody?
Thanks!
------------------------------------------------------------------------
intraclast's Profile: http://forums.slimdevices.com/member.php?userid=41806
View this thread: http://forums.slimdevices.com/showthread.php?t=115062
_______________________________________________
Squeezecenter mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/squeezecenter
