Chronyd Won't Start

I finally got chrony to compile and install on RHL 9. When I entered,
/usr/local/sbin/chronyd, essentially nothing happened. No process started.
I'm trying to operate this assuming I have nothing more than a wrist watch
to use (isolated networks). I used the chrony.conf file in the chrony.txt
with a slight modification to account for IP addresses and command. I am
root and there's only one machine, 192.168.0.1. Here's what I have for
/etc/chrony.conf:

driftfile /etc/chrony.drift
commandkey 1
keyfile /etc/chrony.keys
initstepslew 10 192.168.0.1
local stratum 8
manual
allow 192.168.0

For chrony.keys:
1 192.168.0.1

The above is the master and I have no clients.

--
Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet

Web Page: <home.earthlink.net/~mtnviews>

"W. Wat son" <(E-Mail Removed)> writes:

>I finally got chrony to compile and install on RHL 9. When I entered,
>/usr/local/sbin/chronyd, essentially nothing happened. No process started.
>I'm trying to operate this assuming I have nothing more than a wrist watch
>to use (isolated networks). I used the chrony.conf file in the chrony.txt
>with a slight modification to account for IP addresses and command. I am
>root and there's only one machine, 192.168.0.1. Here's what I have for
>/etc/chrony.conf:

>driftfile /etc/chrony.drift
>commandkey 1
>keyfile /etc/chrony.keys
>initstepslew 10 192.168.0.1
>local stratum 8
>manual
>allow 192.168.0

>For chrony.keys:
>1 192.168.0.1

chrony.keys has the number together with a password. 192.168.0.1 is a very
strange password.

Look in /var/log/messages to see if there is a message from chronyd telling
you what the problem is.
Your initstepslew makes no sense. You have to give it an ntp server. It
itself cannot act as a chrony server.
Why the allow line? As you said it is alone.


>The above is the master and I have no clients.

