Stats server update
The Allstar Link admin team is pleased to announce the successful migration of the stats server. The old stats server was severely overloaded and has been migrated to a new much faster, and better connected machine. We've added some speedups/fixes to the code and have enabled the big network wide map now and is updated every 3 minutes. We bought a newer G7 HP DL360 server with 12 cores, 128 gb ram, and 880g of 15k SAS raid 50. https://i.imgur.com/Lx6Ul8E.jpg We've racked it at one of the premier east coast data centers, and running on our own IP space. Simply put, we should see much higher availability and have power for adding new features. http://stats.allstarlink.org/ is now at 44.98.254.130, and the old server is at http://stats-old.allstarlink.org/ Check the old server, as there are still 13 nodes pointed at it. If you see one of your nodes in that list, this means you're not using DNS and have the IP hardcoded in rpt.conf or /etc/hosts. If you're showing up on the old server check your config for this. 73s -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
On 2018-01-18 11:34 AM, Bryan Fields wrote:
The Allstar Link admin team is pleased to announce the successful migration of the stats server.
The old stats server was severely overloaded and has been migrated to a new much faster, and better connected machine. We've added some speedups/fixes to the code and have enabled the big network wide map now and is updated every 3 minutes.
We bought a newer G7 HP DL360 server with 12 cores, 128 gb ram, and 880g of 15k SAS raid 50. https://i.imgur.com/Lx6Ul8E.jpg
We've racked it at one of the premier east coast data centers, and running on our own IP space. Simply put, we should see much higher availability and have power for adding new features.
http://stats.allstarlink.org/ is now at 44.98.254.130, and the old server is at http://stats-old.allstarlink.org/
Check the old server, as there are still 13 nodes pointed at it. If you see one of your nodes in that list, this means you're not using DNS and have the IP hardcoded in rpt.conf or /etc/hosts. If you're showing up on the old server check your config for this.
<-- Hi Brian and all: Nice work... 2 of my nodes (on the same Pi - i.e., 27919 and 28762) are still reporting to the old server. I do have the correct url in rpt.conf and do not have a hard-coded entry in my hosts file. Any ideas? Thanks, Ramesh.
Ramesh, Until your pi can resolve the address correctly (for whatever reason) it's still a problem. Does "ping stats.allstarlink.org" return the new address or the old? Does it resolve correctly from another PC on your LAN? etc. 73 Danny K5CG
From: "Ramesh Dhami" <Ramesh@va3uv.com> To: "app rpt-users" <app_rpt-users@lists.allstarlink.org> Sent: Friday, January 19, 2018 9:04:09 AM Subject: Re: [App_rpt-users] Stats server update
On 2018-01-18 11:34 AM, Bryan Fields wrote:
The Allstar Link admin team is pleased to announce the successful migration of the stats server.
The old stats server was severely overloaded and has been migrated to a new much faster, and better connected machine. We've added some speedups/fixes to the code and have enabled the big network wide map now and is updated every 3 minutes.
We bought a newer G7 HP DL360 server with 12 cores, 128 gb ram, and 880g of 15k SAS raid 50. https://i.imgur.com/Lx6Ul8E.jpg
We've racked it at one of the premier east coast data centers, and running on our own IP space. Simply put, we should see much higher availability and have power for adding new features.
http://stats.allstarlink.org/ is now at 44.98.254.130, and the old server is at http://stats-old.allstarlink.org/
Check the old server, as there are still 13 nodes pointed at it. If you see one of your nodes in that list, this means you're not using DNS and have the IP hardcoded in rpt.conf or /etc/hosts. If you're showing up on the old server check your config for this.
<-- Hi Brian and all: Nice work... 2 of my nodes (on the same Pi - i.e., 27919 and 28762) are still reporting to the old server. I do have the correct url in rpt.conf and do not have a hard-coded entry in my hosts file.
Any ideas?
Thanks,
Ramesh. _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
On 2018-01-19 10:20 AM, K5CG wrote:
Ramesh,
Until your pi can resolve the address correctly (for whatever reason) it's still a problem.
Does "ping stats.allstarlink.org" return the new address or the old?
Does it resolve correctly from another PC on your LAN? etc.
<-- Hi Danny: a ping from the Pi still returns the old (209.x.x.x) address; I rebooted the Pi to ensure any cached DNS entries get flushed. I've just logged into my D-STAR system on the same network (so NAT'd behind the same router) and get the same issue. So perhaps the DNS changes have not propagated through. I'll wait a little longer and, if needed, I'll hard-code the change in my host file to force the new IP... until the DNS changes catch-up. Cheers, Ramesh.
On 1/19/18 10:04 AM, Ramesh Dhami wrote:
<-- Hi Brian and all: Nice work... 2 of my nodes (on the same Pi - i.e., 27919 and 28762) are still reporting to the old server. I do have the correct url in rpt.conf and do not have a hard-coded entry in my hosts file.
Can you do dig stats.allstarlink.org and past the results here? Also do ping stats.allstarlink.org as well and paste th first couple lines of output. Thank you, -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
On 2018-01-19 10:23 AM, Bryan Fields wrote:
On 1/19/18 10:04 AM, Ramesh Dhami wrote:
<-- Hi Brian and all: Nice work... 2 of my nodes (on the same Pi - i.e., 27919 and 28762) are still reporting to the old server. I do have the correct url in rpt.conf and do not have a hard-coded entry in my hosts file. Can you do dig stats.allstarlink.org and past the results here?
root@repeater:~# dig stats.allstarlink.org ; <<>> DiG 9.9.5-9+deb8u3-Debian <<>> stats.allstarlink.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58101 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;stats.allstarlink.org. IN A ;; ANSWER SECTION: stats.allstarlink.org. 25932082 IN A 209.198.22.194 ;; Query time: 9 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Fri Jan 19 10:27:11 EST 2018 ;; MSG SIZE rcvd: 55 root@repeater:~#
Also do ping stats.allstarlink.org as well and paste th first couple lines of output.
root@repeater:~# ping stats.allstarlink.org PING stats.allstarlink.org (209.198.22.194) 56(84) bytes of data. 64 bytes from xarax-vm-209-198-22-194.xarix.net (209.198.22.194): icmp_seq=1 ttl=53 time=38.9 ms 64 bytes from xarax-vm-209-198-22-194.xarix.net (209.198.22.194): icmp_seq=2 ttl=53 time=40.9 ms
On 2018-01-19 10:28 AM, Ramesh Dhami wrote:
root@repeater:~# dig stats.allstarlink.org
; <<>> DiG 9.9.5-9+deb8u3-Debian <<>> stats.allstarlink.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58101 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION: ;stats.allstarlink.org. IN A
;; ANSWER SECTION: stats.allstarlink.org. 25932082 IN A 209.198.22.194
;; Query time: 9 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Fri Jan 19 10:27:11 EST 2018 ;; MSG SIZE rcvd: 55
<-- Just changed my nameserver from 192.168.1.1 to 8.8.8.8 (in resolv.conf) and voila! R.
Could it be that your upstream DNS provider is holding the record in cache? What if you dig against say 8.8.8.8 does it return right then? What is 192.168.1.1 (your home router I assume) what is he looking at for DNS? Probably upstream and it is probably cached. Unless 192.168.1.1 keeps some cache and needs a flush. Mike Kb8zgl On 1/19/18, 10:29 AM, "App_rpt-users on behalf of Ramesh Dhami" <app_rpt-users-bounces@lists.allstarlink.org on behalf of Ramesh@va3uv.com> wrote: On 2018-01-19 10:23 AM, Bryan Fields wrote: > On 1/19/18 10:04 AM, Ramesh Dhami wrote: >> <-- Hi Brian and all: Nice work... 2 of my nodes (on the same Pi - >> i.e., 27919 and 28762) are still reporting to the old server. I do have >> the correct url in rpt.conf and do not have a hard-coded entry in my >> hosts file. > Can you do dig stats.allstarlink.org and past the results here? root@repeater:~# dig stats.allstarlink.org ; <<>> DiG 9.9.5-9+deb8u3-Debian <<>> stats.allstarlink.org ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58101 ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;stats.allstarlink.org. IN A ;; ANSWER SECTION: stats.allstarlink.org. 25932082 IN A 209.198.22.194 ;; Query time: 9 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Fri Jan 19 10:27:11 EST 2018 ;; MSG SIZE rcvd: 55 root@repeater:~# > > Also do ping stats.allstarlink.org as well and paste th first couple lines of > output. > > root@repeater:~# ping stats.allstarlink.org PING stats.allstarlink.org (209.198.22.194) 56(84) bytes of data. 64 bytes from xarax-vm-209-198-22-194.xarix.net (209.198.22.194): icmp_seq=1 ttl=53 time=38.9 ms 64 bytes from xarax-vm-209-198-22-194.xarix.net (209.198.22.194): icmp_seq=2 ttl=53 time=40.9 ms _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
On 1/19/18 10:28 AM, Ramesh Dhami wrote:
;; ANSWER SECTION: stats.allstarlink.org. 25932082 IN A 209.198.22.194
holy crap, your dns server is messing with the ASL.org ttl 25932082 seconds is 7203 _hours_ or over 300 days! The TTL should be 300 seconds or less. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
holy crap, your dns server is messing with the ASL.org ttl
25932082 seconds is 7203 _hours_ or over 300 days!
The TTL should be 300 seconds or less.
I can't tell you how many SOHO routers I've fought with that don't handle DNS TTL correctly and/or return some ridiculously long TTL to the workstation that made the query...which is why I never let those kind of routers handle DNS, I point right to a real server (typically Google, OpenDNS, or the ISP depending on the situation). --- Jeff WN3A --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
I go one better, and run my own recursor/authoritative pair inside my network. All my hosts point to a bind9 server on Ubuntu, which is authoritative for my internal domain name I use for all my machines. Anything it's not authoritative for gets forwarded on to a PiHole VM, which acts as a nice ad filter. If the PiHole doesn't have it cached, it asks Google's DNS servers for it. Of course, my network is much more complex than most people will run - I have multiple 802.1Q vlans, a dedicated UBNT router box, and a dedicated PFSense firewall box. Jeremy, NQ0M -----Original Message----- From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Jeff DePolo Sent: Friday, January 19, 2018 9:54 AM To: 'Users of Asterisk app_rpt' <app_rpt-users@lists.allstarlink.org> Subject: Re: [App_rpt-users] Stats server update
holy crap, your dns server is messing with the ASL.org ttl
25932082 seconds is 7203 _hours_ or over 300 days!
The TTL should be 300 seconds or less.
I can't tell you how many SOHO routers I've fought with that don't handle DNS TTL correctly and/or return some ridiculously long TTL to the workstation that made the query...which is why I never let those kind of routers handle DNS, I point right to a real server (typically Google, OpenDNS, or the ISP depending on the situation). --- Jeff WN3A --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
-----Original Message----- From: App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] On Behalf Of Ramesh Dhami Sent: Friday, January 19, 2018 9:29 AM To: app_rpt-users@lists.allstarlink.org Subject: Re: [App_rpt-users] Stats server update ;; ANSWER SECTION: stats.allstarlink.org. 25932082 IN A 209.198.22.194 Just for information purposes, that huge number before "IN" is the problem. That represents the Time-To-Live (in seconds), which is how long a recursive DNS server is allowed to cache the entry before checking back in with the authoritative server to see if it's updated. With that long of a TTL, it would stay for months. You mentioned in a later email your old DNS server was 192.168.1.1 - does that represent your router? If so, either your router, or something upstream of you, is doing some very bad stuff like overriding the DNS TTL. Changing DNS server will work, probably until the next time you reboot the machine, as DHCP will then again grab the 192.168.1.1 IP for DNS. Jeremy, NQ0M
participants (6)
-
Bryan Fields -
Jeff DePolo -
Jeremy Utley -
K5CG -
Michael Wolthuis -
Ramesh Dhami