I didn't remove any lines, only credentials etc. and yes, that's the version I had a problem with (am on Python v3.8.5). I'm happy to know that the problem is not the database. To be clear, this was the sequence
1. Fresh install of WeeWX 4.x on new Pi (upgraded later) 2. Old skin and conf files copied to new Pi; simulator configured initially in place of WH1080 driver; uploads to Internet services commented out 3. GW1000 driver installed on new Pi, skin changes made 4. weewx.conf copied in preparation for cutover; uploads reinstated by removing commenting 5. Old WeeWX (also 4.4) stopped and database copied and swapped in 6. New weewx.conf with uncommented uploads swapped in and weewx restarted When it failed I compared the old and new weewx.conf files using Beyond Compare, which highlights changes. I started commenting things out again to see if I could figure out what was wrong before eventually reverting to prior db and conf file. File edits were made using Atom via an exported NFS share, which I haven't had any issues with doing before. What I was aiming to do was keep both systems running but swap the uploads task from one to another. My concern to minimize the outage time -- and perhaps doing it at midnight -- may have led to some mistake. I wouldn't have posted at all if I knew for sure it wasn't potentially db related. Many thanks for checking the file. I'll repeat the process and try again after I've merged the records I want. On Thursday, March 18, 2021 at 12:02:18 AM UTC tke...@gmail.com wrote: > The version you posted parsed just fine, at least on my Python 3.9 > implementation. Your log says weewxd was reading /etc/weewx/weewx.conf. Is > that the version you posted? If so, the offending line either got commented > out, or was removed. > > It's in there somewhere! > > -tk > > On Wed, Mar 17, 2021 at 4:19 PM PJO <pon...@gmail.com> wrote: > >> This (attached) is the file with passwords, ids and coordinates removed. >> >> Here's what I did: >> >> I stopped weewx on both RPis; copied the database to the new one, having >> backed up the database there, and then swapped in a copy of my weewx.conf >> with the uploads to wunderground etc. enabled. When that didn't work I went >> through and disabled all those. I did check both the weewx.conf files >> carefully using a split screen file comparison utility and didn't see >> anything wrong. I then went through and disabled the uploads, as shown >> here. I reverted to the original database and previous weewx.conf--and >> weewx ran again, so I assumed the problem was something in the >> database/configuration. >> >> If you can see anything wrong at line 153 I'll be interested to know what >> it is! And many thanks, of course, for looking. >> >> On Wednesday, March 17, 2021 at 8:37:37 PM UTC tke...@gmail.com wrote: >> >>> You likely have a typo in weewx.conf but without seeing yours it's >>>> impossible to know where. >>>> >>> >>> In this case, we do know where: line 153 in weewx.conf. >>> >> -- >> > 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/451deb4d-665a-40fc-ad2b-f1a801bdc7e7n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/451deb4d-665a-40fc-ad2b-f1a801bdc7e7n%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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/f5a1b6ee-9bea-4172-8f76-1090a245227dn%40googlegroups.com.
