Hi Andrew and Gary, thank you so much for taking the time to try to help me further - and between you, you've cracked the problem !
I ran the .tables command in sqlite3 and found lots of archive_day_xxxxx tables in my database, which were still present after I executed the drop-daily command. However, when I prefixed that command with sudo as suggested, those tables disappeared. Then I ran the rebuild-daily command, also pre-fixing it with sudo - and now for the first time I see messages about numbers of records processed etc and that command takes a number of seconds to complete, rather than just ending instantly. I then deleted all the png, html and NOAA files and re-started weewx......and lo and behold all my reports are now correct with no rogue data, yippee !! Perhaps Tom K needs to update his wiki guide on how to do all this as I'm guessing I'm not the only person who has these permission problems preventing drop-daily and rebuild-daily from working ? And yes, it does seem odd that those weewx_database commands do not produce an error of any kind when they fail due to lack of permission. Anyway, its working for me now---- thank you so much Andrew and Gary for your fantastic help, you guys rock ! Regards, Paul On Thursday, August 2, 2018 at 6:14:48 AM UTC+1, Andrew Milner wrote: > > wow. Well if you're right then it's a bug in wee_database for not > reporting an error of some kind. > > On Thursday, 2 August 2018 07:02:08 UTC+3, gjr80 wrote: >> >> I would have thought so bu I just tried it on a VM and it didn't throw an >> error, it looked for all intents and purposes as if --drop-daily worked but >> when I checked with sqlite3 the tables remained. Have not had a chance to >> dig any deeper. >> >> 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]. For more options, visit https://groups.google.com/d/optout.
