| View previous topic :: View next topic |
| Author |
Message |
captwiggum
n00b
Joined: 10 Mar 2006
Posts: 39
Location: Atlanta, Georgia, USA
|
 Posted: Fri Mar 10, 2006 4:26 pm Post subject: net-misc/openntpd-3.7_p1 "adjtime failed: Invalid argum |
 |
|
SUMMARY:
I had a nice clean emerge of net-misc/openntpd-3.7_p1 and when I run it (as root of course) it syslogs this error: adjtime failed: Invalid argument. Any ideas appreciated.
Thanks!
DETAIL:
I like the idea of using openntpd, rather than net-misc/ntp-4.2.0.20040617-r3, because the dependencies and the implementation are so much simpler. So I hope I can solve this problem and not have to switch apps. Below is the full syslog when I run openntpd as root:
Feb 10 09:20:10 homer ntpd[10186]: ntp engine ready
Feb 10 14:20:30 homer ntpd[10186]: peer 202.234.64.222 now valid
Feb 10 14:20:30 homer ntpd[10186]: peer 83.137.103.134 now valid
Feb 10 14:20:31 homer ntpd[10186]: peer 64.172.230.138 now valid
Feb 10 14:20:31 homer ntpd[10186]: peer 83.137.16.7 now valid
Feb 10 14:20:32 homer ntpd[10186]: peer 194.100.206.70 now valid
Feb 10 14:20:34 homer ntpd[10186]: peer 24.9.197.224 now valid
Feb 10 14:20:35 homer ntpd[10186]: peer 65.19.139.44 now valid
Feb 10 09:21:31 homer ntpd[10185]: adjusting local clock by 2419212.974903s
Feb 10 09:21:31 homer ntpd[10185]: adjtime failed: Invalid argument
Feb 10 09:25:49 homer ntpd[10185]: adjusting local clock by 2419212.962974s
Feb 10 09:25:49 homer ntpd[10185]: adjtime failed: Invalid argument
Here is a link to the log of my emerge with all config and compile detail:
http://captwiggum.com/tmp/openntpd.txt |
|
| Back to top |
|
 |
PaulBredbury
Watchman
Joined: 14 Jul 2005
Posts: 7310
|
| Posted: Fri Mar 10, 2006 5:02 pm Post subject: Re: net-misc/openntpd-3.7_p1 "adjtime failed: Invalid a |
|
|
| captwiggum wrote: | | because the dependencies and the implementation are so much simpler. |
Which dependency of ntp don't you like?
See openntp wiki entry, and perhaps you will switch to ntp after all, due to the "clock drift" issue  |
|
| Back to top |
|
|
captwiggum
n00b
Joined: 10 Mar 2006
Posts: 39
Location: Atlanta, Georgia, USA
|
| Posted: Fri Mar 10, 2006 9:24 pm Post subject: |
|
|
I did not mean to make any insult to net-misc/ntp-4.2.0.20040617-r3, only it required three packages amounting to about 5MB, and the openntpd package had no emerge dependencies for the current state of my system. Also its motto of minimal-simple appealed to me.
Now that I'm using it, it does not have the one feature that I did want, a flag to "update system clock and exit". I've asked the maintainer if they would be interested in a patch from me to add this functionality. If they do not want it, then I'll fall back to ntp-4.2.0.
Also, I still have the above posted problem. openntpd is simply not working. Looks like a system call its making has a bad parameter or something.
Thanks for your reply. |
|
| Back to top |
|
|
PaulBredbury
Watchman
Joined: 14 Jul 2005
Posts: 7310
|
| Posted: Fri Mar 10, 2006 9:38 pm Post subject: |
|
|
| captwiggum wrote: | | a flag to "update system clock and exit". |
Sounds like you might be interested in the rdate command/package.
But, ntp is the way to keep a reasonably-Internet-connected PC synced to the right time. Note that /etc/init.d/ntp-client is intended to set the date instantly, to be executed when the PC boots up and has an Internet connection. |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Fri Mar 10, 2006 10:18 pm Post subject: Re: net-misc/openntpd-3.7_p1 "adjtime failed: Invalid a |
|
|
| captwiggum wrote: | Feb 10 09:21:31 homer ntpd[10185]: adjusting local clock by 2419212.974903s
Feb 10 09:21:31 homer ntpd[10185]: adjtime failed: Invalid argument |
Your clock is too far out to be synced. Either set it manually or start openntpd with the -s parameter (option in /etc/conf.d/ntpd); see man ntpd: | Code: | -s Set the time immediately at startup if the local clock is off by more than 180 seconds. Allows
for a large time correction, eliminating the need to run rdate(8) before starting ntpd.
|
rdate not necessary.
Chris
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
captwiggum
n00b
Joined: 10 Mar 2006
Posts: 39
Location: Atlanta, Georgia, USA
|
| Posted: Fri Mar 10, 2006 11:26 pm Post subject: |
|
|
Good catch. What worries me is how the time changed around in those log messages. Also, my TZ env var and /etc/localtime are set correctly (EST) and my clock is only off by less than a minute. So how did openntpd get that crazy adjustment? My /etc/conf.d/clock is set to UTC, and maybe openntpd doesn't know about this method of keeping utc/local? I dunno. I give up. I'll just clean it and emerge net-misc/ntp-4.2.0.20040617-r3.
THANKS to all for your responses! |
|
| Back to top |
|
|
darkphader
Veteran
Joined: 09 May 2002
Posts: 1225
Location: Motown
|
| Posted: Fri Mar 10, 2006 11:39 pm Post subject: |
|
|
| captwiggum wrote: | | Also, my TZ env var and /etc/localtime are set correctly (EST) and my clock is only off by less than a minute. So how did openntpd get that crazy adjustment? My /etc/conf.d/clock is set to UTC, and maybe openntpd doesn't know about this method of keeping utc/local? |
It works right on at least 10 different systems for me. All systems have there HW clock set to UTC and TZ is EST5EDT or equivalent. Several of them are time servers for the LAN as well.
Chris
_________________
WYSIWYG - What You See Is What You Grep |
|
| Back to top |
|
|
|
Networking & Security
