Re: [weewx-user] How to limit syslog logging

[LeaF]

Disregard my last post! 

Taking Gary's suggestion, only line 78 needs to be commented out.  

On Friday, January 22, 2021 at 5:50:58 PM UTC-8 gjr80 wrote:

> Not sure why you are thanking me, you took no notice of what I suggested. 
> Commenting out log lines is a poor choice, in future if you ever want to 
> troubleshoot you have no means of obtaining any meaningful log info unless 
> you again modify source code. A better solution is to change the log level 
> of the noisy log output as i suggested so that it is only logged when you 
> run WeeWX with debug = 1. 
>
> Gary
> On Saturday, 23 January 2021 at 11:37:31 UTC+10 mksm...@gmail.com wrote:
>
>> Commenting out line 78 or line 107 only did not work, but Commenting out 
>> (line 78 & 107) did the trick. no more unnecessary writing to (/var/log)
>>
>> Thank you *vince & gjr80*
>>
>> On Saturday, January 23, 2021 at 3:16:42 AM UTC+3 gjr80 wrote:
>>
>>> If it's this one 
>>> 
>>>  
>>> then the only change that is needed is to change the loginf() call at 
>>> line 78 to logdbg(). Everything else should be left untouched. 
>>> Commenting out logging to fix a chatty log is really a case of cutting off 
>>> your nose to spite your face. Just like restarting WeeWX daily, far better 
>>> to engineer out the problem.
>>>
>>> Gary
>>>
>>> On Saturday, 23 January 2021 at 10:06:06 UTC+10 vince wrote:
>>>
 We'd have to see 'exactly' what code you have installed now in order to 
 help.   At this point we've seen so many partial descriptions that it's 
 impossible to know what exactly you're currently running and what error 
 messages you are seeing when you run that code.



-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/385a6ecd-b4fe-4c66-a05b-b0f7dfe4212en%40googlegroups.com.

Re: [weewx-user] How to limit syslog logging

[LeaF]

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 mksm...@gmail.com 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 tke...@gmail.com 
>> wrote:
>>
>>> Those things are generally set in /etc/rsyslog.d
>>>
>>> On Wed, Jan 20, 2021 at 10:54 AM LeaF  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 tke...@gmail.com 
>>>> 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  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.304, '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-use

Re: [weewx-user] How to limit syslog logging

[LeaF]

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 tke...@gmail.com wrote:

> Those things are generally set in /etc/rsyslog.d
>
> On Wed, Jan 20, 2021 at 10:54 AM LeaF  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 tke...@gmail.com 
>> 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  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.304, '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 weewx-user+...@googlegroups.com.
>>>> 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_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 weewx-user+...@googlegroups.com.
>>
> 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_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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/1ca1f295-9116-4ade-bccc-8ec496f8688dn%40googlegroups.com.

Re: [weewx-user] How to limit syslog logging

[LeaF]

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 tke...@gmail.com 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  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.304, '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 weewx-user+...@googlegroups.com.
>> 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_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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/08c304c3-aa29-4a12-a1ac-d0824643d2f7n%40googlegroups.com.

[weewx-user] How to limit syslog logging

[LeaF]

 

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.304, '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 weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7c9cae95-4bcd-4dd6-b293-2113d6a5054cn%40googlegroups.com.

Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 months of data?

[LeaF]

Mike,
You mentioned up above that you do a nightly backup to AWS S3 for the 
database.  Can you show us how that was accomplished?   (I followed your 
instructions on how to upload my weather data to S3, and it has worked 
perfectly. Thanks)
Lee

On Sunday, January 3, 2021 at 2:29:38 AM UTC-8 mi...@cougar.eu.com wrote:

