WXforum.net
May 23, 2013, 08:56:32 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
Members: 6617  •  Posts: 178651  •  Topics: 18129
Please welcome TheMOX, our newest member.
Welcome to the the new hosting for WXforum.net.
 
   Home   Help Search Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: CWOP Tier 2 Servers Have Withdrawn  (Read 4405 times)
0 Members and 1 Guest are viewing this topic.
GaryTX
Administrator
Member
*****
Offline Offline

Posts: 7



WWW
« on: January 06, 2007, 09:08:36 PM »

Anyone posting data to CWOP using the Tier 2 servers need to change your settings, as the Tier 2 servers are offline.  Only the core servers are currently in service.  Things may change, but that's the present status.

Russ Chadwick from NOAA posted the following message on the CWOP QC message list a little while ago:

"As of a few hours ago, the Tier 2 operators abruptly withdrew support
for CWOP traffic through their servers.  We're sorry for any
inconvenience this causes CWOP members, but you will have to change the server designation in your local software.  More details at
http://www.wxqa.com/news.html

Russ"

Available servers at present are:

aprsfl.net : port 14580 - - - Dave, KG4YZY - - - Tampa Bay, FL (Core 3)
first.aprs.net : port 14580 - - - Gerry, N5JXS - - - College Station, TX (Core 1)
rotate.aprs.net : port 14580 - - - connects to a Core APRS-IS server and rotates to a different one if that connection drops.
second.aprs.net : port 14580 - - - Greg, WB6ZSU - - - Irvine, CA (Core 2)

The rotate.aprs.net server is probably the best choice at present.
Logged




<a href="http://www.wilcowx.com"><img src="http://www.wilcowx.com/rhwc_banner2.jpg" alt="Current Weather in Round Rock, Texas"></a>
Mark / Ohio
Live from Mars!
Forecaster
*****
Offline Offline

Posts: 2351



WWW
« Reply #1 on: January 06, 2007, 10:38:08 PM »

I switched my VP Live over to rotate.aprs.net : port 14580

All seems to be well again.  I seen the email from Russ a couple of hours ago and found they had not received my data for four hours.

This Calvin quote seems an especially fitting description of the server operators at the moment:

"A little rudeness and disrespect can elevate a meaningless interaction to a battle of wills and add drama to an otherwise dull day."  

  Wink

P.S. Good to hear from you Gary!
Logged

Mark 
2002 Davis VP I Wireless, WeatherLink (Serial), VWS, ImageSalsa, GRLevel3, VirtualVP, VPLive, StartWatch, Windows XP (SP3)

W3DRM
Forecaster
*****
Offline Offline

Posts: 1346



WWW
« Reply #2 on: January 07, 2007, 01:43:47 AM »

Quote from: "Mark / Ohio"
I switched my VP Live over to rotate.aprs.net : port 14580

All seems to be well again.  I seen the email from Russ a couple of hours ago and found they had not received my data for four hours.

This Calvin quote seems an especially fitting description of the server operators at the moment:

"A little rudeness and disrespect can elevate a meaningless interaction to a battle of wills and add drama to an otherwise dull day."  

  Wink

P.S. Good to hear from you Gary!


And of course, guess who suffers from that "drama"? We, the users who have no control over anything...  Crying or Very sad
Logged

Don - W3DRM - Minden, Nevada --- Davis Wireless VP2, VWS 14.00 p101,
StartWatch, VirtualVP, VPLive, WL 5.9.3, Win7 Ultimate-SP1
--- Logitech QuickCam Fusion webcam
tinplate
Forecaster
*****
Offline Offline

Posts: 368


WWW
« Reply #3 on: January 07, 2007, 01:47:53 AM »

VPLive should have detected the failure of the tier 2 servers and switched automatically to the core servers, but there was, unfortunately a bug in the error detection. I have uploaded a new version of VPLive to fix that bug and also change the default servers.

Also, the tier 2 servers switched from taking data on port 23 to taking it via port 14850. For now, VPLive 1.1.6 is using the core servers as the primary, and the tier 2 servers as failovers.

Steve
Logged
wuhu_software
Forecaster
*****
Offline Offline

Posts: 682


WWW
« Reply #4 on: January 07, 2007, 07:54:10 AM »

Quote from: "Mark / Ohio"
I switched my VP Live over to rotate.aprs.net : port 14580


Having watched over the QC list for the past few days, what is being said about Windows and DNS servers preventing the proper use of the rotate server does make sense to me.

Have you guys already disabled DNS caching when using the rotate server?

Thoughts?

Thanks.

---

PS - I found this page that goes in to detail on how to disable your DNS caching on a Windows 2000 or XP machine.

http://www.speedguide.net/read_articles.php?id=158

---
Logged
tinplate
Forecaster
*****
Offline Offline

Posts: 368


WWW
« Reply #5 on: January 07, 2007, 09:00:26 AM »

After doing some research into the DNS topic, I think that changing your windows DNS caching setting may be unnecessary. It turns out that the setting is just the maximum caching period. The DNS record itself has its own cache period (called the TTL - time to live). Windows uses the smaller of the two. Right now, rotate.aprs.net has a TTL of 60 seconds. That means that if you are uploading your CWOP data every 5 minutes, windows will hit the DNS server to resolve the address every time you do a CWOP upload. I've tested this out, and I get the same results (i.e. I don't get stuck hitting a single server) whether I have a short period set in windows or a long period. You still may hit the same server a few times in a row because right now there are only two servers in the core rotation (first and third).

By contrast, the tier 2 rotation has a TTL of 2400 seconds (40 minutes), so that is likely why it looked like you got stuck on a single server using that rotation.
Logged
wuhu_software
Forecaster
*****
Offline Offline

Posts: 682


WWW
« Reply #6 on: January 07, 2007, 09:19:56 AM »

Quote from: "tinplate"
After doing some research into the DNS topic, I think that changing your windows DNS caching setting may be unnecessary. It turns out that the setting is just the maximum caching period. The DNS record itself has its own cache period (called the TTL - time to live). Windows uses the smaller of the two. Right now, rotate.aprs.net has a TTL of 60 seconds. That means that if you are uploading your CWOP data every 5 minutes, windows will hit the DNS server to resolve the address every time you do a CWOP upload. I've tested this out, and I get the same results (i.e. I don't get stuck hitting a single server) whether I have a short period set in windows or a long period. You still may hit the same server a few times in a row because right now there are only two servers in the core rotation (first and third).

By contrast, the tier 2 rotation has a TTL of 2400 seconds (40 minutes), so that is likely why it looked like you got stuck on a single server using that rotation.



Thanks for the detailed response. I see why this is a non-issue.

Too bad that answer could have not been posted in the QC list!
Logged
daveh
Member
*
Offline Offline

Posts: 4


WWW
« Reply #7 on: January 25, 2007, 02:37:58 AM »

Hi Everyone,

Seems the word is out on this Forum concerning the Citizen Weather Observer Program (CWOP) recommended server list, but I'll restate the list anyway...

In order to enhance network stability and increase the potential of your weather reports getting to NOAA, we (Russ and I) are recommending everyone use the following server to send data to CWOP:
Default Server:  rotate.aprs.net                        Port: 14580

Alternative Servers:
Server Name:   first.aprs.net                           Port: 14580
Server Name:   second.aprs.net                      Port: 14580
Server Name:   third.aprs.net                          Port: 14580
Server Name:   fifth.aprs.net                           Port: 14580

Please check the following CWOP links to see the latest info:
CWOP News: http://www.wxqa.com/news.html
CWOP Server List:  http://www.wxqa.com/activecwd.html

Please contact me if you have any questions,

DaveH
CW0351
dave@cwop.info
Logged

CW0351
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.201 seconds with 18 queries.