Topic: "Map is not current. Data from Blitzortung is not available."

[gwwilk]

Ken's NA and US past 2 hour strikes maps aren't getting any data for some reason.  I also use these scripts and have the same problem.

I'm curious as to what's going on with this!

[miraculon]

See this thread: https://www.wxforum.net/index.php?topic=31584.0
The upshot is that the data source was moved from lightningmaps.org to blitzortung.org.

Greg H.

[gwwilk]

Thanks, Greg, but the relevant configuration in 'BO-mapgen.inc' is already set to

Code: [Select]

$mainURL = 'data.blitzortung.org';
and it's still not receiving data.

There has been a server IP change recently, and I wonder if it hasn't propagated through the DNS servers yet.

[miraculon]

Is this the actual animate.txt file that you are using? This seems to be the default and HDIR is not pointing to your own server directory... (assuming that you are not "kunden")

#!/bin/bash
# generic bash script for gen-BO-maps.php.  K. True - saratoga-weather.org
# Version 1.00 - 18-Apr-2015 - initial release
#
# --- begin settings
# set HDIR to full file path to BOmaps directory on your website
HDIR=/kunden/homepages/9/d141952417/htdocs/wx/BOmaps

# set PHPcmd to full path to PHP V5+ on your host
PHPcmd=/usr/bin/php

# --- end settings
#
cd $HDIR
$PHPcmd -q gen-BO-maps.php > status.txt 2>&1
#

Maybe your animate.txt got overwritten during an update?

Greg H.

[miraculon]

Hmmm... Mine shows no strikes either...

Greg H.

[gwwilk]

Hmmm... Mine shows no strikes either...

Greg H.

Frustrating problem this morning, eh?

[miraculon]

My status page is showing 0 B is strikes.txt file size used by Blitzortung.

Greg H.

[gwwilk]

I suspect that server changes, possibly including a modified data format, are responsible for our current difficulties.

In trying to reference specific posts on the forum I came up with no way to do so.  There are references to a changed IP address as well as a new data format, but they have to be chased down rather than linked to.  Why don't they allow links individual posts?

[miraculon]

Thanks, Greg, but the relevant configuration in 'BO-mapgen.inc' is already set to

Code: [Select]

$mainURL = 'data.blitzortung.org';
and it's still not receiving data.

There has been a server IP change recently, and I wonder if it hasn't propagated through the DNS servers yet.

https://dnschecker.org/#A/data.blitzortung.org reports all green check marks, so DNS is OK.

Greg H.

[miraculon]

My http://miraculon.net/BOmaps/cache/gen-BO-maps-log.txt is reporting a bunch of [0] => HTTP/1.1 401 Unauthorized errors.

Greg H.

p.s. I tried entering the http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2018/07/16/11/10.json.gz directly into the browser URL bar and I get apparent login failures with that.
(yes, I did change the user:pass-omitted to the correct entries)

[PaulMy]

Hi Greg,
Mine shows similar but notice a newer version http://www.komokaweather.com/BOmaps/cache/gen-BO-maps-log.txt

I notice mine is:

BOmapgen - V1.04 - 29-Sep-2017

and yours:

BOmapgen - V1.00 - 18-Apr-2015

Paul

[saratogaWX]

I suggest changing to data2.blitzortung.org from data.blitzortung.org for the lightning data .. the data server seems to be overloaded at this time.

[gwwilk]

Thanks, Ken!  I see you have data available again, so I just made the change you suggested.

[miraculon]

Thanks, Ken. That seems to be loading again.

Greg H.

[fpalafox]

Hello, I start having issues with lightning update in my web page. I am using a Saratoga scripts to include lightning in climason.com but now not strikes are included. I validate my user/ password and is ok from my blitzortung account. I check my local log and not strikes are downloaded. DO you know if servers or configurations are changed? I try using data.blitzortung.org or data2.blitzortung.org servers and still same issued.

Thank you in advance.

[saratogaWX]

Blitzortung has changed the structure of the stations file .. you need the updated V1.05 of the maps.  I've sent the link via PM.

The updates are to BO-mapgen-inc.php and BO-station-inc.php to support the revised stations file format.

[fpalafox]

Thank you very much for your help. Now blitzortung scripts are working fine.
Have a happy new year!!

[fpalafox]

