Found these line in the file bme280wx.py
---------------------------------------
def logmsg(level, msg):
syslog.syslog(level, 'bme280: %s' % msg)
def logdbg(msg):
logmsg(syslog.LOG_DEBUG, msg)
def loginf(msg):
logmsg(syslog.LOG_INFO, msg)
def logerr(msg):
logmsg(syslog.LOG_ERR, msg)
-------------------------------------
I changed 2nd line as suggested
#def logdbg(msg):
# logmsg(syslog.LOG_DEBUG, msg)
started weewx and fail to run with this log below
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: Caught
unrecoverable exception:
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: **** global
name 'logdbg' is not defined
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: ****
Traceback (most recent call last):
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: **** File
"/usr/share/weewx/weewxd", line 154, in main
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: ****
engine.run()
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: **** File
"/usr/share/weewx/weewx/engine.py", line 210, in run
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: ****
self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: **** File
"/usr/share/weewx/weewx/engine.py", line 245, in dispatchEvent
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: ****
callback(event)
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: **** File
"/usr/share/weewx/user/bme280wx.py", line 107, in new_loop_packet
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: ****
logdbg(packet)
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: ****
NameError: global name 'logdbg' is not defined
Jan 22 21:05:13 raspberrypi weewx[7491] CRITICAL __main__: ****
Exiting.
I am not sure but I may have different bme280wx.py than yours.
I used this link (https://gitlab.com/wjcarpenter/bme280wx) during the
installation for this driver and it worked fine with weewx 3.92 but when
(https://github.com/merbanan/rtl_433) made alot of changes for Acurite
devices and no one seem to be looking after
(https://github.com/matthewwall/weewx-sdr) (sdr.py) and weewx got updated
further thats where things got lost and we are struggling with these
problems.
I truly appreciate your help
On Friday, January 22, 2021 at 8:01:05 PM UTC+3 LeaF wrote:
> Edit the bme280wx.py file and comment out anything you don't want logged.
> For example, I commented out the following lines in the file:
>
> #def logdbg(msg):
> # logmsg(syslog.LOG_DEBUG, msg).
>
> You'll need to review the entire file for other lines that are writing to
> a log file and determine whether or not you want that information logged.
>
>
>
> On Thursday, January 21, 2021 at 9:26:55 AM UTC-8 [email protected] wrote:
>
>> Dear Leaf
>> need your help to correct my system because I am having the same issue of
>> logging so kindly advice of the correction to done to bme280wx.py and which
>> lines to be commented.
>>
>> thanks
>>
>> On Wednesday, January 20, 2021 at 10:11:22 PM UTC+3 LeaF wrote:
>>
>>> So taking your advice, I looked into the bme280wx.py file and noticed
>>> that there were a number of places where it was writing out information to
>>> various file; syslog, debug and user. When I commented those lines out,
>>> voila no more excessive logging.
>>> Thanks again tk
>>> Lee
>>>
>>> On Wednesday, January 20, 2021 at 10:58:46 AM UTC-8 [email protected]
>>> wrote:
>>>
>>>> Those things are generally set in /etc/rsyslog.d
>>>>
>>>> On Wed, Jan 20, 2021 at 10:54 AM LeaF <[email protected]> wrote:
>>>>
>>>>> tk
>>>>> Thanks for the observation. I'll do some snooping around the bme280
>>>>> and see what I can find.
>>>>>
>>>>> (It's not only syslog getting overwhelmed with entries, but debug and
>>>>> user log files are filled with the same info)
>>>>>
>>>>> Thanks
>>>>> Lee
>>>>>
>>>>> On Wednesday, January 20, 2021 at 10:50:01 AM UTC-8 [email protected]
>>>>> wrote:
>>>>>
>>>>>> It looks like an extension you are using, bme280, is what is creating
>>>>>> the chatter. Unfortunately, from the little log snippet you gave, it
>>>>>> does
>>>>>> not appear to be WeeWX V4 compliant, so muzzling it will not be as easy
>>>>>> as
>>>>>> a weewx.conf setting. You could ask the author to update it to V4, then
>>>>>> you
>>>>>> could follow the directions in the Wiki article *WeeWX V4 and
>>>>>> logging <https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging>*.
>>>>>>
>>>>>> OTOH, fortunately, it looks like the log entry is a debug entry, so
>>>>>> setting debug=0 in weewx.conf should help reduce the number of entries.
>>>>>>
>>>>>> -tk
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Jan 20, 2021 at 10:39 AM LeaF <[email protected]> wrote:
>>>>>>
>>>>>>> I have a question regarding what goes into the /var/log/syslog file.
>>>>>>>
>>>>>>> I’m running the latest version of weewx on a Raspberry Pi 4. My
>>>>>>> station is a Peet Bros Ultimeter 100. I also added a Adafruit BME280
>>>>>>> breakout board to measure pressure and humidity.
>>>>>>>
>>>>>>> This all works very well. Thank you
>>>>>>>
>>>>>>> When I run sudo tail -f /var/log/syslog, there appears to be three
>>>>>>> entries per second being written to the log file. So as you can
>>>>>>> imagine, the log file has a lot of info that I don’t want in there.
>>>>>>> Any errors are being written to weewx.log file.
>>>>>>>
>>>>>>> How can I limit what is going to the log file so they don’t grow so
>>>>>>> large? I looked at rsyslog.conf, but don’t know if this is the
>>>>>>> correct place to limit the log entries.
>>>>>>>
>>>>>>> Example, one entry into log file:
>>>>>>>
>>>>>>> Jan 20 10:22:47 WeatherPi /weewxd: bme280: {'dateTime':
>>>>>>> 1611166967, 'usUnits': 1, 'windSpeed': 0.0, 'windDir': 55.058796,
>>>>>>> 'outTemp': 38.300000000000004, 'rain_total': 0.5, 'barometer': None,
>>>>>>> 'inTemp': None, 'outHumidity': 77.02371597125266, 'inHumidity': None,
>>>>>>> 'day_of_year': 19, 'minute_of_day': 620, 'daily_rain': 0.0,
>>>>>>> 'wind_average':
>>>>>>> 0.0, 'rain': 0.0, 'pressure': 29.53154056121909}
>>>>>>>
>>>>>>> Thanks for your help.
>>>>>>>
>>>>>>> Lee
>>>>>>>
>>>>>>> --
>>>>>>> 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/7c9cae95-4bcd-4dd6-b293-2113d6a5054cn%40googlegroups.com
>>>>>>>
>>>>>>> <https://groups.google.com/d/msgid/weewx-user/7c9cae95-4bcd-4dd6-b293-2113d6a5054cn%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>> .
>>>>>>>
>>>>>> --
>>>>> 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/08c304c3-aa29-4a12-a1ac-d0824643d2f7n%40googlegroups.com
>>>>>
>>>>> <https://groups.google.com/d/msgid/weewx-user/08c304c3-aa29-4a12-a1ac-d0824643d2f7n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>
--
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/b5602945-f37a-4179-bc06-256e548154c7n%40googlegroups.com.
