Author Topic: wx advisories not updating...  (Read 1153 times)

0 Members and 1 Guest are viewing this topic.

Offline W3DRM

  • Forecaster
  • *****
  • Posts: 3360
    • Emmett Weather
wx advisories not updating...
« on: March 20, 2018, 12:28:11 AM »
Is it me or is there an issue with the wx advisories? My last update was March 16th at 10:12am. Have had no updates since then. I restarted my alerts vbs cron job routine but still no update.
Don - W3DRM - Emmett, Idaho --- Blitzortung ID: 808 --- FlightRadar24 ID: F-KBOI7
Davis Wireless VP2, WD 10.37s150,
StartWatch, VirtualVP, VPLive, Win10 Pro
--- Logitech HD Pro C920 webcam (off-line)
--- RIPE Atlas Probe - 32849

Offline saratogaWX

  • Administrator
  • Forecaster
  • *****
  • Posts: 9257
  • Saratoga, CA, USA Weather - free PHP scripts
    • Saratoga-Weather.org
Re: wx advisories not updating...
« Reply #1 on: March 20, 2018, 01:14:44 AM »
I think the issue is with your cron job.  I ran nws-alerts.php on your site and (in a view-source) showed
Quote
<!-- nws-alerts.php - V1.42 - 27-Jan-2018 -->
<!-- 12 unique Zone entries found. Zones='NVZ003,NVC005,NVC019,NVC029,NVC031,NVC510,NVZ002,CAZ072,CAC017,CAC003,CAC061,CAC057' -->
<!-- Cron job enabled -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=NVZ003&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.060 conn=0.075 pxfer=0.111 get=0.222 total=0.332 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=NVC005&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.046 get=0.186 total=0.233 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=NVC019&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.049 get=0.194 total=0.243 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=NVC029&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.047 get=0.192 total=0.239 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=NVC031&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.015 pxfer=0.050 get=0.194 total=0.244 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=NVC510&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.047 get=0.193 total=0.239 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=NVZ002&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.048 get=0.219 total=0.267 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=NVC005&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.049 get=0.016 total=0.065 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=NVC510&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.015 pxfer=0.058 get=0.017 total=0.075 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=NVC031&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.049 get=0.020 total=0.069 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=CAZ072&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.016 pxfer=0.054 get=0.223 total=0.277 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=CAC017&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.046 get=0.220 total=0.266 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=CAC003&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.047 get=0.178 total=0.224 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=CAC061&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.015 pxfer=0.050 get=0.218 total=0.268 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwaatmget.php?x=CAC057&y=1 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.046 get=0.182 total=0.228 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwacapget.php?x=NV125A98C1F2A0.SpecialWeatherStatement.125A98CFECC0NV.REVSPSREV.4194344b5294b4432d13f802c629e180 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.057 get=0.155 total=0.212 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwacapget.php?x=NV125A98C1F048.WinterStormWatch.125A98FDB380NV.REVWSWREV.57df72b76a3f4678433d0981cb0ff5bb -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.047 get=0.150 total=0.197 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwacapget.php?x=CA125A98C1F2A0.SpecialWeatherStatement.125A98CFECC0CA.REVSPSREV.f51911dcd906a2d31a45e6e498c88179 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.016 pxfer=0.051 get=0.144 total=0.196 secs -->
<!-- XML source: https://alerts.weather.gov/cap/wwacapget.php?x=CA125A98C1F048.WinterStormWatch.125A98FDB380CA.REVWSWREV.b8c8e7a61662ceb1cadb6a42e7a223d7 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.046 get=0.146 total=0.193 secs -->

<!-- 10:13:15 -->
<!-- Error: Operation timed out after 2001 milliseconds with 0 bytes received -->
<!-- Source: https://alerts.weather.gov/cap/wwacapget.php?x=CA125A98C21884.WinterStormWatch.125A98FDB380CA.STOWSWSTO.c70672a80734c03e6966f0eb4db7deb9 -->
<!-- non XML source: https://alerts.weather.gov/cap/wwacapget.php?x=CA125A98C21884.WinterStormWatch.125A98FDB380CA.STOWSWSTO.c70672a80734c03e6966f0eb4db7deb9 -->
<!-- HTTP stats:  RC=0 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.016 pxfer=0.055 get=1.147 total=1.202 secs -->
<!-- header type='' -->
<!-- First attempt in getting primary data failed -->
<!-- XML source: https://alerts.weather.gov/cap/wwacapget.php?x=CA125A98C21884.WinterStormWatch.125A98FDB380CA.STOWSWSTO.c70672a80734c03e6966f0eb4db7deb9 -->
<!-- HTTP stats:  RC=200 dest=23.33.164.174 port=443 (from sce=198.71.62.63)
      Times: dns=0.000 conn=0.014 pxfer=0.048 get=0.016 total=0.064 secs -->
