The odd miss with the WOW upload

[WindnFog]

I've been getting the occasional fail on uploads to the Met Office for the past week or so.  Any idea if there is some tweaking I could do with weewx, or does this appear to be Internet latency or their site occasionally being unresponsive?  It mostly works, so I don't think this is very important.

- Paul VE1DX

root@rhubarb:~# journalctl -f -n 1600 | grep WOW

Sep 20 08:35:16 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 08:35:00 ADT (1568979300)
Sep 20 08:50:18 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 08:50:00 ADT (1568980200)
Sep 20 09:05:25 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 09:05:00 ADT (1568981100)
Sep 20 09:20:16 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 09:20:00 ADT (1568982000)
Sep 20 09:35:16 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 09:35:00 ADT (1568982900)
Sep 20 09:50:42 rhubarb weewx[587]: restx: WOW: Failed to publish record 2019-09-20 09:50:00 ADT (1568983800): Failed upload after 3 tries
Sep 20 10:05:22 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 10:05:00 ADT (1568984700)
Sep 20 10:20:16 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 10:20:00 ADT (1568985600)
Sep 20 10:35:16 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 10:35:00 ADT (1568986500)
Sep 20 10:50:16 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 10:50:00 ADT (1568987400)
Sep 20 11:05:31 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 11:05:00 ADT (1568988300)
Sep 20 11:20:34 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 11:20:00 ADT (1568989200)
Sep 20 11:35:23 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 11:35:00 ADT (1568990100)
Sep 20 11:50:23 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 11:50:00 ADT (1568991000)
Sep 20 12:05:17 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 12:05:00 ADT (1568991900)
Sep 20 12:20:18 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 12:20:00 ADT (1568992800)
Sep 20 12:35:16 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 12:35:00 ADT (1568993700)
Sep 20 12:50:17 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 12:50:00 ADT (1568994600)
Sep 20 13:05:17 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 13:05:00 ADT (1568995500)
Sep 20 13:20:51 rhubarb weewx[587]: restx: WOW: Failed to publish record 2019-09-20 13:20:00 ADT (1568996400): Failed upload after 3 tries
Sep 20 13:35:16 rhubarb weewx[587]: restx: WOW: Published record 2019-09-20 13:35:00 ADT (1568997300)

[Thomas Keffer]

If you run debug=1, the log should show you the reason for the failed uploads.

-tk

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4ed8afbb-de7d-49bb-b494-10cbf40660ae%40googlegroups.com.

[WindnFog]

Thanks, Tom,

The reason is:

Sep 20 14:25:26 rhubarb weewx[6635]: restx: WOW: Failed upload attempt 1: timed out
Sep 20 14:25:31 rhubarb weewx[6635]: restx: WOW: Failed upload attempt 2: HTTP Error 429: Too frequent observations.
Sep 20 14:25:37 rhubarb weewx[6635]: restx: WOW: Failed upload attempt 3: HTTP Error 429: Too frequent observations.
Sep 20 14:25:42 rhubarb weewx[6635]: restx: WOW: Failed to publish record 2019-09-20 14:25:00 ADT (1569000300): Failed upload after 3 tries

Their site: https://wow.metoffice.gov.uk/support/dataformats says:

Frequency of submitting observations

It is recommended that the interval between automatic observations from your AWS is at least 5 minutes.

My log shows that weewx uploads every 15 minutes, which is 3 times less frequent than 5 minutes and should be OK.  There's no "setting" in the weewx.conf file to make it even less frequent, and I don't think that's the way to go.  I'm inclined to leave it alone or contact them as it appears they can't (or don't want to) handle even 15-minute updates.  I don't know when this changed.  It's only complaining once every few hours, and it might have been doing so for quite a while.  Unless you feel otherwise, I'll wait a week or so and then contact them.  There doesn't seem to be anything we can do on the weewx end.  I wonder if anyone else is getting this.

- Paul VE1DX

To unsubscribe from this group and stop receiving emails from it, send an email to weewx...@googlegroups.com.

[Thomas Keffer]

I've noticed "Failed upload after 3  tries" errors every once in a while with my WOW uploader. I've set debug=1 on my own station to find out why.

-tk

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/b5c934b1-11cf-45cc-951e-45246e4036d7%40googlegroups.com.

[gjr80]

Almost sounds like that despite the first upload appearing to time out it actually takes and the second and subsequent uploads are deemed too frequent based upon the first attempted upload.

Perhaps a few laid off WU employees have moved across the Atlantic? :)

Gary

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/b5c934b1-11cf-45cc-951e-45246e4036d7%40googlegroups.com.

[Thomas Keffer]

My WOW errors are following the same pattern: a time-out, followed by 429 errors.

 

I think Gary's analysis is correct. The first post is going through, so the subsequent ones get 429 errors.

NB: The text "Too many requests; data already seen; or too out of date." is from WeeWX, not WOW. The text is what gets put in the log when a 429 error occurs.

So, nothing to worry about, or, at least, there's nothing we can do about it.

-tk

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/590fbbdb-e83a-4f8b-873e-ae52e92252b2%40googlegroups.com.