On 11/18/10 10:14, Brian Utterback wrote:
> On 11/18/10 09:12, James Carlson wrote:
>> I'm getting messages like this:
>>
>> Nov 18 09:01:17 carlson ntpd_intres[1004]: [ID 702911 daemon.error] ntpd
>> indicates no data available!
>>
>> They seem to be generated once every minute. As far as I can tell, NTP
>> is working fine and ntpq shows that it's in sync, but the daemon whines
>> anyway. The only "special" thing I have (in an otherwise ordinary
>> client configuration) is a directive to broadcast on an internal network.
>>
>> Does anyone know what this message might mean?
>>
>
> I'll look at what the specific message is, but right away I can give
> you an idea. Notice that it isn't really the ntpd daemon, it is
> ntpd_intres, which is NTP's resolver. The ntpd daemon does not call
> getaddrinfo or other name service calls directly because they can
> block and the daemon is single threaded. So to do name resolution
> asynchronously, it forks a child. So, my guess is that there is
> something going on with the hostname lookups. Do you have anything in
> your ntp.conf file that won't resolve?
>
Ok, it is a little more complex than I thought. The particular error
is not a problem with the resolver, it is a problem in ntpd after all.
Basically, the resolver process is sending back the data it resolved,
but the ntpd is returning an error. And this error is a bit of a catch
all, returned in a bunch of different places.
Try running this script with the pid of the parent ntpd:
#!/usr/sbin/dtrace -s
pid$1::req_ack:entry
{ ustack(); }
What function is calling req_ack?
--
blu
It's bad civic hygiene to build technologies that could someday be
used to facilitate a police state. - Bruce Schneier
-----------------------------------------------------------------------|
Brian Utterback - Solaris RPE, Oracle Corporation.
Ph:603-262-3916, Em:brian.utterb...@oracle.com
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org
