Hey,

Yesterday my NOAA script stopped working. I've been using KGPI, Glacier Park Int. Airport
which up until yesterday was working fine. No other changes in that time.
The event log shows it timing out. Is there something else I can check on to trouble shoot
this?

Thanks,

Carl

ckeyes888 wrote:Hey,

Yesterday my NOAA script stopped working. I've been using KGPI, Glacier Park Int. Airport
which up until yesterday was working fine. No other changes in that time.
The event log shows it timing out. Is there something else I can check on to trouble shoot
this?

Thanks,

Carl

Same here ...

Weather NOAA GetXMLfile:URL Access Scripting got an error: AppleEvent timed out.(-1712)

The site for KGPI seems to be up and running: http://www.weather.gov/xml/current_obs/KGPI.xml

Carl

Something on the NOAA site has changed - I just noticed that I stopped getting "Weather_Condition" in my feed. However, I'm still getting the rest of the data, so perhaps they're just having sporadic outages or network issues.

I saw a press item that the NOAA servers had been swamped due to the widespread storms the last couple of days; they were upgrading equipment to deal with it. Might or might not be coincidental.

BitStream wrote:Same here ...

Weather NOAA GetXMLfile:URL Access Scripting got an error: AppleEvent timed out.(-1712)

I was getting that error. I updated the script (per another post in this topic) to use the shell script instead of URL access.

Code: Select all

do shell script "/usr/bin/curl -s -S -m " & webQueryTimeout & " http://www.nws.noaa.gov/xml/current_obs/" & stationID & ".xml >" & myFile
      (*tell application "URL Access Scripting"
         download "http://www.nws.noaa.gov/xml/current_obs/" & stationID & ".xml" to file myFile replacing yes
         
         -- work around -31040 error:
         tell application "URL Access Scripting" to quit
      end tell*)

I tried the ‘curl’ approach to accessing NOAA data:

do shell script "/usr/bin/curl -s -S -m " & webQueryTimeout & " http://www.nws.noaa.gov/xml/current_obs/" & stationID & ".xml >" & myFile’’

but am now receiving the following error:

--> error "curl: (6) Couldn't resolve host 'HD:private:var:folders:FM:FM9kxceaFeGIS-VfYVnbvU+++TI:TemporaryItems:noaa_sync_temp.xml'" number 6

Not quite sure what this means...

wmcorbin wrote:I tried...
do shell script "/usr/bin/curl -s -S -m " & webQueryTimeout & " http://www.nws.noaa.gov/xml/current_obs/" & stationID & ".xml >" & myFile’’

Try this:

Code: Select all

do shell script "/usr/bin/curl -s -S -m " & webQueryTimeout & " http://www.nws.noaa.gov/xml/current_obs/" & stationID & ".xml >" & myFile

You had 2 single quotes at the end of your line.

For some reason my original script has started working again.

ckeyes888 wrote:For some reason my original script has started working again.

This might explain your script's return to life:

BillC previously wrote:I saw a press item that the NOAA servers had been swamped due to the widespread storms the last couple of days; they were upgrading equipment to deal with it...

ckeyes888 wrote:For some reason my original script has started working again.

Thus my "perhaps they're just having sporadic outages or network issues" post from above...

A bit off-topic but has anyone found or know of a site that simply shows the season snowfall
total for a zip code? Tons of useless links are all I've been able to come up with.
Would just like to parse out that info for a variable.

Thanks,

Carl

The first issue I had with the NOAA and TED scripts running in the background seem to be fixed. I am now having a problem where both of these scripts randomly quitting. They seem to run for about 1-2 days before they stop and without any apparent errors.

When I noticed when they have stopped running, I can manually start the trigger actions and they start running again without any errors.

Yep, that's a problem. Background scripts are run using /usr/bin/osascript - that's the system's built-in command line tool to execute an AppleScript. Periodically I'll have background scripts that quit for no apparent reason. The return code doesn't indicate an error, it just appears that the script quit. Of course, these scripts should never quit, so something else is going on. But because we have nothing returned by osascript there's nothing we can do to try to figure it out.

I have a time/date action that runs every couple of minutes and checks to see if those scripts are running and if not it restarts them. We're looking at adding that kind of functionality into Indigo 5.0 (the ability for a background script to be restarted if it quits).

How does your time date action work to check on those background scripts?