Hi,

Noticed clock (ntpd) shows up in syslog with lots of errors:



This is just a default F1 install, tried north-america.pool.ntp.org and returns same message, any hints?

ntpdate -u north-america.pool.ntp.org works fine.

mike

Hi Mike,

Have you been "doing something" to ntp? That's the obvious question, to which I know you will answer "no" because I know you, kinda

I don't, however, know how much unix you have, so...

Is it running with suid root? Permission could mean you don't have permission to open the log file, place the lock file or open the binary. It could also mean you don't have permission to access that particular ntp server (or one of them: It's a pool).

Do you have port 123 blocked?

Is the ntp server(/s) down? (Hey, it's possible. May only take one)

Do they have (you|external access) blocked?

I would stop ntpd, install ntpdate and try setting the time directly from that server with "ntpdate north-america.pool.ntp.org". You'll have to stop ntpd as it locks port 123 for itself.

If it all works perfectly with ntpdate, restart the process and check the error log. If it doesn't, try another server.

(other) Mike

_________________
*********************
LinHES 7.4
Australian Dragon
*********************

Hi Mike,

Thanks for the ideas and will poke around a little farther tomorrow. It is just a standard F1 install and I noticed it on a machine I was tinkering with at work. (they have much newer toys than me ) So I checked mine at home and it has same error.

the /etc/ntp.conf uses four servers, . "server 0,1,2,3.debian.pool.ntp.org iburst" .I tried the north-america pool and have the same result so you are probably correct about who it runs as.

The ntpdate -u (a trick from Human?) allows you to not have to stop the ntpd. I usually put it in the bootmisc.sh just to tweak things on boot up.

As for access, I control the firewall they so that is not an issue. I think it is a flaw in F1 and I just happened to notice it.

I know a little about linux in general but with out a mentor to answer a few questions over the years the knowledge gain has been slow to come about. I first started with Slackware, Caldera 1.3, never cared for RH, a little Mandrake, dsl, and since R4V2 (still have that iso...) has been only Debian.

Gentlemen like Cecil, Dale, tjc, Human and many more that have taken a few moments to answer a my dumb questions along the way, have taken my knowledge level up a few notches.

I beat on my KM boxes pretty hard but they never complain and just keep running. I put an A16 machine to work in Dec 05 and it is still doing what I told it to do then. I have to reboot it weekly so the record schedule gets refreshed. But on the other extreme, I have a KM box that was booted up >305 days ago and is subjected to outdoor temp swings. i been able to limit the high temp so far to only a mere 118 F (it will never record tv yet thousands of people see it everyday )

Anyway, thanks again for the ideas:)
Mike
.