chronyd startup issues
When my system boots up it starts chronyd. The problem is that it seems to not have (or find) a network connection at the time, so it comes up in offline mode. If I restart it then everything is fine. Otherwise, the box gradually loses time. Since I rarely reboot my system I always forget that I need to restart chronyd. What do I need to do to get it to start up in online mode? Do I need to position it farther down in /etc/rc2.d? I thought that I had changed it to run AFTER network-manager, but, if so, something changed it back. Here is a what I have in /etc/rc2.d: lrwxrwxrwx 1 root root 30 Oct 2 20:14 K01vmware-USBArbitrator -> ../init.d/vmware-USBArbitrator -rw-r--r-- 1 root root 677 Jul 14 2013 README lrwxrwxrwx 1 root root 14 Jun 28 2013 S01motd -> ../init.d/motd lrwxrwxrwx 1 root root 17 Oct 2 20:14 S01vmamqpd -> ../init.d/vmamqpd lrwxrwxrwx 1 root root 17 Jun 28 2013 S14portmap -> ../init.d/portmap lrwxrwxrwx 1 root root 17 Jun 28 2013 S14rpcbind -> ../init.d/rpcbind lrwxrwxrwx 1 root root 20 Jun 28 2013 S15nfs-common -> ../init.d/nfs-common lrwxrwxrwx 1 root root 24 Jun 28 2013 S17binfmt-support -> ../init.d/binfmt-support lrwxrwxrwx 1 root root 20 Jun 28 2013 S17fancontrol -> ../init.d/fancontrol lrwxrwxrwx 1 root root 15 Oct 19 13:31 S17jetty -> ../init.d/jetty lrwxrwxrwx 1 root root 17 Jun 28 2013 S17rsyslog -> ../init.d/rsyslog lrwxrwxrwx 1 root root 14 Jun 28 2013 S17sudo -> ../init.d/sudo lrwxrwxrwx 1 root root 20 Jun 28 2013 S17virtualbox -> ../init.d/virtualbox lrwxrwxrwx 1 root root 15 Jun 28 2013 S18acpid -> ../init.d/acpid lrwxrwxrwx 1 root root 17 Jun 28 2013 S18anacron -> ../init.d/anacron lrwxrwxrwx 1 root root 13 Jun 28 2013 S18atd -> ../init.d/atd lrwxrwxrwx 1 root root 16 Jan 12 11:53 S18chrony -> ../init.d/chrony lrwxrwxrwx 1 root root 14 Jun 28 2013 S18cron -> ../init.d/cron lrwxrwxrwx 1 root root 14 Jun 28 2013 S18dbus -> ../init.d/dbus lrwxrwxrwx 1 root root 15 Jun 28 2013 S18exim4 -> ../init.d/exim4 lrwxrwxrwx 1 root root 16 Jun 28 2013 S18gdomap -> ../init.d/gdomap lrwxrwxrwx 1 root root 20 Jun 28 2013 S18kerneloops -> ../init.d/kerneloops lrwxrwxrwx 1 root root 21 Jun 28 2013 S18loadcpufreq -> ../init.d/loadcpufreq lrwxrwxrwx 1 root root 13 Jun 28 2013 S18ssh -> ../init.d/ssh lrwxrwxrwx 1 root root 16 Oct 2 20:13 S18vmware -> ../init.d/vmware lrwxrwxrwx 1 root root 22 Jun 28 2013 S19avahi-daemon -> ../init.d/avahi-daemon lrwxrwxrwx 1 root root 19 Jun 28 2013 S19bluetooth -> ../init.d/bluetooth lrwxrwxrwx 1 root root 22 Jun 28 2013 S19cpufrequtils -> ../init.d/cpufrequtils lrwxrwxrwx 1 root root 25 Jun 28 2013 S19network-manager -> ../init.d/network-manager lrwxrwxrwx 1 root root 14 Jun 28 2013 S20cups -> ../init.d/cups lrwxrwxrwx 1 root root 13 Jun 28 2013 S20gdm -> ../init.d/gdm lrwxrwxrwx 1 root root 15 Jun 28 2013 S20saned -> ../init.d/saned lrwxrwxrwx 1 root root 18 Jun 28 2013 S21bootlogs -> ../init.d/bootlogs lrwxrwxrwx 1 root root 18 Jun 28 2013 S22rc.local -> ../init.d/rc.local lrwxrwxrwx 1 root root 19 Jun 28 2013 S22rmnologin -> ../init.d/rmnologin lrwxrwxrwx 1 root root 23 Jun 28 2013 S22stop-bootlogd -> ../init.d/stop-bootlogd lrwxrwxrwx 1 root root 32 Oct 2 20:14 S50vmware-USBArbitrator -> /etc/init.d/vmware-USBArbitrator -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52e8b675.3020...@gmail.com
Re: chronyd startup issues
On Wed, 2014-01-29 at 00:06 -0800, Marc Shapiro wrote: > When my system boots up it starts chronyd. The problem is that it seems > to not have (or find) a network connection at the time, so it comes up > in offline mode. If I restart it then everything is fine. Otherwise, > the box gradually loses time. Since I rarely reboot my system I always > forget that I need to restart chronyd. What do I need to do to get it > to start up in online mode? Edit /etc/chrony/chrony.conf and remove the 'offline' directives? That's what I have in my system setup notes, unfortunately, as I've already done that I'm not 100% sure where they exist in the default conf file, but I assume it's pretty obvious otherwise I would have been clearer in my notes to myself :-) -- Tixy -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1390986208.2866.5.ca...@computer5.home
Re: chronyd startup issues
On Wed, Jan 29, 2014 at 12:06:13AM -0800, Marc Shapiro wrote: > When my system boots up it starts chronyd. The problem is that it > seems to not have (or find) a network connection at the time, so it > comes up in offline mode. If I restart it then everything is fine. > Otherwise, the box gradually loses time. Since I rarely reboot my > system I always forget that I need to restart chronyd. What do I > need to do to get it to start up in online mode? Do I need to > position it farther down in /etc/rc2.d? I thought that I had > changed it to run AFTER network-manager, but, if so, something > changed it back. > Chrony will put "offline" sources to "online" when a PPP link comes up (any PPP link, bug #252131) but not when an ethernet link comes up (bug #312092). If you like, there are instructions and a patch in bug #389961 to fix this. signature.asc Description: Digital signature
Re: chronyd startup issues
* Darac Marjal wrote on 2014-01-29 at 10:22 (+): > On Wed, Jan 29, 2014 at 12:06:13AM -0800, Marc Shapiro wrote: > > When my system boots up it starts chronyd. The problem is > > that it seems to not have (or find) a network connection at > > the time, so it comes up in offline mode. If I restart it > > then everything is fine. Otherwise, the box gradually loses > > time. Since I rarely reboot my system I always forget that I > > need to restart chronyd. What do I need to do to get it to > > start up in online mode? Do I need to position it farther > > down in /etc/rc2.d? I thought that I had changed it to run > > AFTER network-manager, but, if so, something changed it back. > > Chrony will put "offline" sources to "online" when a PPP link > comes up (any PPP link, bug #252131) but not when an ethernet > link comes up (bug #312092). > > If you like, there are instructions and a patch in bug #389961 > to fix this. Yes, but expect some tricky fiddling :-) However, comparing the bug history - some of chrony's ones haven't been handled or closed for 5+ years, also the relevant ones here - and the number of users of chrony (847) and openntpd (1902), I strongly suggest you considering a switch to the openntpd package. Regards, Mathias -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140129111021.ga17...@gmx.org
Re: chronyd startup issues
On 01/29/2014 06:10 AM, Mathias Bauer wrote: * Darac Marjal wrote on 2014-01-29 at 10:22 (+): On Wed, Jan 29, 2014 at 12:06:13AM -0800, Marc Shapiro wrote: When my system boots up it starts chronyd. The problem is that it seems to not have (or find) a network connection at the time, so it comes up in offline mode. If I restart it then everything is fine. Otherwise, the box gradually loses time. Since I rarely reboot my system I always forget that I need to restart chronyd. What do I need to do to get it to start up in online mode? Do I need to position it farther down in /etc/rc2.d? I thought that I had changed it to run AFTER network-manager, but, if so, something changed it back. Chrony will put "offline" sources to "online" when a PPP link comes up (any PPP link, bug #252131) but not when an ethernet link comes up (bug #312092). If you like, there are instructions and a patch in bug #389961 to fix this. Yes, but expect some tricky fiddling :-) However, comparing the bug history - some of chrony's ones haven't been handled or closed for 5+ years, also the relevant ones here - and the number of users of chrony (847) and openntpd (1902), I strongly suggest you considering a switch to the openntpd package. I have just done exactly that for exactly that reason on one machine. Chrony is apparently quite comfortable with some kinds of intermittent connections but not others. That happened only this morning, so I don't have a track record to confirm that it's worth it. Also, it's probably a good idea to add the -s option to DAEMON_OPTS in /etc/default/openntpd. -- Philippe -- The trouble with common sense it that it is so uncommon. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52e99a61.4000...@gcal.net
Re: chronyd startup issues
On 01/29/2014 03:10 AM, Mathias Bauer wrote: * Darac Marjal wrote on 2014-01-29 at 10:22 (+): On Wed, Jan 29, 2014 at 12:06:13AM -0800, Marc Shapiro wrote: When my system boots up it starts chronyd. The problem is that it seems to not have (or find) a network connection at the time, so it comes up in offline mode. If I restart it then everything is fine. Otherwise, the box gradually loses time. Since I rarely reboot my system I always forget that I need to restart chronyd. What do I need to do to get it to start up in online mode? Do I need to position it farther down in /etc/rc2.d? I thought that I had changed it to run AFTER network-manager, but, if so, something changed it back. Chrony will put "offline" sources to "online" when a PPP link comes up (any PPP link, bug #252131) but not when an ethernet link comes up (bug #312092). If you like, there are instructions and a patch in bug #389961 to fix this. Yes, but expect some tricky fiddling :-) However, comparing the bug history - some of chrony's ones haven't been handled or closed for 5+ years, also the relevant ones here - and the number of users of chrony (847) and openntpd (1902), I strongly suggest you considering a switch to the openntpd package. Regards, Mathias I was not aware of the openntpd package. I will look into it. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52eafe43.9010...@gmail.com
Re: chronyd startup issues
On 01/29/2014 04:18 PM, Philippe Clérié wrote: On 01/29/2014 06:10 AM, Mathias Bauer wrote: * Darac Marjal wrote on 2014-01-29 at 10:22 (+): On Wed, Jan 29, 2014 at 12:06:13AM -0800, Marc Shapiro wrote: When my system boots up it starts chronyd. The problem is that it seems to not have (or find) a network connection at the time, so it comes up in offline mode. If I restart it then everything is fine. Otherwise, the box gradually loses time. Since I rarely reboot my system I always forget that I need to restart chronyd. What do I need to do to get it to start up in online mode? Do I need to position it farther down in /etc/rc2.d? I thought that I had changed it to run AFTER network-manager, but, if so, something changed it back. Chrony will put "offline" sources to "online" when a PPP link comes up (any PPP link, bug #252131) but not when an ethernet link comes up (bug #312092). If you like, there are instructions and a patch in bug #389961 to fix this. Yes, but expect some tricky fiddling :-) However, comparing the bug history - some of chrony's ones haven't been handled or closed for 5+ years, also the relevant ones here - and the number of users of chrony (847) and openntpd (1902), I strongly suggest you considering a switch to the openntpd package. I have just done exactly that for exactly that reason on one machine. Chrony is apparently quite comfortable with some kinds of intermittent connections but not others. That happened only this morning, so I don't have a track record to confirm that it's worth it. Also, it's probably a good idea to add the -s option to DAEMON_OPTS in /etc/default/openntpd. OK, I just replaced chrony, yesterday. I have one question. Is there an equivalent to using chronyc to check how accurate the time is, or what server is being used? That way, I could verify that it is connecting on its own when I have to do a reboot. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52ebbcb9.3050...@gmail.com
Re: chronyd startup issues
Philippe, * Philippe Clérié wrote on 2014-01-29 at 19:18 (-0500): > On 01/29/2014 06:10 AM, Mathias Bauer wrote: > > Also, it's probably a good idea to add the -s option to > DAEMON_OPTS in /etc/default/openntpd. maybe. But consider time jumps just after booting won't make reconstructing things easier in case something goes wrong. Maybe some process already started before ntpd also won't be very amused about that. If you take a look into the logs of an unsynced machine, you will see that it is "soon" resynced again. So I won't do it. Regards, Mathias -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140131175624.gb11...@gmx.org
Re: chronyd startup issues
Marc, * Marc Shapiro wrote on 2014-01-31 at 07:09 (-0800): > OK, I just replaced chrony, yesterday. I have one question. > Is there an equivalent to using chronyc to check how accurate > the time is, or what server is being used? That way, I could > verify that it is connecting on its own when I have to do a > reboot. unfortunately, there isn't. However you may run something like # lsof -i UDP:123 | grep ^ntpd You also can look (grep?) in /var/log/daemon.log for messages like ntpd[12345]: ntp engine ready ntpd[12345]: peer 1.2.3.4 now valid ntpd[12345]: clock is now synced Perhaps it also helps to check the periodically written drift file /var/lib/openntpd/ntpd.drift. Also sending "a SIGINFO signal, it [ntpd] will write its peer and sensor status to syslog" does not work either as there is no SIGINFO signal in Linux. ntpd(8) is wrong here. Regards, Mathias -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140131175026.ga11...@gmx.org
