|
Bugzilla – Full Text Bug Listing |
| Summary: | ntp server do not work | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | Pavel Nemec <pnemec> |
| Component: | YaST2 | Assignee: | Peter Varkoly <varkoly> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | mvidner, varkoly |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | 32bit | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/etc/sysconfig/ntp
/etc/ntp.conf |
||
Created attachment 247803 [details]
/etc/ntp.conf
/var/log/messeges when rcntp restart Oct 10 23:38:56 deepblue ntpd[13803]: ntpd 4.2.4p5@1.1541-o Tue Oct 14 17:16:13 UTC 2008 (1) Oct 10 23:38:56 deepblue ntpd[13804]: precision = 1.000 usec Oct 10 23:38:56 deepblue ntpd[13804]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Oct 10 23:38:56 deepblue ntpd[13804]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Oct 10 23:38:56 deepblue ntpd[13804]: Listening on interface #1 wildcard, ::#123 Disabled Oct 10 23:38:56 deepblue ntpd[13804]: Listening on interface #2 lo, ::1#123 Enabled Oct 10 23:38:56 deepblue ntpd[13804]: Listening on interface #3 lo, 127.0.0.1#123 Enabled Oct 10 23:38:56 deepblue ntpd[13804]: Listening on interface #4 lo, 127.0.0.2#123 Enabled Oct 10 23:38:56 deepblue ntpd[13804]: Listening on interface #5 eth1, 192.168.1.12#123 Enabled Oct 10 23:38:56 deepblue ntpd[13804]: kernel time sync status 0040 Oct 10 23:38:56 deepblue ntpd[13804]: frequency initialized 0.000 PPM from /var/lib/ntp/drift/ntp.drift Now I just try different approach. I switch off ntp using YaST module ntp. I go to system-> date and time and go with Change date and time. I select using network and select random ntp server from pool. Date and time is now correct. ntp YaST module and rcntp show that ntp ?server?client? do not run. ntp YaST module claim it is server/client configuration. I am quite confused now. Please enahnce the line "server cz.pool.ntp.org" with the option iburst: server cz.pool.ntp.org iburst and restart the ntp-server again. Withouth this option the initial synchronization lasts a longer time. now I've patched yast2-ntp-client. iburst will be set as default for the servers |
Created attachment 247797 [details] /etc/sysconfig/ntp I set NTP server using YaST2 NTP module. I add "Undiscipled local time" and also "Server" random from pool. I test connection to server and Test was successful. My date is now 10-10-2008. Whenever I reboot to 10.2 clock gets right (I also use ntp there) . After that reboot to 11.1 trigger forcecheck of all disks because their date is in future. I am not sure if problem is in ntp server, or YaST module. Configs will be attached.