>--
> Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
> (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
> Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet

> Web Page: <home.earthlink.net/~mtnviews>

Bill Unruh wrote:
> "W. Wat son" <(E-Mail Removed)> writes:
>
>
>>I finally got chrony to compile and install on RHL 9. When I entered,
>>/usr/local/sbin/chronyd, essentially nothing happened. No process started.
>>I'm trying to operate this assuming I have nothing more than a wrist watch
>>to use (isolated networks). I used the chrony.conf file in the chrony.txt
>>with a slight modification to account for IP addresses and command. I am
>>root and there's only one machine, 192.168.0.1. Here's what I have for
>>/etc/chrony.conf:
>
>
>>driftfile /etc/chrony.drift
>>commandkey 1
>>keyfile /etc/chrony.keys
>>initstepslew 10 192.168.0.1
>>local stratum 8
>>manual
>>allow 192.168.0
>
>
>>For chrony.keys:
>>1 192.168.0.1
>
>
> chrony.keys has the number together with a password. 192.168.0.1 is a very
> strange password.
>
> Look in /var/log/messages to see if there is a message from chronyd telling
> you what the problem is.
> Your initstepslew makes no sense. You have to give it an ntp server. It
> itself cannot act as a chrony server.
> Why the allow line? As you said it is alone.
>
>
>
>>The above is the master and I have no clients.
>
Bueno. I'll take a look at /var/...
initstepslew was taken directly from the chrony.txt file. Note in the the
chrony.txt file:
========
An example of use of the command is:
initstepslew 30 foo.bar.com baz.quz.com
========
The chrony.conf was taken directly from the txt section, 3.3, on isolated
networks, with a few modifications. The example includes allow.

Yes, passwords for chrony.key.
--
Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet

Web Page: <home.earthlink.net/~mtnviews>

"W. Wat son" <(E-Mail Removed)> writes:

>>
>>>driftfile /etc/chrony.drift
>>>commandkey 1
>>>keyfile /etc/chrony.keys
>>>initstepslew 10 192.168.0.1
>>>local stratum 8
>>>manual
>>>allow 192.168.0
>initstepslew was taken directly from the chrony.txt file. Note in the the
>chrony.txt file:
>========
>An example of use of the command is:
> initstepslew 30 foo.bar.com baz.quz.com

Yes, but you have to know what it means. It means that if the system is at
initialization is more than 30 sec out, the system time is stepped. It
determines how out it is by querying the ntp servers listed. Your own
system is NOT an ntp server. It precisely does not know what its own time
is so asing it to query itself makes no sense at all. " My wristwatch is
not at the correct time. I will adjust it by looking at my wristwatch to
see what the time is." Can yousee something wrong with that logic?

allow makes no sense either, since there are no other machines which will
use this machine as their time standard. Remove both items.
>========
>The chrony.conf was taken directly from the txt section, 3.3, on isolated
>networks, with a few modifications. The example includes allow.



>Yes, passwords for chrony.key.
>--
> Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
> (121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
> Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet

> Web Page: <home.earthlink.net/~mtnviews>

Bill Unruh wrote:
> "W. Wat son" <(E-Mail Removed)> writes:
>
>
....
> is so asing it to query itself makes no sense at all. " My wristwatch is
> not at the correct time. I will adjust it by looking at my wristwatch to
> see what the time is." Can yousee something wrong with that logic?
>
> allow makes no sense either, since there are no other machines which will
> use this machine as their time standard. Remove both items.
>
>>========
>>The chrony.conf was taken directly from the txt section, 3.3, on isolated
>>networks, with a few modifications. The example includes allow.
>
>
>
>
>>Yes, passwords for chrony.key.

From messages:

Feb 16 08:18:07 AstroPC2004 chronyd[3861]: chronyd version V1_20 starting
Feb 16 08:18:08 AstroPC2004 chronyd[3861]: Initial txc.tick=10000
txc.freq=0 (0.00000000) txc.offset=0 => hz=100 shift_hz=7
Feb 16 08:18:08 AstroPC2004 chronyd[3861]: 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
Feb 16 08:18:08 AstroPC2004 chronyd[3861]: Linux kernel major=2 minor=4
patch=20
Feb 16 08:18:08 AstroPC2004 chronyd[3861]: calculated_freq_scale=0.99902439
freq_scale=0.99902439
Feb 16 08:18:08 AstroPC2004 chronyd[3861]: Fatal error : Could not bind
socket : Address already in use



--
Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet

Web Page: <home.earthlink.net/~mtnviews>

"W. Wat son" <(E-Mail Removed)> writes:


> From messages:

>Feb 16 08:18:08 AstroPC2004 chronyd[3861]: Fatal error : Could not bind
>socket : Address already in use

That indicates that you are running something like ntpd as well
ps aux|grep ntp
should show if you are.
Or chronyd is already running.

Bill Unruh wrote:

> "W. Wat son" <(E-Mail Removed)> writes:
>
>
>
>>From messages:
>
>
>>Feb 16 08:18:08 AstroPC2004 chronyd[3861]: Fatal error : Could not bind
>>socket : Address already in use
>
>
> That indicates that you are running something like ntpd as well
> ps aux|grep ntp
> should show if you are.
> Or chronyd is already running.
>
>
Killed and chronyd has started. Issuance of trimrtc produces "501 not
authoris[z]ed" I find no reference to 501 or authorised in chrony.txt.

I noticed a command, rtcdata. It proclaimed I did not have a /dev/rtc
driver, so I added a rtcdriver /dev/rtc and rtcfile /etc/chrony.rtc to to
chrony.conf. It liked it. trimrtc still gave the same result. This little
trail seems false at the moment.

New trail?

--
Wayne T. Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet

Web Page: <home.earthlink.net/~mtnviews>

"W. Wat son" <(E-Mail Removed)> writes:

>Bill Unruh wrote:

>> "W. Wat son" <(E-Mail Removed)> writes:
>>
>>
>>
>>>From messages:
>>
>>
>>>Feb 16 08:18:08 AstroPC2004 chronyd[3861]: Fatal error : Could not bind
>>>socket : Address already in use
>>
>>
>> That indicates that you are running something like ntpd as well
>> ps aux|grep ntp
>> should show if you are.
>> Or chronyd is already running.
>>
>>
>Killed and chronyd has started. Issuance of trimrtc produces "501 not
>authoris[z]ed" I find no reference to 501 or authorised in chrony.txt.

trimrtc is a protected command. You must enter the
password <yourpassword>
into chronyc, where <yourpassowrd> is the word you associated with the
commandkey number.
(ie in chrony.conf you have a line which says
commandkey 11
or some other number.
In chrony.keys you have a line which says
11 <yourpassword>
That is the password you use.)



>I noticed a command, rtcdata. It proclaimed I did not have a /dev/rtc
>driver, so I added a rtcdriver /dev/rtc and rtcfile /etc/chrony.rtc to to
>chrony.conf. It liked it. trimrtc still gave the same result. This little
>trail seems false at the moment.

Be careful. If yo uare running a a kernel after about 2.6.7, the rtc driver
is broken and chronyd is severely broken (it will fill up your
/var/partition in seconds with error messages to /var/log/messages and
syslog ie they will grow at teh rate of GB/min.)
If you have that problem use the genrtc module instead of the rtc module.

Bill Unruh wrote:

> "W. Wat son" <(E-Mail Removed)> writes:
>
....

>
>>Killed and chronyd has started. Issuance of trimrtc produces "501 not
>>authoris[z]ed" I find no reference to 501 or authorised in chrony.txt.
>
>
> trimrtc is a protected command. You must enter the
> password <yourpassword>
> into chronyc, where <yourpassowrd> is the word you associated with the
> commandkey number.
> (ie in chrony.conf you have a line which says
> commandkey 11
> or some other number.
> In chrony.keys you have a line which says
> 11 <yourpassword>
> That is the password you use.)
>
>
>>I noticed a command, rtcdata. It proclaimed I did not have a /dev/rtc
>>driver, so I added a rtcdriver /dev/rtc and rtcfile /etc/chrony.rtc to to
>>chrony.conf. It liked it. trimrtc still gave the same result. This little
>>trail seems false at the moment.
>
>
> Be careful. If yo uare running a a kernel after about 2.6.7, the rtc driver
> is broken and chronyd is severely broken (it will fill up your
> /var/partition in seconds with error messages to /var/log/messages and
> syslog ie they will grow at teh rate of GB/min.)
> If you have that problem use the genrtc module instead of the rtc module.
>
Tried password and it gave me: "501 not authorised -- Reply not certified"
I tried two different passwords. My original was 8 chars, and the second 4.

"W. Wat son" <(E-Mail Removed)> writes:

>Bill Unruh wrote:

>> "W. Wat son" <(E-Mail Removed)> writes:
>>
>...

>>
>>>Killed and chronyd has started. Issuance of trimrtc produces "501 not
>>>authoris[z]ed" I find no reference to 501 or authorised in chrony.txt.
>>
>>
>> trimrtc is a protected command. You must enter the
>> password <yourpassword>
>> into chronyc, where <yourpassowrd> is the word you associated with the
>> commandkey number.
>> (ie in chrony.conf you have a line which says
>> commandkey 11
>> or some other number.
>> In chrony.keys you have a line which says
>> 11 <yourpassword>
>> That is the password you use.)
>>
>>
>>>I noticed a command, rtcdata. It proclaimed I did not have a /dev/rtc
>>>driver, so I added a rtcdriver /dev/rtc and rtcfile /etc/chrony.rtc to to
>>>chrony.conf. It liked it. trimrtc still gave the same result. This little
>>>trail seems false at the moment.
>>
>>
>> Be careful. If yo uare running a a kernel after about 2.6.7, the rtc driver
>> is broken and chronyd is severely broken (it will fill up your
>> /var/partition in seconds with error messages to /var/log/messages and
>> syslog ie they will grow at teh rate of GB/min.)
>> If you have that problem use the genrtc module instead of the rtc module.
>>
>Tried password and it gave me: "501 not authorised -- Reply not certified"
>I tried two different passwords. My original was 8 chars, and the second 4.

So you put a line like
commandkey 11
into /etc/chrony.conf
and a line like
11 mypassword
into /etc/chrony.keys

Then you restart chronyd ( eg on redhat or mandrake
service chronyd restart
) since chrony only reads its configuration files
when started up.
Then start chronyc and type in
password mypassword