Excessive Syslog data

87 views
Skip to first unread message

Andy Peterman

unread,
Apr 29, 2022, 12:50:14 PM4/29/22
to weewx-user
I've recently updated to 4.7.0 and just noticed the system log (syslog) has been getting dumps of loop data every few seconds.  Here's what I've been seeing:

Apr 29 09:46:35 Multipass com.weewx.weewxd[2617]: LOOP:   2022-04-29 09:46:14 PDT (1651250774) 'altimeter': '30.112925788902526', 'appTemp': '51.403945964940384', 'barometer': '30.111', 'cloudbase': '1509.5918641388919', 'consBatteryVoltage': '4.28', 'dateTime': '1651250774', 'dayET': '0.0', 'dayRain': '0.03', 'dewpoint': '47.34379579778888', 'ET': 'None', 'extraAlarm1': '0', 'extraAlarm2': '0', 'extraAlarm3': '0', 'extraAlarm4': '0', 'extraAlarm5': '0', 'extraAlarm6': '0', 'extraAlarm7': '0', 'extraAlarm8': '0', 'forecastIcon': '6', 'forecastRule': '44', 'heatindex': '52.483000000000004', 'humidex': '54.82771626032395', 'inDewpoint': '43.399219063882676', 'inHumidity': '34.0', 'insideAlarm': '0', 'inTemp': '73.5', 'maxSolarRad': '565.2481829491581', 'monthET': '0.0', 'monthRain': '5.9', 'outHumidity': '79.0', 'outsideAlarm1': '0', 'outsideAlarm2': '0', 'outTemp': '53.7', 'pressure': '30.039635406360034', 'rain': 'None', 'rainAlarm': '0', 'rainRate': '0.0', 'soilLeafAlarm1': '0', 'soilLeafAlarm2': '0', 'soilLeafAlarm3': '0', 'soilLeafAlarm4': '0', 'stormRain': '0.08', 'stormStart': '1651129200', 'sunrise': '1651237860', 'sunset': '1651288620', 'txBatteryStatus': '0', 'usUnits': '1', 'windchill': '53.7', 'windDir': '246.0', 'windGust': '3.0', 'windGustDir': '246.0', 'windrun': 'None', 'windSpeed': '3.0', 'windSpeed10': '3.0', 'yearET': '0.02', 'yearRain': '57.57'

This results in a syslog file of over 20MB per day!

I've managed to locate where this is coming from, engine.py in Class StdPrint at new_loop_packet.

Any idea why this is happening.  I'm not versed in Python enough to track this down.

Thanks!

vince

unread,
Apr 29, 2022, 2:19:04 PM4/29/22
to weewx-user
Usual FAQ how to report a problem answer applies....

- what driver are you running ?
- what os ?
- what kind of installation (docker ?  setup.py ?  dpkg ?  rpm ?)

Andy Peterman

unread,
Apr 29, 2022, 2:39:56 PM4/29/22
to weewx-user
Oops, forgot that info.

VantagePro weather station (Vantage driver)
MacOS 10.6.8 (yea, it's an older Mac Mini, but it works really well for this) along with Python 3.6.15
Not sure about installation - I assume it was setup.py

I looked at that link, but I'm not sure what it was talking about.  I'm not really familiar with what StdPrint is supposed to be doing.  I do see logging information at /var/log/weewx.log and there also seems to be a file weewx.stderr in the weewx directory, but I don't understand why I'm getting all this LOOP info in the system log.  I have all the "successful" logging turned off and all the "unsuccessful" logging on.

Doug Jenkins

unread,
Apr 29, 2022, 2:59:30 PM4/29/22
to weewx...@googlegroups.com
In the weewx engine section, remove stdprint. That is what is printing the loop data in your log. Make sure you recycle your weewx service to take effect

--
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/1249f468-07fc-4c85-8133-2c0008cdc507n%40googlegroups.com.

Tom Keffer

unread,
Apr 29, 2022, 5:59:33 PM4/29/22
to weewx-user
Andy, you didn't say, but I'll bet you're trying to run weewxd as a daemon. If that's the case, you need to use the --daemon flag.

Among other things, the --daemon flag causes weewxd to reassign standard output to /dev/null. Otherwise, any output will go to the log.

Andy Peterman

unread,
Apr 29, 2022, 7:02:14 PM4/29/22
to weewx-user
Removing stdprint fixed the problem.  Thanks!  

But why is that there in the first place.

---

Also, I'll give the --daemon flag a try - I'll bet that's been the problem all along.  I'm using the LaunchDaemon script that came with the install, so that's probably why it's not set.
Reply all
Reply to author
Forward
0 new messages