Sun Oct 23 11:08:23, Klaus Schmidinger wrote:
I agree, here's what I noticed with a more thorough look at yesterday's syslog. I attached the relevant parts of the log to avoid line wrapping.
The timer enumeration of the problematic timers all changed from their respective value to 1 after being "set to no event" - please note that the actual recording happened as expected. Any thoughts on how to debug the issue?