Your VP2 has an archive interval of one hour, so it will take that long to
generate an archive record, and kick off a reporting cycle.

If you want something more often, change the interval to, say, 5 minutes.
See the section *Archive interval
<http://weewx.com/docs/usersguide.htm#archive_interval>* in the User's
Guide.

-tk

On Tue, Jul 30, 2019 at 7:50 PM Richard Rosa <richardro...@gmail.com> wrote:

> The main program IS running. How do I tell it to generate reports? When
> the program started, no reports were generated until the 'wee_reports'
> command was issued.
>
>
>
> System Log (journalctl):
>
>
> Jul 30 19:39:54 rubberducky.rbm systemd[1]: Started weewx weather system.
> Jul 30 19:39:54 rubberducky.rbm weewx[11021]: engine: Initializing weewx
> version 3.9.2
> Jul 30 19:39:54 rubberducky.rbm weewx[11021]: engine: Using Python 2.7.14
> (default, Oct 12 2017, 15:50:02) [GCC]
> Jul 30 19:39:54 rubberducky.rbm weewx[11021]: engine: Platform
> Linux-4.12.14-lp151.28.10-default-x86_64-with-glibc2.2.5
> Jul 30 19:39:54 rubberducky.rbm weewx[11021]: engine: Locale is
> 'en_US.UTF-8'
> Jul 30 19:39:54 rubberducky.rbm weewx[11021]: engine: pid file is
> /var/run/weewx.pid
> Jul 30 19:39:54 rubberducky.rbm systemd[1]: weewx.service: Supervising
> process 11033 which is not our child. We'll most likely not notice when it
> exits.
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Using configuration
> file /etc/weewx/weewx.conf
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Debug is 1
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Initializing engine
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading station type
> Vantage (weewx.drivers.vantage)
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: vantage: Driver version is
> 3.1.1
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: vantage: Opened up serial
> port /dev/vpro; baud 19200; timeout 4.00
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: vantage: Gentle wake up of
> console successful
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: vantage: Hardware type is 16
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: vantage: ISS ID is 1
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: vantage: Hardware name:
> Vantage Pro2
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.engine.StdTimeSynch
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.engine.StdTimeSynch
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.engine.StdConvert
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: StdConvert target
> unit is 0x1
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.engine.StdConvert
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.engine.StdCalibrate
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.engine.StdCalibrate
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.engine.StdQC
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.engine.StdQC
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.wxservices.StdWXCalculate
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: wxcalculate: The following
> values will be calculated: barometer=prefer_hardware,
> windchill=prefer_hardware, dewpoint=prefer_hardware,
> appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=prefer_hardware,
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware,
> humidex=prefer_hardware, pressure=prefer_hardware,
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware,
> cloudbase=prefer_hardware
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: wxcalculate: The following
> algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.wxservices.StdWXCalculate
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.engine.StdArchive
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Archive will use
> data binding wx_binding
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Record generation
> will be attempted in 'hardware'
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Using archive
> interval of 1800 seconds (specified by hardware)
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Use LOOP data in
> hi/low calculations: 1
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: manager: Daily summary
> version is 2.0
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Using binding
> 'wx_binding' to database 'weewx.sdb'
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: manager: Starting backfill
> of daily summaries
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.engine.StdArchive
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.restx.StdStationRegistry
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: restx: StationRegistry:
> Registration not requested.
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.restx.StdStationRegistry
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.restx.StdWunderground
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: restx: Wunderground: Posting
> not enabled.
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.restx.StdWunderground
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.restx.StdPWSweather
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: restx: PWSweather: Posting
> not enabled.
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.restx.StdPWSweather
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.restx.StdCWOP
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: restx: CWOP: Posting not
> enabled.
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.restx.StdCWOP
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.restx.StdWOW
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: restx: WOW: Posting not
> enabled.
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.restx.StdWOW
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.restx.StdAWEKAS
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: restx: AWEKAS: Posting not
> enabled.
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.restx.StdAWEKAS
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.engine.StdPrint
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.engine.StdPrint
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Loading service
> weewx.engine.StdReport
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Finished loading
> service weewx.engine.StdReport
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Starting up weewx
> version 3.9.2
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: vantage: Gentle wake up of
> console successful
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Clock error is -0.86
> seconds (positive is fast)
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: vantage: Getting archive
> packets since 2019-07-30 19:30:00 EDT (1564529400)
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: vantage: Gentle wake up of
> console successful
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: vantage: Retrieving 0
> page(s); starting index= 0
> Jul 30 19:39:54 rubberducky.rbm weewx[11033]: engine: Starting main packet
> loop.
> Jul 30 19:39:58 rubberducky.rbm weewx[11033]: vantage: Retry  #0 failed
> Jul 30 19:39:58 rubberducky.rbm weewx[11033]: vantage: Gentle wake up of
> console successful
> Jul 30 19:39:58 rubberducky.rbm weewx[11033]: vantage: Requesting 200 LOOP
> packets.
> Jul 30 19:39:58 rubberducky.rbm weewx[11033]: vantage: Gentle wake up of
> console successful
>
>
>
> On Tuesday, July 30, 2019 at 7:03:13 PM UTC-4, Thomas Keffer wrote:
>>
>> wee_reports is for generating reports only. It is a standalone program,
>> mostly used for testing purposes.
>>
>> You want weewxd: the main weewx program.
>>
>> Take a look in the section *Running weewx
>> <http://weewx.com/docs/usersguide.htm#running>* in the manual. If you
>> still have questions, come on back, but be sure to include the system log
>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user>.
>>
>> -tk
>>
>> On Tue, Jul 30, 2019 at 5:53 PM Richard Rosa <richar...@gmail.com> wrote:
>>
>>>
>>> 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 weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/efb3984a-2be2-412d-8273-489a2c1bc4ef%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/efb3984a-2be2-412d-8273-489a2c1bc4ef%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/7bc2a16d-ecbe-4749-91a8-7d7376f615bd%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/7bc2a16d-ecbe-4749-91a8-7d7376f615bd%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/CAPq0zEC3n6K96PYXL7eHn9%2BvjoqYEpo6Vcu1X9VGRk-cU-suKA%40mail.gmail.com.

Reply via email to