Weather Station Hardware > Blitzortung

"Map is not current. Data from Blitzortung is not available." message

(1/5) > >>

miraculon:
I am getting the Subject error in a red band on my lightning maps.

https://www.rogerscityweather.com/NorthAm-blitz.php

Saratoga-Weather has the same message on the map at https://saratoga-weather.org/NA-lightning.php

The main Blitzortung site and Lightningmaps.org seem to be OK though.

Any ideas on this?

Greg H.

saratogaWX:
The sites seem to be up, but the data site is getting 404s (Not Found) for the files needed:

--- Code: ---fetching new strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/19/40.json
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/19/40.json
Array
(
    [0] => HTTP/1.1 404 Not Found
    [Server] => nginx/1.14.0 (Ubuntu)
    [Date] => Sun, 20 Mar 2022 21:40:03 GMT
    [Content-Type] => text/html
    [Content-Length] => 178
    [Connection] => close
)

fetching new GZ strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/19/40.json.gz
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/19/40.json.gz
Array
(
    [0] => HTTP/1.1 404 Not Found
    [Server] => nginx/1.14.0 (Ubuntu)
    [Date] => Sun, 20 Mar 2022 21:40:04 GMT
    [Content-Type] => text/html
    [Content-Length] => 178
    [Connection] => close
)

fetching new strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/19/50.json
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/19/50.json
Array
(
    [0] => HTTP/1.1 404 Not Found
    [Server] => nginx/1.14.0 (Ubuntu)
    [Date] => Sun, 20 Mar 2022 21:40:04 GMT
    [Content-Type] => text/html
    [Content-Length] => 178
    [Connection] => close
)

fetching new GZ strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/19/50.json.gz
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/19/50.json.gz
Array
(
    [0] => HTTP/1.1 404 Not Found
    [Server] => nginx/1.14.0 (Ubuntu)
    [Date] => Sun, 20 Mar 2022 21:40:05 GMT
    [Content-Type] => text/html
    [Content-Length] => 178
    [Connection] => close
)

fetching new strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/20/00.json
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/20/00.json
Array
(
    [0] => HTTP/1.1 404 Not Found
    [Server] => nginx/1.14.0 (Ubuntu)
    [Date] => Sun, 20 Mar 2022 21:40:05 GMT
    [Content-Type] => text/html
    [Content-Length] => 178
    [Connection] => close
)

fetching new GZ strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/20/00.json.gz
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/20/00.json.gz
Array
(
    [0] => HTTP/1.1 404 Not Found
    [Server] => nginx/1.14.0 (Ubuntu)
    [Date] => Sun, 20 Mar 2022 21:40:06 GMT
    [Content-Type] => text/html
    [Content-Length] => 178
    [Connection] => close
)

fetching new strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/20/10.json
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/20/10.json
Array
(
    [0] => HTTP/1.1 404 Not Found
    [Server] => nginx/1.14.0 (Ubuntu)
    [Date] => Sun, 20 Mar 2022 21:40:06 GMT
    [Content-Type] => text/html
    [Content-Length] => 178
    [Connection] => close
)

fetching new GZ strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/20/10.json.gz
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/20/10.json.gz
Array
(
    [0] => HTTP/1.1 404 Not Found
    [Server] => nginx/1.14.0 (Ubuntu)
    [Date] => Sun, 20 Mar 2022 21:40:07 GMT
    [Content-Type] => text/html
    [Content-Length] => 178
    [Connection] => close
)

fetching new strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/20/20.json
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/20/20.json
Array
(
    [0] => HTTP/1.1 404 Not Found
    [Server] => nginx/1.14.0 (Ubuntu)
    [Date] => Sun, 20 Mar 2022 21:40:07 GMT
    [Content-Type] => text/html
    [Content-Length] => 178
    [Connection] => close
)

fetching new GZ strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/20/20.json.gz
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2022/03/20/20/20.json.gz
Array
(
    [0] => HTTP/1.1 404 Not Found
    [Server] => nginx/1.14.0 (Ubuntu)
    [Date] => Sun, 20 Mar 2022 21:40:08 GMT
    [Content-Type] => text/html
    [Content-Length] => 178
    [Connection] => close
)

...

--- End code ---
Unknown why this is happening.  The Service Monitor shows all is well with data.blitzortung.org

I'll poke around a bit...

saratogaWX:
Looks like the data server stopped posting updates after 2022-03-19 18:20 GMT .. the 2022-03-20 set is completely empty.  So it is (at this time) a Blitzortung data issue (they're not publishing it).

W0BTU:
This page stopped updating about the same time.
https://www.lightningmaps.org/blitzortung/america/index.php?bo_page=statistics&bo_show=station&lang=en&bo_station_id=1174

Cutty Sark Sailor:
If this isn't simply a 'glitch', I suspect this will prove to be related to stroke/station "regional assignment" realignments and upgrades. Example, since last year stations in 'North America' count activity to two "servers": 3 and 10,  which relate to'geographic areas' for stroke location. I have 'personally' (While awaiting Egon's 'final' designations and processing) have been referring to them as
"North America 1 (NA Global) Updates @ 1-5 min All GLOBAL stations localizing Atlantic, Pacific, Americas.
(old 'region 3)
and
North America 2 (NA  Local) Updates @ 1 min NORTH AMERICA stations ONLY localized.
(although not reflecting the 'actual' intent and activity of the 'name' I'm using...that is 'quick and dirty')
Something similar for the other 'original' regions, as the refinements continue...
... and I would expect a bit of further confusion as the season begins in Northern Hemisphere and Egon pulls a bit more together...

Navigation

[0] Message Index

[#] Next page

Go to full version