> This was on of my main concerns when I first moved my WeeWX station to a 
> Raspberry Pi, so I have added a nightly backup to AWS S3 for the database 
> and as S3 now has versioning that will be my next addition so I have more 
> than one backup .
>
> I haven't gotten around to writing this up yet, but it has been working 
> uninterrupted for 213 days.
>
> If you want to know how I did it just reach out, the process is very 
> similar to my solution for publishing to S3 which I have just finished 
> writing up this week
>
> On Friday, January 1, 2021 at 8:35:37 PM UTC lang@googlemail.com 
> wrote:
>
>> @ (not only) weatherlist
>>
>> If you had copied the list completely,  
>>
>> See below - bold by me.
>>
>> (but possibly a SSD comes cheaper than the higher capacity SLC micro SD 
>> cards - still may need an enclosure with USB (best 3) interface; not too 
>> expensive either)
>>
>> .
>>
>> Meteobridge enforces the use of one of the following industrial SLC cards:
>>
>> ..
>>
>>- Western Digital/SanDisk SDSDQED-00*8G*-XI, SDSDQED-0*16G*-XI, 
>>SDSDQED-0*32G*-XI, SDSDQED-064G-XI (microSD Card, 8-*64* GB, SLC 
>>Flash) 
>>- Greenliant GLS93MP008G1-I-BZ801 (microSD Card, *8 GB*, SLC Flash) 
>>
>> On 01.01.2021 20:44, Michael Form wrote:
>>
>> As someone has previously suggested, you can boot and run a Raspberry Pi 
>> off of a SSD. These are a lot more reliable than most SD cards and are 
>> available with huge capacities. Unless you are buying a 1 TB or 2 TB SSD, 
>> they are also relatively inexpensive. I am running several Pis, both models 
>> 3 and 4, on some 500 GB and 250 GB SSDs with no problems. You can also use 
>> a MSATA or M2 drive as well. 
>>
>> Although there are off the shelf solutions to do this (check out 
>> Geekworm), the easiest way is to buy an inexpensive SATA, MSATA or M2 to 
>> USB external interface and plug it into the Pi's USB port. If you use a 
>> Pi4, then you can run it as a USB3 device, which is faster.
>>
>> Mike
>>
>> On 1/1/2021 2:21 PM, steep...@gmail.com wrote:
>>
>> There are more SLC cards available from Mouser and other distributors 
>> with much lager capacities. Those quoted below would struggle to contain an 
>> operating system, WeeWX and data.
>>
>>  
>>
>> Sent from Mail  for 
>> Windows 10
>>
>>  
>>
>> *From: *weather list
>> *Sent: *01 January 2021 17:32
>> *To: *weewx...@googlegroups.com
>> *Subject: *Re: [weewx-user] Re: Corrupted Memory card. Now I lost 6 
>> months of data?
>>
>>  
>>
>> The Meteobridge builder requires a high endurance microSD card for their 
>> NANO SD unit; I haven’t investigated to see if they come in higher 
>> capacities though it seems likely they would.
>>
>>  
>>
>> *Choice of microSD Card *
>>
>> To avoid lots of system fails caused by worn out consumer microSD cards 
>> we restrict microSD cards that can be used in the NANO to 1GB and 2GB 
>> industrial SLC cards. These are world-wide available from Mouser and other 
>> electronic distributors. We decided to enforce use of these high endurance 
>> cards to avoid having tons of unnecessary support requests and not to harm 
>> the reputation of the NANO SD by failed cards. Please trust in our 
>> experience with flash storage issues that there is simply no reasonable way 
>> to avoid buying of high-price, high-endurance SLC storage. These are the 
>> currently supported microSD cards: 
>>
>> swissbit SFSD1024N1BM1TO-I-DF-221-STD (microSD Card, 1 GB, SLC Flash, 
>> -40°C - 85°C)
>> swissbit SFSD2048N1BM1MT-I-ME-221-STD (microSD Card, 2 GB, SLC Flash, 
>> -40°C - 85°C) 
>>
>> swissbit SFSD2048N1BM1MT-E-ME-221-STD (microSD Card, 2 GB, SLC Flash, 
>> -25°C - 85°C)
>> ATP AF2GUDI (microSD Card, 2 GB, SLC Flash, -40°C – 80°C)
>> Cactus KS2GRIT-803M (microSD Card, 2 GB, SLC Flash, -45°C – 90°C)
>>
>> Panasonic SMSC02DA1 (microSD Card, 2 GB, SLC Flash, -40°C - 85°C)
>>
>> Apacer MSD02GIDI-T (microSD Card, 2 GB, SLC Flash) 
>>
>>
>>
>>
>>
>> On 1 Jan, 2021, at 08:52, Joe  wrote:
>>
>>  
>>
>> Sandisk extreme with the red and brown two tone color.  Unfortuantely, I 
>> did not have one of these in the PI at the time.  Though I do now.  I've 
>> never had one fail .
>>
>> On Monday, December 28, 2020 at 7:23:04 PM UTC-6 robcr...@gmail.com 
>> wrote:
>>
>> With all this talk about "good quality" SD cards, can anyone share a 
>> recommendation?
>>
>>  
>>
>> I have an SSD that I run my main WeeWX/HomeAssistant server on, but I 
>> have several others that I play around with, and need to get some new SD 
>> cards for that purpose, so I figure I may as well get some "good" ones.
>>
>>  
>>
>>