It was running for around 5 minutes. I wanted to first test if the script detects files accessed from SMB shares.
I’ve good news: I think I detected what caused this problem.
It was either:
- Stopped cron (I resumed yesterday to let it run for a full day)
- External NAS device with OpenMediaVault. I restarted it before night. Not sure if it was the issue, but I’ll be observing it more.
Seems like it helped:
2019-04-12T07:09:15.645208+02:00 di=H10IhkTgem notice logger: exit standby after 13416 (since 2019-04-12 03:25:39.760101001 +0200)
2019-04-12T08:01:09.496722+02:00 di=H10IhkTgem notice logger: exit standby after 2503 (since 2019-04-12 07:19:26.880101001 +0200)
2019-04-12T08:01:19.212473+02:00 di=H10IhkTgem notice logger: Rotated atop, atop_size=3055062 atop_upload_size=1065
2019-04-12T08:12:11.661327+02:00 di=H10IhkTgem notice logger: exit standby after 51 (since 2019-04-12 08:11:20.670101001 +0200)
2019-04-12T08:26:19.178958+02:00 di=H10IhkTgem notice logger: exit standby after 237 (since 2019-04-12 08:22:22.710101001 +0200)
2019-04-12T11:48:48.555133+02:00 di=H10IhkTgem notice logger: exit standby after 11538 (since 2019-04-12 08:36:30.300101001 +0200)
Thanks for help.
One more question, I know that “chroot” exists, which would prevent those random wake-ups. Does anyone know if it has the “full” WD firmware running on it? Would it lose files/shares after installing? (I have full backups, but still restoring takes a very long time).