<!-- Second attempt successful -->

<!-- Cache file updated: Mon 03-19-2018 10:13 pm -->
<!-- Alert box data file updated -->
<!-- Icon data file updated -->
<!-- Alert logging enabled -->
<!-- Log file updated Mon 03-19-2018 10:13 pm -->
<!-- Total process time: 7.1479 seconds -->
so it will run if the cron is running :)
Ken True/Saratoga, CA, USA main site: saratoga-weather.org
Davis VP1+ FARS, Blitzortung RED, GRLevel3, WD, WL, VWS, Cumulus, Meteobridge
Free weather PHP scripts/website templates - update notifications on Twitter saratogaWXPHP

Offline W3DRM

  • Forecaster
  • *****
  • Posts: 3360
    • Emmett Weather
Re: wx advisories not updating...
« Reply #2 on: March 20, 2018, 08:00:36 PM »
Thanks Ken. I had restarted the cron job about ten minutes before I had posted my comment. At that time, the data was not updating. This morning, however, all looked fine. Am wondering if it takes some time for the data to be updated on the website after the cron job is restarted? Perhaps I was just too anxious and should have waited longer before posting the question. Other than making routine template updates, I've made no changes to the system or the website for a long time.

We have a lot of watches, warnings and advisories at the moment as this next round of storms comes our way.

Thanks again for the help! BTW, it looks like you are getting hit by these storms as they come in off the Pacific. Hope the mudslides don't get to bad...
Don - W3DRM - Emmett, Idaho --- Blitzortung ID: 808 --- FlightRadar24 ID: F-KBOI7
Davis Wireless VP2, WD 10.37s150,
StartWatch, VirtualVP, VPLive, Win10 Pro
--- Logitech HD Pro C920 webcam (off-line)
--- RIPE Atlas Probe - 32849

Offline saratogaWX

  • Administrator
  • Forecaster
  • *****
  • Posts: 9257
  • Saratoga, CA, USA Weather - free PHP scripts
    • Saratoga-Weather.org
Re: wx advisories not updating...
« Reply #3 on: March 20, 2018, 09:10:31 PM »
Hi Don, glad it is working again.

We're on the northern fringe of this atmospheric river .. we should get 1 to 2 inches by Friday, but so far.. only 0.16
Our house is at 394ft in a gently rolling area about 0.5 mile from the start of the Santa Cruz Mountains foothills .. here there are no burn scars to assist a mudslide and dense foliage on the hills, so no worries about that right here.

I'm more concerned about SLOweather Chris in San Luis Obispo where he is more in the thick of the AR, and those poor folks in Santa Barbara County where the 'bulls eye' of the AR seems to be pointed -- the massive Thomas fire left a lot of bare hills around there to liquefy and flow.
Ken True/Saratoga, CA, USA main site: saratoga-weather.org
Davis VP1+ FARS, Blitzortung RED, GRLevel3, WD, WL, VWS, Cumulus, Meteobridge
Free weather PHP scripts/website templates - update notifications on Twitter saratogaWXPHP

Offline SLOweather

  • Global Moderator
  • Forecaster
  • *****
  • Posts: 3456
    • Weatherelement Moline IL
Re: wx advisories not updating...
« Reply #4 on: March 20, 2018, 11:43:43 PM »
I'm more concerned about SLOweather Chris in San Luis Obispo where he is more in the thick of the AR, and those poor folks in Santa Barbara County where the 'bulls eye' of the AR seems to be pointed -- the massive Thomas fire left a lot of bare hills around there to liquefy and flow.

Thanks for the concern, Ken, but we should be OK. While the NWS graphical  precip forecast says we could get ~4.5" over the next few days, the ground here is still not saturated to the point of runoff, and we actually need runoff to recharge our water company wells. This is the time of year that the levels should be at their highest, yet they are still declining.

