You may be right. I have followed the log through and I cannot see the
casue, it is almost as if the restart after the database error results in
an instance of the interceptor driver that is in a confused state. There
were some substantial changes to the WeeWX engine code in v4.0, not so much
the code itself but a good deal was moved from engine.py to weewxd. Perhaps
there is some unusual effect going on. I think this is one for Matthew or
Tom.
The vibe I get from your posts is that jthis is not a one off occurrence,
but it does happen semi-regularly. In that case as a workaround you could
make a small patch to the interceptor driver. In
usr/share/weewx/user/interceptor.py locate the following lines (circa line
2395):
if 'totalrainin' not in data and 'yearlyrainin' in data:
self.LABEL_MAP.pop('totalrainin')
self.LABEL_MAP['yearlyrainin'] = 'rain_total'
and change it to read:
if 'totalrainin' not in data and 'yearlyrainin' in data:
if 'totalrainin' in self.LABEL_MAP:
self.LABEL_MAP.pop('totalrainin')
self.LABEL_MAP['yearlyrainin'] = 'rain_total'
Save and restart WeeWX. That will prevent the specific error you originally
posted but if other oddball issues come up they may well still bring down
WeeWX. If it doesn't cause a problem it might be worth continuing to
run/monitor the logs with debug = 1 for the time being.
Gary
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/c9a58846-6e94-4439-a211-82e9b6feeab3o%40googlegroups.com.
