NTP on boot seems broken

[nephele]

hrev53536

I can't recall a hrev where ntp on boot worked for me though, not quite sure how to debug this, it failed on a laptop for me (with a busted battery, and probably busted cmos battery) aswell as on this desktop (which has an ethernet connection).

On the desktop atleast clicking "synchronize now" gets me the correct time after boot.

attaching syslog since i am not sure what is needed to debug this.

[pulkomandy]

The relevant part of /system/data/user_launch/user:

        job update-time {
                launch /system/preferences/Time "" --update
                if setting ~/config/settings/networktime\ settings "synchronize at boot"
                on network_available
        }

So I see 3 possible causes:

• The command line used there does not work
• The setting is disabled
• The network_available event is triggered too early and the network isn't actually available yet

I suggest checking the first 2 as they seem easier to do, and hope it's an easy fix there.

[pulkomandy]

In particular I don't see what's the empty string as first argument to Time doing, and that could well be the problem?

[waddlesplash]

I wrote that rule. I can't remember off the top of my head what the purpose of the empty string was, but IIRC all other launch rules used it too. I think it's argv 0?

[nephele]

# cat networktime\ settings pool.ntp.orgde.pool.ntp.orgtime.nist.govdefault serversynchronize at boottry all servers#

# koder networktime\ steeings

HMF1tstn

Not sure what that is about, atleast for cat the setting seams to be there? though i am not quite sure what the format is

to test the commandline, how would i invoke a job via user_launch manually?

[pulkomandy]

The settings are in BMessage format, the "message" command line tool will give more readable output (in particular the boolean value of the setting, but you can as well see that the checkbox is ticked in Time preferences)

As for testing, the launch_roster command can be used, I don't know if it allows triggering this however.

[nephele]

synchronize at boot = bool(true)

So, case two should be fine

[nephele]

I tried severall locations to overwrite what launch_roster pulls from, but no luck, so not quite sure how i would test condition #1

[mrentropy]

I'm seeing the same issue on an ASRock DESKMINI A300W The clock is set to use local time, not UTC The BIOS is set to local time The timezone is set correctly (or as correctly as it can be)

Boot to desktop, and clock is set about five hours ahead Bring up the clock prefs and manually sync the time server Everything works fine, until a reboot.

[pulkomandy]

Fixed in hrev53666.

[nephele]

This is still an issue on hrev53673, I have had severall boots with ethernet connection that kept the clock state from the previous shutdown.

[waddlesplash]

Did you actually set a timezone, or set your hardware clock to UTC? If you do not do one of those things I don't think it will synchronize.

[nephele]

Yes, the system seems to be configured correctly, i do have the HW clock set to UTC and my timezone set to "Germany Time", as i said, synchronizing after boot works fine, but the system comes up with a wrong time untill i trigger a sync manually