Re: ntpd sync fails on boot
On Sat, 10 Jan 2009 15:28:40 +1030, Tim wrote:
> On Fri, 2009-01-09 at 18:43 +, Mike -- EMAIL IGNORED wrote:
>> On my FC7 system, on boot up:
>>ntpd: Synchronizing with time server:
>> always fails. However, after the boot, if I log on and restart ntpd,
>> the sync always succeeds.
>
> I also always had that problem on my Fedora 7 installations. NTPD would
> try to start before the network was up (or fully up) and never recover.
> I ran a script that would start up NTPD quite late in the boot process.
>
[...]
Here is my workaround, which works:
#!/bin/sh
#
# 01/10/09
#
# chkconfig: 3 99 1
# description: restarts ntpd
#
# Source function library.
case $1 in
start)
/etc/init.d/ntpd restart
sleep 5
;;
stop)
;;
restart)
;;
condrestart)
;;
reload)
;;
status)
;;
*)
echo "Usage: $DAEMON {start|stop|restart|condrestart|reload|status}"
exit 1
esac
exit 0
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 2009-01-09 at 18:43 +, Mike -- EMAIL IGNORED wrote: > On my FC7 system, on boot up: >ntpd: Synchronizing with time server: > always fails. However, after the boot, > if I log on and restart ntpd, the sync > always succeeds. I also always had that problem on my Fedora 7 installations. NTPD would try to start before the network was up (or fully up) and never recover. I ran a script that would start up NTPD quite late in the boot process. -- [...@localhost ~]$ uname -r 2.6.27.9-73.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Sat, 2009-01-10 at 02:14 +, Mike -- EMAIL IGNORED wrote: > This may be because my FC7 is old. As suggested in > other posts, it may be time to upgrade. Still, it > would be interesting to figure out what the problems > is (if it could be done with only moderate effort). I suspect so... You could try to push ntpd startup back Edit /etc/init.d/ntpd # ntpd This shell script takes care of starting and stopping # ntpd (NTPv4 daemon). # # chkconfig: 35 58 74 change the 58 to maybe 80 or 90 or ... i.e. chkconfig ntpd off edit /etc/init.d/ntpd chkconfig ntpd on reboot or you could just fiddle with the symbolic links in your runlevel... i.e. mv /etc/rc5.d/S58ntpd /etc/rc5.d/S91ntpd of course this is just speculation and I have no basis to believe that this will actually work. or you could just try adding this to the end of /etc/rc.d/rc.local /etc/init.d/ntpd restart & Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 09 Jan 2009 17:05:42 -0800, Rick Stevens wrote:
> Mike -- EMAIL IGNORED wrote:
>> On Fri, 09 Jan 2009 23:57:02 +, Mike -- EMAIL IGNORED wrote:
>>
>>> On Fri, 09 Jan 2009 16:38:23 -0700, Craig White wrote:
>>>
>> [...]
as root...
# fixfiles onboot
# shutdown now -r
>> [...]
>>
>> fixfiles onreboot is not available on my fixfiles.
>
> "fixfiles onboot" not "fixfiles onreboot"
>
>> I did: fixfiles restore
>> and then rebooted. It cleaned up the log some, but the failure
>> persists.
>>
>> boot messages excerpt:
>>
>> Jan 9 19:12:16 mbrc32 hpiod: 1.7.4a accepting connections at 2208...
>> Jan 9 19:12:17 mbrc32 ntpdate[2220]: sendto(mbrc21): Operation not
>> permitted
>
> The fact that you can start it once you're logged in really states that
> the network is not running before at boot which is a classic NM thing. I
> know this was discussed earlier in the thread, but are you REALLY sure
> the network is up?
>
> When you boot up and BEFORE you log into the GUI, can you log in as root
> on a text console (press CTRL-ALT-F2 and log in as root) and do an
> "ifconfig" to verify eth0 is up and has an IP on it? If not, then as
> the MythBusters would say, "THERE'S your problem!" and you either will
> have to always start ntpd after you log in or abandon NM and go back to
> the older network startup mechanism. Don't try to use both... they
> don't play nice with each other.
>
> To go back to the GUI, press ALT-F1.
> -- -
> Rick Stevens, Systems Engineer ri...@nerd.com - -
> AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -
> - -
> Never eat anything larger than your head -
> --
I always boot to level 3, and for all these tests,
logged on as root. (My initial experience with
computers long predates GUI's of any kind; I
consider them a necessary evil.) I tried your
ifconfig suggestion, and eth0 is just fine, (as
are the tap devices for openvpn). This is not a
surprise, since immediately after boot I can
restart ntpd and get a rapid sync. Of course, I
can't be sure the network is up during the boot when
ntpd tries to sync. It should be according to the
order of things. I suppose I could create a fake
demon file in init.d and run ifconfig during the
boot? What do you think?
I don't know what you mean by "older network startup
mechanism". Is this something I should try? In
case this is relevant, I do not start NetworkManager.
BTW:
[root]# fixfiles onboot
Usage: /sbin/fixfiles [-l logfile ] [-o outputfile ] { check | restore|[-
F] relabel } [[dir] ... ]
or
Usage: /sbin/fixfiles -R rpmpackage[,rpmpackage...] -C
PREVIOUS_FILECONTEXT [-l logfile ] [-o outputfile ] { check | restore }
This may be because my FC7 is old. As suggested in
other posts, it may be time to upgrade. Still, it
would be interesting to figure out what the problems
is (if it could be done with only moderate effort).
Mike.
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
Mike -- EMAIL IGNORED wrote: > On my FC7 system Fedora 7 is no longer supported, please upgrade to at least Fedora 9. (Support for Fedora 8 was also dropped.) Kevin Kofler -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
Mike -- EMAIL IGNORED wrote: On Fri, 09 Jan 2009 23:57:02 +, Mike -- EMAIL IGNORED wrote: On Fri, 09 Jan 2009 16:38:23 -0700, Craig White wrote: [...] as root... # fixfiles onboot # shutdown now -r [...] fixfiles onreboot is not available on my fixfiles. "fixfiles onboot" not "fixfiles onreboot" I did: fixfiles restore and then rebooted. It cleaned up the log some, but the failure persists. boot messages excerpt: Jan 9 19:12:16 mbrc32 hpiod: 1.7.4a accepting connections at 2208... Jan 9 19:12:17 mbrc32 ntpdate[2220]: sendto(mbrc21): Operation not permitted The fact that you can start it once you're logged in really states that the network is not running before at boot which is a classic NM thing. I know this was discussed earlier in the thread, but are you REALLY sure the network is up? When you boot up and BEFORE you log into the GUI, can you log in as root on a text console (press CTRL-ALT-F2 and log in as root) and do an "ifconfig" to verify eth0 is up and has an IP on it? If not, then as the MythBusters would say, "THERE'S your problem!" and you either will have to always start ntpd after you log in or abandon NM and go back to the older network startup mechanism. Don't try to use both... they don't play nice with each other. To go back to the GUI, press ALT-F1. -- - Rick Stevens, Systems Engineer ri...@nerd.com - - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 - -- - Never eat anything larger than your head - -- -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 09 Jan 2009 17:51:48 -0700, Craig White wrote: [...] > I would recommend that you take DNS & /etc/hosts out of this equation by > changing mbrc21 with the ip address but beyond that - I simply don't > know > > Craig I did that and it didn't help. Maybe I should think of upgrading the system. Mike. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Sat, 2009-01-10 at 00:24 +, Mike -- EMAIL IGNORED wrote: > On Fri, 09 Jan 2009 23:57:02 +, Mike -- EMAIL IGNORED wrote: > > > On Fri, 09 Jan 2009 16:38:23 -0700, Craig White wrote: > > > [...] > >> as root... > >> # fixfiles onboot > >> # shutdown now -r > [...] > > fixfiles onreboot is not available on my fixfiles. > I did: fixfiles restore > and then rebooted. It cleaned up the log some, > but the failure persists. > > boot messages excerpt: > > Jan 9 19:12:16 mbrc32 hpiod: 1.7.4a accepting connections at 2208... > Jan 9 19:12:17 mbrc32 ntpdate[2220]: sendto(mbrc21): Operation not > permitted > Jan 9 19:12:20 mbrc32 last message repeated 3 times > Jan 9 19:12:21 mbrc32 ntpdate[2220]: no server suitable for > synchronization found > Jan 9 19:12:21 mbrc32 ntpd[2223]: ntpd 4.2@1.1495-o Thu Jun 21 > 10:53:04 UTC 2007 (1) > Jan 9 19:12:21 mbrc32 ntpd[2224]: precision = 1.000 usec > Jan 9 19:12:21 mbrc32 ntpd[2224]: Listening on interface #0 wildcard, > 0.0.0.0#123 Disabled > Jan 9 19:12:21 mbrc32 ntpd[2224]: Listening on interface #1 > wildcard, ::#123 Disabled > Jan 9 19:12:21 mbrc32 ntpd[2224]: Listening on interface #2 lo, ::1#123 > Enabled > Jan 9 19:12:21 mbrc32 ntpd[2224]: Listening on interface #3 eth0, > fe80::20e:a6ff:fe82:ab1c#123 Enabled > Jan 9 19:12:21 mbrc32 ntpd[2224]: Listening on interface #4 lo, > 127.0.0.1#123 Enabled > Jan 9 19:12:21 mbrc32 ntpd[2224]: Listening on interface #5 eth0, > 192.168.9.32#123 Enabled > Jan 9 19:12:21 mbrc32 ntpd[2224]: kernel time sync status 0040 > Jan 9 19:12:21 mbrc32 ntpd[2224]: frequency initialized 184.463 PPM > from /var/lib/ntp/drift > Jan 9 19:12:22 mbrc32 kernel: tun: Universal TUN/TAP device driver, 1.6 I would recommend that you take DNS & /etc/hosts out of this equation by changing mbrc21 with the ip address but beyond that - I simply don't know Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
My time server is a CentOS 5 box and gets its time from tock.usno.navy.mil . I just rebooted it to see if its ntpd could sync on boot. It did it, although it took about half a dramatic minute. Mike. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 09 Jan 2009 23:57:02 +, Mike -- EMAIL IGNORED wrote: > On Fri, 09 Jan 2009 16:38:23 -0700, Craig White wrote: > [...] >> as root... >> # fixfiles onboot >> # shutdown now -r [...] fixfiles onreboot is not available on my fixfiles. I did: fixfiles restore and then rebooted. It cleaned up the log some, but the failure persists. boot messages excerpt: Jan 9 19:12:16 mbrc32 hpiod: 1.7.4a accepting connections at 2208... Jan 9 19:12:17 mbrc32 ntpdate[2220]: sendto(mbrc21): Operation not permitted Jan 9 19:12:20 mbrc32 last message repeated 3 times Jan 9 19:12:21 mbrc32 ntpdate[2220]: no server suitable for synchronization found Jan 9 19:12:21 mbrc32 ntpd[2223]: ntpd 4.2@1.1495-o Thu Jun 21 10:53:04 UTC 2007 (1) Jan 9 19:12:21 mbrc32 ntpd[2224]: precision = 1.000 usec Jan 9 19:12:21 mbrc32 ntpd[2224]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Jan 9 19:12:21 mbrc32 ntpd[2224]: Listening on interface #1 wildcard, ::#123 Disabled Jan 9 19:12:21 mbrc32 ntpd[2224]: Listening on interface #2 lo, ::1#123 Enabled Jan 9 19:12:21 mbrc32 ntpd[2224]: Listening on interface #3 eth0, fe80::20e:a6ff:fe82:ab1c#123 Enabled Jan 9 19:12:21 mbrc32 ntpd[2224]: Listening on interface #4 lo, 127.0.0.1#123 Enabled Jan 9 19:12:21 mbrc32 ntpd[2224]: Listening on interface #5 eth0, 192.168.9.32#123 Enabled Jan 9 19:12:21 mbrc32 ntpd[2224]: kernel time sync status 0040 Jan 9 19:12:21 mbrc32 ntpd[2224]: frequency initialized 184.463 PPM from /var/lib/ntp/drift Jan 9 19:12:22 mbrc32 kernel: tun: Universal TUN/TAP device driver, 1.6 Mike. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 09 Jan 2009 16:38:23 -0700, Craig White wrote: > On Fri, 2009-01-09 at 23:04 +, Mike -- EMAIL IGNORED wrote: >[...] > > 1 - you're using mbrc32 in /etc/ntp/step-tickers but 192.168.9.21 in > /etc/ntp.conf No, mbrc32 (192.168.9.32) is the machine that I am rebooting and has the problem. mdrc21 (192.168.9.21) is the time server. > > 2 - You really need to relabel your disk for selinux... > > as root... > # fixfiles onboot > # shutdown now -r Ok, I'll do it. Do you think that this will help even though selinux should not really doing anything? > > Go to lunch...rebooting/relabeling could take a while I have already had supper at -0500. > > Craig Thanks, Mike. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 2009-01-09 at 23:04 +, Mike -- EMAIL IGNORED wrote: > On Fri, 09 Jan 2009 15:21:42 -0500, Todd Denniston wrote: > > [...] > > any ntpd messages in /var/log/messages during boot? If ntpd detects what > > the problem is, it often gives a clue there. > > > > do you see any messages on boot where network is being delayed? > > > > Is it only the ntpdate failing or is ntpd also not finding hosts on > > boot? if only ntpdate, then I would suspect the /etc/ntp/ntpservers or > > /etc/ntp/step-tickers to have a bad name. if it is both ntpdate and ntpd > > failing, then I would suspect some problem with DNS, but that usually > > leaves traces in /var/log/messages. > > > > -- > > Todd Denniston > > Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the > > Power of Technology for the Warfighter > > Here are some excerpts from /var/log/messages: > > This is a failure on boot: > > Jan 9 17:30:24 mbrc32 automount[2112]: lookup_read_master: lookup > (nisplus): couldn't locat nis+ table auto.master > Jan 9 17:30:25 mbrc32 nscd: 2137 Access Vector Cache (AVC) started > Jan 9 17:30:25 mbrc32 hpiod: 1.7.4a accepting connections at 2208... > Jan 9 17:30:26 mbrc32 ntpdate[2223]: sendto(mbrc21): Operation not > permitted > Jan 9 17:30:27 mbrc32 setroubleshoot: SELinux is preventing the / > usr/sbin/nscd from using potentially mislabeled files (/etc/hosts). > For complete SELinux messages. r > un sealert -l d4747998-8ff4-4f42-8688-a3671216 > Jan 9 17:30:27 mbrc32 ntpdate[2223]: sendto(mbrc21): Operation not > permitted > Jan 9 17:30:29 mbrc32 last message repeated 2 times > Jan 9 17:30:30 mbrc32 ntpdate[2223]: no server suitable for > synchronization found > Jan 9 17:30:30 mbrc32 ntpd[2228]: ntpd 4.2@1.1495-o Thu Jun 21 > 10:53:04 UTC 2007 (1) > > > > Ihis is a successful command line restart of ntp: > > Jan 9 17:31:34 mbrc32 setroubleshoot: SELinux is preventing /usr/ > sbin/openvpn (openvpn_t) "write" to /etc/openvpn/openvpn-status.log > (openvpn_etc_t). For complete SELinux messages. run sealert -l > c3e4092f-9526-45a2-9eaf-effe3284ee2c > Jan 9 17:31:42 mbrc32 setroubleshoot: SELinux is preventing the / > usr/sbin/nscd from using potentially mislabeled files (/etc/hosts). > For complete SELinux messages. run sealert -l d4747998-8ff4-4f42-8688- > a3671216 > Jan 9 17:32:47 mbrc32 ntpd[2229]: ntpd exiting on signal 15 > Jan 9 17:32:47 mbrc32 ntpdate[3264]: step time server 192.168.9.21 > offset 0.110985 sec > Jan 9 17:32:47 mbrc32 ntpd[3266]: ntpd 4.2@1.1495-o Thu Jun 21 > 10:53:04 UTC 2007 (1) > Jan 9 17:32:47 mbrc32 ntpd[3267]: precision = 1.000 usec > Jan 9 17:32:47 mbrc32 ntpd[3267]: Listening on interface #0 wildcard, > 0.0.0.0#123 Disabled > > Could selinux be interfering even though > /etc/selinux/config (comments removed): > SELINUX=permissive > SELINUXTYPE=targeted > SETLOCALDEFS=0 > > When I first looked at messages per your suggestion, it looked > like openvpn might be related to the problem. I therefore > changed /etc/init.d/openvpn so openvpn would start after ntpd. > No difference. 1 - you're using mbrc32 in /etc/ntp/step-tickers but 192.168.9.21 in /etc/ntp.conf 2 - You really need to relabel your disk for selinux... as root... # fixfiles onboot # shutdown now -r Go to lunch...rebooting/relabeling could take a while Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 09 Jan 2009 15:21:42 -0500, Todd Denniston wrote: [...] > any ntpd messages in /var/log/messages during boot? If ntpd detects what > the problem is, it often gives a clue there. > > do you see any messages on boot where network is being delayed? > > Is it only the ntpdate failing or is ntpd also not finding hosts on > boot? if only ntpdate, then I would suspect the /etc/ntp/ntpservers or > /etc/ntp/step-tickers to have a bad name. if it is both ntpdate and ntpd > failing, then I would suspect some problem with DNS, but that usually > leaves traces in /var/log/messages. > > -- > Todd Denniston > Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the > Power of Technology for the Warfighter Here are some excerpts from /var/log/messages: This is a failure on boot: Jan 9 17:30:24 mbrc32 automount[2112]: lookup_read_master: lookup (nisplus): couldn't locat nis+ table auto.master Jan 9 17:30:25 mbrc32 nscd: 2137 Access Vector Cache (AVC) started Jan 9 17:30:25 mbrc32 hpiod: 1.7.4a accepting connections at 2208... Jan 9 17:30:26 mbrc32 ntpdate[2223]: sendto(mbrc21): Operation not permitted Jan 9 17:30:27 mbrc32 setroubleshoot: SELinux is preventing the / usr/sbin/nscd from using potentially mislabeled files (/etc/hosts). For complete SELinux messages. r un sealert -l d4747998-8ff4-4f42-8688-a3671216 Jan 9 17:30:27 mbrc32 ntpdate[2223]: sendto(mbrc21): Operation not permitted Jan 9 17:30:29 mbrc32 last message repeated 2 times Jan 9 17:30:30 mbrc32 ntpdate[2223]: no server suitable for synchronization found Jan 9 17:30:30 mbrc32 ntpd[2228]: ntpd 4.2@1.1495-o Thu Jun 21 10:53:04 UTC 2007 (1) Ihis is a successful command line restart of ntp: Jan 9 17:31:34 mbrc32 setroubleshoot: SELinux is preventing /usr/ sbin/openvpn (openvpn_t) "write" to /etc/openvpn/openvpn-status.log (openvpn_etc_t). For complete SELinux messages. run sealert -l c3e4092f-9526-45a2-9eaf-effe3284ee2c Jan 9 17:31:42 mbrc32 setroubleshoot: SELinux is preventing the / usr/sbin/nscd from using potentially mislabeled files (/etc/hosts). For complete SELinux messages. run sealert -l d4747998-8ff4-4f42-8688- a3671216 Jan 9 17:32:47 mbrc32 ntpd[2229]: ntpd exiting on signal 15 Jan 9 17:32:47 mbrc32 ntpdate[3264]: step time server 192.168.9.21 offset 0.110985 sec Jan 9 17:32:47 mbrc32 ntpd[3266]: ntpd 4.2@1.1495-o Thu Jun 21 10:53:04 UTC 2007 (1) Jan 9 17:32:47 mbrc32 ntpd[3267]: precision = 1.000 usec Jan 9 17:32:47 mbrc32 ntpd[3267]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Could selinux be interfering even though /etc/selinux/config (comments removed): SELINUX=permissive SELINUXTYPE=targeted SETLOCALDEFS=0 When I first looked at messages per your suggestion, it looked like openvpn might be related to the problem. I therefore changed /etc/init.d/openvpn so openvpn would start after ntpd. No difference. Mike. ~ ~ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 09 Jan 2009 14:49:34 -0700, Craig White wrote: > On Fri, 2009-01-09 at 21:42 +, Mike -- EMAIL IGNORED wrote: >> On Fri, 09 Jan 2009 13:12:35 -0700, Craig White wrote: >> >> > On Fri, 2009-01-09 at 20:04 +, Mike -- EMAIL IGNORED wrote: >> >> On Fri, 09 Jan 2009 11:58:25 -0700, Craig White wrote: >> >> >> >> >> [...] >> > >> > yeah - not a NetworkManager issue at all. >> > >> > # cat /etc/ntp/step-tickers >> > # List of servers used for initial synchronization. >> > >> > What do you have there? >> > >> > Craig >> >> [root]# cat /etc/ntp/step-tickers >> mbrc21 >> >> Not much. What you see is the name of the local ntp server (among >> other things). It is correctly defined in /etc/hosts . > > that's likely to be the problem though... > > is mbrc21 listed by itself in /etc/hosts? > > You might want to temporarily put in the actual IP Address instead > > Craig mbrc21 is on a line with other names. I put in the IP address as you suggested. It didn't help. Mike. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 2009-01-09 at 21:42 +, Mike -- EMAIL IGNORED wrote: > On Fri, 09 Jan 2009 13:12:35 -0700, Craig White wrote: > > > On Fri, 2009-01-09 at 20:04 +, Mike -- EMAIL IGNORED wrote: > >> On Fri, 09 Jan 2009 11:58:25 -0700, Craig White wrote: > >> > > [...] > > > > yeah - not a NetworkManager issue at all. > > > > # cat /etc/ntp/step-tickers > > # List of servers used for initial synchronization. > > > > What do you have there? > > > > Craig > > [root]# cat /etc/ntp/step-tickers > mbrc21 > > Not much. What you see is the name of the > local ntp server (among other things). It > is correctly defined in /etc/hosts . that's likely to be the problem though... is mbrc21 listed by itself in /etc/hosts? You might want to temporarily put in the actual IP Address instead Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 09 Jan 2009 13:12:35 -0700, Craig White wrote: > On Fri, 2009-01-09 at 20:04 +, Mike -- EMAIL IGNORED wrote: >> On Fri, 09 Jan 2009 11:58:25 -0700, Craig White wrote: >> [...] > > yeah - not a NetworkManager issue at all. > > # cat /etc/ntp/step-tickers > # List of servers used for initial synchronization. > > What do you have there? > > Craig [root]# cat /etc/ntp/step-tickers mbrc21 Not much. What you see is the name of the local ntp server (among other things). It is correctly defined in /etc/hosts . Mike. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 2009-01-09 at 20:04 +, Mike -- EMAIL IGNORED wrote: > On Fri, 09 Jan 2009 11:58:25 -0700, Craig White wrote: > > [...] > > sounds like an old discussion... > > > > perhaps ntpd starts before network is up and running - i.e. running > > 'NetworkManager' > > > > What is output of (as root) > > > > chkconfig --list NetworkManager > > chkconfig --list network > > > > Craig > > Here is the information you requested as well as some other > relevant information. As you can see, I am not using > NetworkManager. The other things appear to start in the > correct order. > > ... > > # iptables Start iptables firewall > # > # chkconfig: 2345 08 92 > > [root]# chkconfig --list iptables > iptables0:off 1:off 2:on3:on4:on5:on6:off > > ... > > # network Bring up/down networking > # > # chkconfig: 2345 10 90 > > [root]# chkconfig --list network > network 0:off 1:off 2:on3:on4:on5:on6:off > > ... > > # ntpd This shell script takes care of starting and stopping > # ntpd (NTPv4 daemon). > # > # chkconfig: 35 58 74 > > [root]# chkconfig --list ntpd > ntpd0:off 1:off 2:off 3:on4:off 5:on6:off > > ... > > # NetworkManager: NetworkManager daemon > # > # chkconfig: - 98 02 > > [root]# chkconfig --list NetworkManager > NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off yeah - not a NetworkManager issue at all. # cat /etc/ntp/step-tickers # List of servers used for initial synchronization. What do you have there? Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
Mike -- EMAIL IGNORED wrote, On 01/09/2009 01:43 PM: On my FC7 system, on boot up: ntpd: Synchronizing with time server: always fails. However, after the boot, if I log on and restart ntpd, the sync always succeeds. I note that the time server it uses is "right next door", on my LAN on the same hub. Thanks for your suggestions. (Yes I know FC7 is old; might that be the problem?) Mike. any ntpd messages in /var/log/messages during boot? If ntpd detects what the problem is, it often gives a clue there. do you see any messages on boot where network is being delayed? Is it only the ntpdate failing or is ntpd also not finding hosts on boot? if only ntpdate, then I would suspect the /etc/ntp/ntpservers or /etc/ntp/step-tickers to have a bad name. if it is both ntpdate and ntpd failing, then I would suspect some problem with DNS, but that usually leaves traces in /var/log/messages. -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 09 Jan 2009 11:58:25 -0700, Craig White wrote: [...] > sounds like an old discussion... > > perhaps ntpd starts before network is up and running - i.e. running > 'NetworkManager' > > What is output of (as root) > > chkconfig --list NetworkManager > chkconfig --list network > > Craig Here is the information you requested as well as some other relevant information. As you can see, I am not using NetworkManager. The other things appear to start in the correct order. ... # iptables Start iptables firewall # # chkconfig: 2345 08 92 [root]# chkconfig --list iptables iptables0:off 1:off 2:on3:on4:on5:on6:off ... # network Bring up/down networking # # chkconfig: 2345 10 90 [root]# chkconfig --list network network 0:off 1:off 2:on3:on4:on5:on6:off ... # ntpd This shell script takes care of starting and stopping # ntpd (NTPv4 daemon). # # chkconfig: 35 58 74 [root]# chkconfig --list ntpd ntpd0:off 1:off 2:off 3:on4:off 5:on6:off ... # NetworkManager: NetworkManager daemon # # chkconfig: - 98 02 [root]# chkconfig --list NetworkManager NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off ... Mike. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: ntpd sync fails on boot
On Fri, 2009-01-09 at 18:43 +, Mike -- EMAIL IGNORED wrote: > On my FC7 system, on boot up: >ntpd: Synchronizing with time server: > always fails. However, after the boot, > if I log on and restart ntpd, the sync > always succeeds. > > I note that the time server it uses is > "right next door", on my LAN on the same > hub. > > Thanks for your suggestions. (Yes I know > FC7 is old; might that be the problem?) sounds like an old discussion... perhaps ntpd starts before network is up and running - i.e. running 'NetworkManager' What is output of (as root) chkconfig --list NetworkManager chkconfig --list network Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
ntpd sync fails on boot
On my FC7 system, on boot up: ntpd: Synchronizing with time server: always fails. However, after the boot, if I log on and restart ntpd, the sync always succeeds. I note that the time server it uses is "right next door", on my LAN on the same hub. Thanks for your suggestions. (Yes I know FC7 is old; might that be the problem?) Mike. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
