[weewx-user] Re: Limiting weewx logging only to error/fail

[Andrew Milner]

Another method is to not use syslog at all!!  
Diverted weewx log messages to a separate log file (see the wiki) so they 
never clutter syslog and receive a daily weewx email giving the log summary 
for the previous day (see logwatch in wiki).  syslog thus remains 
unaffected by weewx.  This has an added advantage in that debugging levels 
can be set also without cluttering the syslog.

A monitoring program is obviously the best to maintain integrity - my 
option was intended to mean that having regular logged messages does allow 
one to pinpoint and spot possible issues caused by situations which do not 
necessarily result in weewx stopping - weewx is very reliable and rarely, 
if ever, crashes without recovering itself and there being no need for 
manual intervention.



On Thursday, 7 December 2017 08:04:54 UTC+2, Daniel Jönsson wrote:

> No. To make shore processes are running you use a monitoring tool. For 
> example Monit.
> The problem with one process flooding the syslog, is that errors not 
> declared in monitoring tools, are missed because you cant find them by 
> reading the log.
> And for shore no other programs/servers/process I have ever had running on 
> the server behaves this way (except Home Assistant, which is also written i 
> Python). 
>
> For examepl now (since I changed the conf for rsyslog 10 hours ago) in my 
> syslog I have 120 lines. All are from weewx and looks like this:
>
> Dec  6 11:50:50 server weewx[30571]: manager: added record 2017-12-06 
> 11:47:01 CET (1512557221) to database 'weewx'
> Dec  6 11:50:50 server weewx[30571]: manager: added record 2017-12-06 
> 11:47:01 CET (1512557221) to daily summary in 'weewx'
>
>
> Exept ONE line that says:
>
> Dec  6 11:46:50 server weewx[30571]: fousb: get_observations failed: ignoring 
> suspected bogus data from 0xbe40 (delay=5 interval=5)
>
>
> This one I want to be in sys log. And the only reason I saw this is 
> because I was looking for an example of important messages getting lost. I 
> would never have seen this if I was reading through the log next week. Then 
> there would be 1 000 lines of successful reading, and 1 line of an error.
>
>
> Den torsdag 7 december 2017 kl. 04:41:25 UTC+1 skrev Andrew Milner:
>>
>> Just a thought for you to think about.  You may find it helpful to retain 
>> the 'record added' log information just to make it easier to see if weewx 
>> is running normally or if it has stopped (as in the case of an obscure bug 
>> that did not cause an error message) - although I accept that that could be 
>> determined from examination of the database.
>>
>>
>> On Wednesday, 6 December 2017 21:29:25 UTC+2, Daniel Jönsson wrote:
>>
>>> Something strange here with Google groups. Sorry if double posting now, 
>>> but my messages are dispersing..
>>>
>>> I have now made changes to rsyslog config, to only log messages with 
>>> level 5 and above, and weewx is still flooding my syslog with the following 
>>> two lines every 5 minutes:
>>>
>>> Dec  6 19:51:03 server weewx[30571]: manager: added record 2017-12-06 
>>> 19:51:00 CET (1512586260) to database 'weewx'
>>> Dec  6 19:51:03 server weewx[30571]: manager: added record 2017-12-06 
>>> 19:51:00 CET (1512586260) to daily summary in 'weewx'
>>>
>>>
>>> How could this be considered "normal but significant condition" as per RFC 
>>> 5424? I would vote for that to be level 6 (info)
>>>
>>>
>>> And here is my weewx.conf:
>>> # WEEWX CONFIGURATION FILE
>>> #
>>> # Copyright (c) 2009-2015 Tom Keffer 
>>> # See the file LICENSE.txt for your rights.
>>>
>>>
>>> ##
>>>
>>> # This section is for general configuration information.
>>>
>>> # Set to 1 for extra debug info, otherwise comment it out or set to zero
>>> debug = 0
>>>
>>> # Root directory of the weewx data file hierarchy for this station
>>> WEEWX_ROOT = /
>>>
>>> # How long to wait before timing out a socket (FTP, HTTP) connection
>>> socket_timeout = 20
>>>
>>> # Do not modify this. It is used when installing and updating weewx.
>>> version = 3.6.1
>>>
>>>
>>> ##
>>>
>>> #   This section is for information about the station.
>>>
>>> [Station]
>>> 
>>> # Description of the station location
>>> location = "Munka Ljungby, Sweden"
>>> 
>>> # Latitude and longitude in decimal degrees
>>> latitude = 56.261
>>> longitude = 12.988
>>> 
>>> # Altitude of the station, with unit it is in. This is downloaded 
>>> from
>>> # from the station if the hardware supports it.
>>> altitude = 53, meter
>>> 
>>> # Set to type of station hardware. There must be a corresponding 
>>> stanza
>>> # in this file with a 'driver' parameter indicating the driver to be 
>>> used.
>>> station_type = FineOffsetUSB
>>> 
>>> # If you have a website, you may specify an URL
>>> #station_url = 

[weewx-user] Re: Limiting weewx logging only to error/fail

[Daniel Jönsson]

No. To make shore processes are running you use a monitoring tool. For 
example Monit.
The problem with one process flooding the syslog, is that errors not 
declared in monitoring tools, are missed because you cant find them by 
reading the log.
And for shore no other programs/servers/process I have ever had running on 
the server behaves this way (except Home Assistant, which is also written i 
Python). 

For examepl now (since I changed the conf for rsyslog 10 hours ago) in my 
syslog I have 120 lines. All are from weewx and looks like this:

Dec  6 11:50:50 server weewx[30571]: manager: added record 2017-12-06 11:47:01 
CET (1512557221) to database 'weewx'
Dec  6 11:50:50 server weewx[30571]: manager: added record 2017-12-06 11:47:01 
CET (1512557221) to daily summary in 'weewx'


Exept ONE line that says:

Dec  6 11:46:50 server weewx[30571]: fousb: get_observations failed: ignoring 
suspected bogus data from 0xbe40 (delay=5 interval=5)


This one I want to be in sys log. And the only reason I saw this is because 
I was looking for an example of important messages getting lost. I would 
never have seen this if I was reading through the log next week. Then there 
would be 1 000 lines of successful reading, and 1 line of an error.


Den torsdag 7 december 2017 kl. 04:41:25 UTC+1 skrev Andrew Milner:
>
> Just a thought for you to think about.  You may find it helpful to retain 
> the 'record added' log information just to make it easier to see if weewx 
> is running normally or if it has stopped (as in the case of an obscure bug 
> that did not cause an error message) - although I accept that that could be 
> determined from examination of the database.
>
>
> On Wednesday, 6 December 2017 21:29:25 UTC+2, Daniel Jönsson wrote:
>
>> Something strange here with Google groups. Sorry if double posting now, 
>> but my messages are dispersing..
>>
>> I have now made changes to rsyslog config, to only log messages with 
>> level 5 and above, and weewx is still flooding my syslog with the following 
>> two lines every 5 minutes:
>>
>> Dec  6 19:51:03 server weewx[30571]: manager: added record 2017-12-06 
>> 19:51:00 CET (1512586260) to database 'weewx'
>> Dec  6 19:51:03 server weewx[30571]: manager: added record 2017-12-06 
>> 19:51:00 CET (1512586260) to daily summary in 'weewx'
>>
>>
>> How could this be considered "normal but significant condition" as per RFC 
>> 5424? I would vote for that to be level 6 (info)
>>
>>
>> And here is my weewx.conf:
>> # WEEWX CONFIGURATION FILE
>> #
>> # Copyright (c) 2009-2015 Tom Keffer 
>> # See the file LICENSE.txt for your rights.
>>
>>
>> ##
>>
>> # This section is for general configuration information.
>>
>> # Set to 1 for extra debug info, otherwise comment it out or set to zero
>> debug = 0
>>
>> # Root directory of the weewx data file hierarchy for this station
>> WEEWX_ROOT = /
>>
>> # How long to wait before timing out a socket (FTP, HTTP) connection
>> socket_timeout = 20
>>
>> # Do not modify this. It is used when installing and updating weewx.
>> version = 3.6.1
>>
>>
>> ##
>>
>> #   This section is for information about the station.
>>
>> [Station]
>> 
>> # Description of the station location
>> location = "Munka Ljungby, Sweden"
>> 
>> # Latitude and longitude in decimal degrees
>> latitude = 56.261
>> longitude = 12.988
>> 
>> # Altitude of the station, with unit it is in. This is downloaded from
>> # from the station if the hardware supports it.
>> altitude = 53, meter
>> 
>> # Set to type of station hardware. There must be a corresponding 
>> stanza
>> # in this file with a 'driver' parameter indicating the driver to be 
>> used.
>> station_type = FineOffsetUSB
>> 
>> # If you have a website, you may specify an URL
>> #station_url = http://www.example.com
>> 
>> # The start of the rain year (1=January; 10=October, etc.). This is
>> # downloaded from the station if the hardware supports it.
>> rain_year_start = 1
>> 
>> # Start of week (0=Monday, 6=Sunday)
>> week_start = 0
>>
>>
>> ##
>>
>> [FineOffsetUSB]
>> # This section is for the Fine Offset series of weather stations.
>> 
>> # The station model, e.g., WH1080, WS1090, WS2080, WH3081
>> model = WS1080
>> 
>> # How often to poll the station for data, in seconds
>> polling_interval = 60
>> 
>> # The driver to use:
>> driver = weewx.drivers.fousb
>> 
>> # Filter unreal values:
>> max_rain_rate = 15# measured in cm/hr
>>
>>
>> ##
>>
>> #   This section is for uploading data to Internet sites
>>
>> [StdRESTful]
>> log_success = False

[weewx-user] Re: Limiting weewx logging only to error/fail

[Andrew Milner]

Just a thought for you to think about.  You may find it helpful to retain 
the 'record added' log information just to make it easier to see if weewx 
is running normally or if it has stopped (as in the case of an obscure bug 
that did not cause an error message) - although I accept that that could be 
determined from examination of the database.


On Wednesday, 6 December 2017 21:29:25 UTC+2, Daniel Jönsson wrote:

> Something strange here with Google groups. Sorry if double posting now, 
> but my messages are dispersing..
>
> I have now made changes to rsyslog config, to only log messages with level 
> 5 and above, and weewx is still flooding my syslog with the following two 
> lines every 5 minutes:
>
> Dec  6 19:51:03 server weewx[30571]: manager: added record 2017-12-06 
> 19:51:00 CET (1512586260) to database 'weewx'
> Dec  6 19:51:03 server weewx[30571]: manager: added record 2017-12-06 
> 19:51:00 CET (1512586260) to daily summary in 'weewx'
>
>
> How could this be considered "normal but significant condition" as per RFC 
> 5424? I would vote for that to be level 6 (info)
>
>
> And here is my weewx.conf:
> # WEEWX CONFIGURATION FILE
> #
> # Copyright (c) 2009-2015 Tom Keffer 
> # See the file LICENSE.txt for your rights.
>
>
> ##
>
> # This section is for general configuration information.
>
> # Set to 1 for extra debug info, otherwise comment it out or set to zero
> debug = 0
>
> # Root directory of the weewx data file hierarchy for this station
> WEEWX_ROOT = /
>
> # How long to wait before timing out a socket (FTP, HTTP) connection
> socket_timeout = 20
>
> # Do not modify this. It is used when installing and updating weewx.
> version = 3.6.1
>
>
> ##
>
> #   This section is for information about the station.
>
> [Station]
> 
> # Description of the station location
> location = "Munka Ljungby, Sweden"
> 
> # Latitude and longitude in decimal degrees
> latitude = 56.261
> longitude = 12.988
> 
> # Altitude of the station, with unit it is in. This is downloaded from
> # from the station if the hardware supports it.
> altitude = 53, meter
> 
> # Set to type of station hardware. There must be a corresponding stanza
> # in this file with a 'driver' parameter indicating the driver to be 
> used.
> station_type = FineOffsetUSB
> 
> # If you have a website, you may specify an URL
> #station_url = http://www.example.com
> 
> # The start of the rain year (1=January; 10=October, etc.). This is
> # downloaded from the station if the hardware supports it.
> rain_year_start = 1
> 
> # Start of week (0=Monday, 6=Sunday)
> week_start = 0
>
>
> ##
>
> [FineOffsetUSB]
> # This section is for the Fine Offset series of weather stations.
> 
> # The station model, e.g., WH1080, WS1090, WS2080, WH3081
> model = WS1080
> 
> # How often to poll the station for data, in seconds
> polling_interval = 60
> 
> # The driver to use:
> driver = weewx.drivers.fousb
> 
> # Filter unreal values:
> max_rain_rate = 15# measured in cm/hr
>
>
> ##
>
> #   This section is for uploading data to Internet sites
>
> [StdRESTful]
> log_success = False # default is True
> log_failure = True  # default is True
> 
> [[StationRegistry]]
> # To register this weather station with weewx, set this to true
> register_this_station = false
> 
> [[AWEKAS]]
> # This section is for configuring posts to AWEKAS.
> 
> # If you wish to do this, set the option 'enable' to true,
> # and specify a username and password.
> enable = false
> username = replace_me
> password = replace_me
> 
> [[CWOP]]
> # This section is for configuring posts to CWOP.
> 
> # If you wish to do this, set the option 'enable' to true,
> # and specify the station ID (e.g., CW1234).
> enable = false
> station = replace_me
> 
> # If this is an APRS (radio amateur) station, uncomment
> # the following and replace with a passcode (e.g., 12345).
> #passcode = replace_me (APRS stations only)
> 
> [[PWSweather]]
> # This section is for configuring posts to PWSweather.com.
> 
> # If you wish to do this, set the option 'enable' to true,
> # and specify a station and password.
> enable = false
> station = replace_me
> password = replace_me
> 
> [[WOW]]
> # This section is for configuring posts to WOW.
> 
> # If you wish to do this, set the option 

[weewx-user] Re: Limiting weewx logging only to error/fail

[Daniel Jönsson]

Sorry for late answer. Been away for work.

All this I see in syslog:

Dec  6 10:40:28 server weewx[30571]: fousb: synchronising to the weather 
station (quality=1)
Dec  6 10:41:14 server weewx[30571]: manager: added record 2017-12-06 10:37:01 
CET (1512553021) to database 'weewx'
Dec  6 10:41:14 server weewx[30571]: manager: added record 2017-12-06 10:37:01 
CET (1512553021) to daily summary in 'weewx'
Dec  6 10:41:15 server weewx[30571]: GaugeGenerator: Generated 6 images for 
HTMLPages in 0.19 seconds
Dec  6 10:41:15 server weewx[30571]: translategenerator.pyc: Language is swedish
Dec  6 10:41:15 server weewx[30571]: historygenerator.pyc: Generated 6 tables 
in 0.33 seconds
Dec  6 10:41:16 server weewx[30571]: cheetahgenerator: Generated 10 files for 
report HTMLPages in 1.68 seconds
Dec  6 10:41:16 server weewx[30571]: reportengine: copied 0 files to 
/var/www/weewx/Bootstrap
Dec  6 10:41:16 server weewx[30571]: translategenerator.pyc: Language is swedish
Dec  6 10:41:17 server weewx[30571]: genimages: Generated 6 images for 
BigImages in 0.80 seconds
Dec  6 10:41:17 server weewx[30571]: translategenerator.pyc: Language is swedish
Dec  6 10:41:17 server weewx[30571]: genimages: Generated 6 images for 
SmallImages in 0.33 seconds




Den fredag 24 november 2017 kl. 01:08:09 UTC+1 skrev mwall:
>
> On Wednesday, November 22, 2017 at 3:02:53 AM UTC-5, Daniel Jönsson wrote:
>>
>>
>> This was exactly how I understood it to be when I read up on the commit 
>> on github, and this is what I have been trying to do. But it does not 
>> effect the logging.
>> I am running version 3.6.1, and if I understand it correct this was 
>> implemented in 3.6.0, so it should work but isn't.
>>
>> I have tried to put it under [StdReport] and all reports their under, 
>> and under [StdRESTful]. No matter where I put it, it does 
>> absolutely nothing to lessen the output to syslog.
>>
>
> could you post some log output and highlight the messages that you think 
> should not be emitted?
>
> also post a sanitized copy of the weewx.conf
>
> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[Andrew Milner]

In my instance the need for the filter changes were raw and 
historygenerator parts of the meso and bootstrap skin extensions to weewx.

On Monday, 27 November 2017 01:13:27 UTC+2, gjr80 wrote:
>
> Ok, poor choice of words on my behalf. I am not advocating users changing 
> the actual filter script, as I have pointed out this will lead to problems. 
> Rather users need to have a mechanism to customise the logwatch filter, 
> similar in broad concept to how users can use search list extensions to add 
> to the available tags in a report.
>
> Gary
>
> On Monday, 27 November 2017 05:25:25 UTC+10, vince wrote:
>>
>> On Sunday, November 26, 2017 at 3:26:19 AM UTC-8, gjr80 wrote:
>>>
>>> So I guess the issue is making sure there is a means of users being able 
>>> to customise the logwatch script such that the user customisations are 
>>> retained across upgrades 
>>
>>
>>
>> I don't think you should even attempt to support that.  If the user 
>> essentially hacks on the logwatch script, they are doing so at their own 
>> risk.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[gjr80]

Ok, poor choice of words on my behalf. I am not advocating users changing 
the actual filter script, as I have pointed out this will lead to problems. 
Rather users need to have a mechanism to customise the logwatch filter, 
similar in broad concept to how users can use search list extensions to add 
to the available tags in a report.

Gary

On Monday, 27 November 2017 05:25:25 UTC+10, vince wrote:
>
> On Sunday, November 26, 2017 at 3:26:19 AM UTC-8, gjr80 wrote:
>>
>> So I guess the issue is making sure there is a means of users being able 
>> to customise the logwatch script such that the user customisations are 
>> retained across upgrades 
>
>
>
> I don't think you should even attempt to support that.  If the user 
> essentially hacks on the logwatch script, they are doing so at their own 
> risk.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[vince]

On Sunday, November 26, 2017 at 3:26:19 AM UTC-8, gjr80 wrote:
>
> So I guess the issue is making sure there is a means of users being able 
> to customise the logwatch script such that the user customisations are 
> retained across upgrades 



I don't think you should even attempt to support that.  If the user 
essentially hacks on the logwatch script, they are doing so at their own 
risk.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[gjr80]

