Wunderground crocked?

[RayProudfoot]

is that different from the "Key" shown on the landing page? I've been using the "Key" in place of the password for as long as I can remember.

To be honest I can’t remember. I did change the password in the Cumulus.ini file a while back. Maybe more than a year. I’ll look at the file tomorrow.

[GlueGuy2]

The "Key" and the "API Key" are two different things. There is this notice on their support page:

WU_PWS_Key_info.jpg

[AndyKF650]

You should use the "Key" as your password when setting up Weather Underground on CMX - settings - 3rd party uploads. Weather Underground suggest rebooting your pc to ensure the data flows but I did not need this extra step.

[RayProudfoot]

is that different from the "Key" shown on the landing page? I've been using the "Key" in place of the password for as long as I can remember.

Looking at the 'password' for WU in cumulus.ini it's a combination of alpha and numeric values so it's likely to be the Key rather than my old password.

[GlueGuy2]

I did a reboot. Several in fact. Still no joy in Mudville.

[SamiS]

I did a little more looking, and I am getting kind of strange results WRT the URL. See these results from ping and nslookup:

Code: Select all

>ping weatherstation.wunderground.com

Pinging a60f001b0bdcd4f64a49719eb2307270-ee5cf64f94dbf2ed.elb.us-east-1.amazonaws.com [34.232.250.77] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 34.232.250.77:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

>nslookup
Default Server:  dns.google
Address:  8.8.8.8

> weatherstation.wunderground.com
Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
Name:    a60f001b0bdcd4f64a49719eb2307270-ee5cf64f94dbf2ed.elb.us-east-1.amazonaws.com
Addresses:  52.22.134.222
          54.159.105.134
          34.232.250.77
Aliases:  weatherstation.wunderground.com
          rtupdate.wunderground.com
          pws-ingest-use1-01.sun.weather.com

I don't know how to interpret those results.

The site seems to be hosted in amazon cloud. Nslookup returns 3 alternative ip addresses that can be used to connect to that site. Ping has randomly selected one of those. But it seems that none of the ip addresses respond to ping from my home either. However this does not necessarily mean that the server is not working. When I try ”curl weatherstation.wunderground.com” it responds 404 not found. So the server responds to me at least.

Are you still getting the ”no such host is known” -error to your logfile? Have you stopped and restarted cmx itself (presuming that the ping and nslookup are from same computer that cumulus is running on)?

[GlueGuy2]

I did a little more looking, and I am getting kind of strange results WRT the URL. See these results from ping and nslookup:

Code: Select all

>ping weatherstation.wunderground.com

Pinging a60f001b0bdcd4f64a49719eb2307270-ee5cf64f94dbf2ed.elb.us-east-1.amazonaws.com [34.232.250.77] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 34.232.250.77:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

>nslookup
Default Server:  dns.google
Address:  8.8.8.8

> weatherstation.wunderground.com
Server:  dns.google
Address:  8.8.8.8

Non-authoritative answer:
Name:    a60f001b0bdcd4f64a49719eb2307270-ee5cf64f94dbf2ed.elb.us-east-1.amazonaws.com
Addresses:  52.22.134.222
          54.159.105.134
          34.232.250.77
Aliases:  weatherstation.wunderground.com
          rtupdate.wunderground.com
          pws-ingest-use1-01.sun.weather.com

I don't know how to interpret those results.

The site seems to be hosted in amazon cloud. Nslookup returns 3 alternative ip addresses that can be used to connect to that site. Ping has randomly selected one of those. But it seems that none of the ip addresses respond to ping from my home either. However this does not necessarily mean that the server is not working. When I try ”curl weatherstation.wunderground.com” it responds 404 not found. So the server responds to me at least.

Are you still getting the ”no such host is known” -error to your logfile? Have you stopped and restarted cmx itself (presuming that the ping and nslookup are from same computer that cumulus is running on)?

Yes, I have rebooted the server multiple times. When I attempt to ping any of the list of IPs, I get timeouts, which as you point out doesn't necessarily mean anything, as they probably block ICMP requests (don't blame them for that).

I agree, that the requests are getting lost in the AWS cloud somewhere. That is also not all that unusual. Too bad they can't sort it out, and even worse that they think they've solved the problem.

[SamiS]

I agree, that the requests are getting lost in the AWS cloud somewhere. That is also not all that unusual. Too bad they can't sort it out, and even worse that they think they've solved the problem.

Did you try curl or a browser to weatherstation.wunderground.com? Does it timeout? Or have you run traceroute to that address (actually not very helpful on this case, because they block this also).

Sometimes this kind of issues are related to routing issues between some specific isp’s. For example once a big german cloud hosting company was unreachable from our corporate isp, but worked fine from 4g networks. Therefore it is possible that wunderground does not even see the issue, if the problem is in AWS’s routing layer.

[GlueGuy2]

I clipped the URL from the log file, and replaced the "********" with our actual key (AKA password); pasted it in a browser, and got:

Code: Select all

success

This is what's in the log file:

Code: Select all

2023-01-26 09:02:00.373 Wunderground: URL = http://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?ID=KCALAHON9&PASSWORD=********&dateutc=2023-01-26+17%3A02%3A00&winddir=16&windspeedmph=5.0&windgustmph=13.0&windspdmph_avg2m=5.0&winddir_avg2m=16&humidity=46&tempf=50.8&rainin=0.00&dailyrainin=0.00&baromin=30.422&dewptf=30.7&softwaretype=Cumulus%20v3.14.0&action=updateraw

I did a couple more

Code: Select all

systemctl stop cumulusmx
systemctl start cumulusmx

for hee hees, but it's still not working

[SamiS]

I clipped the URL from the log file, and replaced the "********" with our actual key (AKA password); pasted it in a browser, and got:

Code: Select all

success

This is what's in the log file:

Code: Select all

2023-01-26 09:02:00.373 Wunderground: URL = http://weatherstation.wunderground.com/weatherstation/updateweatherstation.php?ID=KCALAHON9&PASSWORD=********&dateutc=2023-01-26+17%3A02%3A00&winddir=16&windspeedmph=5.0&windgustmph=13.0&windspdmph_avg2m=5.0&winddir_avg2m=16&humidity=46&tempf=50.8&rainin=0.00&dailyrainin=0.00&baromin=30.422&dewptf=30.7&softwaretype=Cumulus%20v3.14.0&action=updateraw

All this indicates that there is no error and the sending of the data succeeds. So the issue of ”no such host is known” is resolved. If your data still is not showing, then it definitely is an error on wunderground’s system.

[GlueGuy2]

Finally figured it out. DNS was working correctly, but I was experimenting with a PiHole, and had messed up the hostname lookup precedence. Once I left it to the default, it was fine.

Coincidence was that wunderground was having trouble at the same time.

[SamiS]

More than one change or an independent fault at the same time is definitely a fault finder’s nightmare. And of course we others can’t suspect something that is not told about.

But glad to hear problem resolved.

[GlueGuy2]

I'm tagging onto this thread, but if not enough people notice, I may post a new thread.

After updating to the latest CMX, and fiddling around with the DNS (look back in this thread), I notice that now my PWS in Wunderground is only updating every 5 minutes. Turning on CMX logging confirms that I am indeed sending updates to Wunderground every 1 minute. Did Wunderground change something to override the 1 minute update, or am I missing another setting somewhere within CMX (or Wunderground)?