Closed rkaiser0324 closed 1 year ago
Yes, NOAA is having trouble with one of its image servers - it started on Nov 17th. I've been in touch with a sys admin who says that they're working on it.
On Mon, 28 Nov 2022 at 08:34, Rolf Kaiser @.***> wrote:
Running fetch.sh you get this after a short while:
[image: image] https://user-images.githubusercontent.com/1090569/204331240-ca08e2d7-6c53-426c-b25e-e99c862e308a.png
— Reply to this email directly, view it on GitHub https://github.com/lanceberc/ycwx/issues/2, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA33HMZFLFP6VLXFYDMH3GTWKTNJTANCNFSM6AAAAAASNQ5DSA . You are receiving this because you are subscribed to this thread.Message ID: @.***>
NOAA rebooted one of their servers around the 23rd/24th which has improved availability quite a bit but there are still occasional issues. The fetch code retries some errors (like open and read timeouts) but assumes that others like gateway issues are fatal. Those files will be retried the next time the script runs so files bypassed on one run will eventually be fetched if they actually exist (sometimes they don't).
I haven't seen any fetch issues on either the yc or dev machines for several days since NOAA rebooted the image server and may have made other network changes. Either way, I don't think the problem is on this end.
Running
fetch.sh
I got this after a short while:I also see intermittent timeouts, maybe this is to be expected: