Page 1 of 1

v3.11.4-b3133 WL.com Partial Service Disruption

Posted: Tue 25 May 2021 2:00 pm
by PaulMy
B3133 started fine with the WiFiLogger setup, and all looks good.

Then updated the WLL setup and the DOS screen included a Weatherlink.com "Partial Service Disruption" message.

Code: Select all

Cumulus MX v.3.11.4 build 3133
Working Dir: C:\KomokaWeather\CumulusMXwll\
Waiting for PING reply from 192.168.0.100
Received PING response from 192.168.0.100, continuing...
Delaying start for 10 seconds
Start-up delay complete, continuing...
Cumulus running at: http://*:8999/
  (Replace * with any IP address on this machine, or localhost)
  Open the admin interface by entering this URL in a browser.
Today.ini = data\today.ini
Last update=2021-05-25T09:40:00
Weatherlink.com overall System Status: 'Partial Service Disruption', Updated: 25/05/21 9:44:06 AMError:
   wl.com system: WeatherLink Website, status: Partial Service Disruption, updated: 25/05/21 9:44:06 AM
   wl.com system: Data Ingestion, status: Operational, updated: 25/05/21 9:44:06 AM
   wl.com system: Mobile Applications, status: Partial Service Disruption, updated: 25/05/21 9:44:06 AM
   wl.com system: APIs and Data Feeds, status: Operational, updated: 25/05/21 9:44:06 AM
25/05/21 9:44:09 AM
Type Ctrl-C to terminate
Downloading Historic Data from WL.com from: 2021-05-25T09:40:00 to: 2021-05-25T09:44:09
 - No historic data available
Connecting real time FTP
Normal running

Looking at the local interface and all looks fine.
I have not seen this message before.

Decided to stop CMX and restart, and the same message, but everything seems to be working fine.
My Weatherlink.com site also seems ok and being updated and logged at the 5-min interval.

Possibly a temporary WL.com issue?

Enjoy,
Paul

Re: v3.11.4-b3133 WL.com Partial Service Disruption

Posted: Tue 25 May 2021 3:38 pm
by mcrossley
Hi Paul, CMX just logs the wl.com system status if it is anything other than normal for information purposes. It may help explain any issues as the service is accessed later in the log.

In this case it is showing that they have some issues with the web site, but data feeds and API queries are not affected. So nothing for MX to be worried about.