Yes -- I had debug=1 -- did not see any sign of trouble either in /var/log/messages or to the terminal running weewxd in the foreground (vs. daemon mode as a service).
m. On Thursday, August 16, 2018 at 10:54:15 AM UTC-4, Thomas Keffer wrote: > > It does seem odd. Did you have debug=1? That should have logged all > failures. > > Otherwise, only the final failure gets logged. > > -tk > > On Thu, Aug 16, 2018 at 7:46 AM Michael Gray <[email protected] > <javascript:>> wrote: > >> I have found/fixed my problem! As I suspected, it was nothing to do >> with weewx per se... Somehow, my DNS config (resolv.conf etc.) was changed >> so my Pi was not resolving hostnames. This caused weewx rest code not >> to resolve urls needed for posting to public servers: >> >> ./weewx/restx.py: rf_url = " >> http://rtupdate.wunderground.com/weatherstation/updateweatherstation.php"; >> ./weewx/restx.py: pws_url = " >> http://weatherstation.wunderground.com/weatherstation/updateweatherstation.php >> " >> ./weewx/restx.py: default_servers = ['cwop.aprs.net:14580', ' >> cwop.aprs.net:23'] >> >> Once I got name resolution back on the rails, weewx publishing started >> working. >> >> I'm a little surprised that with all the error checking in the code, >> weewx was silent on the issue of not being able to resolve the hostnames in >> the URLs >> upon which it depends -- nothing about GET failing or anything... >> >> It looks like the except's on the try's to connect to the servers could >> use some more generic error catching -- I might give it a go but my python >> foo is not strong... >> >> Would a bug report be in order here? I know this wasn't weewx fault per >> se, but had there been an error like "unknown host", I would have probably >> found the >> name resolution problem quickly... >> >> Thanks to all who looked at my post and sent along their thoughts -- >> great community here! >> >> >> On Thursday, August 16, 2018 at 10:02:34 AM UTC-4, Michael Gray wrote: >>> >>> It's always said that -- I never explicitly requested "hardware >>> generation" -- I'll try adding record_generation = software explicitly >>> >>> last restart before "upgrade" when all was well: Aug 14 15:17:11 >>> raspberrypi weewx[654]: engine: Record generation will be attempted in >>> 'hardware' >>> post-upgrade: Aug >>> 15 22:01:18 raspberrypi weewx[29842]: engine: Record generation will be >>> attempted in 'hardware' >>> >>> hardware is the default and comments suggest it will use hardware in >>> devices that support it -- software if not... But I've added the >>> following: >>> >>> # If possible, new archive records are downloaded from the station >>> # hardware. *If the hardware does not support this, then new >>> archive* >>> * # records will be generated in software.* >>> # Set the following to "software" to force software record >>> generation. >>> *# *record_generation = hardware >>> * record_generation = software* >>> >>> Log now reports this: >>> >>> Aug 16 09:56:18 raspberrypi weewx[2791]: engine: *Record generation >>> will be attempted in 'software'* >>> >>> No change in behavior -- still getting data, storing records and >>> generating web pages -- but no publish... >>> >>> I'm wondering if something in all the linux updates (not updated for >>> several months) changed -- python or some library weewx uses... >>> >>> >>> On Thursday, August 16, 2018 at 8:15:00 AM UTC-4, gjr80 wrote: >>>> >>>> Let's try that again. >>>> >>>> Hi, >>>> >>>> Any reason you are using hardware record generation? As far as I am >>>> aware the AcuRite stations only emit loop packets (in fact the AcuRite >>>> driver does not have a genArchiveRecords() method necessary to generate >>>> archive records from the hardware). Suggest you try setting >>>> record_generation = software under [StdArchive] in weewx.conf. Once you >>>> make the change you will need to restart weeWX. >>>> >>>> Gary >>>> >>>> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- 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]. For more options, visit https://groups.google.com/d/optout.
