Weewx stopped updating /var/www/html/weewx/index.html

Troy Lass

unread,

Feb 5, 2020, 9:37:29 PM2/5/20

to weewx-user

Ok, I've been fighting this for a quite a while now.... I did have this working fine then 1 day is just stopped updating the data. It writes new index.html files but it's from over a month ago when I rebooted and I've had this issue for months. I've tried setting mobile=true and it's the same, last update 1/16/20.

I've turned debug on and don't see anything that stands out.

I did update to the latest version ( 3.9.2 ) a couple months back hoping that would help and it didn't. I did see something that didn't look right in the weewx.conf, the WEEWX_ROOT was = /. I tried changing to /var/lib/weewx as that's where I think the data should be but that made no difference. I'm attaching the conf file and the output from the messages file from a weewx restart is below.

Any guidance would be very welcome. I was a wview using and gave up on that a couple years back and have had good luck with weewx until this issue. I really like this tool and have come to rely on it.

URL=http://www.deadduck.net/weather

root@deadduck:/etc# lsb_release -a

No LSB modules are available.

Distributor ID: Ubuntu

Description: Ubuntu 18.04.3 LTS

Release: 18.04

Codename: bionic

root@deadduck:/etc#

I have a DavisPro weather station and have a Weather envoy connected to the server via USB. I have multiple other Davis consoles in the house and they're all working properly.

What else can I tell you??

Thanks,

Troy

weewx.conf

weewx.syslog

gjr80

unread,

Feb 5, 2020, 10:43:47 PM2/5/20

to weewx-user

Hi,

Looks like a classic case of corrupted station memory, can easily happen if you have a power outage. Have a read of the section Corrupt station memory in the User's Guide. There are a couple of suggested ways ahead in there. If you get to the stage of clearing the memory with wee_device, make sure you follow the link to dump your stations memory first as this will minimise any data loss. Note that you need to stop WeeWX before running wee_device.

Oh, and you should put WEEWX_ROOT back to what it was.

Gary

Troy Lass

unread,

Feb 6, 2020, 6:20:16 PM2/6/20

to weewx-user

Thanks for the help!

Ok, So I tried pulling the cord and batteries and let the Weather Envoy sit for about 5 minutes and that didn't help.

I next tried the wee_device -- clear-memory and got the following...

root@deadduck:/etc/init.d# wee_device --clear-memory

Using configuration file /etc/weewx/weewx.conf

Using Vantage driver version 3.1.1 (weewx.drivers.vantage)

Proceeding will erase all archive records.

Are you sure you wish to proceed (y/n)? y

Erasing all archive records ...

Traceback (most recent call last):

File "/usr/bin/wee_device", line 66, in <module>

main()

File "/usr/bin/wee_device", line 62, in main

device.configure(config_dict)

File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure

self.do_options(options, parser, config_dict, prompt)

File "/usr/share/weewx/weewx/drivers/vantage.py", line 1987, in do_options

self.clear_memory(station, options.noprompt)

File "/usr/share/weewx/weewx/drivers/vantage.py", line 2287, in clear_memory

station.clearLog()

File "/usr/share/weewx/weewx/drivers/vantage.py", line 1109, in clearLog

raise weewx.RetriesExceeded("While clearing log")

weewx.RetriesExceeded: While clearing log

After the wee_ device command I get the following in the syslog, over and over...

Feb 6 16:09:45 deadduck weewx[947]: engine: retrying...

Feb 6 16:09:45 deadduck weewx[947]: engine: Using configuration file /etc/weewx/weewx.conf

Feb 6 16:09:45 deadduck weewx[947]: engine: Debug is 1

Feb 6 16:09:45 deadduck weewx[947]: engine: Initializing engine

Feb 6 16:09:45 deadduck weewx[947]: engine: Loading station type Vantage (weewx.drivers.vantage)

Feb 6 16:09:45 deadduck weewx[947]: vantage: Driver version is 3.1.1

Feb 6 16:09:45 deadduck weewx[947]: vantage: Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00

Feb 6 16:09:46 deadduck weewx[947]: vantage: Gentle wake up of console successful

Feb 6 16:09:46 deadduck weewx[947]: vantage: Hardware type is 16

Feb 6 16:09:46 deadduck weewx[947]: vantage: ISS ID is 1

Feb 6 16:09:46 deadduck weewx[947]: vantage: Hardware name: Vantage Pro2

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.engine.StdTimeSynch

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.engine.StdTimeSynch

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.engine.StdConvert

Feb 6 16:09:46 deadduck weewx[947]: engine: StdConvert target unit is 0x1

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.engine.StdConvert

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.engine.StdCalibrate

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.engine.StdCalibrate

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.engine.StdQC

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.engine.StdQC

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.wxservices.StdWXCalculate

Feb 6 16:09:46 deadduck weewx[947]: 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

Feb 6 16:09:46 deadduck weewx[947]: wxcalculate: The following algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.wxservices.StdWXCalculate

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.engine.StdArchive

Feb 6 16:09:46 deadduck weewx[947]: engine: Archive will use data binding wx_binding

Feb 6 16:09:46 deadduck weewx[947]: engine: Record generation will be attempted in 'hardware'

Feb 6 16:09:46 deadduck weewx[947]: engine: Using archive interval of 600 seconds (specified by hardware)

Feb 6 16:09:46 deadduck weewx[947]: engine: Use LOOP data in hi/low calculations: 1

Feb 6 16:09:46 deadduck weewx[947]: manager: Daily summary version is 2.0

Feb 6 16:09:46 deadduck weewx[947]: engine: Using binding 'wx_binding' to database 'weewx.sdb'

Feb 6 16:09:46 deadduck weewx[947]: manager: Starting backfill of daily summaries

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.engine.StdArchive

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.restx.StdStationRegistry

Feb 6 16:09:46 deadduck weewx[947]: restx: StationRegistry: Station will be registered.

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.restx.StdStationRegistry

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.restx.StdWunderground

Feb 6 16:09:46 deadduck weewx[947]: restx: WU essentials: {}

Feb 6 16:09:46 deadduck weewx[947]: restx: Wunderground-PWS: Data for station KCOBERTH88 will be posted

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.restx.StdWunderground

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.restx.StdPWSweather

Feb 6 16:09:46 deadduck weewx[947]: restx: PWSweather: Posting not enabled.

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.restx.StdPWSweather

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.restx.StdCWOP

Feb 6 16:09:46 deadduck weewx[947]: restx: CWOP: Posting not enabled.

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.restx.StdCWOP

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.restx.StdWOW

Feb 6 16:09:46 deadduck weewx[947]: restx: WOW: Posting not enabled.

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.restx.StdWOW

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.restx.StdAWEKAS

Feb 6 16:09:46 deadduck weewx[947]: restx: AWEKAS: Posting not enabled.

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.restx.StdAWEKAS

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.engine.StdPrint

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.engine.StdPrint

Feb 6 16:09:46 deadduck weewx[947]: engine: Loading service weewx.engine.StdReport

Feb 6 16:09:46 deadduck weewx[947]: engine: Finished loading service weewx.engine.StdReport

Feb 6 16:09:46 deadduck weewx[947]: engine: Starting up weewx version 3.9.2

Feb 6 16:09:46 deadduck weewx[947]: manager: Daily summary version is 2.0

Feb 6 16:09:46 deadduck weewx[947]: vantage: Gentle wake up of console successful

Feb 6 16:09:46 deadduck weewx[947]: engine: Clock error is -0.52 seconds (positive is fast)

Feb 6 16:09:46 deadduck weewx[947]: vantage: Getting archive packets since 2020-01-16 17:20:00 MST (1579220400)

Feb 6 16:09:46 deadduck weewx[947]: vantage: Gentle wake up of console successful

Feb 6 16:09:47 deadduck weewx[947]: vantage: send_data_with_crc16; try #1

Feb 6 16:09:47 deadduck weewx[947]: vantage: Unable to pass CRC16 check while sending data

Feb 6 16:09:47 deadduck weewx[947]: vantage: DMPAFT try #1; error: Unable to pass CRC16 check while sending data to Vantage console

Feb 6 16:09:47 deadduck weewx[947]: vantage: Getting archive packets since 2020-01-16 17:20:00 MST (1579220400)

Feb 6 16:09:47 deadduck weewx[947]: vantage: Gentle wake up of console successful

Feb 6 16:09:48 deadduck weewx[947]: vantage: send_data_with_crc16; try #1

Feb 6 16:09:48 deadduck weewx[947]: vantage: Unable to pass CRC16 check while sending data

Feb 6 16:09:48 deadduck weewx[947]: vantage: DMPAFT try #2; error: Unable to pass CRC16 check while sending data to Vantage console

Feb 6 16:09:48 deadduck weewx[947]: vantage: Getting archive packets since 2020-01-16 17:20:00 MST (1579220400)

Feb 6 16:09:48 deadduck weewx[947]: vantage: Gentle wake up of console successful

Feb 6 16:09:49 deadduck weewx[947]: vantage: send_data_with_crc16; try #1

Feb 6 16:09:49 deadduck weewx[947]: vantage: Unable to pass CRC16 check while sending data

Feb 6 16:09:49 deadduck weewx[947]: vantage: DMPAFT try #3; error: Unable to pass CRC16 check while sending data to Vantage console

Feb 6 16:09:49 deadduck weewx[947]: vantage: Getting archive packets since 2020-01-16 17:20:00 MST (1579220400)

Feb 6 16:09:49 deadduck weewx[947]: vantage: Gentle wake up of console successful

Feb 6 16:09:50 deadduck weewx[947]: vantage: send_data_with_crc16; try #1

Feb 6 16:09:50 deadduck weewx[947]: vantage: Unable to pass CRC16 check while sending data

Feb 6 16:09:50 deadduck weewx[947]: vantage: DMPAFT try #4; error: Unable to pass CRC16 check while sending data to Vantage console

