SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Everything in BIOS that refers to the word "clock" says "AUTO".
What should I look for?
BTW this is the same BIOS I've been using for years, never messed with it and no problems while npt was working perfectly Until I Installed slackware-14.1.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
Posts: 3,541
Rep:
Quote:
Originally Posted by WilliamS
Everything in BIOS that refers to the word "clock" says "AUTO".
What should I look for?
I dunno -- but, what time is it? Can you look at the date and time and see if it's set to accurately to UTC? Maybe click on it or something (the BIOS's on my machines display the clock time and date and you hit the right arrow key or the enter key or click to see what the date and time are).
Never referenced time to WWV or CHU, just set it during installation of the OS and no problems.
That would take special setup and probably a recompile of ntpd. Because you live too close to CHU, I'll back off of the radio clock idea. The WWV ntpd driver is awesome, but the way it works with audio samples almost requires a separate PC with little running on it.
Quote:
I have no access to the modem control.
Not even a Web interface? Usually, there's a Web interface at http://numeric_address_of_router, though I've had a ZyXEL router that put it at http://numeric_address_of_router:8080. See the instruction manual for your modem to get the details. This may require a trip to the manufacturer's Web site--your ISP may not provide more than the modem and some papers--and it helps to have the papers that came with the original modem installation by your ISP.
Quote:
nmap scan of port 123 shows as it should be, same as before.
I found a macro for ntp in my firewall and enabled it to make sure that port is working; no difference in anything detected.
How well does ntpd work with the firewall turned off? Should you not wish to turn the firewall off for security reasons, you can still test ntpd between two PCs with no Internet connection and firewalls shut off.
Alternatively, you could somehow install chrony and see if it somehow works. At least according to the chronyd FAQ, it uses ports 123/udp and 323/udp. So if chronyd works, it's not total proof that port 123/udp is broken, but you would get your time somehow. Just don't run it at the same time as ntpd. I'm doubtful that this is the solution, just putting it there as an option.
I dunno -- but, what time is it? Can you look at the date and time and see if it's set to accurately to UTC? Maybe click on it or something (the BIOS's on my machines display the clock time and date and you hit the right arrow key or the enter key or click to see what the date and time are).
We did that already, and the hardware clock and system clock show UTC and local time. Difference of a fraction of a second, which is my reaction time.
mlslk31, thanks for the chrony advice - I've installed it and been playing. Has better documentation for troubleshooting.
Tried the chronyc accheck command, and got:
Code:
# chronyc accheck 0.ca.pool.ntp.org
501 Not authorised
Does this tell anything useful?
But it does not work either.
My satellite modem is a black box. Only thing I can do to it is reset it by pulling the power plug, wait 2 minutes, then pwr up.
This from the install manual.
Disabled firewall according to eloi, tried ntpq -pn, still no change.
Then tried shorewall clear command, from the man page:
Clear will remove all rules and chains installed by Shorewall. The
firewall is then wide open and unprotected. Existing connections
are untouched. Clear is often used to see if the firewall is
causing connection problems.
And that also made no difference to ntpq -pn.
Then did slackpkg reinstall ntp*
--entered the server stuff and commented out the fudge lines.
no difference to ntpq -pn.
Every time, the above command shows that ntpd is getting the server names, so it is communicating through port 123, but it looks like it gets no data from these servers, or it is not doing anything with whatever data comes in (I may not know what I'm talking about):
Code:
# ntpq -pn
remote refid st t when poll reach delay offset jitter
==============================================================================
72.51.27.50 .INIT. 16 u - 256 0 0.000 0.000 0.000
67.215.197.151 .INIT. 16 u - 256 0 0.000 0.000 0.000
198.27.65.66 .INIT. 16 u - 256 0 0.000 0.000 0.000
192.95.20.208 .INIT. 16 u - 256 0 0.000 0.000 0.000
Every time, the above command shows that ntpd is getting the server names, so it is communicating through port 123, but it looks like it gets no data from these servers, or it is not doing anything with whatever data comes in (I may not know what I'm talking about):
Code:
# ntpq -pn
remote refid st t when poll reach delay offset jitter
==============================================================================
72.51.27.50 .INIT. 16 u - 256 0 0.000 0.000 0.000
67.215.197.151 .INIT. 16 u - 256 0 0.000 0.000 0.000
198.27.65.66 .INIT. 16 u - 256 0 0.000 0.000 0.000
192.95.20.208 .INIT. 16 u - 256 0 0.000 0.000 0.000
Like tronayne explained you, that happens when ntpd doesn't get synchronized in the first attempt (/etc/rc.d/rc.ntpd uses the option -g). That's why after each thing you modify to try you have to *restart* the daemon.
"When trying to debug problems using ntpdate and ntpq, note that these utilities may use unprivileged high-numbered ports, while ntpd requires full bidirectional access to the privileged UDP port 123."
So it still remains that no matter how many tests, there is nothing wrong with ntp, shorewall, clock.
I would like to look elsewhere, but don't know where.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
