Bug #382

named.montime runs forever, restarts ntp and named forever

Added by Dave Täht about 1 year ago. Updated 8 months ago.

Status:New Start date:05/01/2012
Priority:Immediate Due date:
Assignee:Dave Täht % Done:

0%
Category:Build Spent time: -
Target version:1st Public Cerowrt release

Description

I think this is related to why ntp keeps getting restarted

3578     1 root     S     1696   3%   0% {named.montime} /bin/sh /usr/sbin/nam

in that the sort of fix for bug #113 which still doesn't work well, we updated ntp to head,
and ntpq now returns stuff that that script can't parse.

ntpq> peers
remote refid st t when poll reach delay offset jitter ==============================================================================
malformed srcadr=149.20.54.81
-0.0.0.0 3 p 10 64 17 0.362 1.747 4.572
malformed srcadr=46.166.138.172
+0.0.0.0 2 p 3 64 17 21.008 8.186 1.919
malformed srcadr=38.229.71.1
*0.0.0.0 2 p 4 64 17 53.762 7.853 3.160
malformed srcadr=24.124.0.251
-0.0.0.0 3 p 6 64 17 65.623 -3.194 2.748
malformed srcadr=64.16.211.38
-0.0.0.0 3 p 9 64 17 66.077 2.962 3.207
malformed srcadr=169.229.70.201
+0.0.0.0 3 p 66 64 7 4.034 7.393 2.044
malformed srcadr=2001:470:79::14:123
-0.0.0.0

Related issues

related to Cerowrt - Bug #113: circular dependency on time in DNS New 05/05/2011

History

#1
Updated by Dave Täht about 1 year ago

ntpdc is just plain busted in this build (and probably for a long time past)

root@test334-3:/etc/init.d# ntpdc -n -p | grep -v "^==" | egrep '^=|^\*' | awk ' { print $3 }'
127.0.0.1: timed out, nothing received
***Request timed out

#2
Updated by Dave Täht 11 months ago

  • Priority changed from Normal to Immediate

This bug makes it impossible to have sync time across devices. must fix. soon.

Also available in: Atom PDF