Feb 6 16:09:50 deadduck weewx[947]: vantage: DMPAFT max tries (4) exceeded.

Feb 6 16:09:50 deadduck weewx[947]: engine: Main loop exiting. Shutting engine down.

Feb 6 16:09:50 deadduck weewx[947]: restx: Shut down Wunderground-PWS thread.

Feb 6 16:09:50 deadduck weewx[947]: restx: Shut down StationRegistry thread.

Feb 6 16:09:50 deadduck weewx[947]: engine: Caught WeeWxIOError: Max tries exceeded while getting archive data.

Feb 6 16:09:50 deadduck weewx[947]: **** Waiting 60 seconds then retrying...

Feb 6 16:10:08 deadduck systemd[1]: Stopping LSB: weewx weather system...

Feb 6 16:10:08 deadduck weewx[2606]: * Stopping weewx weather system weewx

Feb 6 16:10:08 deadduck weewx[947]: engine: Received signal TERM (15).

Feb 6 16:10:13 deadduck weewx[2606]: . ...done.

I can get a good response from the envoy when I try...

root@deadduck:/etc/init.d# wee_device --info

Using configuration file /etc/weewx/weewx.conf

Using Vantage driver version 3.1.1 (weewx.drivers.vantage)

Querying...

Davis Vantage EEPROM settings:

CONSOLE TYPE: Vantage Pro2

CONSOLE FIRMWARE:

Date: Dec 30 2008

Version: 1.82

CONSOLE SETTINGS:

Archive interval: 600 (seconds)

Altitude: 6100 (foot)

Wind cup type: large

Rain bucket type: 0.01 inches

Rain year start: 1

Onboard time: 2020-02-06 16:14:51

CONSOLE DISPLAY UNITS:

Barometer: inHg

Temperature: degree_F

Rain: inch

Wind: mile_per_hour

CONSOLE STATION INFO:

Latitude (onboard): +40.3°

Longitude (onboard): -105.2°

Use manual or auto DST? MANUAL

DST setting: OFF

Use GMT offset or zone code? GMT_OFFSET

Time zone code: N/A

GMT offset: -7.0 hours

Temperature logging: LAST

Retransmit channel: ON (255)

TRANSMITTERS:

Channel Receive Repeater Type

1 inactive none (N/A)

2 active none iss

3 inactive none (N/A)

4 inactive none (N/A)

5 inactive none (N/A)

6 inactive none (N/A)

7 inactive none (N/A)

8 inactive none (N/A)

RECEPTION STATS:

Total packets received: 0

Total packets missed: 0

Number of resynchronizations: 0

Longest good stretch: 0

Number of CRC errors: 0

BAROMETER CALIBRATION DATA:

Current barometer reading: 29.703 inHg

Altitude: 6100 feet

Dew point: 255 F

Virtual temperature: 25 F

Humidity correction factor: 3.6

Correction ratio: 1.259

Correction constant: +0.000 inHg

Gain: 0.000

Offset: -36.000

OFFSETS:

Wind direction: +0 deg

Inside Temperature: +0.0 F

Inside Humidity: +0 %

Outside Temperature: +0.0 F

Outside Humidity: +0 %

root@deadduck:/etc/init.d#

I'm really at a loss here... I don't understand the errors from the wee_device --clear-memory command...

File "/usr/bin/wee_device", line 66, in <module>

main()

File "/usr/bin/wee_device", line 62, in main

device.configure(config_dict)

File "/usr/share/weewx/weewx/drivers/__init__.py", line 69, in configure

self.do_options(options, parser, config_dict, prompt)

File "/usr/share/weewx/weewx/drivers/vantage.py", line 1987, in do_options

self.clear_memory(station, options.noprompt)

File "/usr/share/weewx/weewx/drivers/vantage.py", line 2287, in clear_memory

station.clearLog()

File "/usr/share/weewx/weewx/drivers/vantage.py", line 1109, in clearLog

raise weewx.RetriesExceeded("While clearing log")

weewx.RetriesExceeded: While clearing log

What else can I try??

Thanks!

Troy

Thomas Keffer

unread,

Feb 6, 2020, 7:24:12 PM2/6/20

to weewx-user

Did you stop WeeWX before trying to clear the log?

--
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/2f118d47-f996-42ef-adac-c6d04834c44b%40googlegroups.com.

Troy Lass

unread,

Feb 6, 2020, 7:43:27 PM2/6/20

to weewx...@googlegroups.com

Yes, I stopped it prior to running the clear-memory... I was running a tail -f /var/log/syslog and watched it stop...

I'm updating the firmware on the envoy now. I was able to get it to connect to the WeatherLink app on my Windoze machine and downloaded firmware revision 3.8. Maybe reflashing the firmware will help??

-Troy

You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/ic4IK_-eX4Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEAffbA6AMU%2Bvn_Fb09gE%2BnqqG%2BDqvFUcj4z6dWihnjfrg%40mail.gmail.com.

Thomas Keffer

unread,

Feb 6, 2020, 7:58:32 PM2/6/20

to weewx-user

This is a new one to me. Other things to try:

1. Any particular reason why the retransmit bit is on? I'm not familiar with this bit, but I can see it could cause CRC problems if the Envoy is looking for a channel that doesn't exist. And, I'm sure channel 255 does not exist.

2. Is the power supply to the Envoy OK?

3. Try reseating the logger. Just take it out, then put it back in.

If none of this works, you'll have to call Davis.

-tk

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CALBrUnH7rLwofztEkNe%2BB3YUM_LPp4sLezEJrzfOc60nX6HnFQ%40mail.gmail.com.

Troy Lass

unread,

Feb 6, 2020, 8:00:22 PM2/6/20

to weewx...@googlegroups.com

Ok, updating the envoy firmware to 3.8 didn't help....

root@deadduck:/etc/init.d# wee_device --info
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
Querying...
Davis Vantage EEPROM settings:

CONSOLE TYPE: Vantage Pro2

CONSOLE FIRMWARE:

Date: Sep 12 2017
Version: 3.80

CONSOLE SETTINGS:
Archive interval: 60 (seconds)

Altitude: 6100 (foot)
Wind cup type: large
Rain bucket type: 0.01 inches
Rain year start: 1

Onboard time: 2020-02-06 17:54:31

Total packets received: 104

Total packets missed: 0
Number of resynchronizations: 0

Longest good stretch: 104

Number of CRC errors: 0

BAROMETER CALIBRATION DATA:

Current barometer reading: 29.741 inHg
Altitude: 6100 feet
Dew point: 24 F
Virtual temperature: 26 F
Humidity correction factor: 1.3
Correction ratio: 1.258

Correction constant: +0.000 inHg
Gain: 0.000
Offset: -36.000

OFFSETS:
Wind direction: +0 deg
Inside Temperature: +0.0 F
Inside Humidity: +0 %
Outside Temperature: +0.0 F
Outside Humidity: +0 %

I did another clear memory....

root@deadduck:/etc/init.d# wee_device --clear-memory
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
Proceeding will erase all archive records.
Are you sure you wish to proceed (y/n)? y
Erasing all archive records ...

Archive records erased.
root@deadduck:/etc/init.d#

Below is the syslog from when I brought weewx down before the above commands to after when I brought it back up...

