openSUSE Forums > Archives > Novell Archives » NTP failing to adjust the system time

Go Back   openSUSE Forums > Archives > Novell Archives
Forums FAQ Members List Search Today's Posts Mark Forums Read


Novell Archives Archived content from Novell openSUSE support forums

 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 23-Jul-2006, 01:44
forenconnnntact1@arcor.e
Guest
 
Posts: n/a
Default NTP failing to adjust the system time

Hi,

using Suse 10.1 on a 64Bit System ( Athlon 3000+ ) I tried to make use of
the NTP service but it does not work. If I launch the respective YAST
module to configure NTP I can select an NTP server and test it
successfully. Doing so the screen gets dark and comes back only if I strike
a key on my keyboard or if I move the mouse. The system time gets adjusted
but after rebooting the system time it is exxtremely wrong (> 1 hour )

The protokoll shows the following entries:
"12 Jul 19:18:32 ntpd[3156]: parent died before we finished, exiting
13 Jul 19:38:20 ntpd[2994]: signal_no_reset: signal 17 had flags 4000000
13 Jul 19:38:22 ntpd[2994]: signal_no_reset: signal 14 had flags 4000000
13 Jul 19:44:17 ntpd[2993]: ntpd exiting on signal 15
13 Jul 19:44:17 ntpd[2994]: ntpd exiting on signal 15
13 Jul 18:36:08 ntpd[3502]: synchronized to 129.69.1.153, stratum 1
13 Jul 18:36:08 ntpd[3502]: kernel time sync disabled 0041
13 Jul 18:37:14 ntpd[3502]: kernel time sync enabled 0001
13 Jul 18:58:34 ntpd[3502]: ntpd exiting on signal 15
13 Jul 19:00:48 ntpd[3158]: signal_no_reset: signal 17 had flags 4000000
13 Jul 19:00:50 ntpd[3158]: signal_no_reset: signal 14 had flags 4000000
13 Jul 19:09:00 ntpd[3157]: ntpd exiting on signal 15
13 Jul 19:09:06 ntpd[3158]: ntpd exiting on signal 15
13 Jul 19:14:34 ntpd[2998]: signal_no_reset: signal 17 had flags 4000000
13 Jul 19:14:36 ntpd[2998]: signal_no_reset: signal 14 had flags 4000000
13 Jul 19:17:59 ntpd[2997]: ntpd exiting on signal 15
13 Jul 19:18:06 ntpd[2998]: parent died before we finished, exiting
13 Jul 23:07:47 ntpd[3168]: signal_no_reset: signal 17 had flags 4000000
13 Jul 23:07:49 ntpd[3168]: signal_no_reset: signal 14 had flags 4000000
13 Jul 23:08:27 ntpd[3165]: ntpd exiting on signal 15
13 Jul 23:08:49 ntpd[3168]: parent died before we finished, exiting
13 Jul 23:10:44 ntpd[2989]: signal_no_reset: signal 17 had flags 4000000
13 Jul 23:10:46 ntpd[2989]: signal_no_reset: signal 14 had flags 4000000
13 Jul 23:15:37 ntpd[2988]: ntpd exiting on signal 15
13 Jul 23:15:46 ntpd[2989]: parent died before we finished, exiting
13 Jul 23:34:35 ntpd[17721]: sendto(129.69.1.153): Invalid argument
13 Jul 23:34:38 ntpd[17721]: sendto(130.149.17.21): Invalid argument
13 Jul 23:34:39 ntpd[17721]: sendto(141.82.30.251): Invalid argument
13 Jul 23:35:39 ntpd[17721]: sendto(129.69.1.153): Invalid argument
13 Jul 23:35:42 ntpd[17721]: sendto(130.149.17.21): Invalid argument
13 Jul 23:35:43 ntpd[17721]: sendto(141.82.30.251): Invalid argument
13 Jul 23:36:45 ntpd[17721]: sendto(129.69.1.153): Invalid argument
13 Jul 23:36:46 ntpd[17721]: sendto(130.149.17.21): Invalid argument
13 Jul 23:36:49 ntpd[17721]: sendto(141.82.30.251): Invalid argument
13 Jul 23:37:49 ntpd[17721]: sendto(130.149.17.21): Invalid argument
13 Jul 23:37:51 ntpd[17721]: sendto(129.69.1.153): Invalid argument
13 Jul 23:37:53 ntpd[17721]: sendto(141.82.30.251): Invalid argument
13 Jul 23:38:52 ntpd[17721]: sendto(130.149.17.21): Invalid argument
13 Jul 23:38:57 ntpd[17721]: sendto(141.82.30.251): Invalid argument
13 Jul 23:38:57 ntpd[17721]: sendto(129.69.1.153): Invalid argument
13 Jul 23:39:58 ntpd[17721]: sendto(130.149.17.21): Invalid argument
13 Jul 23:40:03 ntpd[17721]: sendto(141.82.30.251): Invalid argument
13 Jul 23:40:03 ntpd[17721]: sendto(129.69.1.153): Invalid argument
13 Jul 23:41:02 ntpd[17721]: sendto(130.149.17.21): Invalid argument
13 Jul 23:41:06 ntpd[17721]: sendto(141.82.30.251): Invalid argument
13 Jul 23:41:09 ntpd[17721]: sendto(129.69.1.153): Invalid argument
13 Jul 23:42:07 ntpd[17721]: sendto(130.149.17.21): Invalid argument
13 Jul 23:42:10 ntpd[17721]: sendto(141.82.30.251): Invalid argument
13 Jul 23:42:14 ntpd[17721]: sendto(129.69.1.153): Invalid argument
13 Jul 23:42:41 ntpd[17721]: ntpd exiting on signal 15
14 Jul 08:30:41 ntpd[3154]: signal_no_reset: signal 17 had flags 4000000
14 Jul 08:30:43 ntpd[3154]: signal_no_reset: signal 14 had flags 4000000
14 Jul 08:36:35 ntpd[3153]: ntpd exiting on signal 15
14 Jul 08:36:43 ntpd[3154]: parent died before we finished, exiting
15 Jul 11:20:36 ntpd[3137]: signal_no_reset: signal 17 had flags 4000000
15 Jul 11:20:38 ntpd[3137]: signal_no_reset: signal 14 had flags 4000000
15 Jul 11:49:01 ntpd[3131]: ntpd exiting on signal 15
15 Jul 11:49:09 ntpd[3137]: parent died before we finished, exiting
15 Jul 20:52:59 ntpd[3157]: signal_no_reset: signal 17 had flags 4000000
15 Jul 20:53:01 ntpd[3157]: signal_no_reset: signal 14 had flags 4000000
15 Jul 20:56:47 ntpd[3156]: ntpd exiting on signal 15
15 Jul 19:45:41 ntpd[3157]: parent died before we finished, exiting
15 Jul 19:48:58 ntpd[5193]: synchronized to 141.82.30.251, stratum 2
15 Jul 19:48:58 ntpd[5193]: kernel time sync disabled 0041
15 Jul 19:49:00 ntpd[5193]: synchronized to 129.69.1.153, stratum 1
15 Jul 19:50:03 ntpd[5193]: kernel time sync enabled 0001
15 Jul 20:16:12 ntpd[5193]: ntpd exiting on signal 15
16 Jul 07:31:28 ntpd[3170]: signal_no_reset: signal 17 had flags 4000000
16 Jul 07:31:30 ntpd[3170]: signal_no_reset: signal 14 had flags 4000000
16 Jul 09:49:00 ntpd[3169]: ntpd exiting on signal 15
16 Jul 09:49:11 ntpd[3170]: ntpd exiting on signal 15
16 Jul 22:38:02 ntpd[3168]: signal_no_reset: signal 17 had flags 4000000
16 Jul 22:38:04 ntpd[3168]: signal_no_reset: signal 14 had flags 4000000
16 Jul 22:49:21 ntpd[3165]: ntpd exiting on signal 15
16 Jul 22:11:37 ntpd[3168]: parent died before we finished, exiting
17 Jul 20:23:47 ntpd[3166]: signal_no_reset: signal 17 had flags 4000000
17 Jul 20:23:50 ntpd[3166]: signal_no_reset: signal 14 had flags 4000000
17 Jul 20:31:16 ntpd[3165]: ntpd exiting on signal 15
17 Jul 20:31:20 ntpd[3166]: parent died before we finished, exiting
18 Jul 19:45:33 ntpd[3201]: signal_no_reset: signal 17 had flags 4000000
18 Jul 19:45:35 ntpd[3201]: signal_no_reset: signal 14 had flags 4000000
18 Jul 22:16:22 ntpd[3200]: ntpd exiting on signal 15
18 Jul 21:05:08 ntpd[3201]: parent died before we finished, exiting
18 Jul 22:47:05 ntpd[3122]: signal_no_reset: signal 17 had flags 4000000
18 Jul 22:47:07 ntpd[3122]: signal_no_reset: signal 14 had flags 4000000
18 Jul 23:44:44 ntpd[3121]: ntpd exiting on signal 15
18 Jul 23:45:02 ntpd[3122]: ntpd exiting on signal 15
19 Jul 20:22:30 ntpd[3157]: signal_no_reset: signal 17 had flags 4000000
19 Jul 20:22:32 ntpd[3157]: signal_no_reset: signal 14 had flags 4000000
19 Jul 21:21:16 ntpd[3156]: ntpd exiting on signal 15
19 Jul 21:21:29 ntpd[3157]: ntpd exiting on signal 15
20 Jul 19:53:35 ntpd[3181]: signal_no_reset: signal 17 had flags 4000000
20 Jul 19:53:37 ntpd[3181]: signal_no_reset: signal 14 had flags 4000000
20 Jul 20:44:46 ntpd[3180]: ntpd exiting on signal 15
20 Jul 20:45:06 ntpd[3181]: ntpd exiting on signal 15
20 Jul 21:36:03 ntpd[3234]: signal_no_reset: signal 17 had flags 4000000
20 Jul 21:36:05 ntpd[3234]: signal_no_reset: signal 14 had flags 4000000
20 Jul 22:14:02 ntpd[3233]: ntpd exiting on signal 15
20 Jul 22:14:05 ntpd[3234]: parent died before we finished, exiting
21 Jul 06:55:52 ntpd[3158]: signal_no_reset: signal 17 had flags 4000000"

It should be mentioned that
- I am alwys online
- the NTP daemon fails on other HW and with older versions of Suse (e.g.
10.0) , too.

Who can help an advice?
  #2 (permalink)  
Old 27-Jul-2006, 03:35
Automatic reply
Guest
 
Posts: n/a
Default Re: NTP failing to adjust the system time

Forenconnnntact1,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
- Check all of the other support tools and options available at
http://support.novell.com.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://support.novell.com/forums)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://support.novell.com/forums/faq_general.html

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://support.novell.com/forums/


 

Bookmarks


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2