Send connman mailing list submissions to
        connman@lists.01.org

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
        connman-requ...@lists.01.org

You can reach the person managing the list at
        connman-ow...@lists.01.org

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)


----------------------------------------------------------------------

Message: 1
Date: Thu, 22 Mar 2018 23:12:40 +0000
From: Craig McQueen <craig.mcqu...@innerrange.com>
To: Daniel Wagner <w...@monom.org>
Cc: "connman@lists.01.org" <connman@lists.01.org>
Subject: RE: Retry NTP servers periodically on startup
Message-ID: <0f799419de904723b2c0dc64ea7a3...@innerrange.com>
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.

Mar 21 18:56:05 ws000024 daemon.info connmand[1047]: ntp: adjust (slew): 
-0.001583 sec
Mar 21 19:13:09 ws000024 daemon.info connmand[1047]: ntp: adjust (slew): 
-0.000066 sec
Mar 21 19:30:13 ws000024 daemon.info connmand[1047]: ntp: adjust (slew): 
+0.000107 sec
Mar 21 19:47:17 ws000024 daemon.info connmand[1047]: ntp: adjust (slew): 
+0.000584 sec
Mar 21 20:04:21 ws000024 daemon.info connmand[1047]: ntp: adjust (slew): 
-0.000795 sec
Mar 21 20:04:52 ws000024 daemon.info connmand[1047]: ntp: adjust (slew): 
-0.009179 sec
Mar 21 20:21:56 ws000024 daemon.info connmand[1047]: ntp: adjust (slew): 
+0.000409 sec
Mar 21 20:39:00 ws000024 daemon.info connmand[1047]: ntp: adjust (slew): 
-0.000277 sec
Mar 21 20:56:04 ws000024 daemon.info connmand[1047]: ntp: adjust (slew): 
+0.000192 sec
Mar 21 21:04:55 ws000024 authpriv.warn dropbear[9011]: lastlog_perform_login: 
Couldn't stat /var/log/lastlog: No such file or directory
Mar 21 21:04:55 ws000024 authpriv.warn dropbear[9011]: lastlog_openseek: 
/var/log/lastlog is not a file or directory!
Mar 21 21:12:21 ws000024 user.info kernel: [212910.721918] cpsw 
4a100000.ethernet eth0: Link is Down
Mar 21 21:12:21 ws000024 daemon.info connmand[1047]: eth0 {RX} 34690 packets 
6471180 bytes
Mar 21 21:12:21 ws000024 daemon.info connmand[1047]: eth0 {TX} 7913 packets 
925409 bytes
Mar 21 21:12:21 ws000024 daemon.info connmand[1047]: eth0 {update} flags 36867 
<UP>
Mar 21 21:12:21 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
address 00:11:B9:09:00:06 mtu 1500
Mar 21 21:12:21 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
operstate 2 <DOWN>
Mar 21 21:12:21 ws000024 daemon.info avahi-daemon[949]: Withdrawing address 
record for 192.168.178.28 on eth0.
Mar 21 21:12:21 ws000024 daemon.info avahi-daemon[949]: Leaving mDNS multicast 
group on interface eth0.IPv4 with address 192.168.178.28.
Mar 21 21:12:21 ws000024 daemon.info avahi-daemon[949]: Interface eth0.IPv4 no 
longer relevant for mDNS.
Mar 21 21:12:21 ws000024 daemon.info connmand[1047]: eth0 {del} address 
192.168.178.28/24 label eth0
Mar 21 21:12:21 ws000024 daemon.info connmand[1047]: eth0 {del} route 
192.168.178.0 gw 0.0.0.0 scope 253 <LINK>
Mar 21 21:12:29 ws000024 user.info kernel: [212919.252634] cpsw 
4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
Mar 21 21:12:29 ws000024 daemon.info connmand[1047]: eth0 {RX} 34690 packets 
6471180 bytes
Mar 21 21:12:29 ws000024 daemon.info connmand[1047]: eth0 {TX} 7913 packets 
925409 bytes
Mar 21 21:12:29 ws000024 daemon.info connmand[1047]: eth0 {update} flags 102467 
<UP,RUNNING,LOWER_UP>
Mar 21 21:12:29 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
address 00:11:B9:09:00:06 mtu 1500
Mar 21 21:12:29 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
operstate 6 <UP>
Mar 21 21:12:29 ws000024 daemon.warn connmand[1047]: ipconfig state 3 ipconfig 
method 1
Mar 21 21:12:42 ws000024 daemon.info connmand[1047]: eth0 {RX} 34690 packets 
6471180 bytes
Mar 21 21:12:42 ws000024 daemon.info connmand[1047]: eth0 {TX} 7916 packets 
927179 bytes
Mar 21 21:12:42 ws000024 daemon.info connmand[1047]: eth0 {update} flags 36867 
<UP>
Mar 21 21:12:42 ws000024 user.info kernel: [212931.762940] cpsw 
4a100000.ethernet eth0: Link is Down
Mar 21 21:12:42 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
address 00:11:B9:09:00:06 mtu 1500
Mar 21 21:12:42 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
operstate 2 <DOWN>
Mar 21 21:13:24 ws000024 user.info kernel: [212974.215729] cpsw 
4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Mar 21 21:13:24 ws000024 daemon.info connmand[1047]: eth0 {RX} 34690 packets 
6471180 bytes
Mar 21 21:13:24 ws000024 daemon.info connmand[1047]: eth0 {TX} 7916 packets 
927179 bytes
Mar 21 21:13:24 ws000024 daemon.info connmand[1047]: eth0 {update} flags 102467 
<UP,RUNNING,LOWER_UP>
Mar 21 21:13:24 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
address 00:11:B9:09:00:06 mtu 1500
Mar 21 21:13:24 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
operstate 6 <UP>
Mar 21 21:13:24 ws000024 daemon.warn connmand[1047]: ipconfig state 3 ipconfig 
method 1
Mar 21 21:13:35 ws000024 daemon.info avahi-daemon[949]: Joining mDNS multicast 
group on interface eth0.IPv4 with address 192.168.178.28.
Mar 21 21:13:35 ws000024 daemon.info avahi-daemon[949]: New relevant interface 
eth0.IPv4 for mDNS.
Mar 21 21:13:35 ws000024 daemon.info avahi-daemon[949]: Registering new address 
record for 192.168.178.28 on eth0.IPv4.
Mar 21 21:13:35 ws000024 daemon.info connmand[1047]: Setting domainname to 
fritz.box
Mar 21 21:13:35 ws000024 daemon.info connmand[1047]: eth0 {add} address 
192.168.178.28/24 label eth0 family 2
Mar 21 21:13:35 ws000024 daemon.info connmand[1047]: eth0 {add} route 
192.168.178.0 gw 0.0.0.0 scope 253 <LINK>
Mar 21 21:13:35 ws000024 daemon.info connmand[1047]: eth0 {add} route 
192.168.178.1 gw 0.0.0.0 scope 253 <LINK>
Mar 21 21:13:35 ws000024 daemon.info connmand[1047]: eth0 {add} route 0.0.0.0 
gw 192.168.178.1 scope 0 <UNIVERSE>
Mar 21 21:13:39 ws000024 daemon.warn connmand[1047]: Online check failed for 
0xd8ae8 Wired
Mar 21 21:14:21 ws000024 daemon.info connmand[1047]: Skipping server 
192.168.178.1 KoD code 

