-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, May 22, 2009 at 01:20:56AM -0400, Celejar wrote:
>
> Just to go through the obvious, since you haven't told us how you're
> connecting to the internet: *are* you connecting through ppp? If so,
> can you provide the relevant syslog from the period right before,
> during and after you bring up the connection? The log should give us a
> clue as to why the sources aren't going online.
>
> Celejar
Not exactly knowing what ppp is I googled and I am not. So I believe
if-up/if-down is responsible? Looking in both of those files there is not
a corresponding file to chrony. Would I be able to copy
/etc/ppp/ip-up.d/chrony to /etc/if-up.d/chrony? (and ip-down.d) I don't
know much about scripts, the only line that stands out to me that may not
work as expected is touch /var/run/chrony-ppp-up
# cat /etc/ppp/ip-up.d/chrony
#!/bin/sh
# This script tells chronyd that the connection is up so that it can
# contact the server. John Hasler <jhas...@debian.org> 1998-2003
# Any possessor of a copy of this program may treat it as if it
# were in the public domain. I waive all rights.
/bin/pidof chronyd > /dev/null || exit 0
KEY=$(awk '$1 ~ /^commandkey$/ { print $2; exit}' /etc/chrony/chrony.conf)
PASSWORD=`awk '$1 ~ /^'$KEY'$/ {print $2; exit}' /etc/chrony/chrony.keys`
/usr/bin/chronyc << EOF
password $PASSWORD
online
burst 5/10
quit
EOF
touch /var/run/chrony-ppp-up
exit 0
# cat /etc/ppp/ip-down.d/chrony
#!/bin/sh
# This script tells chronyd that the connection is down
# so that it won't try to contact the server.
# John Hasler <jhas...@debian.org> 1998-2003
# Any possessor of a copy of this program may treat it as if it
# were in the public domain. I waive all rights.
/bin/pidof chronyd > /dev/null || exit 0
# Don't mark the connection offline unless we know ppp brought it up.
test -e /var/run/chrony-ppp-up || exit 0
KEY=$(awk '$1 ~ /^commandkey$/ { print $2; exit}' /etc/chrony/chrony.conf)
PASSWORD=`awk '$1 ~ /^'$KEY'$/ {print $2; exit}' /etc/chrony/chrony.keys`
/usr/bin/chronyc << EOF
password $PASSWORD
offline
EOF
rm -f /var/run/chrony-ppp-up
exit 0
- From recent restart of chrony
# grep chrony /var/log/syslog
May 22 01:34:48 T61 chronyd[6638]: chronyd exiting on signal
May 22 01:34:49 T61 chronyd[5673]: chronyd version 1.23 starting
May 22 01:34:49 T61 chronyd[5673]: Initial txc.tick=10000 txc.freq=-21449
(-0.32728577) txc.offset=0 => hz=100 shift_hz=7
May 22 01:34:49 T61 chronyd[5673]: set_config_hz=0 hz=100 shift_hz=7
basic_freq_scale=1.28000000 nominal_tick=10000 slew_delta_tick=833
max_tick_bias=1000
May 22 01:34:49 T61 chronyd[5673]: Linux kernel major=2 minor=6 patch=26
May 22 01:34:49 T61 chronyd[5673]: calculated_freq_scale=0.99902439
freq_scale=0.99902439
May 22 01:34:50 T61 chronyd[5673]: Source 216.45.57.38 online
May 22 01:34:50 T61 chronyd[5673]: Source 216.14.97.75 online
May 22 01:34:50 T61 chronyd[5673]: Selected source 216.45.57.38
May 22 01:34:52 T61 chronyd[5673]: Selected source 216.14.97.75
So what I'm starting to understand is by default install chrony assumes
limited connectivity with a PPP connection (e.g. dialup) with the correct
scripts to handle such circumstances. However, because I do not use PPP
but still have a somewhat limited connection depending on my location to a
wired or wireless access point chrony isn't aware (yet) if I'm connected
or not. Which still leaves me somewhat confused as to what is telling
chrony there is a connection when I restart the service, as the servers are
listed to start in an offline state until chrony is told I am now
connected via /etc/ppp/ip-up.d/chrony. If that mouthful makes sense.
- --
Daryl Styrk
Naples, FL USA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iEYEARECAAYFAkoWP6EACgkQ6baBhW8CzriuwACeM9DW4t8jYMskITiJx56KuWM+
xZkAnAiiTnM+OX+kbtxvdYKEI1LyNh4v
=7vVY
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
