[opensuse-arm] openSUSE MicroOS on Raspi4: How to get the time right
Hi all, not sure if this is a regression, if I am missing some configuration or if this is normal behaviour: I installed openSUSE microOS on a Raspberry Pi 4 (4GB RAM), which works very nice, apart from the fact that the wrong time on boot messes up lots of things. I checked that chronyd is enabled and has valid upstream servers, and now the time gets set right on each boot. But for some reason postfix does not like my dependency on chronyd (/etc/systemd/system/postfix.service.d/after_chronyd.conf with Requires= and After=) and always states that the service files have changed and I should trigger a "systemctl daemon-reload". Also, it states that the system is running for 4 weeks, which seems to be from the time before fixing until the correct time. Not really nice. I thought there was a "time is set correctly" systemd target, but had no time yet to dig if that is in use on MicroOS. Is this normal behaviour? Or a regression in the latest microOS snapshots? Kind Regards, Johannes -- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
Hi, On Fri, May 22, Johannes Kastl wrote:
Hi all,
not sure if this is a regression, if I am missing some configuration or if this is normal behaviour:
I installed openSUSE microOS on a Raspberry Pi 4 (4GB RAM), which works very nice, apart from the fact that the wrong time on boot messes up lots of things.
I checked that chronyd is enabled and has valid upstream servers, and now the time gets set right on each boot.
But for some reason postfix does not like my dependency on chronyd (/etc/systemd/system/postfix.service.d/after_chronyd.conf with Requires= and After=) and always states that the service files have changed and I should trigger a "systemctl daemon-reload". Also, it states that the system is running for 4 weeks, which seems to be from the time before fixing until the correct time. Not really nice.
Sounds like you need to fix the time stamps manual.
I thought there was a "time is set correctly" systemd target, but had no time yet to dig if that is in use on MicroOS.
Yes, there is such a target and I requested that this get activated by default. But it got disabled again, since Tumbleweed Notebook users don't like to configure their system the correct way and all the hacks they are using are breaking boot for them :(
Is this normal behaviour? Or a regression in the latest microOS snapshots?
I don't see any problems with MicroOS and chrony/correct time. But I'm also not using postfix yet (building a container for this use case currently). It just works on my 5 Raspberry Pis. But the images should have chrony configured and enabled by default. Thorsten -- Thorsten Kukuk, Distinguished Engineer, Senior Architect SLES & MicroOS SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany Managing Director: Felix Imendoerffer (HRB 36809, AG Nürnberg) -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
Am 22.05.20 um 18:10 schrieb Thorsten Kukuk:
On Fri, May 22, Johannes Kastl wrote: [...]
I thought there was a "time is set correctly" systemd target, but had no time yet to dig if that is in use on MicroOS.
Yes, there is such a target and I requested that this get activated by default. But it got disabled again, since Tumbleweed Notebook users don't like to configure their system the correct way and all the hacks they are using are breaking boot for them :(
You mean https://bugzilla.opensuse.org/show_bug.cgi?id=1145193 ? IMO the conclusion in that ticket is simply that a general purpose system can neither rely on network present, online, nor NTP available nor reachable. A normal Laptop usually has a reasonable RTC so that doesn't matter and waiting for super accurate time sync is simply not needed by default. YaST however has implemented controls to enable waiting for network time sync by default depending on product. AFAICS the option is neither set in the control file for MicroOS, nor do the presets enable chrony-wait.service, nor does the appliance do it specifically for RPis. Johannes, could you check if "systemctl enable chrony-wait.service" helps? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, HRB 36809 (AG Nürnberg), GF: Felix Imendörffer -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org
participants (3)
-
Johannes Kastl -
Ludwig Nussel -
Thorsten Kukuk