SUSE :: Setting Up NTPD On 11.2 And Using From 11.0 Plus
May 7, 2010
I am rebuilding / updating my internal server. It is strange to me that 11.0 will not install on this ASUS M3A78 MB but 11.2 will go through. I am setting up the ntp server and run into new things, ntpdate is not used anymore so you have this long string : sntp -P no -r pool.ntp.org which does the same thing or a couple of other calls that may work. It seems that pool.ntp.org will not work however so I switched to another time server.
pool.ntp.org does work on 11.0 however, it still uses ntpdate atm.
I can use ntpdate to my server from other clients and get the time but I can't use Yast to set it up, it hangs (or maybe it will eventually time out) when you test the server in the gui tool. rcntp ntptimeset comes back with no server reached on the ntp server machine so I am not confident that it will auto update itself, which I think is an issue, the server will not respond to client queries after a day or two.
What configuration options in /etc/ntp.conf do I have to set to allow other computers to receive time from a ntpd server? I've tried removing "nopeers" and "noquery" from the restrict lines, but I can't see anything on port 123.
I am facing issue in ntp, it is getting killed frequently. see below error; # /etc/init.d/ntpd status ntpd dead but pid file exists After starting service it is works fine but again after sometimes it get in dead postition.
I am setting up a PDC using suse 10.1 but I get the error(failed to modify entry:
structural object class modification from 'sambaDomain' to 'inetOrgPerson' not allowed at /usr/sbin/smbldap-populate line 464, <GEN1> line 21.) when I run /usr/sbin/smbldap-populate command linux-5r4o:~ # /usr/sbin/smbldap-populate
I am accessing a program through X11. My OS is Suse 10.3. However when I access this program, the menu bar title are not letter but a string of characters of "[]". I need to find a way to perform a character setting for X11 using SUSE.
i have installed SUSE 11 recently and have set the domain name and netmask using YaST settings after installation.But, the domain name is empty after rebooting. I have verified this using domainname command from terminal. But, in Network settings it is there.I think the system is not picking up the domain name from YaST settings.
Im relatively new to Linux - just started working with it this week - and Im having some trouble setting up NFS. We have a 12 computer cluster running open SUSE in our lab at school, and I am trying to troubleshoot the NFS system we have created.My basic question is this - I want to find the file that sets whether or not the NFS server and client processes run on setup. Google indicates that in most linux installations, these settings can be found in the /etc/rc.conf file. I cant find this file in open SUSE, so what Im trying to figure out is where I would find the equivalent commands in open SUSE. I am basically trying to find the lines highlighted in this: <http://www.freebsd.org/doc/handbook/network-nfs.html> article are stored. I already know how to enable/disable the NFS server/client using YaST in the GUI, but I would prefer to find the file directly, as changing the settings in the GUI involves plugging a monitor, keyboard, and mouse into each of 12 boxes, and is very time consuming. I can change files straight from the terminal command line - much faster.
Additional background: We are using NFS in two ways on our cluster - firstly, we have installed the software package (Fluent) on the host computer, and then setup the host to share this folder with the 11 slaves. To do this, we set the host as an NFS server, with the 11 slaves as NFS clients of this folder.
Secondly, we have setup working folders on each of the slaves that we would like to use to store data (each computer has a 1.5TB drive inside). To do this, we have set each of the slaves as an NFS server, sharing the working directory with the host computer, which we setup as an NFS client of each of these 11 working folders.
The problem that I am experiencing is that each of these two things works properly by itself, but when we try to use a computer as both an NFS server and an NFS client at the same time (albeit to different folders), neither works.Any thoughts on how to move forward in troubleshooting this? My current plan of attack is to unplug all of the slaves except for one from the network, and try to get a single slave to communicate properly with the host. Once I get the first slave running, I was going to add additional slaves one at a time until they were all working. Thoughts?
I just installed Suse 11.3 64bit on a new build. My video card is a nvidia gt240. I am using the default drivers. My monitor is a NEC 17" LCD.
When I boot up the screen resolution defaults to 1280x1024. I can go to applications>configure desktop>display and set it to 1024x768, which is my resolution of choice, and it works until I reboot or log out and log back in, then it resets to 1280x1024.
I would like to make 1024x768 the default so I don't have to keep changing it. Is there a way to do this? The output of xrandr looks like this:
$~> xrandr Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192 DVI-I-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 338mm x 270mm 1280x1024 60.0 + 1152x864 75.0 1024x768 75.1 70.1* 60.0
[Code]...
Is there something I can change to set a new default resolution?
I have a Dell Windows7 PC configured with BIOS RAID1. I want to install SLES10 and configure it with Software RAID1. My question is: Do I need to reconfigure the BIOS RAID setting and if so What should it be.
I want to attach disk with Suse 11.2 to another motherboard with Integrated ATI Radeon HD 4290 GPU ( at the moment I am using Nvidia GeForce 6800). How can I change settings for new video chip?
The suse 10.0 64 bit partition on my box stops booting when it is setting up the cmos clock. The suse 10.0 32 bit partition boots up without a problem. I never had a problem with the suse 10.0 64 bit partition up until now. Is it possible to fix the problem using puppy linux and editing a configuration file? I do not think it is a hardware issue if the other partition on the drive boots up. Would puppy linux be a good way to backup files from this partition or can I mount the partition using the 32 bit os?
I have a Windows 2003 server that runs a Win32 time server which synchronizes with off site time sources. I have a CentOS 5.4 server which I just configured and installed NTP on. For some reason, I keep getting time discrepancies even after the server is (apparently) synching with my local NTP server on the Windows box.
Hwclock is set to UTC true/etc/localtime is properly symlinked to appropriate /usr/share/zoneinfo fileNTPD is setup as a service which loads on startupNTP.conf is configured to only retrieve from my local Windows 2003 time serverntpq -p seems to verify that the system is indeed synching up properlyThe problem is, whenever I run the 'date' command it is displaying my system time in (presumably) UTC. That is, even though my the CentOS box appears to be synching up to the local time, it's not translating it into my proper time zone. Consequently, the date is always at -6 hours from the actual local time. It was my understanding that the hwclock is fine to remain at UTC as ntpd should be synching with my local Windows 2003 time server periodically and updating it, and the system time should be getting translated to my localtime.
what I do, after rebooting the box the hwclock and system clock display the improper time.Maybe I just have a fundamental misunderstanding of how this is supposed to operate.Update: I'm not sure why, but after I commented out the other servers and added a fudge declaration for my internal server and rebooted, everything is working as it should and the time is correct.I'm still not really sure if it was adding the "fudge <hostname> stratum 2" declaration that corrected things, or commenting out the additional hosts, so I'll leave this open if anyone cares to comment or contribute.
i'm trying to use the ntpd -gq instead of ntpdate. The result is that clock not set. as below. However ntpdate is working ok and had set the clock correctly.this is the ntp.conf file:
[root@CentOS5 ~]# cat /etc/ntp.conf logfile /var/log/ntp.log driftfile /var/lib/ntp/drift server 0.centos.pool.ntp.org
this is the output of command: [root@CentOS5 ~]# ntpd -dqg ntpd 4.2.2p1@1.1570-o Sat Dec 19 00:58:16 UTC 2009 (1)[code]....
Also attached is the trace file, from the trace file, everything seems ok, timestamps is sent and received:
I can compile and run ntpd 4.2.6p2, but after a while the reach indicator falls back from 377 to 0 and then the ntpd is in an unsynced state for a while. So far I haven't seen any indication why we have this.
I'm trying to use the ntpd -gq instead of ntpdate. The result is that clock not set. as below. However ntpdate is working ok and had set the clock correctly
This is the ntp.conf file: Code: [root@CentOS5 ~]# cat /etc/ntp.conf logfile /var/log/ntp.log driftfile /var/lib/ntp/drift server 0.centos.pool.ntp.org
This is the output of command: Code: [root@CentOS5 ~]# ntpd -dqg ntpd 4.2.2p1@1.1570-o Sat Dec 19 00:58:16 UTC 2009 (1) addto_syslog: precision = 1.000 usec create_sockets(123) addto_syslog: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 ..... clock_filter: n 6 off 42905.489022 del 0.390840 dsp 0.000132 jit 4.733917, age 12 16 addto_syslog: no reply; clock not set
Also attached is the trace file, from the trace file, everything seems ok, timestamps is sent and received:
I am trying to synchronize the time of my VM server with ntpd. I have the following configuration. And in the /etc/ntp.conf, I have the following line:
restrict default ignore restrict 127.0.0.1. server time1.server server time2.server
Whenever I have this line, the erver is not able to synchronize its time... So far as I understood, this line prevents other servers using this machine as a time server. And the second line says to allow localhost to use as time server. But why do I need to use its own time server when I have specified to use time1.server and time2.server ? ( firewall for tcp and udp ports 123 is open)
However, when I replace the first line of the configuration with the following line, it works. restrict default kod nomodify notrap noquery But with this, i am allowing other servers to use this server a ntp (which I wouldn't like to). Why this machine tries to use ntp server of its own (to snyc time) and why it is not working though i have the entry "restrict 127.0.0.1" ??
I have a problem with a server with os Linux RedHat Enterprise AS 4.7:
when the server boots both ntpd and rpc.statd fail to start.
looking into /var/log/messages I found:
and
For ntp, when the server completed the boot process, altough it seems ntpd started, no external server is used for syncronization. The rpc.statd does not start at all and it doesn't appear if I issue a rpcinfo -p The strange thing is that at this point if I manually start or restart /etc/init.d/ntpd and /etc/init.d/nfslock both services start with no errors. Another strange thing is the timestamp for messages into /var/log/messages. How could it be possible to have a line with a certain timestamp and the following with a timestamp 30 seconds before?
The kernel version in use is 2.6.9-55.0.12.ELsmp #1 SMP x86_64
I'd like to get the 13.0 "synchronized to <time server>, stratum <stratum>" messages back on 13.1.
- On 13.0, running ntpd 4.2.4p8, reassuring messages appeared in /var/log/messages like "synchronized to 211.233.84.186, stratum 2". - On 13.1, running ntpd 4.2.6p1, there are no messages in /var/log/messages to confirm that time is being synchronised.
rc.ntpd on both starts ntpd with the same options. /etc/ntp.conf is identical on both, a "get it working and then make it secure" version: Code: cat /etc/ntp.conf | grep -E -v '^$|^#' cat /etc/ntp.conf | grep -E -v '^$|^#' server in.pool.ntp.org server asia.pool.ntp.org server 127.127.1.0 fudge 127.127.1.0 stratum 10 driftfile /etc/ntp/drift
According to Linux Home Networking, synchronization can be checked using ntpq -p. This shows synchronization is working. I would prefer to see that confirmation in /var/log/messages without having to run a command manually to check it. How to get the old messages back?
I'm trying to sync my clock. I think I would like to do this by the "ntpd" daemon running. I think it should start up on boot, but it doesn't.
I have the following in my /var/log/syslog: Jul 18 23:44:14 neo ntpd[1780]: ntpd 4.2.6p2@1.2194-o Sun Oct 17 13:45:13 UTC 2010 (1) Jul 18 23:44:14 neo ntpd[1781]: proto: precision = 0.634 usec Jul 18 23:44:14 neo ntpd[1781]: unable to bind to wildcard address 0.0.0.0 - another process may be running - EXITING Jul 18 23:44:14 neo ntpdate[1194]: step time server 72.26.125.125 offset -0.505108 sec
Other posts say if ntpd and ntpdate run too close together, they cause one to think the other is locking a resource. It works to type "ntpdate pool.ntp.org" to manually update the clock. My Debian version is squeeze (6.0.2)
It works to start the ntpd daemon manually: ... sudo /etc/init.d/ntp start ... Starting NTP server: ntpd.
Code: remote refid st t when poll reach delay offset jitter plesk2.datacent .INIT. 16 u - 64 0 0.000 0.000 0.000 91.198.87.118.b .INIT. 16 u - 64 0 0.000 0.000 0.000 core.fr.zeroloo .INIT. 16 u - 64 0 0.000 0.000 0.000 178-26-105-100- .INIT. 16 u - 64 0 0.000 0.000 0.000 and it remains so no matter how long I wait...
Hoping to get better results with ntpdate, I stopped NTPS and tried : Code: # ntpdate ntp.skynet.be 29 Mar 09:12:26 ntpdate[4715]: no server suitable for synchronization found # ntpdate -ud ntp.skynet.be 29 Mar 09:14:02 ntpdate[4814]: ntpdate 4.2.4p4@1.1520-o Sun Nov 22 16:14:35 UTC 2009 (1) transmit(195.13.23.5) receive(195.13.23.5) .....
I am running Debian Lenny 64b, and every packages are totally updated. I have 25 identical servers. And there is just one giving me this problem. From what I see, it is not a connection/FW issue since ntpdate get replies from the ntp server (ntp.skynet.be is my isp's stratum 2 ntp server).
I have recently installed Slackware 13 (64bit) (Kernel 2.6.29.6) on an Acer Veriton M series with AMD Athlon cpu. I have started ntpd server and from it's log file it seems to be synchronising to each of the three stratum 2 servers specified in the ntp.conf file.
25 Mar 18:27:02 ntpd[4542]: time reset +2.163491 s 25 Mar 18:33:08 ntpd[4542]: synchronized to 130.88.200.4, stratum 2 25 Mar 18:37:25 ntpd[4542]: synchronized to 130.88.200.6, stratum 2 25 Mar 18:42:59 ntpd[4542]: time reset +2.282097 s 25 Mar 18:49:21 ntpd[4542]: synchronized to 130.88.200.6, stratum 2 25 Mar 18:50:17 ntpd[4542]: synchronized to 130.159.196.118, stratum 2 25 Mar 18:55:57 ntpd[4542]: synchronized to 130.88.200.6, stratum 2 25 Mar 18:58:57 ntpd[4542]: time reset +2.147508 s
If I invoke ntpdate from another linux machine, that ntpdate reports that the stratum of the ntpd server is too high and won't use it.
transmit(192.168.175.8) receive(192.168.175.8) transmit(192.168.175.8) receive(192.168.175.8) transmit(192.168.175.8) 192.168.175.8: Server dropped: strata too high server 192.168.175.8, port 123 stratum 16, precision -20, leap 11, trust 000 refid [192.168.175.8], delay 0.02577, dispersion 0.00000 transmitted 4, in filter 4 reference time: cf562778.a310c705 Thu, Mar 25 2010 18:18:32.636 originate timestamp: cf562cdd.048cbee3 Thu, Mar 25 2010 18:41:33.017 transmit timestamp: cf562cd0.56618ce2 Thu, Mar 25 2010 18:41:20.337 filter delay: 0.02579 0.02577 0.02579 0.02579 0.00000 0.00000 0.00000 0.00000 filter offset: 12.68024 12.68024 12.68024 12.68024 0.000000 0.000000 0.000000 0.000000 delay 0.02577, dispersion 0.00000 offset 12.680248
25 Mar 18:41:20 ntpdate[9683]: no server suitable for synchronization found
I have run ntpd on another platform with Slackware 12 (32bit) and never had any problems.
I have a server running VMWare Server on it with 4 virtual machines running. I am trying to use NTPD to keep the time correct on all of the virtual machines. On my physical server, I have installed ntpd and this is it's config file:
Quote:# ntpd.conf tinker panic 0 restrict 127.0.0.1 restrict default kod nomodify notrap server 0.vmware.pool.ntp.org server 1.vmware.pool.ntp.org server 2.vmware.pool.ntp.org
I'm having a problem with the time on one of my servers jumping forward into the future. We run serveral CentOS 5.4 servers running Xen, some up to date and some a little older. The one in question is running 2.6.18-164.el5xen, with xen-libs-3.0.3-94.el5_4.2 and xen-3.0.3-94.el5_4.2. On this server are several Xen virtual machines, also running CentOS 5.4 with kernel 2.6.18-164.el5xen. One in particular has problems with the clock keeping proper time.
We use NTP (ntpd) to sync time to a central server in the company. Our NTP set-up works fine, and we have problems on only a couple of servers out of many. The problem I see is that one one particular Xen virtual machine, the clock will suddenly jump forward into the future, usually by several minutes but once by more than an hour. This has obvious implications for software running on the machine. Software such as Oracle grid control agent will restart itself under the (incorrect) assumption that it has been hung for several minutes with no activity. Oracle database will cope gracefully, but applications that refer to the clock will be confused.
We detect these time jumps because we have Nagios checking the clock on each host against the centralised time server (Nagios's check_ntp plugin). Nagios will suddenly report a clock offset that is miles into the future. Following the time jump, ntpd on the host in question will re-sync the time. Ntpd keeps the time steady, ticking just a few milliseconds per second until real time catches up with the server. i.e. Nagios will report the time as being 10 minutes ahead, then a minute later the host will be 9 minutes ahead, and then a further minute later the host will be 8 minutes ahead of real time. The clock on the host stays running very slow until it eventually is correct.
