# cron.daily/systemd message after reboot

**URL:** https://dietpi.com/forum/t/cron-daily-systemd-message-after-reboot/5388
**Category:** Troubleshooting
**Created:** [1 June 2021 00:35 UTC](https://dietpi.com/forum/t/cron-daily-systemd-message-after-reboot/5388 "2021-06-01T00:35:39Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![ecognito](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/e/ecae2f/32.png) [@ecognito](https://dietpi.com/forum/u/ecognito)
#### Post date: [1 June 2021 00:35 UTC](https://dietpi.com/forum/t/cron-daily-systemd-message-after-reboot/5388/1 "2021-06-01T00:35:39Z")

</div>

After I reboot my dietpi, the cron.daily task always emits the following email:

```nohighlight
Subject: Cron <root@myhost> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )

/etc/cron.daily/dietpi:
Warning: systemd-timesyncd.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: systemd-timesyncd.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Warning: systemd-timesyncd.service changed on disk. Run 'systemctl daemon-reload' to reload units.

```

Running the recommended “systemctl daemon-reload” does fix the issue, but only until the next reboot.

Any ideas?

---

<div class="post-metadata">

### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)
#### Post date: [3 June 2021 10:09 UTC](https://dietpi.com/forum/t/cron-daily-systemd-message-after-reboot/5388/2 "2021-06-03T10:09:41Z")

</div>

Hi,

I guess it’s not a critical issue as long as the time sync success. You can check this by running

```nohighlight
systemctl status systemd-timesyncd.service

```

MichaIng  
can you have a look pls

---

<div class="post-metadata">

### Author: ![MichaIng](https://dietpi.com/forum/user_avatar/dietpi.com/michaing/32/7_2.png) [@MichaIng](https://dietpi.com/forum/u/MichaIng)
#### Post date: [4 June 2021 10:28 UTC](https://dietpi.com/forum/t/cron-daily-systemd-message-after-reboot/5388/3 "2021-06-04T10:28:59Z")

</div>

While on reboot, of course all systemd units are reloaded, as whenever an APT install/upgrade ships a systemd unit, I observe this error by times and never found out how this is the case, especially since timestamps on that systemd unit stay untouched. It can be safely ignored.

If you want to debug, you can start checking kernel logs for errors and verify/compare system time and timestamps of the unit file, whether it is all as expected:

```nohighlight
dmesg -l emerg,alert,crit,err
systemctl status systemd-timesyncd
ls -l /lib/systemd/system/systemd-timesyncd.service
date

```

And to trigger the warning without overhead:

```nohighlight
systemctl restart systemd-timesyncd

```

I’m not sure how systemd derives whether a unit has changed or not, without either a database to store mtimes or by comparing timestamps of last reload and current mtime. E.g. when on first reload, the system time is way in the past, earlier than the units mtime, then the time is synced, then on next reload systemd sees an mtime that is newer than the timestamp of the last reload, or so.