Tom, I think the 502 is from station registry. Nothing is displaying on the map and GET stations is returning a 502 rich
On Sunday, 21 May 2023 at 11:59:08 UTC-4 Tom Keffer wrote: > I don't know anything about the windguru uploader. You can try asking the > author. > > I will say that "Bad Gateway" usually means a problem with a load > balancing server, or something like that. It could be a problem on the > windguru end. > > There's also a pending "pull request > <https://github.com/claudobahn/weewx-windguru/pull/4>" that updates how > authentication is done. Perhaps that's the problem? Don't know. You can > give it a try. > > -tk > > On Sun, May 21, 2023 at 8:47 AM [email protected] <[email protected]> > wrote: > >> Thank you for the replies and suggestions. The logging is now working to >> /var/log/weewx.log >> >> When I run weewx directly I can see the sensor data coming in. It seems >> like it's just the final step when it uploads the data to windguru that it >> is failing. I have confirmed that the station details are correct. When I >> ping windguru.cz, there is a reply. Any ideas? >> >> 2023-05-21 19:35:41 weewx[3859] DEBUG weewx.reportengine: Report 'RSYNC' >> not enabled. Skipping. >> 2023-05-21 19:35:44 weewx[3859] DEBUG weewx.restx: WindGuru: Failed >> upload attempt 2: Server response: b'ERROR (no data)' >> 2023-05-21 19:35:45 weewx[3859] DEBUG weewx.restx: StationRegistry: >> Failed upload attempt 2: HTTP Error 502: Bad Gateway >> 2023-05-21 19:35:50 weewx[3859] DEBUG weewx.restx: WindGuru: Failed >> upload attempt 3: Server response: b'ERROR (no data)' >> 2023-05-21 19:35:50 weewx[3859] ERROR weewx.restx: WindGuru: Failed to >> publish record 2023-05-21 19:35:00 +04 (1684683300): Failed upload after 3 >> tries >> 2023-05-21 19:35:51 weewx[3859] DEBUG weewx.restx: StationRegistry: >> Failed upload attempt 3: HTTP Error 502: Bad Gateway >> 2023-05-21 19:35:51 weewx[3859] ERROR weewx.restx: StationRegistry: >> Failed to publish record 2023-05-21 19:35:00 +04 (1684683300): Failed >> upload after 3 tries >> >> >> >> On Sunday, May 21, 2023 at 3:43:15 PM UTC+4 Tom Keffer wrote: >> >>> I have never been able to get system logging from Python to work on the >>> Mac. I'm sure it can be done --- I just don't know how. If you Google >>> around, apparently others have struggled to get it to work as well. >>> >>> Instead, I just log to a rotating file. See the section *Logging to >>> rotating files >>> <https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging#logging-to-rotating-files>* >>> in >>> the Wiki. The example logs to /var/log/weewx.log, which will require >>> root privileges. Another option is to log to >>> /Users/Shared/weewx/weewx.log, or some other place where you don't need >>> those privileges. >>> >>> >>> >>> On Sun, May 21, 2023 at 2:47 AM Graham Eddy <[email protected]> wrote: >>> >>>> tom did not say that 4.10.2 removed [Logging], he did ask you to remove >>>> that section temporarily, to get it to use default, in case your own >>>> content of that section was wrong. tom said that you were using a specific >>>> item (i think it was ‘rotate’) that was removed in 4.10.2 and thus causing >>>> your runtime error >>>> >>>> i think in macOS the default behaviour is to log under >>>> /var/log/system.log >>>> >>>> once the default configuration is working, no doubt you will add some >>>> entries to [Logging] to use a file of your choice, such as >>>> /var/log/weewx.log >>>> *⊣GE⊢* >>>> >>>> On 21 May 2023, at 7:33 pm, [email protected] <[email protected]> >>>> wrote: >>>> >>>> However, I am still having some problem and I'm struggling to identify >>>> exactly what because I'm not sure how to check the logs on MacOS. I'm >>>> sorry >>>> for the noob question, but can someone please guide me on where weewx is >>>> logging to? I can confirm that it is not /var/log/weewx.log or >>>> /var/tmp/weewx.log. Originally I had added a [Logging] section in >>>> weewx.conf but now the weewx 4.10.2 has removed that functionality I am >>>> not >>>> sure how else to log weewx output to a different file. >>>> >>>> >>>> -- >>>> 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 [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/weewx-user/ADD2976B-D69E-4BD4-A23F-FA1D439063DC%40geddy.au >>>> >>>> <https://groups.google.com/d/msgid/weewx-user/ADD2976B-D69E-4BD4-A23F-FA1D439063DC%40geddy.au?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> 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 [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/c18a02bc-6371-49a8-ad07-42e794b524e9n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/c18a02bc-6371-49a8-ad07-42e794b524e9n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e6b2b60e-e273-4834-b63d-c3685146aadfn%40googlegroups.com.
