1

service unreliable - not filtering - long query times - setup page showing 'unconfigured'

11 replies

null
    • Timothy_Hull
    • 4 yrs agoThu, April 1, 2021 at 6:59 PM UTC
    • Reported - view

    I am experiencing the same problems.

    • deimos
    • 4 yrs agoThu, April 1, 2021 at 7:09 PM UTC
    • Reported - view

    From what I can tell, it started having issues six days ago: 

    syslog.7.gz:Mar 25 20:55:36 nextdns[1040]: Query 127.0.0.1 UDP A dns.nextdns.io.lan. (qry=36/res=12) 5000ms : doh resolve: context deadline exceeded
syslog.7.gz:Mar 25 20:55:39  nextdns[1040]: Query 127.0.0.1 UDP A www.theregister.com.lan. (qry=41/res=12) 5000ms : doh resolve: context deadline exceeded
syslog.7.gz:Mar 25 20:55:40 nextdns[1040]: Query 127.0.0.1 UDP A www.theregister.com. (qry=37/res=12) cached HTTP/2.0: doh resolve: context deadline exceeded

    That's PDT timezone.

     

    This is with nextdns 1.11.0 installed and running.

    • deimos
    • 4 yrs agoThu, April 1, 2021 at 7:15 PM UTC
    • Reported - view

    And appears to be getting worse: 

    zgrep -i "context deadline exceeded" syslog* | awk '{print $1, $2}' | uniq -c | sort -n
      4 syslog.2.gz:Mar 31
     37 syslog.3.gz:Mar 29
     78 syslog.5.gz:Mar 27
    154 syslog:Apr 1
    454 syslog.7.gz:Mar 25
   2259 syslog.1:Mar 31
   2878 syslog.2.gz:Mar 30
    • Will_Tisdale
    • 4 yrs agoThu, April 1, 2021 at 7:44 PM UTC
    • Reported - view

    Oh yeah - didn't realise it was borked this badly - maybe my decision about continuing to pay has been made for me seeing as the service is not exactly robust: 

      ~ ❯ journalctl | grep "context deadline exceeded" | awk '{print $1, $2}' | uniq -c | sort -n                       thalamus@nas
      1 Mar 27
      2 Mar 16
      2 Mar 31
      3 Mar 22
      9 Mar 25
     23 Mar 19
    135 Mar 17
    374 Apr 01
   1385 Mar 24
   1422 Mar 23
   2616 Mar 29
   2994 Mar 26
  ~ ❯
    • olivier
    • 4 yrs agoThu, April 1, 2021 at 7:45 PM UTC
    • Reported - view

    A few NextDNS regions got performance issues earlier today, resulting in longer than normal resolution times for some users. The issue is now fully resolved. Please accept our apologies for the inconvenience.

      • Will_Tisdale
      • 4 yrs agoThu, April 1, 2021 at 7:48 PM UTC
      • Reported - view

      Olivier Poitrey it's clearly not a one off issue, it's been happening for days seemingly - see above.

      • olivier
      • 4 yrs agoThu, April 1, 2021 at 7:53 PM UTC
      • Reported - view

      Will Tisdale whatever issue you had for days has nothing to do we what we had here.

      • Will_Tisdale
      • 4 yrs agoThu, April 1, 2021 at 8:01 PM UTC
      • Reported - view

      Olivier Poitrey me and deimos  had exactly the same issue it seems...

      What else would cause thousands of 'content deadline exceeded' messages since the 23rd March and none really before then?

      • olivier
      • 4 yrs agoThu, April 1, 2021 at 8:10 PM UTC
      • Reported - view

      Will Tisdale it could be routing issues or many other things.

      • Brad_Allison
      • 4 yrs agoThu, April 1, 2021 at 9:05 PM UTC
      • Reported - view

      Olivier Poitrey would you mind providing some insight as to culprit and potential for future issues of the like?

    • LL91
    • 4 yrs agoThu, April 1, 2021 at 8:03 PM UTC
    • Reported - view

    i had the same issues as original poster

Login to reply

Content aside

  • 1 Likes
  • 4 yrs agoThu, April 1, 2021 at 9:05 PM UTCLast active
  • 11Replies
  • 320Views
  • 6 Following