Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Our NTP servers are set up as a peer group looking out at us.pool.ntp.org. Our internal servers are set up to look at the local group. These internal servers are also peered to each other (Oracle RAC servers need this I am told. . .). Three servers do not look at the nodes specified in the ntp.conf under the 'server' directive. They look to a nameserver that had previously been used as a time server. This one server doesnt look anywhere.
The /var/log/messages/ entries:
Feb 9 13:06:22 myserver-01 ntpd: ntpd shutdown succeeded
Feb 9 13:06:27 myserver-01 ntpdate: no server suitable for synchronization found
Feb 9 13:06:27 myserver-01 ntpd: failed
Feb 9 13:06:27 myserver-01 ntpd: ntpd firstname.lastname@example.org Thu Oct 5 04:11:33 EDT 2006 (1)
Feb 9 13:06:27 myserver-01 ntpd: precision = 1.000 usec
Feb 9 13:06:27 myserver-01 ntpd: Listening on interface wildcard, 0.0.0.0#123
Feb 9 13:06:27 myserver-01 ntpd: Listening on interface wildcard, ::#123
Feb 9 13:06:27 myserver-01 ntpd: Listening on interface lo, 127.0.0.1#123
Feb 9 13:06:27 myserver-01 ntpd: Listening on interface eth0, 10.200.23.31#123
Feb 9 13:06:27 myserver-01 ntpd: Listening on interface eth0:1, 10.200.23.41#123
Feb 9 13:06:27 myserver-01 ntpd: Listening on interface eth1, 192.168.23.31#123
Feb 9 13:06:27 myserver-01 ntpd: kernel time sync status 0040
Why would none of these servers look to the time server specified in the ntp.conf? It is attached (for syntax review) with identifiers falsified.
well nothing there says that it's not looking at those servers, merely that nothing useful was found, which is different.
run "ntpdate -d my.ser.ver.ip" to do a one shot debugging query of a server, and see what that says. Additionally on your local servers run "ntpp -pn" to check the status of them. If they are flapping around without any synchonrization then nothing is going to use them - ntp is cleverer than that, and more annoying as a result.
you can't tell? well yes it shows in the second line (with the *) that you're happily synced to a strata 2 server online, so in turn will be providing a strata 3 service internally. So if you can't do a one shot ntpdate command from the client to that server, i'd be expecting network issues in the way. local firewall maybe?