Other than NOT changing to MYSQL, those were the instructions I followed. Using *sqlitebrowser,* it appears that the records from WVIEW are in this file, but not being a DB expert, I'm not sure if they are in the right place.
I DID set debug on, and follow the log messages (journalctl -f). The *wee_reports* command generates a handful of messages within a few seconds, then 'Gentle wake up of console'. SeasonsReport seems to be the only thing generated. SmartphoneReport, MobileReport, StandardReport, FTP and RSYNC are not generated. Donno if these should be enabled or not (they were disabled by default in the install). No other messages, no status indication. I don't see any other messages in the log that indicate something is running. CPU & Disk usage seem pretty quiet after the last 'wake up' message. Richard Rosa On Tuesday, July 30, 2019 at 5:15:44 PM UTC-4, vince wrote: > > On Tuesday, July 30, 2019 at 2:04:43 PM UTC-7, Richard Rosa wrote: > >> The problem I have is porting 10+ years of WVIEW logs >> > Following the manual's instructions, I copied archive databases from >> wview/archive -> weewx.sdb >> > > you'd have to point us at which instructions you followed perhaps - > hopefully it was http://weewx.com/docs/usersguide.htm#wview_compatibility > > There appear to be two different WVIEW archive files: *wview-hilow.sdb* >> and *wview-history.sdb*. >> After copying either file, and restarting the service, WEEWX grabbed >> recent data from my Vantage Pro. >> > > yes it will always try to catch up to what's in your VP2 datalogger.... > > I'm pretty sure it's "not" the hilow database, but the wview docs say the > archive is in wview-archive.sdb typically ( > http://www.wviewweather.com/release-notes/wview-User-Manual.html#Advanced-sqlite > ) > > >> After running* wee_reports*, I had HTML files for the past few weeks of >> data, but nothing else. >> No reports for prior months or years. >> > > You want to check your syslog - 10 years of data is a lot, it might take a > long time for weewx to build the summary tables and NOAA files (once) on > your initial bootup. It's possible you have some confusing data in there > perhaps. > > Definitely set debug=1 in weewx.conf to get more verbose logging and watch > your syslogs for info letting you know it looks ok (or not). > > -- 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/efb3984a-2be2-412d-8273-489a2c1bc4ef%40googlegroups.com.
