Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. RE: Retry NTP servers periodically on startup (Craig McQueen)
2. Re: Retry NTP servers periodically on startup (Daniel Wagner)
----------------------------------------------------------------------
Message: 1
Date: Wed, 4 Apr 2018 07:56:20 +0000
From: Craig McQueen <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: RE: Retry NTP servers periodically on startup
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Daniel Wagner wrote:
> Hi Craig,
>
> > I have a device using ConnMan 1.32, which is connected to the Internet
> > through a FritzBox home ADSL router. It is configured with NTP servers:
> > 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org, 3.pool.ntp.org It
> > additionally gets the IPv4 address of the FritzBox router itself as a
> > further NTP server, from DHCP.
> >
> > I have found that if the router is power-cycled just before the time
> > of the next NTP sync (which occurs at roughly 17 minute intervals),
> > then it subsequently never does any more NTP syncs.
>
> So ConnMan tries to sync and the router is down at this point?
>
> > I saw this recent work on CM-636 in the ConnMan git repository, so I
> > have tried upgrading the devices to use a recent git commit of ConnMan.
>
> CM-636 should fix the case where ConnMan hasn't done any NTP sync yet.
> After the first successful sync it is still the old algorithm. It sounds like
> we
> need to address another fallback scenario.
>
> > Then I retested power-cycling the router just before a scheduled NT>
> > sync. I did the test twice, and the first time, it still did a sync a
> > minute later, after the router rebooted. But the second time I did the
> > test, the device subsequently never has done any more NTP syncs. That
> was roughly 14 hours ago.
>
> Could you post the debug log of both tests? It sounds like that in the first
> case, ConnMan falls back to the aggressive retry loop and in the second case
> it doesn't happen.
I sent the debug logs last week. Did that provide what you needed?
I'm interested to fix this issue soon. Has any work been done on this, or could
I look into it?
Regards,
Craig McQueen
------------------------------
Message: 2
Date: Wed, 4 Apr 2018 11:07:33 +0200
From: Daniel Wagner <[email protected]>
To: Craig McQueen <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: Retry NTP servers periodically on startup
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Hi Craig,
On 04/04/2018 09:56 AM, Craig McQueen wrote:
>> Could you post the debug log of both tests? It sounds like that in the first
>> case, ConnMan falls back to the aggressive retry loop and in the second case
>> it doesn't happen.
>
> I sent the debug logs last week. Did that provide what you needed?
Sorry about that. Got lost in the inbox. I did look at it but I need
some more debug prints enabled. There isn't much information in the log.
Could you try to get reproduced though this time with '-d
src/ntp.c:src/timeserver.c' added to ConnMan command line?
> I'm interested to fix this issue soon. Has any work been done on this, or
> could I look into it?
So far I haven't done anything. If you want to dig into the problem, I
suggest to look at the debug output of ntp.c and timeserver.c and figure
out why the state machine is not going back the initial state looking
for a NTP server. From your description it seems we miss the some event
and don't reset the state machine.
Thanks,
Daniel
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 30, Issue 1
**************************************
