'checking skew' is spammed in syslog
Closed this issue · 8 comments
Hi,
hd-idle is prints in the syslog the following messages, continuously since some days.
What is going on? :(
Aug 9 13:36:41 nas hd-idle[1125]: checking skew. skewtime: 3m0s disk: sde now: 2022-08-09 13:36:41 lastNow: 2022-08-09 13:35:41, now-lastNow: 1m0.051608267s
Aug 9 13:36:41 nas hd-idle[1125]: checking skew. skewtime: 3m0s disk: sda now: 2022-08-09 13:36:41 lastNow: 2022-08-09 13:35:41, now-lastNow: 1m0.051607991s
Aug 9 13:36:41 nas hd-idle[1125]: checking skew. skewtime: 3m0s disk: sdb now: 2022-08-09 13:36:41 lastNow: 2022-08-09 13:35:41, now-lastNow: 1m0.051610526s
Aug 9 13:36:41 nas hd-idle[1125]: checking skew. skewtime: 3m0s disk: sdd now: 2022-08-09 13:36:41 lastNow: 2022-08-09 13:35:41, now-lastNow: 1m0.051609478s
Aug 9 13:36:41 nas hd-idle[1125]: checking skew. skewtime: 3m0s disk: sdc now: 2022-08-09 13:36:41 lastNow: 2022-08-09 13:35:41, now-lastNow: 1m0.051608892s
Aug 9 13:37:41 nas hd-idle[1125]: checking skew. skewtime: 3m0s disk: sde now: 2022-08-09 13:37:41 lastNow: 2022-08-09 13:36:41, now-lastNow: 1m0.059241686s
Aug 9 13:37:41 nas hd-idle[1125]: checking skew. skewtime: 3m0s disk: sda now: 2022-08-09 13:37:41 lastNow: 2022-08-09 13:36:41, now-lastNow: 1m0.059241686s
Aug 9 13:37:41 nas hd-idle[1125]: checking skew. skewtime: 3m0s disk: sdb now: 2022-08-09 13:37:41 lastNow: 2022-08-09 13:36:41, now-lastNow: 1m0.059241686s
Aug 9 13:37:41 nas hd-idle[1125]: checking skew. skewtime: 3m0s disk: sdd now: 2022-08-09 13:37:41 lastNow: 2022-08-09 13:36:41, now-lastNow: 1m0.059241686s
Aug 9 13:37:41 nas hd-idle[1125]: checking skew. skewtime: 3m0s disk: sdc now: 2022-08-09 13:37:41 lastNow: 2022-08-09 13:36:41, now-lastNow: 1m0.059241686s
Removed and reinstalled, still spamming
All right, let me know if you need testing.
Hi @auanasgheps
The newest release https://github.com/adelolmo/hd-idle/releases/tag/v1.18 fixes the issue.
I made the v1.17 release from a branch instead of doing it from master. This is why the annoying log made its way into the package.
Thank you for the update!
Unfortunately my server will be unavailable until early September, so let's close this issue and I will reopen if needed.
One last question. I see this entry
Complete the list of targets for the service restart
Is this another attempt to fix resume after standby/hibernation?
Is this another attempt to fix resume after standby/hibernation?
I'm not sure what would help in this case, but for completeness I added to the service all suspend/hibernate related targets.
We can close this issue, the 1.17 version has resolved the issue. Thanks!