Feb 6 17:53:53 deadduck systemd[1]: Stopping LSB: weewx weather system...
Feb 6 17:53:53 deadduck weewx[5056]: * Stopping weewx weather system weewx
Feb 6 17:53:53 deadduck weewx[4851]: engine: Received signal TERM (15).
Feb 6 17:53:53 deadduck weewx[4851]: engine: Main loop exiting. Shutting engine down.
Feb 6 17:53:53 deadduck weewx[4851]: engine: Shutting down StdReport thread
Feb 6 17:53:53 deadduck weewx[4851]: engine: StdReport thread has been terminated
Feb 6 17:53:53 deadduck weewx[4851]: restx: Shut down Wunderground-PWS thread.
Feb 6 17:53:53 deadduck weewx[4851]: restx: Shut down StationRegistry thread.
Feb 6 17:53:53 deadduck weewx[4851]: engine: Terminating weewx version 3.9.2
Feb 6 17:53:53 deadduck weewx[4851]: **** Traceback (most recent call last):
Feb 6 17:53:53 deadduck weewx[4851]: **** File "/usr/share/weewx/weewx/engine.py", line 894, in main
Feb 6 17:53:53 deadduck weewx[4851]: **** engine.run()
Feb 6 17:53:53 deadduck weewx[4851]: **** File "/usr/share/weewx/weewx/engine.py", line 188, in run
Feb 6 17:53:53 deadduck weewx[4851]: **** for packet in self.console.genLoopPackets():
Feb 6 17:53:53 deadduck weewx[4851]: **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 508, in genLoopPackets
Feb 6 17:53:53 deadduck weewx[4851]: **** for _loop_packet in self.genDavisLoopPackets(200):
Feb 6 17:53:53 deadduck weewx[4851]: **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 535, in genDavisLoopPackets
Feb 6 17:53:53 deadduck weewx[4851]: **** _buffer = self.port.read(99)
Feb 6 17:53:53 deadduck weewx[4851]: **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 256, in read
Feb 6 17:53:53 deadduck weewx[4851]: **** _buffer = self.serial_port.read(chars)
Feb 6 17:53:53 deadduck weewx[4851]: **** File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 483, in read
Feb 6 17:53:53 deadduck weewx[4851]: **** ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout.time_left())
Feb 6 17:53:53 deadduck weewx[4851]: **** File "/usr/share/weewx/weewx/engine.py", line 812, in sigTERMhandler
Feb 6 17:53:53 deadduck weewx[4851]: **** raise Terminate
Feb 6 17:53:53 deadduck weewx[4851]: **** Terminate
Feb 6 17:53:58 deadduck weewx[5056]: . ...done.
Feb 6 17:53:58 deadduck systemd[1]: Stopped LSB: weewx weather system.
Feb 6 17:55:40 deadduck update-notifier.desktop[1985]: [2144:2144:0206/175540.258511:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
Feb 6 17:56:23 deadduck wee_device[5141]: vantage: Archive memory cleared.
Feb 6 17:56:30 deadduck kernel: [ 6772.763713] perf: interrupt took too long (3135 > 3131), lowering kernel.perf_event_max_sample_rate to 63750
Feb 6 17:57:52 deadduck systemd[1]: Starting LSB: weewx weather system...
Feb 6 17:57:52 deadduck weewx[5164]: * Starting weewx weather system weewx
Feb 6 17:57:52 deadduck weewx[5175]: engine: Initializing weewx version 3.9.2
Feb 6 17:57:52 deadduck weewx[5175]: engine: Using Python 2.7.17 (default, Nov 7 2019, 10:07:09) #012[GCC 7.4.0]
Feb 6 17:57:52 deadduck weewx[5175]: engine: Platform Linux-4.15.0-76-generic-x86_64-with-Ubuntu-18.04-bionic
Feb 6 17:57:52 deadduck weewx[5175]: engine: Locale is 'en_US.UTF-8'
Feb 6 17:57:52 deadduck weewx[5175]: engine: pid file is /var/run/weewx.pid
Feb 6 17:57:52 deadduck weewx[5179]: engine: Using configuration file /etc/weewx/weewx.conf
Feb 6 17:57:52 deadduck weewx[5179]: engine: Debug is 1
Feb 6 17:57:52 deadduck weewx[5179]: engine: Initializing engine
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading station type Vantage (weewx.drivers.vantage)
Feb 6 17:57:52 deadduck weewx[5164]: ...done.
Feb 6 17:57:52 deadduck systemd[1]: Started LSB: weewx weather system.
Feb 6 17:57:52 deadduck weewx[5179]: vantage: Driver version is 3.1.1
Feb 6 17:57:52 deadduck weewx[5179]: vantage: Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
Feb 6 17:57:52 deadduck weewx[5179]: vantage: Gentle wake up of console successful
Feb 6 17:57:52 deadduck weewx[5179]: vantage: Hardware type is 16
Feb 6 17:57:52 deadduck weewx[5179]: vantage: ISS ID is 1
Feb 6 17:57:52 deadduck weewx[5179]: vantage: Hardware name: Vantage Pro2
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.engine.StdTimeSynch
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.engine.StdTimeSynch
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.engine.StdConvert
Feb 6 17:57:52 deadduck weewx[5179]: engine: StdConvert target unit is 0x1
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.engine.StdConvert
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.engine.StdCalibrate
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.engine.StdCalibrate
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.engine.StdQC
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.engine.StdQC
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.wxservices.StdWXCalculate
Feb 6 17:57:52 deadduck weewx[5179]: 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
Feb 6 17:57:52 deadduck weewx[5179]: wxcalculate: The following algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.wxservices.StdWXCalculate
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.engine.StdArchive
Feb 6 17:57:52 deadduck weewx[5179]: engine: Archive will use data binding wx_binding
Feb 6 17:57:52 deadduck weewx[5179]: engine: Record generation will be attempted in 'hardware'
Feb 6 17:57:52 deadduck weewx[5179]: engine: Using archive interval of 60 seconds (specified by hardware)
Feb 6 17:57:52 deadduck weewx[5179]: engine: Use LOOP data in hi/low calculations: 1
Feb 6 17:57:52 deadduck weewx[5179]: manager: Daily summary version is 2.0
Feb 6 17:57:52 deadduck weewx[5179]: engine: Using binding 'wx_binding' to database 'weewx.sdb'
Feb 6 17:57:52 deadduck weewx[5179]: manager: Starting backfill of daily summaries
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.engine.StdArchive
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.restx.StdStationRegistry
Feb 6 17:57:52 deadduck weewx[5179]: restx: StationRegistry: Station will be registered.
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.restx.StdStationRegistry
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.restx.StdWunderground
Feb 6 17:57:52 deadduck weewx[5179]: restx: WU essentials: {}
Feb 6 17:57:52 deadduck weewx[5179]: restx: Wunderground-PWS: Data for station KCOBERTH88 will be posted
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.restx.StdWunderground
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.restx.StdPWSweather
Feb 6 17:57:52 deadduck weewx[5179]: restx: PWSweather: Posting not enabled.
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.restx.StdPWSweather
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.restx.StdCWOP
Feb 6 17:57:52 deadduck weewx[5179]: restx: CWOP: Posting not enabled.
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.restx.StdCWOP
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.restx.StdWOW
Feb 6 17:57:52 deadduck weewx[5179]: restx: WOW: Posting not enabled.
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.restx.StdWOW
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.restx.StdAWEKAS
Feb 6 17:57:52 deadduck weewx[5179]: restx: AWEKAS: Posting not enabled.
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.restx.StdAWEKAS
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.engine.StdPrint
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.engine.StdPrint
Feb 6 17:57:52 deadduck weewx[5179]: engine: Loading service weewx.engine.StdReport
Feb 6 17:57:52 deadduck weewx[5179]: engine: Finished loading service weewx.engine.StdReport
Feb 6 17:57:52 deadduck weewx[5179]: engine: Starting up weewx version 3.9.2
Feb 6 17:57:52 deadduck weewx[5179]: manager: Daily summary version is 2.0
Feb 6 17:57:52 deadduck weewx[5179]: vantage: Gentle wake up of console successful
Feb 6 17:57:52 deadduck weewx[5179]: engine: Clock error is -0.66 seconds (positive is fast)
Feb 6 17:57:52 deadduck weewx[5179]: vantage: Getting archive packets since 2020-01-16 17:20:00 MST (1579220400)
Feb 6 17:57:52 deadduck weewx[5179]: vantage: Gentle wake up of console successful
Feb 6 17:57:52 deadduck weewx[5179]: vantage: Retrieving 0 page(s); starting index= 0
Feb 6 17:57:52 deadduck weewx[5179]: engine: Starting main packet loop.
Feb 6 17:57:52 deadduck weewx[5179]: vantage: Gentle wake up of console successful
Feb 6 17:57:52 deadduck weewx[5179]: vantage: Requesting 200 LOOP packets.
Feb 6 17:57:52 deadduck weewx[5179]: vantage: Gentle wake up of console successful
Feb 6 17:58:14 deadduck weewx[5179]: vantage: Getting archive packets since 2020-01-16 17:20:00 MST (1579220400)
Feb 6 17:58:14 deadduck weewx[5179]: vantage: Gentle wake up of console successful
Feb 6 17:58:14 deadduck weewx[5179]: vantage: Retrieving 0 page(s); starting index= 0
Feb 6 17:58:14 deadduck weewx[5179]: reportengine: Running reports for latest time in the database.
Feb 6 17:58:14 deadduck weewx[5179]: reportengine: Running report 'SeasonsReport'
Feb 6 17:58:14 deadduck weewx[5179]: vantage: Requesting 200 LOOP packets.
Feb 6 17:58:15 deadduck weewx[5179]: reportengine: Found configuration file /etc/weewx/skins/Seasons/skin.conf for report 'SeasonsReport'
Feb 6 17:58:15 deadduck weewx[5179]: vantage: Gentle wake up of console successful
Feb 6 17:58:15 deadduck weewx[5179]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
Feb 6 17:58:15 deadduck weewx[5179]: manager: Daily summary version is 2.0
Feb 6 17:58:15 deadduck weewx[5179]: cheetahgenerator: Generated 8 files for report SeasonsReport in 0.69 seconds
Feb 6 17:58:15 deadduck weewx[5179]: manager: Daily summary version is 2.0
Feb 6 17:58:15 deadduck weewx[5179]: imagegenerator: Generated 14 images for SeasonsReport in 0.20 seconds
Feb 6 17:58:15 deadduck weewx[5179]: copygenerator: copied 5 files to /var/www/html/weewx
Feb 6 17:58:15 deadduck weewx[5179]: reportengine: Running report 'SmartphoneReport'
Feb 6 17:58:15 deadduck weewx[5179]: reportengine: Found configuration file /etc/weewx/skins/Smartphone/skin.conf for report 'SmartphoneReport'
Feb 6 17:58:15 deadduck weewx[5179]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
Feb 6 17:58:15 deadduck weewx[5179]: manager: Daily summary version is 2.0
Feb 6 17:58:16 deadduck weewx[5179]: cheetahgenerator: Generated 6 files for report SmartphoneReport in 0.06 seconds
Feb 6 17:58:16 deadduck weewx[5179]: manager: Daily summary version is 2.0
Feb 6 17:58:16 deadduck weewx[5179]: imagegenerator: Generated 6 images for SmartphoneReport in 0.08 seconds
Feb 6 17:58:16 deadduck weewx[5179]: copygenerator: copied 6 files to /var/www/html/weewx/smartphone
Feb 6 17:58:16 deadduck weewx[5179]: reportengine: Running report 'MobileReport'
Feb 6 17:58:16 deadduck weewx[5179]: reportengine: Found configuration file /etc/weewx/skins/Mobile/skin.conf for report 'MobileReport'
Feb 6 17:58:16 deadduck weewx[5179]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
Feb 6 17:58:16 deadduck weewx[5179]: manager: Daily summary version is 2.0
Feb 6 17:58:16 deadduck weewx[5179]: cheetahgenerator: Generated 1 files for report MobileReport in 0.02 seconds
Feb 6 17:58:16 deadduck weewx[5179]: manager: Daily summary version is 2.0
Feb 6 17:58:16 deadduck weewx[5179]: imagegenerator: Generated 4 images for MobileReport in 0.05 seconds
Feb 6 17:58:16 deadduck weewx[5179]: copygenerator: copied 2 files to /var/www/html/weewx/mobile
Feb 6 17:58:16 deadduck weewx[5179]: reportengine: Report 'StandardReport' not enabled. Skipping.
Feb 6 17:58:16 deadduck weewx[5179]: reportengine: Report 'FTP' not enabled. Skipping.
Feb 6 17:58:16 deadduck weewx[5179]: reportengine: Report 'RSYNC' not enabled. Skipping.

The URL=www.deadduck.net/weather Date still 1/16/20...

What else can I try?

Thanks!

Troy

Troy Lass

unread,

Feb 6, 2020, 8:10:40 PM2/6/20

to weewx...@googlegroups.com

Hmm, don't know why the retransmit is on? I set it off and cleared memory again, just because...

Power supply is good and put in new batteries today when I did the power cycle first.

I'll try reseating the datalogger in a second.

Why does weewx keep trying to get the archive records from 1/16/20? Could this be a database issue?

Feb 6 18:08:01 deadduck weewx[5510]: vantage: Getting archive packets since 2020-01-16 17:20:00 MST (1579220400)
Feb 6 18:08:01 deadduck weewx[5510]: vantage: Gentle wake up of console successful
Feb 6 18:08:01 deadduck weewx[5510]: vantage: Retrieving 0 page(s); starting index= 0
Feb 6 18:08:01 deadduck weewx[5510]: engine: Starting main packet loop.
Feb 6 18:08:01 deadduck weewx[5510]: vantage: Gentle wake up of console successful
Feb 6 18:08:01 deadduck weewx[5510]: vantage: Requesting 200 LOOP packets.
Feb 6 18:08:01 deadduck weewx[5510]: vantage: Gentle wake up of console successful

root@deadduck:/etc/init.d# wee_device --set-retransmit=OFF

Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)

