v3.9.1 crash adding rnon positive value record

38 views
Skip to first unread message

Invisible Man

unread,
Aug 5, 2019, 4:46:23 PM8/5/19
to weewx-user
Hi there,
I am running WeeWx v3.9.1 on a Raspberry Pi, with a WMR200.
I got the following crash of Weewx. I am wondering if this is a known issue and solved in v3.9.2 by

"Fixed problem that could cause the WMR200 to crash WeeWX if the record
interval is zero. Fixes issue #375."

This is the crash log:

Aug 5 11:11:35 localhost weewx[871]: **** File "/usr/share/weewx/weewx/engine.py", line 601, in new_archive_record
Aug 5 11:11:35 localhost weewx[871]: **** dbmanager.addRecord(event.record, accumulator=self.old_accumulator)
Aug 5 11:11:35 localhost weewx[871]: **** File "/usr/share/weewx/weewx/manager.py", line 246, in addRecord
Aug 5 11:11:35 localhost weewx[871]: **** self._addSingleRecord(record, cursor, log_level)
Aug 5 11:11:35 localhost weewx[871]: **** File "/usr/share/weewx/weewx/manager.py", line 1212, in _addSingleRecord
Aug 5 11:11:35 localhost weewx[871]: **** _weight = self._calc_weight(record)
Aug 5 11:11:35 localhost weewx[871]: **** File "/usr/share/weewx/weewx/manager.py", line 1582, in _calc_weight
Aug 5 11:11:35 localhost weewx[871]: **** raise ValueError("Non-positive value for record field 'interval': %s" % (record['interval'], ))
Aug 5 11:11:35 localhost weewx[871]: **** ValueError: Non-positive value for record field 'interval': 0
Aug 5 11:11:35 localhost weewx[871]: **** Exiting.

Thanks
Axelle

Thomas Keffer

unread,
Aug 5, 2019, 4:48:45 PM8/5/19
to weewx...@googlegroups.com
Yup. That’s the issue fixed by 3.9.2

--
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/8030e2b1-7372-49f0-ba05-f15a38b16a15%40googlegroups.com.
--
-tk

Invisible Man

unread,
Aug 7, 2019, 4:31:35 PM8/7/19
to weewx-user
On Monday, August 5, 2019 at 10:48:45 PM UTC+2, Thomas Keffer wrote:
Yup. That’s the issue fixed by 3.9.2

Thanks !

-- Axelle

Reply all
Reply to author
Forward
0 new messages