Hardware: Old laptop or computer
YunoHost version: 126.96.36.199
I have access to my server : Through SSH | through the webadmin | direct access via keyboard / screen (all three!)
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : yes
If yes, please explain: Using a ynh.fr domain with dynamic DNS managed by Yunohost
Question: Is it typical for the time in Yunohost logs to be UTC time, no matter what time the hardware clock and system time on the server are set to? I live in UTC -4 time zone.
- Yesterday I set my server’s hardware clock to local time; for confirmation, here is the output of cat /etc/adjtime:
0.000000 1631775601 0.000000
- I confirmed that the system (OS) time was correct using this command: date
- I synchronized my hardware clock to the system time using: sudo hwclock --systohc
- I confirmed that the hardware clock time was correct using: sudo hwclock --verbose
- I modified the crontab file using: sudo nano /etc/crontab
- I added the following lines to the crontab file:
0 3 * * * root /sbin/hwclock --systohc # set hardware clock to system clock time each day at 03:00 am
1 3 * * * root /sbin/shutdown -r now “daily reboot” # reboot every day at 03:01 am
Yet here are the first few lines of one of the system logs from today (Fail2Ban journalctl):
-- Logs begin at Thu 2021-09-16 03:04:03 EDT, end at Thu 2021-09-16 14:16:52 EDT. -- Sep 16 07:02:04 systemd: Starting Fail2Ban Service... Sep 16 07:02:05 systemd: Started Fail2Ban Service. Sep 16 07:02:51 fail2ban-server: Server ready
It looks like the reboot happened at 3:01 AM local time, as desired, but the start time for Fail2Ban (and all of the other services on the Services page of the webadmin) shows as just after 7:00 AM–which would be the UTC time compared to local time.
Is this because I have a ynh.fr domain, and Yunohost (in France) manages my dynamic DNS? Or have I done something wrong in setting up the hardware clock / system time synchronization?