Just installed 4.3.0 and now won't start

97 views
Skip to first unread message

Russell Cutcliffe

unread,
Jan 7, 2021, 7:00:29 AM1/7/21
to weewx-user
Hi, I just upgraded to Weewx 4.3.0 via apt upgrade in
Ubuntu 20.04.1, and now Weewx isn't starting.

Syslog gives this:
$ sudo weewxd --config /etc/weewx/weewx.conf
Daily summaries at V2.0. Patching to V3.0
Traceback (most recent call last):0:00 AEST (1605535200)
  File "/usr/share/weewx/weewxd", line 261, in <module>
    main()
  File "/usr/share/weewx/weewxd", line 148, in main
    engine = weewx.engine.StdEngine(config_dict)
  File "/usr/share/weewx/weewx/engine.py", line 93, in __init__
    self.loadServices(config_dict)
  File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
    obj = weeutil.weeutil.get_object(svc)(self, config_dict)
  File "/usr/share/weewx/weewx/wxservices.py", line 38, in __init__
    self.db_manager = engine.db_binder.get_manager(data_binding=data_binding, initialize=True)
  File "/usr/share/weewx/weewx/manager.py", line 534, in get_manager
    self.manager_cache[data_binding] = open_manager(manager_dict, initialize)
  File "/usr/share/weewx/weewx/manager.py", line 682, in open_manager
    return manager_cls.open_with_create(manager_dict['database_dict'],
  File "/usr/share/weewx/weewx/manager.py", line 164, in open_with_create
    dbmanager = cls(connection, table_name=table_name, schema=schema)
  File "/usr/share/weewx/weewx/manager.py", line 831, in __init__
    self.patch_sums()
  File "/usr/share/weewx/weewx/manager.py", line 1255, in patch_sums
    self.recalculate_weights(start_d=datetime.date(2020,6,1))
  File "/usr/share/weewx/weewx/manager.py", line 1182, in recalculate_weights
    self._do_tranche(mark_d, end_of_tranche_d, weight_fn, progress_fn)
  File "/usr/share/weewx/weewx/manager.py", line 1215, in _do_tranche
    weight = weight_fn(self, rec)
  File "/usr/share/weewx/weewx/manager.py", line 1365, in _calc_weight
    raise IntervalError(
weewx.manager.IntervalError: Non-positive value for record field 'interval': 0

I'm using the interceptor driver (with indifferent results of late) but it was running, at least before the upgrade.
Hopefully I'm missing something simple..
Any ideas?

gjr80

unread,
Jan 7, 2021, 7:04:16 AM1/7/21
to weewx-user
Hi,

You might want to have a look at this thread. V4.3.0 is a little more fussy about field interval.

Gary

Russell Cutcliffe

unread,
Jan 7, 2021, 7:07:02 AM1/7/21
to weewx-user
Sorry, logfile snippet at https://pastebin.com/fxrcgSLg

Russell C

Russell Cutcliffe

unread,
Jan 7, 2021, 6:17:26 PM1/7/21
to weewx-user
Yep, that fixed it.
Now to fix the startup issue that's appeared...

vince

unread,
Jan 7, 2021, 6:34:20 PM1/7/21
to weewx-user
On Thursday, January 7, 2021 at 3:17:26 PM UTC-8 Russell Cutcliffe wrote:
Now to fix the startup issue that's appeared...

We can't help without seeing logs to see what 'issue' you are referring to.

I know you're on ubuntu, but I wanted to pass along one edge case I noticed yesterday.  If you're on CentOS and have selinux=enforcing, it is possible that your weewx won't start successfully, depending on how you chose to install it.   On the CentOS platforms, I just set selinux to disabled and it all works fine.   Not the right thing if I ran a real CentOS site of course, but given I just fiddle occasionally LAN-only in Vagrant/VirtualBox I thought I'd take the easy way out.  Bottom line of course is understand your os and check all your logs with debug=1 enabled for debugging.
 
Reply all
Reply to author
Forward
0 new messages