if you have a wmr200 see this post and the fix https://groups.google.com/forum/#!msg/weewx-user/69RvQnD_OQc/M_8q8sDoAgAJ
On Sunday, 3 March 2019 18:34:22 UTC+2, Mark Jenks wrote: > > Crashing has a different message now. Before a week ago, I was still > running 3.8.1, and was still catching crashes with my script. > > I don't know if I can go back that far, but I think this is closer to my > problem why I wrote the script. > > -Mark > > > Mar 3 04:44:37 server weewx[7844]: wmr200: Thread-2: E read_device() USB > Error Reason:[Errno 110] Operation timed out > Mar 3 04:44:37 server weewx[7844]: wmr200: Thread-2: E USB device read > error > Mar 3 04:44:37 server weewxd: LOOP: 2019-03-03 04:43:50 CST > (1551609Exception in thread Thread-2: > Mar 3 04:44:37 server weewxd: Traceback (most recent call last): > Mar 3 04:44:37 server weewxd: File "/usr/lib64/python2.7/threading.py", > line 811, in __bootstrap_inner > Mar 3 04:44:37 server weewxd: self.run() > Mar 3 04:44:37 server weewxd: File > "/home/weewx/bin/weewx/drivers/wmr200.py", line 1278, in run > Mar 3 04:44:37 server weewxd: buf = self.usb_device.read_device() > Mar 3 04:44:37 server weewxd: File > "/home/weewx/bin/weewx/drivers/wmr200.py", line 285, in read_device > Mar 3 04:44:37 server weewxd: raise weewx.WeeWxIOError(msg) > Mar 3 04:44:37 server weewxd: WeeWxIOError: read_device() USB Error > Reason:[Errno 110] Operation timed out > Mar 3 04:44:38 server weewx[7844]: wmr200: MainThread: E USB polling > thread unexpectedly terminated > Mar 3 04:44:38 server weewx[7844]: engine: Main loop exiting. Shutting > engine down. > Mar 3 04:44:38 server weewx[7844]: engine: Shutting down StdReport thread > > > On Friday, March 1, 2019 at 5:11:13 PM UTC-6, Thomas Keffer wrote: >> >> OK, see this post >> <https://groups.google.com/d/msg/weewx-user/69RvQnD_OQc/M_8q8sDoAgAJ>. >> >> -tk >> >> On Fri, Mar 1, 2019 at 1:53 PM Mark Jenks <[email protected]> wrote: >> >>> Yes, it is a WMR200. Eventually changed for something newer in a few >>> months. >>> >>> -Mark >>> >>> >>> On Tuesday, February 26, 2019 at 6:49:13 AM UTC-6, Thomas Keffer wrote: >>>> >>>> Is this, by any chance, a WMR200 or WS28xx? >>>> >>>> -tk >>>> >>>> On Tue, Feb 26, 2019 at 4:30 AM Mark Jenks <[email protected]> wrote: >>>> >>>>> Got one last night.... >>>>> >>>>> Feb 25 22:29:41 server weewx[7721]: wmr200: MainThread: I Driver >>>>> gracefully exiting >>>>> Feb 25 22:29:41 server weewx[7721]: engine: Caught unrecoverable >>>>> exception in engine: >>>>> Feb 25 22:29:41 server weewx[7721]: **** Non-positive value for >>>>> record field 'interval': 0 >>>>> Feb 25 22:29:41 server weewx[7721]: **** Traceback (most recent call >>>>> last): >>>>> Feb 25 22:29:41 server weewx[7721]: **** File >>>>> "/home/weewx/bin/weewx/engine.py", line 890, in main >>>>> Feb 25 22:29:41 server weewx[7721]: **** engine.run() >>>>> Feb 25 22:29:41 server weewx[7721]: **** File >>>>> "/home/weewx/bin/weewx/engine.py", line 160, in run >>>>> Feb 25 22:29:41 server weewx[7721]: **** >>>>> self.dispatchEvent(weewx.Event(weewx.STARTUP)) >>>>> Feb 25 22:29:41 server weewx[7721]: **** File >>>>> "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent >>>>> Feb 25 22:29:41 server weewx[7721]: **** callback(event) >>>>> Feb 25 22:29:41 server weewx[7721]: **** File >>>>> "/home/weewx/bin/weewx/engine.py", line 520, in startup >>>>> Feb 25 22:29:41 server weewx[7721]: **** >>>>> self._catchup(self.engine.console.genStartupRecords) >>>>> Feb 25 22:29:41 server weewx[7721]: **** File >>>>> "/home/weewx/bin/weewx/engine.py", line 635, in _catchup >>>>> Feb 25 22:29:41 server weewx[7721]: **** origin='hardware')) >>>>> Feb 25 22:29:41 server weewx[7721]: **** File >>>>> "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent >>>>> Feb 25 22:29:41 server weewx[7721]: **** callback(event) >>>>> Feb 25 22:29:41 server weewx[7721]: **** File >>>>> "/home/weewx/bin/weewx/engine.py", line 601, in new_archive_record >>>>> Feb 25 22:29:41 server weewx[7721]: **** >>>>> dbmanager.addRecord(event.record, accumulator=self.old_accumulator) >>>>> Feb 25 22:29:41 server weewx[7721]: **** File >>>>> "/home/weewx/bin/weewx/manager.py", line 246, in addRecord >>>>> Feb 25 22:29:41 server weewx[7721]: **** >>>>> self._addSingleRecord(record, cursor, log_level) >>>>> Feb 25 22:29:41 server weewx[7721]: **** File >>>>> "/home/weewx/bin/weewx/manager.py", line 1212, in _addSingleRecord >>>>> Feb 25 22:29:41 server weewx[7721]: **** _weight = >>>>> self._calc_weight(record) >>>>> Feb 25 22:29:41 server weewx[7721]: **** File >>>>> "/home/weewx/bin/weewx/manager.py", line 1582, in _calc_weight >>>>> Feb 25 22:29:41 server weewx[7721]: **** raise >>>>> ValueError("Non-positive value for record field 'interval': %s" % >>>>> (record['interval'], )) >>>>> Feb 25 22:29:41 server weewx[7721]: **** ValueError: Non-positive >>>>> value for record field 'interval': 0 >>>>> Feb 25 22:29:41 server weewx[7721]: **** Exiting. >>>>> >>>>> >>>>> On Saturday, February 23, 2019 at 4:34:06 PM UTC-6, mwall wrote: >>>>>> >>>>>> On Saturday, February 23, 2019 at 10:36:45 AM UTC-5, Mark Jenks wrote: >>>>>>> >>>>>>> I've been running this for a few years now, and once and awhile >>>>>>> weewx just falls over for no good reason. To deal with this, I wrote >>>>>>> a >>>>>>> script that I run in cron to check to make sure it's running, and if >>>>>>> not, >>>>>>> start it over again. >>>>>>> >>>>>> >>>>>> mark, >>>>>> >>>>>> systemctl is supposed to do that for you. >>>>>> >>>>>> in fact, this thread shows that it does, at least in one case: >>>>>> >>>>>> https://groups.google.com/forum/#!topic/weewx-user/bspZEoGqpyY >>>>>> >>>>>> but as tom points out, we really want to know when weewx stops >>>>>> running so that we can fix it. >>>>>> >>>>>> if you need to use a script (or systemctl) to ensure that weewx is >>>>>> automatically restarted, perhaps you could figure out some way to >>>>>> capture >>>>>> and report the log leading up to the crash? >>>>>> >>>>>> m >>>>>> >>>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "weewx-user" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>> You received this message because you are subscribed to the Google >>> Groups "weewx-user" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
