Pi initial Startup clock is messed up (Solved)
Posted: 13 Apr 2018, 11:41
Hi guys,
This isnt a major thing but always grabbed my curiosity.
First let me state that running:
I receive the correct timezone information.
I receive:
When the pi boots the times stamped on the services etc is like 2 years ago (Not using current time as if its not synced yet?).
Example, if i do a simple:
It states:
All services started time stamps around then..?
Now if i restart a service or manually start one it timestamps to the current and correct time/date? It seems something for the clock setup is not running before these startup.
Would love your inputs.
Regards,
Will.
This isnt a major thing but always grabbed my curiosity.
First let me state that running:
- Code: Select all
timedatectl status
I receive the correct timezone information.
I receive:
- Code: Select all
Local time: Fri 2018-04-13 11:33:50 IST
Universal time: Fri 2018-04-13 10:33:50 UTC
RTC time: n/a
Time zone: Europe/Dublin (IST, +0100)
Network time on: yes
NTP synchronized: yes
RTC in local TZ: no
When the pi boots the times stamped on the services etc is like 2 years ago (Not using current time as if its not synced yet?).
Example, if i do a simple:
- Code: Select all
systemctl status rune_PL_wrk
It states:
- Code: Select all
Active: active (running) since Mon 2016-02-22 14:40:18 GMT; 2 years 1 months ago
All services started time stamps around then..?
Now if i restart a service or manually start one it timestamps to the current and correct time/date? It seems something for the clock setup is not running before these startup.
Would love your inputs.
Regards,
Will.