Ludovic Courtès <[email protected]> skribis: >> 2025-02-23 12:00:02 Waiting anew for timer 'kerberos-log-in-refresh' >> (resuming from sleep state?).
The “Waiting anew” message happens when the timer fires 2 seconds or more later than expected (see ‘sleep-operation/check’), which is indeed the case here. It’s not supposed to happen normally. Before we bump that to 10 seconds, say, it would be good to understand why the timer got late here. Are there services that could block shepherd somehow, for instance by calling ‘waitpid’, or running computations at 12:00pm? Ludo’.