Proceeding will set retransmit to 'OFF'
.Are you sure you want to proceed (y/n)? y
Retransmit set to 'OFF'.

root@deadduck:/etc/init.d# wee_device --clear-memory
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
Proceeding will erase all archive records.
Are you sure you wish to proceed (y/n)? y
Erasing all archive records ...

Archive records erased.
root@deadduck:/etc/init.d#

Thanks!

Troy

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zECz%3Dc-pvR-MhCJ98yiBCExvv9-9UtyeJ-k6FAy2AdF1DQ%40mail.gmail.com.

Thomas Keffer

unread,

Feb 6, 2020, 8:18:45 PM2/6/20

to weewx-user

It's asking for records since 1/16/2020 because that's the last timestamp in your database. It's trying to do a backfill.

You cleared the memory and it appears that the Envoy is not putting any new data into the logger, so nothing new is getting into the database. That means the reports will always look the same.

Again, try reseating the logger. If that doesn't work, call Davis.

-tk

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CALBrUnG9nzs%3DcV-f0F3o5m0jqCkQvwMfZvYi4u1212ubGo2e5Q%40mail.gmail.com.

Troy Lass

unread,

Feb 6, 2020, 8:25:11 PM2/6/20

to weewx...@googlegroups.com

Ok, I reseated the data logger, it was tight and looked good, great really.

I was able to get the envoy to link up with WeatherLink on the Windoze PC before and after I updated the firmware to 3.8 so it has to be sending data?? There's something here I don't understand. I know you have LOTS of experience with these critters but I don't get why it would transmit data to Windoze and not Ubuntu.

Hmm, I'm going to swap the USB cable as one last try...

Hey, I have 2 davis consoles in the house, the envoy is for Weewx on the ubuntu server... I'll move the data logger to one of them and try that too. That should give us a good data point to debug this...

Thanks for the work on the app and the help...

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zECC2xrcK4geJXxP1%2BB6ubo1ZQWoMhgnujd%3DDVYZSSe6ng%40mail.gmail.com.

Troy Lass

unread,

Feb 6, 2020, 8:46:51 PM2/6/20

to weewx...@googlegroups.com

Ok, now this is strange....

I moved the data logger to one of the consoles. See the output from the it below from an --info.

The date and time is correct in the output from the console, but check out the following message from the syslog!

Does this point to corrupt data on the console too?

manager: Unable to add record 2020-06-16 10:23:00 MDT (1592324580) to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

How could I have 2 devices with corrupt memories? The batteries are good in the console and it has a power supply, and I have generator backup when I have power outages and am never without power for more than 30 seconds.

The output from the syslog shows something completely different... below.

root@deadduck:/etc/init.d# ./weewx stop
[ ok ] Stopping weewx (via systemctl): weewx.service.

root@deadduck:/etc/init.d# wee_device --info
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
Querying...
Davis Vantage EEPROM settings:

CONSOLE TYPE: Vantage Pro2

CONSOLE FIRMWARE:

Date: Sep 29 2009
Version: 1.90

CONSOLE SETTINGS:
Archive interval: 1800 (seconds)

Altitude: 6100 (foot)
Wind cup type: large
Rain bucket type: 0.01 inches
Rain year start: 1

Onboard time: 2020-02-06 18:26:17

CONSOLE DISPLAY UNITS:
Barometer: inHg
Temperature: degree_F
Rain: inch
Wind: mile_per_hour

CONSOLE STATION INFO:
Latitude (onboard): +40.3°
Longitude (onboard): -105.2°

Use manual or auto DST? AUTO
DST setting: N/A
Use GMT offset or zone code? ZONE_CODE
Time zone code: 5
GMT offset: N/A
Temperature logging: LAST
Retransmit channel: OFF (0)

TRANSMITTERS:
Channel Receive Repeater Type

1 active none (N/A)
2 active none iss
3 active none (N/A)
4 active none (N/A)
5 active none (N/A)
6 active none (N/A)
7 active none (N/A)
8 active none (N/A)

RECEPTION STATS:
Total packets received: 23948
Total packets missed: 242
Number of resynchronizations: 10
Longest good stretch: 1542
Number of CRC errors: 27

BAROMETER CALIBRATION DATA:
Current barometer reading: 29.782 inHg
Altitude: 6100 feet
Dew point: 24 F
Virtual temperature: 27 F
Humidity correction factor: 1.3

Correction ratio: 1.259
Correction constant: +0.000 inHg
Gain: 0.000

Offset: -21.000

OFFSETS:
Wind direction: +0 deg
Inside Temperature: +0.0 F
Inside Humidity: +0 %
Outside Temperature: +0.0 F
Outside Humidity: +0 %

root@deadduck:/etc/init.d# ./weewx start
[ ok ] Starting weewx (via systemctl): weewx.service.
root@deadduck:/etc/init.d#

Where does this date of 6-16/2020 come from??

Feb 6 18:38:19 deadduck weewx[6279]: engine: 2020-06-16 10:23:00 MDT (1592324580) Archive value 'outTemp' -76.9 outside limits (-40.0, 120.0)
Feb 6 18:38:19 deadduck weewx[6279]: engine: 2020-06-16 10:23:00 MDT (1592324580) Archive value 'inTemp' 174.4 outside limits (10.0, 120.0)
Feb 6 18:38:19 deadduck weewx[6279]: manager: Unable to add record 2020-06-16 10:23:00 MDT (1592324580) to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime

Feb 6 18:33:56 deadduck systemd[1]: Starting LSB: weewx weather system...
Feb 6 18:33:56 deadduck weewx[6264]: * Starting weewx weather system weewx
Feb 6 18:33:56 deadduck weewx[6275]: engine: Initializing weewx version 3.9.2
Feb 6 18:33:56 deadduck weewx[6275]: engine: Using Python 2.7.17 (default, Nov 7 2019, 10:07:09) #012[GCC 7.4.0]
Feb 6 18:33:56 deadduck weewx[6275]: engine: Platform Linux-4.15.0-76-generic-x86_64-with-Ubuntu-18.04-bionic
Feb 6 18:33:56 deadduck weewx[6275]: engine: Locale is 'en_US.UTF-8'
Feb 6 18:33:56 deadduck weewx[6275]: engine: pid file is /var/run/weewx.pid
Feb 6 18:33:56 deadduck weewx[6279]: engine: Using configuration file /etc/weewx/weewx.conf
Feb 6 18:33:56 deadduck weewx[6279]: engine: Debug is 1
Feb 6 18:33:56 deadduck weewx[6279]: engine: Initializing engine
Feb 6 18:33:56 deadduck weewx[6279]: engine: Loading station type Vantage (weewx.drivers.vantage)
Feb 6 18:33:56 deadduck weewx[6264]: ...done.
Feb 6 18:33:56 deadduck systemd[1]: Started LSB: weewx weather system.
Feb 6 18:33:56 deadduck weewx[6279]: vantage: Driver version is 3.1.1
Feb 6 18:33:56 deadduck weewx[6279]: vantage: Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
Feb 6 18:34:00 deadduck weewx[6279]: vantage: Retry #0 failed
Feb 6 18:34:00 deadduck weewx[6279]: vantage: Gentle wake up of console successful
Feb 6 18:34:00 deadduck weewx[6279]: vantage: Hardware type is 16
Feb 6 18:34:00 deadduck weewx[6279]: vantage: ISS ID is 1
Feb 6 18:34:00 deadduck weewx[6279]: vantage: Hardware name: Vantage Pro2
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.engine.StdTimeSynch
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdTimeSynch
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.engine.StdConvert
Feb 6 18:34:00 deadduck weewx[6279]: engine: StdConvert target unit is 0x1
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdConvert
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.engine.StdCalibrate
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdCalibrate
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.engine.StdQC
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdQC
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.wxservices.StdWXCalculate
Feb 6 18:34:00 deadduck weewx[6279]: 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
Feb 6 18:34:00 deadduck weewx[6279]: wxcalculate: The following algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.wxservices.StdWXCalculate
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.engine.StdArchive
Feb 6 18:34:00 deadduck weewx[6279]: engine: Archive will use data binding wx_binding
Feb 6 18:34:00 deadduck weewx[6279]: engine: Record generation will be attempted in 'hardware'
Feb 6 18:34:00 deadduck weewx[6279]: engine: Using archive interval of 1800 seconds (specified by hardware)
Feb 6 18:34:00 deadduck weewx[6279]: engine: Use LOOP data in hi/low calculations: 1
Feb 6 18:34:00 deadduck weewx[6279]: manager: Daily summary version is 2.0
Feb 6 18:34:00 deadduck weewx[6279]: engine: Using binding 'wx_binding' to database 'weewx.sdb'
Feb 6 18:34:00 deadduck weewx[6279]: manager: Starting backfill of daily summaries
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdArchive
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.restx.StdStationRegistry
Feb 6 18:34:00 deadduck weewx[6279]: restx: StationRegistry: Station will be registered.
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.restx.StdStationRegistry
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.restx.StdWunderground
Feb 6 18:34:00 deadduck weewx[6279]: restx: WU essentials: {}
Feb 6 18:34:00 deadduck weewx[6279]: restx: Wunderground-PWS: Data for station KCOBERTH88 will be posted
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.restx.StdWunderground
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.restx.StdPWSweather
Feb 6 18:34:00 deadduck weewx[6279]: restx: PWSweather: Posting not enabled.
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.restx.StdPWSweather
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.restx.StdCWOP
Feb 6 18:34:00 deadduck weewx[6279]: restx: CWOP: Posting not enabled.
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.restx.StdCWOP
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.restx.StdWOW
Feb 6 18:34:00 deadduck weewx[6279]: restx: WOW: Posting not enabled.
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.restx.StdWOW
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.restx.StdAWEKAS
Feb 6 18:34:00 deadduck weewx[6279]: restx: AWEKAS: Posting not enabled.
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.restx.StdAWEKAS
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.engine.StdPrint
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdPrint
Feb 6 18:34:00 deadduck weewx[6279]: engine: Loading service weewx.engine.StdReport
Feb 6 18:34:00 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdReport
Feb 6 18:34:00 deadduck weewx[6279]: engine: Starting up weewx version 3.9.2
Feb 6 18:34:00 deadduck weewx[6279]: manager: Daily summary version is 2.0
Feb 6 18:34:00 deadduck weewx[6279]: vantage: Gentle wake up of console successful
Feb 6 18:34:01 deadduck weewx[6279]: engine: Clock error is -325.00 seconds (positive is fast)
Feb 6 18:34:01 deadduck weewx[6279]: vantage: Gentle wake up of console successful
Feb 6 18:34:01 deadduck weewx[6279]: vantage: Clock set to 2020-02-06 18:34:01 MST (1581039241)
Feb 6 18:34:01 deadduck weewx[6279]: vantage: Getting archive packets since 2020-01-16 17:20:00 MST (1579220400)
Feb 6 18:34:02 deadduck weewx[6279]: vantage: Gentle wake up of console successful
Feb 6 18:34:02 deadduck weewx[6279]: vantage: Retrieving 513 page(s); starting index= 0
Feb 6 18:34:02 deadduck weewx[6279]: engine: 2020-06-16 10:23:00 MDT (1592324580) Archive value 'outTemp' -76.9 outside limits (-40.0, 120.0)
Feb 6 18:34:02 deadduck weewx[6279]: engine: 2020-06-16 10:23:00 MDT (1592324580) Archive value 'inTemp' 174.4 outside limits (10.0, 120.0)
Feb 6 18:34:02 deadduck weewx[6279]: manager: Added record 2020-06-16 10:23:00 MDT (1592324580) to database 'weewx.sdb'
Feb 6 18:34:02 deadduck weewx[6279]: manager: Added record 2020-06-16 10:23:00 MDT (1592324580) to daily summary in 'weewx.sdb'
Feb 6 18:34:02 deadduck weewx[6279]: engine: Internal error detected. Catchup abandoned
Feb 6 18:34:02 deadduck weewx[6279]: **** Unknown archive type = 0x7f
Feb 6 18:34:02 deadduck weewx[6279]: engine: Starting main packet loop.
Feb 6 18:34:02 deadduck weewx[6279]: vantage: Gentle wake up of console successful
Feb 6 18:34:02 deadduck weewx[6279]: vantage: Requesting 200 LOOP packets.
Feb 6 18:34:02 deadduck weewx[6279]: vantage: Gentle wake up of console successful
Feb 6 18:34:03 deadduck weewx[6279]: restx: StationRegistry: Published record 2020-06-16 10:23:00 MDT (1592324580)
Feb 6 18:34:03 deadduck weewx[6279]: restx: Wunderground-PWS: Failed upload attempt 1: HTTP Error 401: Unauthorized
Feb 6 18:34:08 deadduck weewx[6279]: restx: Wunderground-PWS: Failed upload attempt 2: HTTP Error 401: Unauthorized
Feb 6 18:34:13 deadduck weewx[6279]: restx: Wunderground-PWS: Failed upload attempt 3: HTTP Error 401: Unauthorized
Feb 6 18:34:18 deadduck weewx[6279]: restx: Wunderground-PWS: Failed to publish record 2020-06-16 10:23:00 MDT (1592324580): Failed upload after 3 tries
Feb 6 18:37:06 deadduck weewx[6279]: vantage: LOOP try #1; error: Expected to read 99 chars; got 0 instead
Feb 6 18:37:06 deadduck weewx[6279]: vantage: Requesting 200 LOOP packets.
Feb 6 18:37:06 deadduck weewx[6279]: vantage: Rude wake up of console successful
Feb 6 18:37:10 deadduck weewx[6279]: vantage: LOOP try #2; error: Expected to read 99 chars; got 0 instead
Feb 6 18:37:10 deadduck weewx[6279]: vantage: Requesting 200 LOOP packets.
Feb 6 18:37:10 deadduck weewx[6279]: vantage: Rude wake up of console successful
Feb 6 18:37:14 deadduck weewx[6279]: vantage: LOOP try #3; error: Expected to read 99 chars; got 0 instead
Feb 6 18:37:14 deadduck weewx[6279]: vantage: Requesting 200 LOOP packets.
Feb 6 18:37:14 deadduck weewx[6279]: vantage: Rude wake up of console successful
Feb 6 18:37:19 deadduck weewx[6279]: vantage: LOOP try #4; error: Expected to read 99 chars; got 0 instead
Feb 6 18:37:19 deadduck weewx[6279]: vantage: LOOP max tries (4) exceeded.
Feb 6 18:37:19 deadduck weewx[6279]: engine: Main loop exiting. Shutting engine down.
Feb 6 18:37:19 deadduck weewx[6279]: restx: Shut down Wunderground-PWS thread.
Feb 6 18:37:19 deadduck weewx[6279]: restx: Shut down StationRegistry thread.
Feb 6 18:37:19 deadduck weewx[6279]: engine: Caught WeeWxIOError: Max tries exceeded while getting LOOP data.
Feb 6 18:37:19 deadduck weewx[6279]: **** Waiting 60 seconds then retrying...
Feb 6 18:38:19 deadduck weewx[6279]: engine: retrying...
Feb 6 18:38:19 deadduck weewx[6279]: engine: Using configuration file /etc/weewx/weewx.conf
Feb 6 18:38:19 deadduck weewx[6279]: engine: Debug is 1
Feb 6 18:38:19 deadduck weewx[6279]: engine: Initializing engine
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading station type Vantage (weewx.drivers.vantage)
Feb 6 18:38:19 deadduck weewx[6279]: vantage: Driver version is 3.1.1
Feb 6 18:38:19 deadduck weewx[6279]: vantage: Opened up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
Feb 6 18:38:19 deadduck weewx[6279]: vantage: Gentle wake up of console successful
Feb 6 18:38:19 deadduck weewx[6279]: vantage: Hardware type is 16
Feb 6 18:38:19 deadduck weewx[6279]: vantage: ISS ID is 1
Feb 6 18:38:19 deadduck weewx[6279]: vantage: Hardware name: Vantage Pro2
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.engine.StdTimeSynch
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdTimeSynch
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.engine.StdConvert
Feb 6 18:38:19 deadduck weewx[6279]: engine: StdConvert target unit is 0x1
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdConvert
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.engine.StdCalibrate
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdCalibrate
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.engine.StdQC
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdQC
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.wxservices.StdWXCalculate
Feb 6 18:38:19 deadduck weewx[6279]: 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
Feb 6 18:38:19 deadduck weewx[6279]: wxcalculate: The following algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.wxservices.StdWXCalculate
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.engine.StdArchive
Feb 6 18:38:19 deadduck weewx[6279]: engine: Archive will use data binding wx_binding
Feb 6 18:38:19 deadduck weewx[6279]: engine: Record generation will be attempted in 'hardware'
Feb 6 18:38:19 deadduck weewx[6279]: engine: Using archive interval of 1800 seconds (specified by hardware)
Feb 6 18:38:19 deadduck weewx[6279]: engine: Use LOOP data in hi/low calculations: 1
Feb 6 18:38:19 deadduck weewx[6279]: manager: Daily summary version is 2.0
Feb 6 18:38:19 deadduck weewx[6279]: engine: Using binding 'wx_binding' to database 'weewx.sdb'
Feb 6 18:38:19 deadduck weewx[6279]: manager: Starting backfill of daily summaries
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdArchive
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.restx.StdStationRegistry
Feb 6 18:38:19 deadduck weewx[6279]: restx: StationRegistry: Station will be registered.
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.restx.StdStationRegistry
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.restx.StdWunderground
Feb 6 18:38:19 deadduck weewx[6279]: restx: WU essentials: {}
Feb 6 18:38:19 deadduck weewx[6279]: restx: Wunderground-PWS: Data for station KCOBERTH88 will be posted
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.restx.StdWunderground
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.restx.StdPWSweather
Feb 6 18:38:19 deadduck weewx[6279]: restx: PWSweather: Posting not enabled.
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.restx.StdPWSweather
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.restx.StdCWOP
Feb 6 18:38:19 deadduck weewx[6279]: restx: CWOP: Posting not enabled.
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.restx.StdCWOP
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.restx.StdWOW
Feb 6 18:38:19 deadduck weewx[6279]: restx: WOW: Posting not enabled.
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.restx.StdWOW
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.restx.StdAWEKAS
Feb 6 18:38:19 deadduck weewx[6279]: restx: AWEKAS: Posting not enabled.
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.restx.StdAWEKAS
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.engine.StdPrint
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdPrint
Feb 6 18:38:19 deadduck weewx[6279]: engine: Loading service weewx.engine.StdReport
Feb 6 18:38:19 deadduck weewx[6279]: engine: Finished loading service weewx.engine.StdReport
Feb 6 18:38:19 deadduck weewx[6279]: engine: Starting up weewx version 3.9.2
Feb 6 18:38:19 deadduck weewx[6279]: manager: Daily summary version is 2.0
Feb 6 18:38:19 deadduck weewx[6279]: vantage: Gentle wake up of console successful
Feb 6 18:38:19 deadduck weewx[6279]: engine: Clock error is -0.50 seconds (positive is fast)
Feb 6 18:38:19 deadduck weewx[6279]: vantage: Getting archive packets since 2020-06-16 10:23:00 MDT (1592324580)
Feb 6 18:38:19 deadduck weewx[6279]: vantage: Gentle wake up of console successful
Feb 6 18:38:19 deadduck weewx[6279]: vantage: Retrieving 513 page(s); starting index= 0
Feb 6 18:38:19 deadduck weewx[6279]: engine: 2020-06-16 10:23:00 MDT (1592324580) Archive value 'outTemp' -76.9 outside limits (-40.0, 120.0)
Feb 6 18:38:19 deadduck weewx[6279]: engine: 2020-06-16 10:23:00 MDT (1592324580) Archive value 'inTemp' 174.4 outside limits (10.0, 120.0)
Feb 6 18:38:19 deadduck weewx[6279]: manager: Unable to add record 2020-06-16 10:23:00 MDT (1592324580) to database 'weewx.sdb': UNIQUE constraint failed: archive.dateTime
Feb 6 18:38:19 deadduck weewx[6279]: engine: Internal error detected. Catchup abandoned
Feb 6 18:38:19 deadduck weewx[6279]: **** Unknown archive type = 0x7f
Feb 6 18:38:19 deadduck weewx[6279]: engine: Starting main packet loop.
Feb 6 18:38:19 deadduck weewx[6279]: vantage: Gentle wake up of console successful
Feb 6 18:38:19 deadduck weewx[6279]: vantage: Requesting 200 LOOP packets.
Feb 6 18:38:19 deadduck weewx[6279]: vantage: Gentle wake up of console successful
Feb 6 18:38:19 deadduck weewx[6279]: restx: StationRegistry: Published record 2020-06-16 10:23:00 MDT (1592324580)
Feb 6 18:38:19 deadduck weewx[6279]: restx: Wunderground-PWS: Failed upload attempt 1: HTTP Error 401: Unauthorized
Feb 6 18:38:25 deadduck weewx[6279]: restx: Wunderground-PWS: Failed upload attempt 2: HTTP Error 401: Unauthorized
Feb 6 18:38:30 deadduck weewx[6279]: restx: Wunderground-PWS: Failed upload attempt 3: HTTP Error 401: Unauthorized
Feb 6 18:38:35 deadduck weewx[6279]: restx: Wunderground-PWS: Failed to publish record 2020-06-16 10:23:00 MDT (1592324580): Failed upload after 3 tries
Feb 6 18:39:01 deadduck CRON[6361]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete)
Feb 6 18:39:04 deadduck weewx[6279]: vantage: LOOP try #1; error: Expected to read 99 chars; got 0 instead
Feb 6 18:39:04 deadduck weewx[6279]: vantage: Requesting 200 LOOP packets.
Feb 6 18:39:04 deadduck weewx[6279]: vantage: Rude wake up of console successful

Troy Lass

unread,

Feb 6, 2020, 10:10:15 PM2/6/20

to weewx...@googlegroups.com

Ok, something is really wrong here. After the above syslog errors looped for a while I stopped weewx, cleared the memory on the console and started weewx and now the web page has the date of 6/16/20 10:23AM with no data.

www.deadduck.net/weather

www.deaduck.net/mobile

This doesn' seem like a HW issue at this point?? The console is getting good data from the station and has the correct date, and I cleared the memory.

There's some data corruption here and I've tried different USB cables, different USB ports, an envoy and a console. Now same issue with a date in the future.

Now when I stop the weewx daemon I get the following in the syslog...

Feb 6 20:08:51 deadduck systemd[1]: Stopping LSB: weewx weather system...
Feb 6 20:08:51 deadduck weewx[7864]: * Stopping weewx weather system weewx
Feb 6 20:08:51 deadduck weewx[7572]: engine: Received signal TERM (15).
Feb 6 20:08:51 deadduck weewx[7572]: engine: Main loop exiting. Shutting engine down.
Feb 6 20:08:51 deadduck weewx[7572]: engine: Shutting down StdReport thread
Feb 6 20:08:51 deadduck weewx[7572]: engine: StdReport thread has been terminated
Feb 6 20:08:51 deadduck weewx[7572]: restx: Shut down Wunderground-PWS thread.
Feb 6 20:08:51 deadduck weewx[7572]: restx: Shut down StationRegistry thread.
Feb 6 20:08:51 deadduck weewx[7572]: engine: Terminating weewx version 3.9.2
Feb 6 20:08:51 deadduck weewx[7572]: **** Traceback (most recent call last):
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/share/weewx/weewx/engine.py", line 894, in main
Feb 6 20:08:51 deadduck weewx[7572]: **** engine.run()
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/share/weewx/weewx/engine.py", line 188, in run
Feb 6 20:08:51 deadduck weewx[7572]: **** for packet in self.console.genLoopPackets():
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 508, in genLoopPackets
Feb 6 20:08:51 deadduck weewx[7572]: **** for _loop_packet in self.genDavisLoopPackets(200):
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 535, in genDavisLoopPackets
Feb 6 20:08:51 deadduck weewx[7572]: **** _buffer = self.port.read(99)
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 256, in read
Feb 6 20:08:51 deadduck weewx[7572]: **** _buffer = self.serial_port.read(chars)
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 483, in read
Feb 6 20:08:51 deadduck weewx[7572]: **** ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout.time_left())
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/share/weewx/weewx/engine.py", line 812, in sigTERMhandler
Feb 6 20:08:51 deadduck weewx[7572]: **** raise Terminate
Feb 6 20:08:51 deadduck weewx[7572]: **** Terminate
Feb 6 20:08:56 deadduck weewx[7864]: . ...done.

I'm really at a loss...

Thanks,

Troy

Thomas Keffer

unread,

Feb 7, 2020, 7:21:31 AM2/7/20

to weewx-user

Troy, slow down. You have way too many moving parts for me to follow what you're doing.

1. You never changed the value of WEEWX_ROOT in weewx.conf. Change it back.

2. It's great that you have a console and an Envoy, each with its own logger. That makes it easier to rule out hardware, but you're not making it clear which we're looking at.

3. In your last email, when you stopped the daemon, that looks totally normal to me. What's your concern here?

4. I don't know where the date in the future, 2020-06-16, came from, but this is typical with corrupted loggers. Same with bad archive types. The only cure is to clear the logger.

5. Now you have a date in the future in the database. You'll have to fix that up, too. See the Wiki article Cleaning up old 'bad' data.

6. Be aware that whichever logger/console combination that we're looking at also has a very long archive interval: 1800 seconds. The earlier combo we were looking at was 60 seconds.

-tk

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CALBrUnGtmDhaaK7%3D3pHV%3DMK%2BYAJDJU%3DTJtBjyybEguQfmXY15Q%40mail.gmail.com.

Troy Lass

unread,

Feb 7, 2020, 8:53:38 AM2/7/20

to weewx...@googlegroups.com

Ok, I've been on the receiving side of this type of thing before so I get it... I've thought I was clear on what I was doing but I understand completely....

1. I changed WEEWX_ROOT back to \ before attempting any of the wee_device commands at the suggestion of the first person who replied so that got done right after the initial response from gjr80 ( Gary ).
2. I have an envoy and a console, but only 1 logger. I moved the logger to the console to try that after you had ran out of ideas on the envoy. I wanted to see if I would see the same issues on the console. So, same data logger but moved to the console after I said I'd try that next... So, everything that I recorded after this comment at 6:46PM MT was on the console... "Ok, now this is strange.... I moved the data logger to one of the consoles. See the output from the it below from an --info...."
3. In my last email I'm concerned that I now have a new date in the future, from the console, after I'd ran the wee_device --clear-memory and now I'm seeing the following that I hadn't seen before, perhaps it's just part of the debug=1 logging?

When I see output in the logs that points to line #s of code I thought that was errors? When I say I hadn't see these messages before I mean before I started having this issue, but I hadn't really been watching weewx in the syslog like I am now.

So, like you say this could be completely normal it's just that when I see the references to line numbers like this I think it's an error in the code, I don't know python....

Feb 6 20:08:51 deadduck weewx[7572]: **** Traceback (most recent call last):
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/share/weewx/weewx/engine.py", line 894, in main
Feb 6 20:08:51 deadduck weewx[7572]: **** engine.run()
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/share/weewx/weewx/engine.py", line 188, in run
Feb 6 20:08:51 deadduck weewx[7572]: **** for packet in self.console.genLoopPackets():
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 508, in genLoopPackets
Feb 6 20:08:51 deadduck weewx[7572]: **** for _loop_packet in self.genDavisLoopPackets(200):
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 535, in genDavisLoopPackets
Feb 6 20:08:51 deadduck weewx[7572]: **** _buffer = self.port.read(99)
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/share/weewx/weewx/drivers/vantage.py", line 256, in read
Feb 6 20:08:51 deadduck weewx[7572]: **** _buffer = self.serial_port.read(chars)
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/lib/python2.7/dist-packages/serial/serialposix.py", line 483, in read
Feb 6 20:08:51 deadduck weewx[7572]: **** ready, _, _ = select.select([self.fd, self.pipe_abort_read_r], [], [], timeout.time_left())
Feb 6 20:08:51 deadduck weewx[7572]: **** File "/usr/share/weewx/weewx/engine.py", line 812, in sigTERMhandler
Feb 6 20:08:51 deadduck weewx[7572]: **** raise Terminate
Feb 6 20:08:51 deadduck weewx[7572]: **** Terminate

4. In reference to the 6/16 date.... When I first connected the console it tried to get data from 1/16, like the console and never updated any of the html files, it wrote out new html files but the data was the same with the 1/16/20 date and no data.

Next I did a weewx stop, then wee_device --info, wee-device --clear-memory, weewx start. After I did the clear memory is when I got the new date of 6/16/20 in the html files ( in the database ). I'd cleared the memory because after the initial try

I was basically seeing the same issue as I was on the envoy. You can see in the thread that I did an --info, --clear-memory, then when I started weewx I got the future date... everything in the thread is in order.

5. Thanks for the link to fix the date, I was looking for that last night and didn't find it. I'll try to take care of the future date when I get home tonight.

6. The 1800 archive interval is the default on the console. I noticed that when I did the first --info when I connected the console, but I was hoping to get the data from the console so I didn't want to change that initially because it will clear the data.

Once I saw that wasn't working and I cleared the memory I set the archive-interval to 300. I'd like to have it at 60 but wanted to make sure it had time to load. If I get this working again I'll change the archive-interval on the device and in the weewx conf to 60.

I did match the 300 interval on the device and in the weewx.conf file.

You said something in this reply that makes me think, you said I needed to clear the data logger. I thought the data logger was really just an interface to connect the USB of the device to a server, but now I get that it's what archives and logs the data?

That is one thing that's in common here with the envoy and the console, I have 1 data logger. I have done the following on it multiple times.... weewx stop, wee_device --clear-memory, weewx start. Other than the first time I tried it the --clear-memory that failed

they all seemed to work and told me it cleared the data.

It's strange that I could connect the envoy to the Windoze PC and get the Davis Weatherlink software to work before and after I upgraded the firmware on the envoy.

To be clear, I have not been swapping back and forth. I started with the envoy and when I said, "Ok, now this is strange.... I moved the data logger to one of the consoles." I did and I've never swapped the data logger back to eh envoy. The console is still connected to the ubuntu server. I didn't see any reason to move it back yet.

Thanks for the help!

Troy

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zECTs2cYsW952Vna__%3DtVx3HTPNycTXOerHV4ofzYGfB%2BA%40mail.gmail.com.

Thomas Keffer

unread,

Feb 7, 2020, 9:29:34 AM2/7/20

to weewx-user

Yes, it is the logger that saves the data. The console (or Envoy) has no memory inside --- it depends on the logger.

The reason why things seem to work under Windows is that the Davis Weatherlink software, oddly, does not take advantage of the presence of a logger. WeeWX can do this too, but you'll lose the ability to do catch ups. If you want to do this, set the option record_generation to software, and add a new option "no_catchup" set to True:

[StdArchive]

...

record_generation = software

no_catchup = True

Now you have a plain old dumb console.

But, really, there are thousands of installations of WeeWX using a Davis logger. There's no reason why yours shouldn't too.

-tk

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CALBrUnFSsZ-5ik7f9r0t%2BHPd1-qKT_jz9Xn76DodSVo_U0B4jg%40mail.gmail.com.

Troy Lass

unread,

Feb 7, 2020, 9:47:41 AM2/7/20

to weewx...@googlegroups.com

Ah, now I understand why Windoze worked. This gives me something to try...

If bypassing the data logger works then that's the common denominator here, maybe the logger is bad? Have you ever heard of a logger going bad? I've had it for about 9 years now.

Is there anyway to test that? It seems that any of the wee_device commands work except for the initial clear-memory, I assume commands like --info and --archive-interval are talking directly to the device and not the logger since the settings survive without the logger. The archive however seem to be the issue here and those are on the logger? I wish I had another data logger to test... Those darn things aren't cheap.

With what I've done and what you see do you think the logger is bad at this point?

Thanks for the help!

Troy

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEBSsE42g%2BuQvBQzW5er%2BHVBpKO9mC30PjwTB47XPTis8A%40mail.gmail.com.

Thomas Keffer

unread,

Feb 7, 2020, 9:54:12 AM2/7/20

to weewx-user

Loggers definitely go bad, although rarely. I've heard of maybe half a dozen that have done so.

One other detail: the logger is actually quite dumb. It's just a memory chip. All of the logic for writing to it, including the archive interval, is held in the console. So, --info and --archive-interval have nothing to do with the logger. Exceptions are --clear-memory and --dump.

Which reminds me: make sure the logger has been started!

wee_device --start

I wouldn't give up quite yet. Try clearing the logger (again), setting your database aside, double-checking your clock(s), then start WeeWX from the command line. See if it runs properly.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CALBrUnEx16iMNgza6fx2GmP%3D-uHQaXDVkTBuHAC3n1VZ7Kb7HQ%40mail.gmail.com.

Troy Lass

unread,

Feb 7, 2020, 10:31:01 AM2/7/20

to weewx...@googlegroups.com

Got it. I'll give that a try tonight or over the weekend and post the results.

I really appreciate the help. I've really grown to love weeWX and miss having the data. I live in a high wind area and like to watch what's happening when I'm not around. It's not unusual for us to get over 100MPH and I like to know when it gets up there...

Thanks again!

Troy

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEADJQrh_B_%2B%3DTTbz0SL4_cD9nQon6c%3DUUHDgMHu%3DFDZng%40mail.gmail.com.

vince

unread,

Feb 7, 2020, 12:02:57 PM2/7/20

to weewx-user

On Friday, February 7, 2020 at 7:31:01 AM UTC-8, Troy Lass wrote:

I live in a high wind area and like to watch what's happening when I'm not around. It's not unusual for us to get over 100MPH and I like to know when it gets up there...

That sure sounds like a reason to want to use the logger and weewx's capability to gracefully catch up when your location has a power outage.....

That's a lot of MPH :-)

Troy Lass

unread,

Feb 7, 2020, 2:45:02 PM2/7/20

to weewx...@googlegroups.com

Ok, I'm trying to cleanup the future dates and I'm a little lost...

I made a copy of the DB in /var/tmp and ran the following....

root@deadduck:/var/tmp# echo "SELECT * FROM archive WHERE (windSpeed > 80);" | sqlite3 /var/tmp/weewx.sdb
1321130400|1|10|30.083|34.79414|44.235535|73.5|53.200001|17.0|24.0|81.0|225.0|115.0|270.0|72.0|1.1|17.36064|53.200001|53.200001|0.0||||||||||||||||||||100.0|0.0|683.0||||||||||
1321132200|1|10|30.073|34.784264|44.223541|72.099998|53.0|18.0|26.0|82.0|315.0|118.0|67.5|82.290001|1.25|19.047731|53.0|53.0|0.0||||||||||||||||||||98.0|0.0|684.0||||||||||

How do I identify the dates to delete? I'm assuming there's a date field? What's the format? I need to delete all dates from 8/18/19 to current.

Thanks,

Troy

--
You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/ic4IK_-eX4Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e52b4eb7-2f33-40b8-bb92-61066300e849%40googlegroups.com.

p q

unread,

Feb 7, 2020, 2:57:17 PM2/7/20

to weewx...@googlegroups.com

Timestamps are stored as epochs (second since 1970). I often use https://www.epochconverter.com/ to help me convert.

The first number looks like a timestamps - 1321130400 = Saturday, November 12, 2011 8:40:00 (there abouts - depending on your time zone)

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/CALBrUnFjVdk3x94Z7T6q3urS1x4cvHumgAreHJmkoAvfF%3Ddyqg%40mail.gmail.com.

--

Peter Quinn
(415)794-2264

Troy Lass

unread,

Feb 7, 2020, 3:15:14 PM2/7/20

to weewx...@googlegroups.com

Got it - thanks. 1 step closer...

How do I query the epoc date though? I don't know the column name to do the query on.

root@deadduck:/var/tmp# echo "SELECT * FROM archive WHERE (epoc > 1566111600);" | sqlite3 /var/tmp/weewx.sdb
Error: near line 1: no such column: epoc
root@deadduck:/var/tmp# echo "SELECT * FROM archive WHERE (date > 1566111600);" | sqlite3 /var/tmp/weewx.sdb
Error: near line 1: no such column: date
root@deadduck:/var/tmp#

Once I know the column name then if we "assume" date is the correct column name then the next steps are to delete all of the dates since 8/18/19 1:00AM MT is to next do the following...

echo "UPDATE archive SET date=NULL WHERE (date > 1566111600);" | sqlite3 /var/tmp/backup.sdb

cp /var/lib/weewx.sdb /var/lob/weewx.sdb.020720

cp /var/tmp/weewx/sdb /var/lib/weewx.sdb

wee_database weewx.conf --drop-daily

wee_database weewx.conf --rebuild-daily

Take a coffee break and wait for the daily summaries to be rebuilt...

/etc/init.d/weewx start

and I should be good??

Thanks,

Troy

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAA1SM21NokLnBEOGH-u1zG8yQeQvS8y0ysrRxLV4XH3DbvvpLA%40mail.gmail.com.

vince

unread,

Feb 7, 2020, 3:22:45 PM2/7/20

to weewx-user

On Friday, February 7, 2020 at 12:15:14 PM UTC-8, Troy Lass wrote:

How do I query the epoc date though? I don't know the column name to do the query on.

Look at the schema. It's called dateTime.

I have some examples at https://github.com/vinceskahan/weewx-odds-and-ends/blob/master/fix-bad-rain.md if that helps any.

Troy Lass

unread,