Mar 21 21:14:22 ws000024 daemon.info connmand[1047]: ntp: adjust (slew): 
-0.000754 sec

Mar 21 21:31:18 ws000024 daemon.info connmand[1047]: eth0 {RX} 35273 packets 
6558646 bytes
Mar 21 21:31:18 ws000024 daemon.info connmand[1047]: eth0 {TX} 8147 packets 
971230 bytes
Mar 21 21:31:18 ws000024 daemon.info connmand[1047]: eth0 {update} flags 36867 
<UP>
Mar 21 21:31:18 ws000024 user.info kernel: [214048.618763] cpsw 
4a100000.ethernet eth0: Link is Down
Mar 21 21:31:19 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
address 00:11:B9:09:00:06 mtu 1500
Mar 21 21:31:19 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
operstate 2 <DOWN>
Mar 21 21:31:19 ws000024 daemon.info avahi-daemon[949]: Withdrawing address 
record for 192.168.178.28 on eth0.
Mar 21 21:31:19 ws000024 daemon.info avahi-daemon[949]: Leaving mDNS multicast 
group on interface eth0.IPv4 with address 192.168.178.28.
Mar 21 21:31:19 ws000024 daemon.info avahi-daemon[949]: Interface eth0.IPv4 no 
longer relevant for mDNS.
Mar 21 21:31:19 ws000024 daemon.info connmand[1047]: eth0 {del} address 
192.168.178.28/24 label eth0
Mar 21 21:31:19 ws000024 daemon.info connmand[1047]: eth0 {del} route 
192.168.178.0 gw 0.0.0.0 scope 253 <LINK>
Mar 21 21:31:29 ws000024 daemon.info connmand[1047]: eth0 {RX} 35273 packets 
6558646 bytes
Mar 21 21:31:29 ws000024 daemon.info connmand[1047]: eth0 {TX} 8147 packets 
971230 bytes
Mar 21 21:31:29 ws000024 daemon.info connmand[1047]: eth0 {update} flags 102467 
<UP,RUNNING,LOWER_UP>
Mar 21 21:31:29 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
address 00:11:B9:09:00:06 mtu 1500
Mar 21 21:31:29 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
operstate 6 <UP>
Mar 21 21:31:29 ws000024 user.info kernel: [214058.749514] cpsw 
4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control off
Mar 21 21:31:29 ws000024 daemon.warn connmand[1047]: ipconfig state 3 ipconfig 
method 1
Mar 21 21:31:41 ws000024 daemon.info connmand[1047]: eth0 {RX} 35273 packets 
6558646 bytes
Mar 21 21:31:41 ws000024 daemon.info connmand[1047]: eth0 {TX} 8150 packets 
973000 bytes
Mar 21 21:31:41 ws000024 daemon.info connmand[1047]: eth0 {update} flags 36867 
<UP>
Mar 21 21:31:41 ws000024 user.info kernel: [214071.259645] cpsw 
4a100000.ethernet eth0: Link is Down
Mar 21 21:31:41 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
address 00:11:B9:09:00:06 mtu 1500
Mar 21 21:31:41 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
operstate 2 <DOWN>
Mar 21 21:31:45 ws000024 daemon.info connmand[1047]: eth0 {RX} 35273 packets 
6558646 bytes
Mar 21 21:31:45 ws000024 daemon.info connmand[1047]: eth0 {TX} 8150 packets 
973000 bytes
Mar 21 21:31:45 ws000024 daemon.info connmand[1047]: eth0 {update} flags 102467 
<UP,RUNNING,LOWER_UP>
Mar 21 21:31:45 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
address 00:11:B9:09:00:06 mtu 1500
Mar 21 21:31:45 ws000024 daemon.info connmand[1047]: eth0 {newlink} index 2 
operstate 6 <UP>
Mar 21 21:31:45 ws000024 user.info kernel: [214075.390595] cpsw 
4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
Mar 21 21:31:45 ws000024 daemon.warn connmand[1047]: ipconfig state 3 ipconfig 
method 1
Mar 21 21:32:31 ws000024 daemon.info avahi-daemon[949]: Joining mDNS multicast 
group on interface eth0.IPv4 with address 169.254.46.220.
Mar 21 21:32:31 ws000024 daemon.info avahi-daemon[949]: New relevant interface 
eth0.IPv4 for mDNS.
Mar 21 21:32:31 ws000024 daemon.info avahi-daemon[949]: Registering new address 
record for 169.254.46.220 on eth0.IPv4.
Mar 21 21:32:32 ws000024 daemon.info connmand[1047]: eth0 {add} address 
169.254.46.220/16 label eth0 family 2
Mar 21 21:32:32 ws000024 daemon.info connmand[1047]: eth0 {add} route 
169.254.0.0 gw 0.0.0.0 scope 253 <LINK>
Mar 21 21:32:32 ws000024 daemon.info connmand[1047]: eth0 {add} route 0.0.0.0 
gw 0.0.0.0 scope 253 <LINK>
Mar 21 21:33:21 ws000024 daemon.info avahi-daemon[949]: Withdrawing address 
record for 169.254.46.220 on eth0.
Mar 21 21:33:21 ws000024 daemon.info avahi-daemon[949]: Leaving mDNS multicast 
group on interface eth0.IPv4 with address 169.254.46.220.
Mar 21 21:33:21 ws000024 daemon.info avahi-daemon[949]: Interface eth0.IPv4 no 
longer relevant for mDNS.
Mar 21 21:33:21 ws000024 daemon.info avahi-daemon[949]: Joining mDNS multicast 
group on interface eth0.IPv4 with address 192.168.178.28.
Mar 21 21:33:21 ws000024 daemon.info avahi-daemon[949]: New relevant interface 
eth0.IPv4 for mDNS.
Mar 21 21:33:21 ws000024 daemon.info avahi-daemon[949]: Registering new address 
record for 192.168.178.28 on eth0.IPv4.
Mar 21 21:33:21 ws000024 daemon.info connmand[1047]: eth0 {del} address 
169.254.46.220/16 label eth0
Mar 21 21:33:21 ws000024 daemon.info connmand[1047]: eth0 {del} route 
169.254.0.0 gw 0.0.0.0 scope 253 <LINK>
Mar 21 21:33:21 ws000024 daemon.info connmand[1047]: eth0 {add} address 
192.168.178.28/24 label eth0 family 2
Mar 21 21:33:21 ws000024 daemon.info connmand[1047]: eth0 {add} route 
192.168.178.0 gw 0.0.0.0 scope 253 <LINK>
Mar 21 21:33:21 ws000024 daemon.info connmand[1047]: eth0 {add} route 
192.168.178.1 gw 0.0.0.0 scope 253 <LINK>
Mar 21 21:33:21 ws000024 daemon.info connmand[1047]: eth0 {add} route 0.0.0.0 
gw 192.168.178.1 scope 0 <UNIVERSE>
Mar 22 12:03:03 ws000024 authpriv.warn dropbear[24228]: Login attempt for 
nonexistent user from 192.168.178.21:43798
Mar 22 12:03:18 ws000024 authpriv.warn dropbear[24307]: lastlog_perform_login: 
Couldn't stat /var/log/lastlog: No such file or directory
Mar 22 12:03:18 ws000024 authpriv.warn dropbear[24307]: lastlog_openseek: 
/var/log/lastlog is not a file or directory!

-- 
Craig McQueen


------------------------------

Subject: Digest Footer

_______________________________________________
connman mailing list
connman@lists.01.org
https://lists.01.org/mailman/listinfo/connman


------------------------------

End of connman Digest, Vol 29, Issue 26
***************************************

Reply via email to