didjean - thank you very much for this posting and the log file! I think
we got a lead:
invalid:
[22-11-17 20:45:01.7436] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd
called with request: stop
[22-11-17 20:45:01.7442] Slim::Utils::Alarm::_alarmEnd (1992) Stopping
alarm
vs. correct:
[22-11-17 21:03:02.2268] Slim::Utils::Alarm::_alarmEnd (1970) _alarmEnd
called with request: stop
[22-11-17 21:03:02.2271] Slim::Utils::Alarm::_alarmEnd (1981) Ignoring
self-created request
If we compare both logs - last 7 lines are different.
Yep! There is code in Alarm (and LMS in general) to define the source of
a request. Alarm would use this to not act on its own commands, but on
commands coming from other parts of the system. In the failing case this
flag seems to be missing or modified. Alarm doesn't recognize the "stop"
command as coming from itself.
It remains to be figured out what that would happen _sometimes_. And
it's my understanding that it would start to fail at some point, and not
recover once in that mode.
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