After I upgrade to Ver 1.05 (Thanks Ken), all was working fine. But now maps is not current, message is displayed. I reinstall again the script, i review user/password and I start the manually update (http://climason.com/BOmaps/gen-BO-maps.php) but still same issue. Any ideas?

this Happend when I start manually:
BOmapgen - V1.05 - 30-Oct-2018 BO MOTD: 'Blitzortung.org message: Network for Lightning and Thunderstorms in Real Time' BO MOTD written to cache/BOmotd.txt with 94 bytes. Parms: URLPath='/BOmaps/' for map gen Parms: maxFilesize='200 MB' for cache/strikes.txt Parms: ourTZ='America/Hermosillo' Running PHP 5.6.38 start processing for region 3 data Fri, 15 Feb 2019 14:37:43 current cache/strikes.txt strikes file size is 0 B cache/strikes.txt filtered for old data First data: Wed, 31 Dec 1969 16:00:00 Last data : Fri, 15 Feb 2019 12:37:43 old data - restart collection from Fri, 15 Feb 2019 12:37:43 fetching new strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/15/19/30.json
Warning: get_headers(http://...@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/15/19/30.json): failed to open stream: operation failed in /home/climaso1/domains/climason.com/public_html/BOmaps/BOmapgen-inc.php on line 196
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/15/19/30.json fetching new GZ strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/15/19/30.json.gz
Warning: get_headers(http://...@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/15/19/30.json.gz): failed to open stream: operation failed in /home/climaso1/domains/climason.com/public_html/BOmaps/BOmapgen-inc.php on line 235
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/15/19/30.json.gz fetching new strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/15/19/40.json
Warning: get_headers(http://...@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/15/19/40.json): failed to open stream: operation failed in /home/climaso1/domains/climason.com/public_html/BOmaps/BOmapgen-inc.php on line 196
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/15/19/40.json fetching new GZ strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/15/19/40.json.gz
Warning: get_headers(http://...@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/15/19/40.json.gz): failed to open stream: operation failed in /home/climaso1/domains/climason.com/public_html/BOmaps/BOmapgen-inc.php on line 235

[saratogaWX]

Since no header info is actually returned, I suspect that your website can't connect to data.blitzortung.org server.  This can be caused by either a DNS issue, or by a routing issue (your webserver to data.blitzortung.org at 88.99.64.19 )
It's something for the tech support for your hoster to check out.  Ask them to SSH to the server and do a nslookup and ping for data.blitzortung.org to further diagnose the problem.

My site is not having issues with access to data.blitzortung.org currently so maps are current.

[fpalafox]

Thank you Ken.
I am trying to contact to my web support. By the way, I created a host.php same directory where BOmaps are located (http://www.climason.com/BOmaps/host.php). THis happend when i try to locate data.blitzortung.org:


data.blitzortung.org resolved to 88.99.64.19

Location:  Unknown

Whois (IP) Results:
sh: whois: command not found
Whois (Domain) Results:
sh: whois: command not found
NS Lookup Results:
Server:   67.207.67.3
Address:   67.207.67.3#53

Non-authoritative answer:
Name:   data.blitzortung.org
Address: 88.99.64.19
Ping Results:
PING data.blitzortung.org (88.99.64.19) 56(84) bytes of data.
64 bytes from static.19.64.99.88.clients.your-server.de (88.99.64.19): icmp_seq=1 ttl=51 time=162 ms
64 bytes from static.19.64.99.88.clients.your-server.de (88.99.64.19): icmp_seq=2 ttl=51 time=161 ms
64 bytes from static.19.64.99.88.clients.your-server.de (88.99.64.19): icmp_seq=3 ttl=51 time=161 ms
64 bytes from static.19.64.99.88.clients.your-server.de (88.99.64.19): icmp_seq=4 ttl=51 time=161 ms

--- data.blitzortung.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 161.145/161.451/162.269/0.551 ms
Traceroute Results:
sh: traceroute: command not found
Tracepath Results:
1?: [LOCALHOST] pmtu 1500
1: XSDA19006.XPRESS.COM.MX 6.823ms reached
1: XSDA19006.XPRESS.COM.MX 7.074ms reached
Resume: pmtu 1500 hops 1 back 1

[saratogaWX]

So it looks like DNS is resolving successfully and you can PING to that host.

Try changing lines in BOmapgen-inc.php

Code: [Select]

$T_begin = microtime(true);
    $lines = @file($filename,0,$context);
to

Code: [Select]

$T_begin = microtime(true);
    $lines = file($filename,0,$context);
so you can see the PHP error messages about the connection.

[fpalafox]

I removed @.
File included.

[saratogaWX]

Well, that was largely unhelpful .. the error messages like

Warning: file(http://...@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/19/13/50.json): failed to open stream: operation failed in /home/climaso1/domains/climason.com/public_html/BOmaps/BOmapgen-inc.php on line 195

don't provide any additional info to point to what might be failing.  Grrrr...

Are you sure that your Blitzortung $region $username and $password are set correctly in gen-BO-maps.php?  Since you are able to access the main site as shown by

BOmapgen - V1.05 - 30-Oct-2018
BO MOTD: 'Blitzortung.org message: Network for Lightning and Thunderstorms in Real Time'
BO MOTD written to cache/BOmotd.txt with 94 bytes.

it appears that data.blitzortung.org is maybe refusing the connection due to improper credentials.

I'd revert the code to put the @ back also.

[fpalafox]

I copy credentials from gen-BO-maps and paste to http://en.blitzortung.org/user_data.php?session=1. Work fine!!!

I try access from my pc to blitzortung server

http://data.blitzortung.org/Data_3/Protected/Strikes/2019/02/19/21/10.json.gz

 If I check, I dont see any .json.gz file, only  .json files are displayed. I dont know if it is a issue or not.

There are references to json.gz files.

Warning: get_headers(http://...@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/19/21/20.json): failed to open stream: operation failed in /home/climaso1/domains/climason.com/public_html/BOmaps/BOmapgen-inc.php on line 196
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/19/21/20.json fetching new GZ strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/19/21/20.json.gz
Warning: get_headers(http://...@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/19/21/20.json.gz): failed to open stream: operation failed in /home/climaso1/domains/climason.com/public_html/BOmaps/BOmapgen-inc.php on line 235
Headers returned from http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/19/21/20.json.gz fetching new strikes file at http://user:pass-omitted@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/19/21/30.json
Warning: file(http://...@data.blitzortung.org/Data_3/Protected/Strikes/2019/02/19/21/30.json): failed to open stream: operation failed in /home/climaso1/domains/climason.com/public_html/BOmaps/BOmapgen-inc.php on line 195

[saratogaWX]

The nn.json files are available on data.blitzortung.org initially as uncompressed, then after a time, they are automatically gzipped by the Blitzortung server to conserve space.  The script always trys the nn.json file first, and if it fails, tries the nn.json.gz file for the data.

I trust that your userid and password for Blitzortung do not contain the characters '@' or ':' in them.. If those characters are in either, the GET-mode URL will fail due to invalid syntax (as the colon separates the userid from the password, and the @ separates the user:pass from the hostname).