You are correct, however, about Santa Barbara, Montecito, and the Ventura burn areas. This is again aimed right at them.  Anyone interested can go to KEYT.com and watch the news from SB.



Meanwhile, we'll keep the home fires burning...




Offline W3DRM

  • Forecaster
  • *****
  • Posts: 3360
    • Emmett Weather
Re: wx advisories not updating...
« Reply #5 on: March 25, 2018, 08:59:32 PM »
Ken - I noticed the alerts listed were stale again this morning. I opened the cron job and discovered that it was set to run for 1-day and then stop. I haven't touched those settings for a very long time. I've now set the cron job to run indefinitely to see if that fixes the problem. Just before I started noticing the stale alerts, Windows 10 did an update. I'm wondering if the update modified the cron settings.

Is there any way to set up something that monitors for the cron job running periodically and then sending a message or something if it fails to run as scheduled? Even a status in the wxstatus.php page would be better than nothing. I just don't know how to do it.
« Last Edit: March 25, 2018, 09:02:10 PM by W3DRM »
Don - W3DRM - Emmett, Idaho --- Blitzortung ID: 808 --- FlightRadar24 ID: F-KBOI7
Davis Wireless VP2, WD 10.37s150,
StartWatch, VirtualVP, VPLive, Win10 Pro
--- Logitech HD Pro C920 webcam (off-line)
--- RIPE Atlas Probe - 32849

Offline saratogaWX

  • Administrator
  • Forecaster
  • *****
  • Posts: 9257
  • Saratoga, CA, USA Weather - free PHP scripts
    • Saratoga-Weather.org
Re: wx advisories not updating...
« Reply #6 on: March 26, 2018, 02:42:13 PM »
I got a note from Mike Gerber at NOAA this morning
Quote
CAP users,

There was a system failure at one of our data center locations which resulted in CAP messages not being generated between 0715 UTC and 1223 UTC. The products from which they are derived have been lost, so no retransmission is possible, unlike in a normal failover scenario.

We're sorry for the inconvenience. 

Mike
.. don't know if that was causing an impact for you, Don.

You can add a status in wxstatus.php by adding
Code: [Select]
############################################################################
# start of custom checks (put your custom checks below)

        $tDir = './cache/';
if(file_exists($tDir.'nws-alertsMainData.php')) {
           do_check(langtransstr("NWS Alerts"),$tDir.'nws-alertsMainData.php',10*60+15,'file');

        }


# end of custom checks
############################################################################
Ken True/Saratoga, CA, USA main site: saratoga-weather.org
Davis VP1+ FARS, Blitzortung RED, GRLevel3, WD, WL, VWS, Cumulus, Meteobridge
Free weather PHP scripts/website templates - update notifications on Twitter saratogaWXPHP

Offline W3DRM

  • Forecaster
  • *****
  • Posts: 3360
    • Emmett Weather
Re: wx advisories not updating...
« Reply #7 on: March 27, 2018, 10:46:57 AM »
Thanks Ken. I installed the code and sure enough, the cron job isn't updating again. It seems to run for a short while and then stop. Will have to dig into what is going on.
Don - W3DRM - Emmett, Idaho --- Blitzortung ID: 808 --- FlightRadar24 ID: F-KBOI7
Davis Wireless VP2, WD 10.37s150,
StartWatch, VirtualVP, VPLive, Win10 Pro
--- Logitech HD Pro C920 webcam (off-line)
--- RIPE Atlas Probe - 32849

Offline W3DRM

  • Forecaster
  • *****
  • Posts: 3360
    • Emmett Weather
Re: wx advisories not updating...
« Reply #8 on: March 27, 2018, 08:10:26 PM »
I gave up trying to run Task Scheduler on my wx laptop. I just couldn't get it to run consistently. So, I dug out some old notes on PuTTY and CRONTAB I had about running CRON jobs on the server and BINGO!, once it was set up, it appears to be updating the nws-alertsMainData.php file every 10-minutes. So far, no hiccups. Will monitor it to see what happens overnight. I disabled the Task Scheduler job so it doesn't interfere.
Don - W3DRM - Emmett, Idaho --- Blitzortung ID: 808 --- FlightRadar24 ID: F-KBOI7
Davis Wireless VP2, WD 10.37s150,
StartWatch, VirtualVP, VPLive, Win10 Pro
--- Logitech HD Pro C920 webcam (off-line)
--- RIPE Atlas Probe - 32849