Feb 7, 2020, 5:43:41 PM2/7/20

to weewx...@googlegroups.com

Ok, that helps, didn't think to read the other examples - thanks.

I did the following....

Below the first query shows the last good record and the next 2 bad records.

root@deadduck:/var/tmp# echo "SELECT * FROM archive WHERE (dateTime >= 1566143400);" | sqlite3 /var/tmp/weewx.sdb

1566143400|1|5|30.4558189104303|30.4558189104303|37.7623351681816|71.733842431388|69.5849521883363|12.532315137224|60.6745673129079|3.22090544784868|244.044984074789|3.8954353891475|243.136938325575|0.0|0.0|55.3830091077274|69.5849521883363|69.5849521883363|0.00120036639468108|701.324093624923|9.81853731074892||||||||||||||||||19.3618624420658|0.0|11.9735444627246||||11.9386770269783|12.0367022469557|11.9772054338739|0.0|0.0|0.183333333333333|0.0
1579220400|1|10|30.215|||69.7|28.3|20.0|51.0|0.0||2.0|67.5|0.0|0.0|12.5154339623535|28.3|28.3|0.0||||||||||||||||||||64.0625||||||||||||
1592324580|1|30|27.704|||||9.0|||3757.5|160.0|5557.5|8.14|0.0||||0.0||14.7||29.0|148.0|69.0||163.0|129.0|93.0|93.0|61.0|253.0|253.0|251.0|253.0|253.0|95.0|249.0|100.0||||||||||||

Next I deleted the 2 bad rows...

root@deadduck:/var/tmp# echo "delete from archive where (dateTime >= 1579220400) limit 2;" | sqlite3 /var/tmp/weewx.sdb

The first query again shows the bad records are gone - whew...
root@deadduck:/var/tmp# echo "SELECT * FROM archive WHERE (dateTime >= 1566143400);" | sqlite3 /var/tmp/weewx.sdb
1566143400|1|5|30.4558189104303|30.4558189104303|37.7623351681816|71.733842431388|69.5849521883363|12.532315137224|60.6745673129079|3.22090544784868|244.044984074789|3.8954353891475|243.136938325575|0.0|0.0|55.3830091077274|69.5849521883363|69.5849521883363|0.00120036639468108|701.324093624923|9.81853731074892||||||||||||||||||19.3618624420658|0.0|11.9735444627246||||11.9386770269783|12.0367022469557|11.9772054338739|0.0|0.0|0.183333333333333|0.0

Next I did the following

cp /var/lib/weewx.sdb /var/lib/weewx.sdb.020720

cp /var/tmp/weewx/sdb /var/lib/weewx.sdb

wee_database weewx.conf --drop-daily

wee_database weewx.conf --rebuild-daily

root@deadduck:/var/lib/weewx# wee_database /etc/weewx/weewx.conf --drop-daily
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 'archive_sqlite'
Proceeding will delete all your daily summaries from database 'weewx.sdb'

Are you sure you want to proceed (y/n)? y

Dropping daily summary tables from 'weewx.sdb' ...
Daily summary tables dropped from database 'weewx.sdb' in 0.69 seconds

root@deadduck:/var/lib/weewx# wee_database /etc/weewx/weewx.conf --rebuild-daily
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 'archive_sqlite'
All daily summaries will be rebuilt.
Proceed (y/n)? y
Rebuilding daily summaries in database 'weewx.sdb' ...
Records processed: 389000; Last date: 2019-08-15 16:00:00 MDT (1565906400)
Processed 389790 records to rebuild 2710 day summaries in 120.91 seconds
Rebuild of daily summaries in database 'weewx.sdb' complete

root@deadduck:/var/lib/weewx# wee_device --info

Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
Querying...
Davis Vantage EEPROM settings:

CONSOLE TYPE: Vantage Pro2

CONSOLE FIRMWARE:

Date: Sep 11 2017
Version: 3.80

CONSOLE SETTINGS:
Archive interval: 300 (seconds)

Altitude: 6100 (foot)
Wind cup type: large
Rain bucket type: 0.01 inches
Rain year start: 1

Onboard time: 2020-02-07 15:53:12

Total packets received: 482

Total packets missed: 0
Number of resynchronizations: 0

Longest good stretch: 482
Number of CRC errors: 9

BAROMETER CALIBRATION DATA:
Current barometer reading: 29.981 inHg
Altitude: 6100 feet
Dew point: 21 F
Virtual temperature: 26 F
Humidity correction factor: 1.2
Correction ratio: 1.258

Correction constant: +0.000 inHg
Gain: 0.000
Offset: -21.000

OFFSETS:
Wind direction: +0 deg
Inside Temperature: +0.0 F
Inside Humidity: +0 %
Outside Temperature: +0.0 F
Outside Humidity: +0 %

root@deadduck:/var/lib/weewx# wee_device --set-time

Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)

Setting time on console...
Current console time is 2020-02-07 15:12:42 MST (1581113562)

root@deadduck:/var/lib/weewx# wee_device --clear-memory

Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
Proceeding will erase all archive records.
Are you sure you wish to proceed (y/n)? y
Erasing all archive records ...
Archive records erased.

root@deadduck:/var/lib/weewx# wee_device --start

Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)

Starting logger ...
Logger started
root@deadduck:/var/lib/weewx#

root@deadduck:/etc/init.d# ./weewx start
[ ok ] Starting weewx (via systemctl): weewx.service.
root@deadduck:/etc/init.d#

Holy crap, I think it's working again... lol I've got couple updates to the web page with today's date and wind vectors. This is on the console right now and I will move back to the envoy later once I give it a day or so to ensure everything is working correctly. This exercise has also helped me notice a wireless deadspot on my desk very near where I had my envoy. It's a lot easier to tell when the console is communicating with the station than the envoy. I'm only about 20ft away from the station and can see it out of the window so I didn't think it would be an issue but there's definitely a dead spot on the desk so I'll keep the envoy where the console is getting updates now.

I had 2 bad records in the DB, one on 1/16/20 and another in the future 6/16/20. After getting rid of those it started working again. I wonder if the first bad entry was part of the problem all along. I'm betting the logger got corrupted on 8/18/19, the last valid update and I needed to clear the mem back then. I've poked at this a couple times but never made any progress until I reached out and everyone was very helpful and timely.

Thanks everyone for the help with this, I learned a lot about this WeeWX and like it even more.

Great support everyone!

Thanks again!

Troy

On a side note - as for the wind look at the peak gusts for 2011, it was a pretty bad year up here. Peak gust was 142, my next door neighbor has a davis weather station too and he clocked 143 also so I'd say that was pretty close. I live on the top of a ridge in Colorado and it's beautiful, unless it's windy.... :-)

http://deadduck.net/weather/tabular.html?report=NOAA/NOAA-2011.txt

--

You received this message because you are subscribed to a topic in the Google Groups "weewx-user" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/weewx-user/ic4IK_-eX4Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/32200cdd-45e6-4620-a70f-f21896b2a78e%40googlegroups.com.

Thomas Keffer

unread,

Feb 7, 2020, 5:49:11 PM2/7/20

to weewx-user

Yay!

Reminds me that the "cleanup up bad data" article really needs an example that deals with time.

-tk

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/CALBrUnHSnSyD5nB7aDvcELVzOxHUiPE0hkRMqT69Mv1h1L87VQ%40mail.gmail.com.

Troy Lass

unread,

Feb 7, 2020, 6:23:14 PM2/7/20

to weewx...@googlegroups.com

Thomas,

I really appreciate all the work you put into this! I used to use wview and liked it but every time I updated the OS it was a fight to get the packages I needed to get it to work and there wasn't any real support. I was happy to find WeeWX the last time I was trying to get Wview to work after an upgrade.

Other than this last logger corruption issue, and that's not a SW issue, it's been flawless.

Adding the time example would be helpful but I got there.

Thanks for sticking in there with me on this!

-Troy

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEBb-aFUQYT2-iTAWqjdHQn-N68Z7F9ZRVj9O0qebHCaaw%40mail.gmail.com.

Troy Lass

unread,

Feb 7, 2020, 6:54:29 PM2/7/20

to weewx...@googlegroups.com

Ok, it looks like I spoke too fast. It worked for about 20 minutes. Console is up and working good.

I have a lot of things to try now and will play with it a little more over the weekend, like trying without the data logger but it's looking more like a bad data logger to me...

-Troy

Troy Lass

unread,

Feb 8, 2020, 9:19:49 PM2/8/20

to weewx...@googlegroups.com

Ok, at this point I'm convinced the data logger is bad and have ordered a new one.

Today I did made the following changes to the weewx.conf and restarted WeeWX...

record_generation = software

no_catchup = True

Since these changes I'm getting data from the console, prior after clearing the memory on the logger multiple times I got it to work and it stopped after only about 20 minutes.

Once I get the new data logger I'll revert the changes I made above and try to use the new data logger. I'll update this post with the results...

Thanks,

Troy

Troy Lass

unread,

Feb 11, 2020, 10:01:48 AM2/11/20

to weewx...@googlegroups.com

Ok, have new data logger installed and everything seems to be working as expected. I did have to do the following to get everything started but once I did that it's been working for 12 hours now. It appears I had a bad datalogger.

I had to enter...

wee_device --clear-memory

wee_device --start

and of course

weewx start

I do now have an issue with posting Weather Underground with my an authorization failure 401 error. I'm using the key as the password and have verified it's correct. I did try putting it in double quotes. I see many are having issues with WU now. I guess I'm going to have to try to create a new station..

I'm also having an issue with intermittent signal quality going to 0. I've had this issue before and have always had intermittent signal quality. The interesting thing is the console is about 25' from the station and I can see the station out of the window in a clear line of side from the console. What types of things can cause signal issues??

It's interesting that it looks "scheduled" and the big outage was when everything was overnight when I was in bed, no cell, no phone, no microwave, etc and out for hours... Doesn't make sense to me.

Reply all

Reply to author

Forward