I enabled INFO logging for Spotty. This morning I was woken by the
annoying default alarm on my Radio and sure enough the network indicator
was red. The alarm was set for 6.00am and in the past if the internet
was down for any reason the alarm would always sound at the correct time
but this time
mherger wrote:
> > This is still happening. This morning playback stopped for 8 minutes
> > then recovered. Nothing in server log.
>
> Are you using Spotty? If so, could you please enable INFO logging for
> Spotty and see whether there's been activity around when LMS is locking
>
> up? Also
slartibartfast wrote:
> To run this monitor I suppose I need to add the command line option
> when LMS is started. Is there an easy way to do that?
It varies according to how LMS is started. I'd expect Max2play to
provide a Web page in an "Advanced" section to enable you to specify
command
bpa wrote:
> The AnyEvent scheduler is just within LMS - it shares out the time
> between tasks looking after webpages, playing audio and other network
> access. So plugins have to play nice or it will just lockup LMS. Other
> application in the Max2play will be unaffected.
>
> As the AnyEvent
slartibartfast wrote:
> It is only LMS that hangs.
The AnyEvent scheduler is just within LMS - it shares out the time
between tasks looking after webpages, playing audio and other network
access. So plugins have to play nice or it will just lockup LMS. Other
application in the Max2play will be
bpa wrote:
> I would interpret this as your IO:Socket:SSL is up to date with your OS
> version/libSSL but then I guess it means lots of other users are OK with
> 2.044.
>
> However, as your system seems to lock up and it doesn't happen to many
> others - we have to look for the "edge"
slartibartfast wrote:
> Just tried updating and apparently I am up to date on the Pi.
I would interpret this as your IO:Socket:SSL is up to date with your OS
version/libSSL but then I guess it means lots of other users are OK with
2.044.
However, as your system seems to lock up and it doesn't
bpa wrote:
> I had to do an explicit apt get to get it updated. It has dependencies
> which may be holding it back.
>
> edit:
> My update was not on a Pi but an Ubuntu.Just tried updating and apparently I
> am up to date on the Pi.[image:
slartibartfast wrote:
> I do occasional apt-get upgrades. Doesn't IO:Socket:SSL get updated?
I had to do an explicit apt get to get it updated. It has dependencies
which may be holding it back.
edit:
My update was not on a Pi but an Ubuntu.
bpa wrote:
> 2.044 is 2.5 years old.
> If you accessing any site which uses TLS 1.3 - it may hang - not sure
> what the TLS fallback prcoeduire is.I do occasional apt-get upgrades. Doesn't
> IO:Socket:SSL get updated?
Sent from my SM-G900F using Tapatalk
slartibartfast wrote:
> IO:Socket:SSL 2.044 on a Pi3B. It normally happens while listening to
> Virgin Radio but probably only coincidence. I cannot remember it ever
> happening while playing local music.
2.044 is 2.5 years old.
If you accessing any site which uses TLS 1.3 - it may hang - not
bpa wrote:
> Just in case it is old https problem as https can results in very long
> hangups/delays.
> What version is your IO::Socket::SSL library ?IO:Socket:SSL 2.044 on a Pi3B.
> It normally happens while listening to
Virgin Radio but probably only coincidence. I cannot remember it ever
Just in case it is old https problem as https can results in very long
hangups/delays.
What version is your IO::Socket::SSL library ?
bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806
View this thread:
This is still happening. This morning playback stopped for 8 minutes
then recovered. Nothing in server log.
Are you using Spotty? If so, could you please enable INFO logging for
Spotty and see whether there's been activity around when LMS is locking
up? Also make sure (and I'm sure I've
mherger wrote:
> > LMS crashed again this morning and there was no sign of LMS as a
> running
> > process in top as shown in the first screenshot. The second screenshot
> > shows the situation after restarting LMS. LMS is now at the top of the
> > list but the number of running processes is
mherger wrote:
> > LMS crashed again this morning and there was no sign of LMS as a
> running
> > process in top as shown in the first screenshot. The second screenshot
> > shows the situation after restarting LMS. LMS is now at the top of the
> > list but the number of running processes is
Your issue may or may not be related to mine as reported here:
https://forums.slimdevices.com/showthread.php?110767-Disappearing-Re-appearing-LMS
After my final post in that thread LMS vanished again so I reinstalled
Windows 10 and set everything up again. LMS runs fine on my Windows 10
PC with
LMS crashed again this morning and there was no sign of LMS as a running
process in top as shown in the first screenshot. The second screenshot
shows the situation after restarting LMS. LMS is now at the top of the
list but the number of running processes is still one for some
reason.
Those
mherger wrote:
> > Recently I have found I need to restart LMS after playback stops on
> all
> > players. When this happens LMS is unreachable. LMS is on a Raspberry
> Pi
> > using Max2Play and the latest 7.9.2. There is nothing in the server
> log
> > related to the crash. What can I log to
mherger wrote:
> > Recently I have found I need to restart LMS after playback stops on
> all
> > players. When this happens LMS is unreachable. LMS is on a Raspberry
> Pi
> > using Max2Play and the latest 7.9.2. There is nothing in the server
> log
> > related to the crash. What can I log to
Recently I have found I need to restart LMS after playback stops on all
players. When this happens LMS is unreachable. LMS is on a Raspberry Pi
using Max2Play and the latest 7.9.2. There is nothing in the server log
related to the crash. What can I log to investigate this.
Check the system's
Recently I have found I need to restart LMS after playback stops on all
players. When this happens LMS is unreachable. LMS is on a Raspberry Pi
using Max2Play and the latest 7.9.2. There is nothing in the server log
related to the crash. What can I log to investigate this. I did report
this in
22 matches
Mail list logo