search

amocoma / lgESSInverter

3 stars 2 forks source link

Logging each item state change in "/var/log/syslog" #2

Open BananaJoeTo opened 4 years ago

BananaJoeTo commented 4 years ago

Hello Dirk,

for me it seems like the lgESSInverter Binding logs each item state change into syslog. For example: tail -n20 /var/log/syslog shows me:

(...) Aug 22 23:24:47 openhab karaf[593]: home#statGridFeedIn : "0" : KILOWATT_HOUR Aug 22 23:24:47 openhab karaf[593]: home#isDirectConsumption : "1" : SWITCH_ONE_ZERO Aug 22 23:24:47 openhab karaf[593]: home#isBatteryCharging : "0" : SWITCH_ONE_ZERO Aug 22 23:24:47 openhab karaf[593]: home#isBatteryDischarging : "0" : SWITCH_ONE_ZERO Aug 22 23:24:47 openhab karaf[593]: home#isGridFeedIn : "0" : SWITCH_ONE_ZERO Aug 22 23:24:47 openhab karaf[593]: home#isGridConsumption : "1" : SWITCH_ONE_ZERO Aug 22 23:24:47 openhab karaf[593]: home#isBatteryChargingFromGrid : "0" : SWITCH_ONE_ZERO (...)

This is done very often and leads to high load on the SD card and also a always full SD card.

Do you have an idea to change this?

Thank you! Berti

BananaJoeTo commented 4 years ago

Hello, short intermediate result, what I was able to find out so far: 1.) All logging settings (OFF; WARN; ERROR; ...) in Openhab (org.ops4j.pax.logging.cfg) were not successful. It is still logged in syslog (see post # 1).

2.) As a workaround I switched off the following in "etc / rsyslog.conf":

##################
# MODULES #
##################
(...)
# module (load = "imuxsock") # provides support for local system logging

Since then, no item state has been logged in syslog. I think as a workaround (so that the syslog does not overflow and the SD card is spared) it is ok, but it would certainly be good if this logging would no longer take place automatically.

Thanks and Greetings, Berti