Comment 52 for bug 1567540

Revision history for this message
In , john.marshall@riverwillow.com.au (john.marshallriverwillow.com.au) wrote :

Martin,

Thanks for looking at this. I'd like to stress that I'm only seeing this on a system with more memory (16GB) and more cores (8) than we have anywhere else.

As you suggested, I tried adding "rlimit memlock 128" to ntp.conf but it made no difference. I then tried "rlimit memlock 256" and it also made no difference.

I am now using:
  FreeBSD 10.2-RELEASE-p1
     ntpd 4.3.70

When ntpd fails, the dump backtrace looks like what I pasted in Comment #5 or like the following. The three backtraces (Hal's + my two) diverge after the blocking_getaddrinfo().

(gdb) bt
#0 0x00000008013ed631 in __h_errno_set () from /lib/libc.so.7
#1 0x00000008013bf90e in __res_vinit () from /lib/libc.so.7
#2 0x00000008013c33b0 in getaddrinfo () from /lib/libc.so.7
#3 0x00000008013e39ef in nsdispatch () from /lib/libc.so.7
#4 0x00000008013c20ec in getaddrinfo () from /lib/libc.so.7
#5 0x000000000043435a in blocking_getaddrinfo ()
#6 0x00000000004352f0 in blocking_child_common ()
#7 0x0000000000437159 in blocking_thread ()
#8 0x00000008010b77d5 in pthread_create () from /lib/libthr.so.3
#9 0x0000000000000000 in ?? ()

Since you mentioned nsswitch.conf in Comment #6, I note that all our servers have "hosts: dns" in nsswitch.conf.