Well I think it is true. If users follow the wiki (and link to the filter 
script) they will have no issues unless they run a modified filter script. If 
they run a modified filter script they will have issues (loss of local changes 
or weeWX upgrade filter script changes not being applied/used) irrespective of 
whether they link to the filter script (loss of local changes) or use a 
modified copy of the filter script saved elsewhere (distributed updates will 
not be applied).

Solve the situation for users running custom filter scripts and all will be 
fine.

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[Andrew Milner]

Ah - not quite true Gary.  The stock messages for added archive record were 
what highlighted my problem in the first place.  As I have installed via 
setup.py, I copied the script to /etc/logwatch - and this copy is not 
updated in the upgrade.  Maybe I should have 'installed' the script a 
different way originally and not copied the script to /etc/logwatch as I 
was instructed to do at the time when I first installed logwatch many moons 
ago!!  If I change to a symlink in /etc/logwatch/scripts/services pointing 
to /home/weewx/util/logwatch/scripts/services does this mean that the new 
script is automagically picked up each upgrade?? 
Right - have changed to a symlink back to 
/home/weewx/util/logwatch/scripts/services/weewx - but now I assume that 
when there is a new upgrade the update will overwrite the util directory, 
and so I will lose my changes - correct??


On Sunday, 26 November 2017 13:26:19 UTC+2, gjr80 wrote:

> So I guess the issue is making sure there is a means of users being able 
> to customise the logwatch script such that the user customisations are 
> retained across upgrades and at the same time the stock logwatch script is 
> upgraded as required during an upgrade. At the moment users that use the 
> stock logwatch script should not experience any problems across upgrades.
>
> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[gjr80]

So I guess the issue is making sure there is a means of users being able to 
customise the logwatch script such that the user customisations are retained 
across upgrades and at the same time the stock logwatch script is upgraded as 
required during an upgrade. At the moment users that use the stock logwatch 
script should not experience any problems across upgrades.

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[Andrew Milner]

Gary
The script had been updated correctly, but I had not copied it over into 
/etc/logwatch (I use setup.py to install), so I only had the two extra 
lines to add for raw and historygenerator once I'd copied it over.  The 
problem I reported in this thread was caused by the fact that I had 
forgotten/not realised I had to do the copy when I did the upgrade.
Andrew


On Sunday, 26 November 2017 12:23:11 UTC+2, gjr80 wrote:

> I'll have a look, at the very least we should have updated the logwatch 
> script if the log output was changed. I too run a custom logwatch script 
> (but haven't noticed any 3.8.0 issues) so I know having to change it is 
> annoying. Matthew is the logwatch expert, will have to metaphoricall pick 
> his brains.
>
> As for bibles, you probably want the GitHub bible rather than the weeWX 
> bible. But to make it easier for simple changes involving one file only I 
> am sure a marked up source would be fine.
>
> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[gjr80]

I'll have a look, at the very least we should have updated the logwatch script 
if the log output was changed. I too run a custom logwatch script (but haven't 
noticed any 3.8.0 issues) so I know having to change it is annoying. Matthew is 
the logwatch expert, will have to metaphoricall pick his brains.

As for bibles, you probably want the GitHub bible rather than the weeWX bible. 
But to make it easier for simple changes involving one file only I am sure a 
marked up source would be fine.

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[Andrew Milner]

Gary

I think I was running 3.6.1 - and those were the only two subtle (and they 
were subtle - a capital A and a change of name) differences I found apart 
from what I assume to be my own edits.

It seems to me that logging to a separate weewx log file, implementing 
logrotate and using logwatch should really be part of the 'standard' weewx 
installation (possibly with a disabling option in weewx.conf/setup) and 
handled/updated accordingly rather than being 'nice to have' extras 
obtained via the wiki.

 and my standard response is "What's a pull request?" as I still 
haven't got to grips with them or GitHub, and the weewx documentation bible 
is no help
Andrew

On Sunday, 26 November 2017 11:28:24 UTC+2, gjr80 wrote:

> Andrew, just out of interest what version did you upgrade from? I did not 
> think that 3.8.0 introduced any significant changes to log output.
>
> > Any chance of getting setup.py to update the logwatch scripts (and keep 
> custom edits) - or perhaps
> > making the update remind one of what else needs to be checked/changed 
> manually - just a thought .
>
> Do you want the standard answer
>
> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[gjr80]

Andrew, just out of interest what version did you upgrade from? I did not think 
that 3.8.0 introduced any significant changes to log output.

> Any chance of getting setup.py to update the logwatch scripts (and keep 
> custom edits) - or perhaps
> making the update remind one of what else needs to be checked/changed 
> manually - just a thought .

Do you want the standard answer

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[Andrew Milner]

Problem SOLVED - There were some subtle text changes to the logwatch script 
with the upgrade (Added instead of added, imagegenerator instead of 
Genimages) so I needed to copy the logwatch script into /etc/logwatch and 
add some custom edits I had made to the old script to ignore raw: and 
historygenerator: . But I think it is now all ok

Any chance of getting setup.py to update the logwatch scripts (and keep 
custom edits) - or perhaps making the update remind one of what else needs 
to be checked/changed manually - just a thought .



On Sunday, 26 November 2017 07:54:55 UTC+2, Andrew Milner wrote:

> Just updated to 3.8 and find that logwatch is logging as unmatched lines 
> the routine entries from manager, copygenerator, imagegenerator:
>
>  unmatched lines:
>Nov 25 08:45:49 RPi3 weewx[29522]: Stopping weewx weather system: 
> weewx..
>Nov 25 08:59:51 RPi3 weewx[541]: engine: Platform 
> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>Nov 25 08:59:51 RPi3 weewx[504]: Starting weewx weather system: weewx.
>Nov 25 08:59:51 RPi3 weewx[701]: wxcalculate: The following values will 
> be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
> rainRate=prefer_hardware, windrun=prefer_hardware, 
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, pressure=prefer_hardware, 
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
> cloudbase=prefer_hardware
>Nov 25 08:59:51 RPi3 weewx[701]: wxcalculate: The following algorithms 
> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>Nov 25 08:59:53 RPi3 weewx[701]: engine: Caught database 
> OperationalError: (2002, "Can't connect to local MySQL server through 
> socket '/var/run/mysqld/mysqld.sock' (2)")
>Nov 25 08:59:53 RPi3 weewx[701]:   Waiting 2 minutes then 
> retrying...
>Nov 25 09:01:52 RPi3 weewx[701]: wxcalculate: The following values will 
> be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
> rainRate=prefer_hardware, windrun=prefer_hardware, 
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, pressure=prefer_hardware, 
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
> cloudbase=prefer_hardware
>Nov 25 09:01:52 RPi3 weewx[701]: wxcalculate: The following algorithms 
> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>Nov 25 09:01:53 RPi3 weewx[701]: manager: Starting backfill of daily 
> summaries
>Nov 25 09:01:53 RPi3 weewx[701]: manager: Daily summaries up to date
>Nov 25 09:01:53 RPi3 weewx[701]: restx: Wunderground-PWS: Data for 
> station ILIMASSO5 will be posted
>Nov 25 09:01:53 RPi3 weewx[701]: restx: PWSweather: Posting not enabled.
>Nov 25 09:01:53 RPi3 weewx[701]: restx: CWOP: Posting not enabled.
>Nov 25 09:01:53 RPi3 weewx[701]: restx: WOW: Posting not enabled.
>Nov 25 09:01:53 RPi3 weewx[701]: restx: AWEKAS: Posting not enabled.
>Nov 25 09:23:04 RPi3 weewx[2102]: Stopping weewx weather system: weewx..
>Nov 25 09:24:26 RPi3 weewx[2187]: engine: Platform 
> Linux-4.9.35-v7+-armv7l-with-debian-8.0
>Nov 25 09:24:26 RPi3 weewx[2187]: engine: Locale is 'en_GB.UTF-8'
>Nov 25 09:24:26 RPi3 weewx[2177]: Starting weewx weather system: weewx.
>Nov 25 09:24:26 RPi3 weewx[2191]: wxcalculate: The following values 
> will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
> dewpoint=prefer_hardware, appTemp=prefer_hardware, 
> rainRate=prefer_hardware, windrun=prefer_hardware, 
> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
> humidex=prefer_hardware, pressure=prefer_hardware, 
> inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
> cloudbase=prefer_hardware
>Nov 25 09:24:26 RPi3 weewx[2191]: wxcalculate: The following algorithms 
> will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
>Nov 25 09:24:27 RPi3 weewx[2191]: manager: Starting backfill of daily 
> summaries
>Nov 25 09:24:27 RPi3 weewx[2191]: restx: Wunderground-PWS: Data for 
> station ILIMASSO5 will be posted
>Nov 25 09:24:27 RPi3 weewx[2191]: restx: PWSweather: Posting not 
> enabled.
>Nov 25 09:24:27 RPi3 weewx[2191]: restx: CWOP: Posting not enabled.
>Nov 25 09:24:27 RPi3 weewx[2191]: restx: WOW: Posting not enabled.
>Nov 25 09:24:27 RPi3 weewx[2191]: restx: AWEKAS: Posting not enabled.
>Nov 25 09:25:00 RPi3 weewx[2191]: manager: Added record 2017-11-25 
> 09:25:00 EET (1511594700) to database 'archive'
>Nov 25 09:25:00 RPi3 weewx[2191]: manager: Added record 2017-11-25 
> 09:25:00 EET (1511594700) to daily summary in 'archive'
>Nov 25 09:25:03 RPi3 weewx[2191]: manager: Added record 2017-11-25 
> 09:25:03 EET (1511594703) to database 'mesowx'
>Nov 25 09:25:56 RPi3 weewx[2191]: manager: Added record 

[weewx-user] Re: Limiting weewx logging only to error/fail

[Andrew Milner]

Just updated to 3.8 and find that logwatch is logging as unmatched lines 
the routine entries from manager, copygenerator, imagegenerator:

 unmatched lines:
   Nov 25 08:45:49 RPi3 weewx[29522]: Stopping weewx weather system: weewx..
   Nov 25 08:59:51 RPi3 weewx[541]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-8.0
   Nov 25 08:59:51 RPi3 weewx[504]: Starting weewx weather system: weewx.
   Nov 25 08:59:51 RPi3 weewx[701]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
   Nov 25 08:59:51 RPi3 weewx[701]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
   Nov 25 08:59:53 RPi3 weewx[701]: engine: Caught database 
OperationalError: (2002, "Can't connect to local MySQL server through 
socket '/var/run/mysqld/mysqld.sock' (2)")
   Nov 25 08:59:53 RPi3 weewx[701]:   Waiting 2 minutes then 
retrying...
   Nov 25 09:01:52 RPi3 weewx[701]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
   Nov 25 09:01:52 RPi3 weewx[701]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
   Nov 25 09:01:53 RPi3 weewx[701]: manager: Starting backfill of daily 
summaries
   Nov 25 09:01:53 RPi3 weewx[701]: manager: Daily summaries up to date
   Nov 25 09:01:53 RPi3 weewx[701]: restx: Wunderground-PWS: Data for 
station ILIMASSO5 will be posted
   Nov 25 09:01:53 RPi3 weewx[701]: restx: PWSweather: Posting not enabled.
   Nov 25 09:01:53 RPi3 weewx[701]: restx: CWOP: Posting not enabled.
   Nov 25 09:01:53 RPi3 weewx[701]: restx: WOW: Posting not enabled.
   Nov 25 09:01:53 RPi3 weewx[701]: restx: AWEKAS: Posting not enabled.
   Nov 25 09:23:04 RPi3 weewx[2102]: Stopping weewx weather system: weewx..
   Nov 25 09:24:26 RPi3 weewx[2187]: engine: Platform 
Linux-4.9.35-v7+-armv7l-with-debian-8.0
   Nov 25 09:24:26 RPi3 weewx[2187]: engine: Locale is 'en_GB.UTF-8'
   Nov 25 09:24:26 RPi3 weewx[2177]: Starting weewx weather system: weewx.
   Nov 25 09:24:26 RPi3 weewx[2191]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
   Nov 25 09:24:26 RPi3 weewx[2191]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
   Nov 25 09:24:27 RPi3 weewx[2191]: manager: Starting backfill of daily 
summaries
   Nov 25 09:24:27 RPi3 weewx[2191]: restx: Wunderground-PWS: Data for 
station ILIMASSO5 will be posted
   Nov 25 09:24:27 RPi3 weewx[2191]: restx: PWSweather: Posting not enabled.
   Nov 25 09:24:27 RPi3 weewx[2191]: restx: CWOP: Posting not enabled.
   Nov 25 09:24:27 RPi3 weewx[2191]: restx: WOW: Posting not enabled.
   Nov 25 09:24:27 RPi3 weewx[2191]: restx: AWEKAS: Posting not enabled.
   Nov 25 09:25:00 RPi3 weewx[2191]: manager: Added record 2017-11-25 
09:25:00 EET (1511594700) to database 'archive'
   Nov 25 09:25:00 RPi3 weewx[2191]: manager: Added record 2017-11-25 
09:25:00 EET (1511594700) to daily summary in 'archive'
   Nov 25 09:25:03 RPi3 weewx[2191]: manager: Added record 2017-11-25 
09:25:03 EET (1511594703) to database 'mesowx'
   Nov 25 09:25:56 RPi3 weewx[2191]: manager: Added record 2017-11-25 
09:25:57 EET (1511594757) to database 'mesowx'
   Nov 25 09:26:50 RPi3 weewx[2191]: manager: Added record 2017-11-25 
09:26:50 EET (1511594810) to database 'mesowx'
   Nov 25 09:27:43 RPi3 weewx[2191]: manager: Added record 2017-11-25 
09:27:44 EET (1511594864) to database 'mesowx'
   Nov 25 09:28:37 RPi3 weewx[2191]: manager: Added record 2017-11-25 
09:28:37 EET (1511594917) to database 'mesowx'
   Nov 25 09:29:30 RPi3 weewx[2191]: manager: Added record 2017-11-25 
09:29:31 EET (1511594971) to database 'mesowx'
   Nov 25 09:30:23 RPi3 weewx[2191]: manager: Added record 2017-11-25 
09:30:24 EET (1511595024) to database 'mesowx'
   Nov 25 09:30:24 RPi3 weewx[2191]: manager: Added record 2017-11-25 
09:30:00 EET (1511595000) to database 'archive'
   

[weewx-user] Re: Limiting weewx logging only to error/fail

[mwall]

On Wednesday, November 22, 2017 at 3:02:53 AM UTC-5, Daniel Jönsson wrote:
>
>
> This was exactly how I understood it to be when I read up on the commit on 
> github, and this is what I have been trying to do. But it does not effect 
> the logging.
> I am running version 3.6.1, and if I understand it correct this was 
> implemented in 3.6.0, so it should work but isn't.
>
> I have tried to put it under [StdReport] and all reports their under, and 
> under [StdRESTful]. No matter where I put it, it does absolutely nothing to 
> lessen the output to syslog.
>

could you post some log output and highlight the messages that you think 
should not be emitted?

also post a sanitized copy of the weewx.conf

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[Daniel Jönsson]

Thank you for quick reply. 

This was exactly how I understood it to be when I read up on the commit on 
github, and this is what I have been trying to do. But it does not effect 
the logging.
I am running version 3.6.1, and if I understand it correct this was 
implemented in 3.6.0, so it should work but isn't.

I have tried to put it under [StdReport] and all reports their under, and 
under [StdRESTful]. No matter where I put it, it does absolutely nothing to 
lessen the output to syslog.



Den tisdag 21 november 2017 kl. 23:13:45 UTC+1 skrev mwall:
>
>
>
> On Tuesday, November 21, 2017 at 4:36:10 PM UTC-5, Daniel Jönsson wrote:
>>
>> I cant seem to get it to work. And I cant find it in the user guide (
>> http://www.weewx.com/docs/usersguide.htm) were to put it.
>> I would also very much like to only have errors in my log.
>>>
>>>
>>>
> commit 6b461c9 
> 
>  applies 
> to reports
>
> use it like this:
>
> [StdReport]
>   log_success = False
>   log_failure = True
>
> then optionally specialize for individual reports.  for example, to log 
> success for StandardReport but not for others:
>
> [StdReport]
>   log_success = False
>   log_failure = True
> ...
>   [[StandardReport]]
> log_success = True
> ...
>   [[AnotherReport]]
> ...
>
> this pattern should also work for uploaders:
>
> [StdRESTful]
>   log_succes = False
>   log_failure = True
>
> we probably should do it for the archive service as well, which would 
> probably indicate that one should be able to specify log_success and 
> log_failure at the root of weewx.conf then override for each service as 
> necessary.
>
> 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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[mwall]

On Tuesday, November 21, 2017 at 4:36:10 PM UTC-5, Daniel Jönsson wrote:
>
> I cant seem to get it to work. And I cant find it in the user guide (
> http://www.weewx.com/docs/usersguide.htm) were to put it.
> I would also very much like to only have errors in my log.
>>
>>
>>
commit 6b461c9 

 applies 
to reports

use it like this:

[StdReport]
  log_success = False
  log_failure = True

then optionally specialize for individual reports.  for example, to log 
success for StandardReport but not for others:

[StdReport]
  log_success = False
  log_failure = True
...
  [[StandardReport]]
log_success = True
...
  [[AnotherReport]]
...

this pattern should also work for uploaders:

[StdRESTful]
  log_succes = False
  log_failure = True

we probably should do it for the archive service as well, which would 
probably indicate that one should be able to specify log_success and 
log_failure at the root of weewx.conf then override for each service as 
necessary.

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 weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: Limiting weewx logging only to error/fail

[Daniel Jönsson]

I cant seem to get it to work. And I cant find it in the user guide 
(http://www.weewx.com/docs/usersguide.htm) were to put it.
I would also very much like to only have errors in my log.

Den torsdag 14 april 2016 kl. 00:42:38 UTC+2 skrev mwall:
>
> On Wednesday, April 13, 2016 at 12:00:49 PM UTC-4, vince wrote:
>>
>> Great stuff - is there any plan/way to have a global log_success or 
>> global log_failure that the sections can supersede perhaps, rather than 
>> requiring setting log_success=false in a bunch of places ?
>>
>
> there is now :)
>
> https://github.com/weewx/weewx/issues/116 
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.