Ich habe auf meiner Synology DS einige updates gemacht - erschreckt stelle ich fest das DBLog nicht mehr funktioniert.
2018.11.11 12:26:33 2: DbLog DbLog -> Error table history - DBD::mysql::st execute_array failed: executing 3638 generated 110 errors at ./FHEM/93_DbLog.pm line 2068.
Hat jemand ne Idee was ich tun kann..?
Du hast wahrscheinlich MariaDB 10 im Einsatz und upgedatet.
Wir hatten das schonmal vor Kurzem. Such mal nach dem Thread, weiß nicht mehr genau wo das war, vmtl. in Automatisierung.
Ich habe momentan keine Zeit, aber setze dir das Attribut "useCharfilter = 1" im DbLog und restarte dein FHEM.
Es liegt an der Art wie manche Module "°C" liefern und komischerweise kommt die neueste Version von Synology MariaDB damit nicht klar.
Grüße
Heiko
Ich habe das attribut gesetzt, gespeichert und neu gestartet - leider hilft das nicht, ich schaue mal ob ich den passenden Thread finde.
Ansonsten hast Du recht MariaDB 10 auf Syno NAS
Habe den Thread zwar gefunden, aber keine der beschriebenen Maßnahmen hilft mir...
Ich habe use Charfilter auf 1 gesetzt, den commitMode auf basic_ta:off und valueFN
{
if ($UNIT eq "°C") {
$UNIT="";
}
}
Kann das damit zusammenhängen das DBLog nicht aus dem Contrib upgedatet wurde..?
Hier noch ein list des DbLog devices:
Internals:
COLUMNS field length used for Device: 64, Type: 64, Event: 512, Reading: 64, Value: 128, Unit: 32
CONFIGURATION ./db.conf
DEF ./db.conf WMZ.*|Lueftung.*:A.*|Power_L.*|R.*|V.*|W.*|Z.*|akt.*
MODE asynchronous
MODEL MYSQL
NAME DbLog
NR 164
NTFY_ORDER 50-DbLog
PID 18107
REGEXP WMZ.*|Lueftung.*:A.*|Power_L.*|R.*|V.*|W.*|Z.*|akt.*
STATE DBD::mysql::st execute_array failed: executing 376 generated 10 errors at ./FHEM/93_DbLog.pm line 2068.
TYPE DbLog
UTF8 1
VERSION 3.12.6
dbconn mysql:database=fhem;host=127.0.0.1;port=3307
dbuser fhem
HELPER:
COLSET 1
DEVICECOL 64
EVENTCOL 512
OLDSTATE DBD::mysql::st execute_array failed: executing 376 generated 10 errors at ./FHEM/93_DbLog.pm line 2068.
READINGCOL 64
TYPECOL 64
UNITCOL 32
VALUECOL 128
READINGS:
2018-11-11 13:14:19 CacheUsage 99
2018-11-11 13:13:28 NextSync 2018-11-11 13:13:58 or if CacheUsage 500 reached
2018-11-10 14:41:48 countCurrent 767
2018-11-10 14:41:48 countHistory 10968723
2018-09-30 21:57:15 reduceLogState reduceLogNbl finished. Rows processed: 0, deleted: 0, time: 0.11sec
2018-11-11 13:14:19 state DBD::mysql::st execute_array failed: executing 376 generated 10 errors at ./FHEM/93_DbLog.pm line 2068.
cache:
index 3632
helper:
bm:
DbLog_Attr:
cnt 5
dmx -1000
dtot 0
dtotcnt 0
mTS 11.11. 13:01:59
max 0.0258240699768066
tot 0.0470433235168457
mAr:
set
DbLog
disable
1
DbLog_Get:
cnt 9
dmx -1000
dtot 0
dtotcnt 0
mTS 11.11. 13:01:59
max 8.89301300048828e-05
tot 0.000359296798706055
mAr:
HASH(0x60c7a10)
DbLog
?
DbLog_Log:
cnt 3065
dmx -1000
dtot 0
dtotcnt 0
mTS 11.11. 13:12:07
max 0.224492788314819
tot 9.03629994392395
mAr:
HASH(0x60c7a10)
HASH(0x6d73308)
DbLog_Set:
cnt 68
dmx -1000
dtot 0
dtotcnt 0
mTS 11.11. 13:12:17
max 0.0196249485015869
tot 0.0680317878723145
mAr:
HASH(0x60c7a10)
DbLog
commitCache
Attributes:
DbLogExclude WMZ
DbLogSelectionMode Exclude/Include
DbLogType Current/History
asyncMode 1
cacheEvents 2
commitMode basic_ta:off
disable 1
group Server
room 99-Controller
useCharfilter 1
valueFn {
if ($UNIT eq "°C") {
$UNIT="";
}
}
Habe DbLog nun erstmal disabled...
Dblog aus dem normalen update ist ok. Die gesetzzen Attribite sind richtig ! So lassen.
Brauchst dblog nicht deaktivieren. Mach mal ein verbose 4 oder 5.
Schaue ich mir an wenn ich wieder zu hause bin.vllt. sehe ich auch gleich was.
Ok, hier ein reverseLog mit verbose 5...
2018.11.11 13:50:27 5: DbLog DbLog -> DbLog_PushAsyncDone finished
2018.11.11 13:50:27 5: DbLog DbLog -> Start DbLog_PushAsyncDone
2018.11.11 13:50:27 5: DbLog DbLog -> DbLog_PushAsync finished
2018.11.11 13:50:21 2: DbLog DbLog -> Error table history - DBD::mysql::st execute_array failed: executing 103 generated 5 errors at ./FHEM/93_DbLog.pm line 2068.
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Waermeleistung: 3700.0, Reading: Waermeleistung, Value: 3700.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: aktAZ: 3.80, Reading: aktAZ, Value: 3.80, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Spreizung: 2.9, Reading: Spreizung, Value: 2.9, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: statGesamtWaermemenge: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001, Reading: statGesamtWaermemenge, Value: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Waermeleistung: 3700.0, Reading: Waermeleistung, Value: 3700.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: aktAZ: 3.80, Reading: aktAZ, Value: 3.80, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Spreizung: 2.9, Reading: Spreizung, Value: 2.9, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Ruecklauftemperatur: 37.1, Reading: Ruecklauftemperatur, Value: 37.1, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Waermeleistung: 3700.0, Reading: Waermeleistung, Value: 3700.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: aktAZ: 3.80, Reading: aktAZ, Value: 3.80, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Spreizung: 3.0, Reading: Spreizung, Value: 3.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: statGesamtWaermemenge: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001, Reading: statGesamtWaermemenge, Value: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Waermeleistung: 3700.0, Reading: Waermeleistung, Value: 3700.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: aktAZ: 3.80, Reading: aktAZ, Value: 3.80, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Spreizung: 3.0, Reading: Spreizung, Value: 3.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Durchfluss: 1140, Reading: Durchfluss, Value: 1140, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Waermeleistung: 3700.0, Reading: Waermeleistung, Value: 3700.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: aktAZ: 3.80, Reading: aktAZ, Value: 3.80, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Spreizung: 3.0, Reading: Spreizung, Value: 3.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: statGesamtWaermemenge: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001, Reading: statGesamtWaermemenge, Value: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Waermeleistung: 3700.0, Reading: Waermeleistung, Value: 3700.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: aktAZ: 3.80, Reading: aktAZ, Value: 3.80, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Spreizung: 3.0, Reading: Spreizung, Value: 3.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: aktWaermeleistung: 3.7, Reading: aktWaermeleistung, Value: 3.7, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Waermeleistung: 3600.0, Reading: Waermeleistung, Value: 3600.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: aktAZ: 3.70, Reading: aktAZ, Value: 3.70, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Spreizung: 3.0, Reading: Spreizung, Value: 3.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: statGesamtWaermemenge: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001, Reading: statGesamtWaermemenge, Value: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Waermeleistung: 3600.0, Reading: Waermeleistung, Value: 3600.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: aktAZ: 3.70, Reading: aktAZ, Value: 3.70, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Spreizung: 3.0, Reading: Spreizung, Value: 3.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: gesamtWaermemenge: 23.478, Reading: gesamtWaermemenge, Value: 23.478, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WMZ, Type: MODBUSATTR, Event: Waermeleistung: 3600.0, Reading: Waermeleistung, Value: 3600.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:58, Device: WMZ, Type: MODBUSATTR, Event: aktAZ: 3.70, Reading: aktAZ, Value: 3.70, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:58, Device: WMZ, Type: MODBUSATTR, Event: Spreizung: 3.0, Reading: Spreizung, Value: 3.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:58, Device: WMZ, Type: MODBUSATTR, Event: statGesamtWaermemenge: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001, Reading: statGesamtWaermemenge, Value: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:58, Device: WMZ, Type: MODBUSATTR, Event: Waermeleistung: 3600.0, Reading: Waermeleistung, Value: 3600.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:58, Device: WMZ, Type: MODBUSATTR, Event: aktAZ: 3.70, Reading: aktAZ, Value: 3.70, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:58, Device: WMZ, Type: MODBUSATTR, Event: Spreizung: 3.0, Reading: Spreizung, Value: 3.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:58, Device: WMZ, Type: MODBUSATTR, Event: Vorlauftemperatur: 40.0, Reading: Vorlauftemperatur, Value: 40.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:58, Device: SDM630, Type: MODBUSSDM630M, Event: Power_L3__W: 0, Reading: Power_L3__W, Value: 0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:58, Device: SDM630, Type: MODBUSSDM630M, Event: Power_L2__W: 974, Reading: Power_L2__W, Value: 974, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:58, Device: SDM630, Type: MODBUSSDM630M, Event: Power_L1__W: 49, Reading: Power_L1__W, Value: 49, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:50:13, Device: LueftungBadEG, Type: HTTPMOD, Event: WRG: 68.7, Reading: WRG, Value: 68.7, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:50:13, Device: LueftungBadEG, Type: HTTPMOD, Event: AbluftTemperatur: 22.3, Reading: AbluftTemperatur, Value: 22.3, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:50:13, Device: LueftungBadEG, Type: HTTPMOD, Event: ZuluftFeuchtigkeit: 45.0, Reading: ZuluftFeuchtigkeit, Value: 45.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: state: T: 9.2°C H: 96%, Reading: state, Value: T: 9.2°C H: 96%, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_kn_avg2m: 0.7, Reading: wind_speed_kn_avg2m, Value: 0.7, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_mph_avg2m: 0.8, Reading: wind_speed_mph_avg2m, Value: 0.8, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_avg2m: 1.3, Reading: wind_speed_avg2m, Value: 1.3, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_compasspoint_avg2m: S, Reading: wind_compasspoint_avg2m, Value: S, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_direction_avg2m: 169, Reading: wind_direction_avg2m, Value: 169, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_gust_direction_avg10m: 186, Reading: wind_gust_direction_avg10m, Value: 186, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_gust_fts: 0.0, Reading: wind_gust_fts, Value: 0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_gust_kn: 0.0, Reading: wind_gust_kn, Value: 0, Unit: kn
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_gust_bft: 0, Reading: wind_gust_bft, Value: 0, Unit: bft
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_fts: 0.0, Reading: wind_speed_fts, Value: 0.0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_kn: 0.0, Reading: wind_speed_kn, Value: 0, Unit: kn
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_bft: 0, Reading: wind_speed_bft, Value: 0, Unit: bft
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_compasspoint: S, Reading: wind_compasspoint, Value: 180, Unit: °
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: indoorHumidityAbs_f: 120.4, Reading: indoorHumidityAbs_f, Value: 120.4, Unit: °F
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: indoorHumidityAbs: 11.2, Reading: indoorHumidityAbs, Value: 11.2, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: humidityAbs_f: 74.4, Reading: humidityAbs_f, Value: 74.4, Unit: °F
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: humidityAbs: 8.6, Reading: humidityAbs, Value: 8.6, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: indoorDewpoint_f: 59.0, Reading: indoorDewpoint_f, Value: 59.0, Unit: °F
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: indoorDewpoint: 13.2, Reading: indoorDewpoint, Value: 13.2, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: pressureAbs_mm: 7.6, Reading: pressureAbs_mm, Value: 7, Unit: mmHg
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: pressure_mm: 7.5, Reading: pressure_mm, Value: 7, Unit: mmHg
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: UVR: 362, Reading: UVR, Value: 362, Unit: W
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: UV: 1, Reading: UV, Value: 1, Unit: UVI
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: solarradiation: 74.17, Reading: solarradiation, Value: 74, Unit: W
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_mps: 0.0, Reading: wind_speed_mps, Value: 0, Unit: m
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: rain_day: 1.8, Reading: rain_day, Value: 2, Unit: mm
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: rain_in: 0.00, Reading: rain_in, Value: 0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: indoorTemperature_f: 70.3, Reading: indoorTemperature_f, Value: 70.3, Unit: °F
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: temperature_f: 48.6, Reading: temperature_f, Value: 48.6, Unit: °F
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_gust: 0.0, Reading: wind_gust, Value: 0, Unit: km
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: dewpoint: 8.6, Reading: dewpoint, Value: 8.6, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: rain_month_in: 0.12, Reading: rain_month_in, Value: 0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: indoorHumidity: 60, Reading: indoorHumidity, Value: 60, Unit: %
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: rain_day_in: 0.07, Reading: rain_day_in, Value: 0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: rain_year_in: 0.64, Reading: rain_year_in, Value: 1, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: pressure: 998.00, Reading: pressure, Value: 998, Unit: hPa
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: rain_week_in: 0.12, Reading: rain_week_in, Value: 0, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_gust_mph: 0.0, Reading: wind_gust_mph, Value: 0, Unit: mi
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed: 0.0, Reading: wind_speed, Value: 0, Unit: km
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: rain_year: 16.2, Reading: rain_year, Value: 16, Unit: mm
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: rain_month: 3.0, Reading: rain_month, Value: 3, Unit: mm
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_mph: 0.0, Reading: wind_speed_mph, Value: 0, Unit: mi
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: pressureAbs_in: 29.74, Reading: pressureAbs_in, Value: 29.74, Unit: inHg
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: temperature: 9.2, Reading: temperature, Value: 9.2, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: rain: 0.0, Reading: rain, Value: 0, Unit: mm
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: indoorTemperature: 21.3, Reading: indoorTemperature, Value: 21.3, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_chill: 9.2, Reading: wind_chill, Value: 9.2, Unit:
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: pressure_in: 29.47, Reading: pressure_in, Value: 29.47, Unit: inHg
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_chill_f: 48.6, Reading: wind_chill_f, Value: 48.6, Unit: °F
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: dewpoint_f: 47.5, Reading: dewpoint_f, Value: 47.5, Unit: °F
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: pressureAbs: 1007.10, Reading: pressureAbs, Value: 1007, Unit: hPa
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: luminosity: 9396.80, Reading: luminosity, Value: 9396, Unit: lx
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: humidity: 96, Reading: humidity, Value: 96, Unit: %
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: rain_week: 3.0, Reading: rain_week, Value: 3, Unit: mm
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_direction: 182, Reading: wind_direction, Value: 182, Unit: °
2018.11.11 13:50:14 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_gust_mps: 0.0, Reading: wind_gust_mps, Value: 0, Unit: m
2018.11.11 13:50:14 5: DbLog DbLog -> Primary Key used in fhem.current: none
2018.11.11 13:50:14 5: DbLog DbLog -> Primary Key used in fhem.history: none
2018.11.11 13:50:14 4: DbLog DbLog -> AutoCommit mode: ON, Transaction mode: OFF
2018.11.11 13:50:14 5: DbLog DbLog -> DbLogType is: Current/History
2018.11.11 13:50:14 5: DbLog DbLog -> Start DbLog_PushAsync
2018.11.11 13:50:14 5: DbLog DbLog -> DbLog_PushAsync called with timeout: 86400
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Waermeleistung: 3700.0|Waermeleistung|3700.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|aktAZ: 3.80|aktAZ|3.80|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Spreizung: 2.9|Spreizung|2.9|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|statGesamtWaermemenge: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001|statGesamtWaermemenge|Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Waermeleistung: 3700.0|Waermeleistung|3700.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|aktAZ: 3.80|aktAZ|3.80|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Spreizung: 2.9|Spreizung|2.9|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Ruecklauftemperatur: 37.1|Ruecklauftemperatur|37.1|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Waermeleistung: 3700.0|Waermeleistung|3700.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|aktAZ: 3.80|aktAZ|3.80|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Spreizung: 3.0|Spreizung|3.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|statGesamtWaermemenge: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001|statGesamtWaermemenge|Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Waermeleistung: 3700.0|Waermeleistung|3700.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|aktAZ: 3.80|aktAZ|3.80|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Spreizung: 3.0|Spreizung|3.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Durchfluss: 1140|Durchfluss|1140|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Waermeleistung: 3700.0|Waermeleistung|3700.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|aktAZ: 3.80|aktAZ|3.80|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Spreizung: 3.0|Spreizung|3.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|statGesamtWaermemenge: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001|statGesamtWaermemenge|Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Waermeleistung: 3700.0|Waermeleistung|3700.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|aktAZ: 3.80|aktAZ|3.80|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Spreizung: 3.0|Spreizung|3.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|aktWaermeleistung: 3.7|aktWaermeleistung|3.7|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Waermeleistung: 3600.0|Waermeleistung|3600.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|aktAZ: 3.70|aktAZ|3.70|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Spreizung: 3.0|Spreizung|3.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|statGesamtWaermemenge: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001|statGesamtWaermemenge|Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Waermeleistung: 3600.0|Waermeleistung|3600.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|aktAZ: 3.70|aktAZ|3.70|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Spreizung: 3.0|Spreizung|3.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|gesamtWaermemenge: 23.478|gesamtWaermemenge|23.478|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WMZ|MODBUSATTR|Waermeleistung: 3600.0|Waermeleistung|3600.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:58|WMZ|MODBUSATTR|aktAZ: 3.70|aktAZ|3.70|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:58|WMZ|MODBUSATTR|Spreizung: 3.0|Spreizung|3.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:58|WMZ|MODBUSATTR|statGesamtWaermemenge: Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001|statGesamtWaermemenge|Hour: 0.003 Day: 0.013 Month: 0.411 Year: 8.001|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:58|WMZ|MODBUSATTR|Waermeleistung: 3600.0|Waermeleistung|3600.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:58|WMZ|MODBUSATTR|aktAZ: 3.70|aktAZ|3.70|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:58|WMZ|MODBUSATTR|Spreizung: 3.0|Spreizung|3.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:58|WMZ|MODBUSATTR|Vorlauftemperatur: 40.0|Vorlauftemperatur|40.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:58|SDM630|MODBUSSDM630M|Power_L3__W: 0|Power_L3__W|0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:58|SDM630|MODBUSSDM630M|Power_L2__W: 974|Power_L2__W|974|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:58|SDM630|MODBUSSDM630M|Power_L1__W: 49|Power_L1__W|49|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:50:13|LueftungBadEG|HTTPMOD|WRG: 68.7|WRG|68.7|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:50:13|LueftungBadEG|HTTPMOD|AbluftTemperatur: 22.3|AbluftTemperatur|22.3|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:50:13|LueftungBadEG|HTTPMOD|ZuluftFeuchtigkeit: 45.0|ZuluftFeuchtigkeit|45.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|state: T: 9.2°C H: 96%|state|T: 9.2°C H: 96%|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_speed_kn_avg2m: 0.7|wind_speed_kn_avg2m|0.7|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_speed_mph_avg2m: 0.8|wind_speed_mph_avg2m|0.8|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_speed_avg2m: 1.3|wind_speed_avg2m|1.3|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_compasspoint_avg2m: S|wind_compasspoint_avg2m|S|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_direction_avg2m: 169|wind_direction_avg2m|169|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_gust_direction_avg10m: 186|wind_gust_direction_avg10m|186|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_gust_fts: 0.0|wind_gust_fts|0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_gust_kn: 0.0|wind_gust_kn|0|kn
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_gust_bft: 0|wind_gust_bft|0|bft
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_speed_fts: 0.0|wind_speed_fts|0.0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_speed_kn: 0.0|wind_speed_kn|0|kn
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_speed_bft: 0|wind_speed_bft|0|bft
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_compasspoint: S|wind_compasspoint|180|°
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|indoorHumidityAbs_f: 120.4|indoorHumidityAbs_f|120.4|°F
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|indoorHumidityAbs: 11.2|indoorHumidityAbs|11.2|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|humidityAbs_f: 74.4|humidityAbs_f|74.4|°F
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|humidityAbs: 8.6|humidityAbs|8.6|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|indoorDewpoint_f: 59.0|indoorDewpoint_f|59.0|°F
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|indoorDewpoint: 13.2|indoorDewpoint|13.2|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|pressureAbs_mm: 7.6|pressureAbs_mm|7|mmHg
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|pressure_mm: 7.5|pressure_mm|7|mmHg
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|UVR: 362|UVR|362|W
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|UV: 1|UV|1|UVI
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|solarradiation: 74.17|solarradiation|74|W
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_speed_mps: 0.0|wind_speed_mps|0|m
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|rain_day: 1.8|rain_day|2|mm
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|rain_in: 0.00|rain_in|0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|indoorTemperature_f: 70.3|indoorTemperature_f|70.3|°F
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|temperature_f: 48.6|temperature_f|48.6|°F
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_gust: 0.0|wind_gust|0|km
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|dewpoint: 8.6|dewpoint|8.6|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|rain_month_in: 0.12|rain_month_in|0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|indoorHumidity: 60|indoorHumidity|60|%
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|rain_day_in: 0.07|rain_day_in|0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|rain_year_in: 0.64|rain_year_in|1|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|pressure: 998.00|pressure|998|hPa
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|rain_week_in: 0.12|rain_week_in|0|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_gust_mph: 0.0|wind_gust_mph|0|mi
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_speed: 0.0|wind_speed|0|km
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|rain_year: 16.2|rain_year|16|mm
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|rain_month: 3.0|rain_month|3|mm
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_speed_mph: 0.0|wind_speed_mph|0|mi
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|pressureAbs_in: 29.74|pressureAbs_in|29.74|inHg
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|temperature: 9.2|temperature|9.2|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|rain: 0.0|rain|0|mm
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|indoorTemperature: 21.3|indoorTemperature|21.3|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_chill: 9.2|wind_chill|9.2|
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|pressure_in: 29.47|pressure_in|29.47|inHg
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_chill_f: 48.6|wind_chill_f|48.6|°F
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|dewpoint_f: 47.5|dewpoint_f|47.5|°F
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|pressureAbs: 1007.10|pressureAbs|1007|hPa
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|luminosity: 9396.80|luminosity|9396|lx
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|humidity: 96|humidity|96|%
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|rain_week: 3.0|rain_week|3|mm
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_direction: 182|wind_direction|182|°
2018.11.11 13:50:14 5: DbLog DbLog -> MemCache contains: 2018-11-11 13:49:59|WH2600|HP1000|wind_gust_mps: 0.0|wind_gust_mps|0|m
2018.11.11 13:50:14 4: DbLog DbLog -> DbLogType is: Current/History
2018.11.11 13:50:14 4: DbLog DbLog -> MemCache contains 103 entries to process
2018.11.11 13:50:14 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:14 4: DbLog DbLog -> ### New database processing cycle - asynchronous ###
2018.11.11 13:50:14 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:14 4: DbLog DbLog -> check Device: DbLog , Event: CacheUsage: 103
2018.11.11 13:50:14 4: DbLog DbLog -> number of events received: 1 for device: DbLog
2018.11.11 13:50:14 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:14 4: DbLog DbLog -> ### start of new Logcycle ###
2018.11.11 13:50:14 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:13 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:50:13, Device: LueftungBadEG, Type: HTTPMOD, Event: WRG: 68.7, Reading: WRG, Value: 68.7, Unit:
2018.11.11 13:50:13 5: DbLog DbLog -> parsed Event: LueftungBadEG , Event: WRG: 68.7
2018.11.11 13:50:13 4: DbLog DbLog -> check Device: LueftungBadEG , Event: WRG: 68.7
2018.11.11 13:50:13 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:50:13, Device: LueftungBadEG, Type: HTTPMOD, Event: AbluftTemperatur: 22.3, Reading: AbluftTemperatur, Value: 22.3, Unit:
2018.11.11 13:50:13 5: DbLog DbLog -> parsed Event: LueftungBadEG , Event: AbluftTemperatur: 22.3
2018.11.11 13:50:13 4: DbLog DbLog -> check Device: LueftungBadEG , Event: AbluftTemperatur: 22.3
2018.11.11 13:50:13 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:50:13, Device: LueftungBadEG, Type: HTTPMOD, Event: ZuluftFeuchtigkeit: 45.0, Reading: ZuluftFeuchtigkeit, Value: 45.0, Unit:
2018.11.11 13:50:13 5: DbLog DbLog -> parsed Event: LueftungBadEG , Event: ZuluftFeuchtigkeit: 45.0
2018.11.11 13:50:13 4: DbLog DbLog -> check Device: LueftungBadEG , Event: ZuluftFeuchtigkeit: 45.0
2018.11.11 13:50:13 4: DbLog DbLog -> number of events received: 3 for device: LueftungBadEG
2018.11.11 13:50:13 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:13 4: DbLog DbLog -> ### start of new Logcycle ###
2018.11.11 13:50:13 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:09 4: DbLog DbLog -> check Device: DS716 , Event: loadavg: 0.90 0.49 0.51
2018.11.11 13:50:09 5: DbLog DbLog -> DbLogExclude of "DS716": .*
2018.11.11 13:50:09 5: DbLog DbLog -> parsed Event: DS716 , Event: eth0_diff: RX: 0.42 MB, TX: 0.26 MB, Total: 0.68 MB
2018.11.11 13:50:09 4: DbLog DbLog -> check Device: DS716 , Event: eth0_diff: RX: 0.42 MB, TX: 0.26 MB, Total: 0.68 MB
2018.11.11 13:50:09 4: DbLog DbLog -> check Device: DS716 , Event: stat_cpu_percent: 4.24 1.71 1.34 87.13 5.56 0.00 0.02
2018.11.11 13:50:09 4: DbLog DbLog -> check Device: DS716 , Event: ram: Total: 7903.75 MB, Used: 611.91 MB, 7.74 %, Free: 5959.38 MB
2018.11.11 13:50:09 4: DbLog DbLog -> number of events received: 4 for device: DS716
2018.11.11 13:50:09 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:09 4: DbLog DbLog -> ### start of new Logcycle ###
2018.11.11 13:50:09 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:09 4: DbLog DbLog -> check Device: DS716 , Event: cpu_freq: 1601
2018.11.11 13:50:09 4: DbLog DbLog -> number of events received: 1 for device: DS716
2018.11.11 13:50:09 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:09 4: DbLog DbLog -> ### start of new Logcycle ###
2018.11.11 13:50:09 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: UnifiController , Event: -AP_SwitchBuero_poePower: 3.14
2018.11.11 13:50:03 5: DbLog DbLog -> DbLogExclude of "UnifiController": .*
2018.11.11 13:50:03 5: DbLog DbLog -> parsed Event: UnifiController , Event: -AP_WLan-Erdgeschoss_utilizationNG: 9
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: UnifiController , Event: -AP_WLan-Erdgeschoss_utilizationNG: 9
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: UnifiController , Event: -AP_SwitchSchaltschrank_poePower: 12.21
2018.11.11 13:50:03 5: DbLog DbLog -> DbLogExclude of "UnifiController": .*
2018.11.11 13:50:03 5: DbLog DbLog -> parsed Event: UnifiController , Event: SonosZP_uptime: 6727809
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: UnifiController , Event: SonosZP_uptime: 6727809
2018.11.11 13:50:03 5: DbLog DbLog -> DbLogExclude of "UnifiController": .*
2018.11.11 13:50:03 5: DbLog DbLog -> parsed Event: UnifiController , Event: SonosZP_uptime: 6727808
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: UnifiController , Event: SonosZP_uptime: 6727808
2018.11.11 13:50:03 5: DbLog DbLog -> DbLogExclude of "UnifiController": .*
2018.11.11 13:50:03 5: DbLog DbLog -> parsed Event: UnifiController , Event: SonosZP_uptime: 6727819
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: UnifiController , Event: SonosZP_uptime: 6727819
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: UnifiController , Event: -UC_events: 370 (last 24h)
2018.11.11 13:50:03 4: DbLog DbLog -> number of events received: 7 for device: UnifiController
2018.11.11 13:50:03 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:03 4: DbLog DbLog -> ### start of new Logcycle ###
2018.11.11 13:50:03 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_08_poe_current: 51.87
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_08_poe_voltage: 47.81
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_08_poe_power: 2.48
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_08_poe_mode: auto
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_08_state: 100 Mbps
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_08_name: IP-Tuerklingel
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_07_poe_current: 78.12
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_07_poe_voltage: 48.01
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_07_poe_power: 3.75
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_07_poe_mode: auto
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_07_state: 1000 Mbps
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_07_name: Port 7
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_06_poe_current: 94.23
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_06_poe_voltage: 47.68
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_06_poe_power: 4.49
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_06_poe_mode: auto
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_06_state: 1000 Mbps
2018.11.11 13:50:03 5: DbLog DbLog -> DbLogExclude of "SwitchSchaltschrank": .*
2018.11.11 13:50:03 5: DbLog DbLog -> parsed Event: SwitchSchaltschrank , Event: port_06_name: WLan-Spitzboden
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_06_name: WLan-Spitzboden
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_05_poe_current: 31.24
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_05_poe_voltage: 47.68
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_05_poe_power: 1.49
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_05_poe_mode: auto
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_05_state: 100 Mbps
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_05_name: ESP-GardenDoor
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_04_state: 1000 Mbps
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_04_name: Synology
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_03_state: 1000 Mbps
2018.11.11 13:50:03 5: DbLog DbLog -> DbLogExclude of "SwitchSchaltschrank": .*
2018.11.11 13:50:03 5: DbLog DbLog -> parsed Event: SwitchSchaltschrank , Event: port_03_name: WagoController
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_03_name: WagoController
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_02_state: 100 Mbps
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_02_name: Cubietruck
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_01_state: 1000 Mbps
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchSchaltschrank , Event: port_01_name: UniFi-Security-Gateway
2018.11.11 13:50:03 4: DbLog DbLog -> number of events received: 32 for device: SwitchSchaltschrank
2018.11.11 13:50:03 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:03 4: DbLog DbLog -> ### start of new Logcycle ###
2018.11.11 13:50:03 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_08_poe_current: 65.55
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_08_poe_voltage: 47.94
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_08_poe_power: 3.14
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_08_poe_mode: auto
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_08_state: 1000 Mbps
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_08_name: Port 8
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_07_poe_current: 0.00
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_07_poe_voltage: 0.00
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_07_poe_power: 0.00
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_07_poe_mode: auto
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_07_state: disconnected
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_07_name: Port 7
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_06_poe_current: 0.00
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_06_poe_voltage: 0.00
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_06_poe_power: 0.00
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_06_poe_mode: auto
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_06_state: disconnected
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_06_name: Port 6
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_05_poe_current: 0.00
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_05_poe_voltage: 0.00
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_05_poe_power: 0.00
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_05_poe_mode: auto
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_05_state: disconnected
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_05_name: GardenDoorESP
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_04_state: disconnected
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_04_name: Port 4
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_03_state: disconnected
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_03_name: Port 3
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_02_state: disconnected
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_02_name: iMac-LAN
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_01_state: 100 Mbps
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: SwitchBuero , Event: port_01_name: Uplink
2018.11.11 13:50:03 4: DbLog DbLog -> number of events received: 32 for device: SwitchBuero
2018.11.11 13:50:03 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:03 4: DbLog DbLog -> ### start of new Logcycle ###
2018.11.11 13:50:03 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:03 4: DbLog DbLog -> check Device: Sonos , Event: LastProcessAnswer: 1541940603.21353
2018.11.11 13:50:03 4: DbLog DbLog -> number of events received: 1 for device: Sonos
2018.11.11 13:50:03 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:03 4: DbLog DbLog -> ### start of new Logcycle ###
2018.11.11 13:50:03 4: DbLog DbLog -> ################################################################
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: state: T: 9.2°C H: 96%, Reading: state, Value: T: 9.2°C H: 96%, Unit:
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: state: T: 9.2°C H: 96%
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: state: T: 9.2°C H: 96%
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_kn_avg2m: 0.7, Reading: wind_speed_kn_avg2m, Value: 0.7, Unit:
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_speed_kn_avg2m: 0.7
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_speed_kn_avg2m: 0.7
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_mph_avg2m: 0.8, Reading: wind_speed_mph_avg2m, Value: 0.8, Unit:
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_speed_mph_avg2m: 0.8
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_speed_mph_avg2m: 0.8
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_avg2m: 1.3, Reading: wind_speed_avg2m, Value: 1.3, Unit:
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_speed_avg2m: 1.3
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_speed_avg2m: 1.3
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_compasspoint_avg2m: S, Reading: wind_compasspoint_avg2m, Value: S, Unit:
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_compasspoint_avg2m: S
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_compasspoint_avg2m: S
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_direction_avg2m: 169, Reading: wind_direction_avg2m, Value: 169, Unit:
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_direction_avg2m: 169
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_direction_avg2m: 169
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_gust_direction_avg10m: 186, Reading: wind_gust_direction_avg10m, Value: 186, Unit:
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_gust_direction_avg10m: 186
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_gust_direction_avg10m: 186
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_gust_fts: 0.0, Reading: wind_gust_fts, Value: 0, Unit:
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_gust_fts: 0.0
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_gust_fts: 0.0
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_gust_kn: 0.0, Reading: wind_gust_kn, Value: 0, Unit: kn
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_gust_kn: 0.0
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_gust_kn: 0.0
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_gust_bft: 0, Reading: wind_gust_bft, Value: 0, Unit: bft
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_gust_bft: 0
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_gust_bft: 0
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_fts: 0.0, Reading: wind_speed_fts, Value: 0.0, Unit:
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_speed_fts: 0.0
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_speed_fts: 0.0
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_kn: 0.0, Reading: wind_speed_kn, Value: 0, Unit: kn
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_speed_kn: 0.0
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_speed_kn: 0.0
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_bft: 0, Reading: wind_speed_bft, Value: 0, Unit: bft
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_speed_bft: 0
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_speed_bft: 0
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_compasspoint: S, Reading: wind_compasspoint, Value: 180, Unit: °
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_compasspoint: S
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_compasspoint: S
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: indoorHumidityAbs_f: 120.4, Reading: indoorHumidityAbs_f, Value: 120.4, Unit: °F
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: indoorHumidityAbs_f: 120.4
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: indoorHumidityAbs_f: 120.4
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: indoorHumidityAbs: 11.2, Reading: indoorHumidityAbs, Value: 11.2, Unit:
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: indoorHumidityAbs: 11.2
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: indoorHumidityAbs: 11.2
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: humidityAbs_f: 74.4, Reading: humidityAbs_f, Value: 74.4, Unit: °F
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: humidityAbs_f: 74.4
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: humidityAbs_f: 74.4
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: humidityAbs: 8.6, Reading: humidityAbs, Value: 8.6, Unit:
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: humidityAbs: 8.6
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: humidityAbs: 8.6
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: indoorDewpoint_f: 59.0, Reading: indoorDewpoint_f, Value: 59.0, Unit: °F
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: indoorDewpoint_f: 59.0
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: indoorDewpoint_f: 59.0
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: indoorDewpoint: 13.2, Reading: indoorDewpoint, Value: 13.2, Unit:
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: indoorDewpoint: 13.2
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: indoorDewpoint: 13.2
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: pressureAbs_mm: 7.6, Reading: pressureAbs_mm, Value: 7, Unit: mmHg
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: pressureAbs_mm: 7.6
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: pressureAbs_mm: 7.6
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: pressure_mm: 7.5, Reading: pressure_mm, Value: 7, Unit: mmHg
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: pressure_mm: 7.5
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: pressure_mm: 7.5
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: UVR: 362, Reading: UVR, Value: 362, Unit: W
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: UVR: 362
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: UVR: 362
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: UV: 1, Reading: UV, Value: 1, Unit: UVI
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: UV: 1
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: UV: 1
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: solarradiation: 74.17, Reading: solarradiation, Value: 74, Unit: W
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: solarradiation: 74.17
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: solarradiation: 74.17
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: wind_speed_mps: 0.0, Reading: wind_speed_mps, Value: 0, Unit: m
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: wind_speed_mps: 0.0
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: wind_speed_mps: 0.0
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: rain_day: 1.8, Reading: rain_day, Value: 2, Unit: mm
2018.11.11 13:50:00 5: DbLog DbLog -> DbLogInclude of "WH2600": .*
2018.11.11 13:50:00 5: DbLog DbLog -> parsed Event: WH2600 , Event: rain_day: 1.8
2018.11.11 13:50:00 4: DbLog DbLog -> check Device: WH2600 , Event: rain_day: 1.8
2018.11.11 13:50:00 4: DbLog DbLog -> added event - Timestamp: 2018-11-11 13:49:59, Device: WH2600, Type: HP1000, Event: rain_in: 0.00, Reading: rain_in, Value: 0, Unit:
Nimm mal die
Readimgs mit Unit: ° oder mit Unit: °F aus dem Log raus bzw bastle die noch mit in die valueFn mit rein.
Ich habe DbLogexclude .* beim Device WH2600 gesetzt, leider hilft das auch nicht..
Hmm, mach nochmal ein verbose 5. Irgendein datensatz muss es ja sein der stört. Geh einfach mal nach dem ausschlussprinzip vor.
Ich hab jetzt 10 minuten mit verbose 5 gelogt, die einzigen ° die ich finde gehören zum Device WH2600...
Kann etwa anderes hier reinspuken? Kann man nicht genauer nachschauen welche Zeile die Fehler verursacht?
Kann freilich auch was anderes sein. Steuerzeichen due man nicht sieht. Aber die habe ich eigentlich alle schon mit dem charfilter entfernt. Irgendeinen anhaltspunkt brauche ich. Vllt. Steht etwas direkt im datenbank log auf der Syno.
Was ich auch noch machen kann ist zu versuchen einen debug Modus mit Hilfe des Perl Datenbank Moduls zu implementieren. Aber das ist etwas Programmierarbeit und aktuell nicht vorhanden.
so komme ich jedanfalls nicht weiter - °C war im Device vorhanden wegen gesetztem stateFormat auf Temperature..
Ich habe das nun rausgeworfen, bekomme immer noch fehler wenn das Modul in die DB schreiben will - aber bei gesetztem verbose 5 kann ich nichts auffälliges im Log finden. Im Log auf der Syno kann ich auch nichts erkennen...
Zeige bitte nochmal ein jetziges verbose 5. Wenn ich wieder zu Hause bin und zeit habe schau ich mal in die module der beteiligten quellen. Vllt. Fällt mir etwas auf.
Ansonsonsten versuche ich etwas in dblog zu implementieren was die Suche in solchen Fällen erleichtert. Braucht halt etwas zeit.
Das Loggen wird trotzdem funktionieren ausser der problematischen sätze.
Du kannst mit einem db tool , z.b. dbrep, in die history schauen welche sätze jeweils fehle. Vllt. Kommt man dadurch weiter.
Weil es schnell sehr viel wird habe ich ein .txt file mit dem verbose 5 in meine Dropbox gelegt - hier der Link.
https://www.dropbox.com/s/rz552scaipw6jwp/Log_Verbose5.rtf?dl=0 (https://www.dropbox.com/s/rz552scaipw6jwp/Log_Verbose5.rtf?dl=0)
Ich setze DbLog nun auf verbose 2 und versuche zu schauen welche einträghe nicht gemacht werden...
Danke Dir für deine Hilfe!
Ich meine mit MariaDB 10 hat sich der MySQL-Port auf 3307 geändert. Kann es das sein?
Gruß Harry
Gesendet von iPad mit Tapatalk
Hallo Harry,
mit dem Port hast du zwar recht, aber es würde eine andere generelle fehlermeldung kommen.
Danke fürs mitdenken ! :)
Grüsse,
Heiko
Also jetzt habe ich dein Log überflogen und bin mir ziemlcih sicher, dass es die Statistikdaten sind.
Es sind nämlich bei jedem Zyklus immer 5 und es sind immer 5 Statistiksätze in einem Zyklus enthalten:
2018.11.11 16:51:50 2: DbLog DbLog -> Error table history - DBD::mysql::st execute_array failed: executing 43 generated 5 errors at ./FHEM/93_DbLog.pm line 2068.\
2018.11.11 16:51:47 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 16:51:35, Device: WMZ, Type: MODBUSATTR, Event: Waermeleistung: 3000.0, Reading: Waermeleistung, Value: 3000.0, Unit: \
2018.11.11 16:51:47 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 16:51:35, Device: WMZ, Type: MODBUSATTR, Event: aktAZ: 6.61, Reading: aktAZ, Value: 6.61, Unit: \
2018.11.11 16:51:47 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 16:51:35, Device: WMZ, Type: MODBUSATTR, Event: Spreizung: 2.5, Reading: Spreizung, Value: 2.5, Unit: \
2018.11.11 16:51:47 5: DbLog DbLog -> processing event Timestamp: 2018-11-11 16:51:35, Device: WMZ, Type: MODBUSATTR, Event: statGesamtWaermemenge: Hour: 0.003 Day: 0.024 Month: 0.422 Year: 8.012, Reading: statGesamtWaermemenge, Value: Hour: 0.003 Day: 0.024 Month: 0.422 Year: 8.012, Unit: \
An den Sätzen an sich kann ich jetzt nichts merkwürdiges auf den ersten Blick erkenne. Aber wenn meine Annahme stimmt können wir uns die mal genauer anschauen.
Nimm die mal aus dem Logging und check das bitte, morgen dann mehr von mir...
Grüße
Heiko
Guten Morgen Heiko,
ich habe gestern abend noch sehr großzügig mit dem DbLogExclude attribut um mich geworfen - es wurde eh viel zu viel geloggt. Leider hatte ich vergessen verbose beim DbLog Device wieder auf 3 zu setzen, kann also leider nicht sagen ob das problem über nacht auftauchte.
Den WMZ hole ich mir über ein weiteres FHEM auf einem Raspi ins Haupt FHEM auf der Syno - das kann ich einfach abstellen.
Aktuell ist das problem aber nicht mehr da - ich werde berichten.
Tausend Dank für Deine hilfe..!
Zu früh gefreut - ich habe wieder einige einträge im Log....
2018.11.12 14:41:17 2: DbLog DbLog -> Error table history - DBD::mysql::st execute_array failed: executing 299 generated 1 errors at ./FHEM/93_DbLog.pm line 2068.
2018.11.12 14:26:17 2: DbLog DbLog -> Error table history - DBD::mysql::st execute_array failed: executing 297 generated 1 errors at ./FHEM/93_DbLog.pm line 2068.
Ich nehm jetzt erst mal den Wärmemengenzähler raus, mal schauen ob der Spuk dann ein ende hat.
Obwohl nun der WMZ und die WH2600 deaktiviert waren habe ich noch einen Fehler im Log gefunden...
Kann es vielleicht sein das die Datenbank nicht mehr ok ist? Ich habe gestern versucht einen dump zu erstellen und nach etwa einer Stunde abgebrochen, ich habe knapp über 10 millionen einträge gesammelt... Vielleicht ist ein problem beim update entstanden weil FHEM schreiben wollte..
Welchen Fehler hast du denn noch bekommen ? Gibt es ein verbose 5 davon ?
ZitatKann es vielleicht sein das die Datenbank nicht mehr ok ist?
Ich denke nicht dass es an dem ist. Wenn es einen echten DB Fehler gäbe müsste man ihn auf der Syno im DB-Log sehen.
Auf der Syno gehe dazu mal in das Verzeichnis:
/var/packages/MariaDB10/target/mysql
Dort gibt es ein File <Servername>.err. Schau da mal rein ob dir was auffällt.
MariaDB ist zwar auch nicht vor Fehler gefeit, aber es ist eine echte Datenbank die Lesen und Schreiben zur gleichen Zeit mit mehreren Tasks problemlos verarbeitet. Ich habe in meiner Test-Db über 36Mio Einträge und die quäle ich wirklich immer wieder. ;)
Kommt bei verbose 5 auch ein Fehler mit 3 hinterm Timestamp?
Ja
Das Log auf der Syno ist meiner meinung nach unauffällig...
ZitatMariaDB ist zwar auch nicht vor Fehler gefeit, aber es ist eine echte Datenbank die Lesen und Schreiben zur gleichen Zeit mit mehreren Tasks problemlos verarbeitet. Ich habe in meiner Test-Db über 36Mio Einträge und die quäle ich wirklich immer wieder.
Sollte es dann auf einer DS716+II nicht etwas schneller gehen einen dump zu erstellen? Oder muss ich mich wirklich in geduld üben?
Über Nacht laufen lassen?
Ich benutze ein "dumpMySQL serverSide" mit einem DbRep-Device. Das läuft dann auf meiner 415+ und ist in ein paar Minuten durch.
Ich habe es gerade gestartet und schreibe dir gleich wie lange es gedauert hat....
So ist durch, hat rund 10 Minuten gedauert. Bei der Zeit ist das komprimieren des Dumps noch mit dabei:
2018.11.12 20:04:07.837 3: DbRep Rep.fhemtest1.Dump - execute command before dump: 'set LogDB1 reopen 3600'
2018.11.12 20:04:07.838 2: DbLog LogDB1: Connection closed until 21:04:07 (3600 seconds).
2018.11.12 20:04:07.877 3: DbRep Rep.fhemtest1.Dump - Searching for tables inside database fhemtest1....
2018.11.12 20:04:07.895 3: DbRep Rep.fhemtest1.Dump - Starting dump of database 'fhemtest1', table 'history'
2018.11.12 20:13:16.115 3: DbRep Rep.fhemtest1.Dump - compress file /sds1/backup/dumps_FHEM/fhemtest1_history_2018_11_12_20_04.csv
2018.11.12 20:15:21.894 3: DbRep Rep.fhemtest1.Dump - file compressed to output file: /sds1/backup/dumps_FHEM/fhemtest1_history_2018_11_12_20_04.csv.gzip
2018.11.12 20:15:23.279 3: DbRep Rep.fhemtest1.Dump - input file deleted: /sds1/backup/dumps_FHEM/fhemtest1_history_2018_11_12_20_04.csv
2018.11.12 20:15:23.280 3: DbRep Rep.fhemtest1.Dump - Number of exported datasets: 36512423
2018.11.12 20:15:23.281 3: DbRep Rep.fhemtest1.Dump - Size of backupfile: 408.31 MB
2018.11.12 20:15:23.284 3: DbRep Rep.fhemtest1.Dump - Deleting old dumpfile 'fhemtest1_history_2018_09_09_17_48.csv.gzip'
2018.11.12 20:15:23.520 3: DbRep Rep.fhemtest1.Dump - Finished backup of database fhemtest1 - total time used: 676 seconds
2018.11.12 20:15:23.560 2: DbRep Rep.fhemtest1.Dump - command message after dump: "Reopen executed."
2018.11.12 20:15:23.610 3: DbRep Rep.fhemtest1.Dump - Database dump finished successfully.
EDIT: Habe gerade mal nach deiner Syno gegoogelt. Die DS716+II dürfte ja noch einen Zacken schneller sein als meine Zumal ich ein Raid 5 habe was eh nicht so ein schnelles Plattensubsystem auf der Syno ist.
Ich habs mal versucht...
2018.11.12 20:23:40 2: DbRep DbRep - DBD::mysql::st execute failed: Access denied for user 'fhem'@'%' (using password: YES) at ./FHEM/93_DbRep.pm line 6647.
2018.11.12 20:23:40 3: DbRep DbRep - Starting dump of database 'fhem', table 'history'
2018.11.12 20:23:40 3: DbRep DbRep - Size of database fhem after optimize (MB): 1612.09
2018.11.12 20:23:40 3: DbRep DbRep - 2 tables have been optimized.
2018.11.12 20:23:40 3: DbRep DbRep - Table 2 `history` optimized successfully.
2018.11.12 20:19:33 3: DbRep DbRep - Optimizing table `history` (INNODB). It will take a while.
2018.11.12 20:19:33 3: DbRep DbRep - Table 1 `current` optimized successfully.
2018.11.12 20:19:32 3: DbRep DbRep - Optimizing table `current` (INNODB). It will take a while.
2018.11.12 20:19:32 3: DbRep DbRep - Optimizing tables
2018.11.12 20:19:32 3: DbRep DbRep - Size of database fhem before optimize (MB): 1452.59
2018.11.12 20:19:32 3: DbRep DbRep - Searching for tables inside database fhem....
2018.11.12 20:19:32 3: DbRep DbRep - ################################################################
2018.11.12 20:19:32 3: DbRep DbRep - ### New database serverSide dump ###
2018.11.12 20:19:32 3: DbRep DbRep - ################################################################
ZitatAccess denied for user 'fhem'@'%'
Der verwendete Datenbankuser benötigt das "FILE"-Privileg.
Steht in der Commandref ... Sorry, hätte ich gleich drauf hinweisen sollen.
Gib dem User mal dieses Recht z.B. mit phpMyAdmin.
Ich habe dir eine neue DbLog-Version nach contrib gestellt (Downloadbutton verwenden):
https://svn.fhem.de/trac/browser/trunk/fhem/contrib/DS_Starter
In dieser Version gibt es zwei neue Attribute um Traces zu aktivieren. Setze dir zu Anfang die Attribute so:
traceFlag = SQL
traceLevel = 2
Damit werden mehr internas ausgegeben.
Wenn alles funktioniert, sieht es dann aus wie bei mir:
mysql_st_internal_execute MYSQL_VERSION_ID 100121
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-12 22:56:04','Dum.Energy','DUMMY','SelfConsumptionQuote: 0.0','SelfConsumptionQuote','0.0','')
<- dbd_st_execute returning imp_sth->row_num 1
2 <- execute= ( 1 ) [1 items] at /usr/lib/x86_64-linux-gnu/perl5/5.24/DBI.pm line 2020 via at ./FHEM/93_DbLog.pm line 2079
2 -> execute for DBD::mysql::st (DBI::st=HASH(0x55f871fde0c8)~INNER '2018-11-12 22:56:04' 'Dum.Energy' 'DUMMY' 'T: 589.7' 'T' '589.7' '') thr#55f866fa8010
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
-> dbd_st_execute for 55f868d0bab0
>- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
<- dbd_st_free_result_sets
mysql_st_internal_execute MYSQL_VERSION_ID 100121
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-12 22:56:04','Dum.Energy','DUMMY','T: 589.7','T','589.7','')
<- dbd_st_execute returning imp_sth->row_num 1
2 <- execute= ( 1 ) [1 items] at /usr/lib/x86_64-linux-gnu/perl5/5.24/DBI.pm line 2020 via at ./FHEM/93_DbLog.pm line 2079
1 <- execute_for_fetch= ( 74 74 ) [2 items] at /usr/lib/x86_64-linux-gnu/perl5/5.24/DBI.pm line 2009 via at ./FHEM/93_DbLog.pm line 2079
<- execute_array= ( 74 74 ) [2 items] at ./FHEM/93_DbLog.pm line 2079 via at ./FHEM/93_DbLog.pm line 2076
-> DESTROY for DBD::mysql::st (DBI::st=HASH(0x55f871fde0c8)~INNER) thr#55f866fa8010
Freeing 7 parameters, bind 0 fbind 0
<- DESTROY= ( undef ) [1 items] at ./FHEM/93_DbLog.pm line 2199 via at ./FHEM/93_DbLog.pm line 2199
Vielleicht kommen wir damit bei dir weiter.
EDIT: setze dann verbose = 3, sonst wird es zuviel.
Grüße
Heiko
Danke Dir,
ich komme leider erst heute abend zum einspielen und testen...
Kannst Du mir noch eine tip geben bzgl. dem File Privileg des fhem users damit das dump erstellen klappt?
In phpmyAdmin finde ich nichts dergleichen, gibt es vielleicht einen SQL befehl den ich absetzen kann?
Hier jetzt ein auszug aus dem Log mit den nagepassten Modulen und den gesetzten Attributen - schaut ähnlich aus wie bei dir, ich frage mich wie ich hier nun einen Fehler erkennen soll...
<- DESTROY= ( undef ) [1 items] at 93_DbLog.pm line 2199
Freeing 7 parameters, bind 0 fbind 0
-> DESTROY for DBD::mysql::st (DBI::st=HASH(0x7f75520)~INNER) thr#1a97010
<- execute_array= ( 6 6 ) [2 items] at 93_DbLog.pm line 2079
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:22:15','SDM630','MODBUSSDM630M','Power_L3__W: 0','Power_L3__W','0','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:22:15','SDM630','MODBUSSDM630M','Power_L2__W: 470','Power_L2__W','470','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:22:15','SDM630','MODBUSSDM630M','Power_L1__W: 18','Power_L1__W','18','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:22:12','WMZ','MODBUSATTR','Waermeleistung: 3000.0','Waermeleistung','3000.0','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:22:12','WMZ','MODBUSATTR','aktAZ: 6.40','aktAZ','6.40','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:22:12','WMZ','MODBUSATTR','aktWaermeleistung: 3.0','aktWaermeleistung','3.0','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
-> dbd_st_FETCH_attrib for 6f09c30, key NUM_OF_PARAMS
-> execute_array in DBD::_::st for DBD::mysql::st (DBI::st=HASH(0x7ee9548)~0x7f75520 HASH(0x829ef88)) thr#1a97010
DBI::st=HASH(0x7f75520) trace level set to 0x100/2 (DBI @ 0x0/0) in DBI 1.637-ithread (pid 11890)
<- DESTROY= ( undef ) [1 items] at 93_DbLog.pm line 2199
Freeing 7 parameters, bind 0 fbind 0
-> DESTROY for DBD::mysql::st (DBI::st=HASH(0x8206af0)~INNER) thr#1a97010
<- execute_array= ( 8 8 ) [2 items] at 93_DbLog.pm line 2079
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:21:43','SDM630','MODBUSSDM630M','Power_L3__W: 0','Power_L3__W','0','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:21:43','SDM630','MODBUSSDM630M','Power_L2__W: 469','Power_L2__W','469','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:21:43','SDM630','MODBUSSDM630M','Power_L1__W: 18','Power_L1__W','18','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:21:42','WMZ','MODBUSATTR','Waermeleistung: 2900.0','Waermeleistung','2900.0','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:21:42','WMZ','MODBUSATTR','aktAZ: 6.18','aktAZ','6.18','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:21:42','WMZ','MODBUSATTR','aktWaermeleistung: 2.9','aktWaermeleistung','2.9','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:21:42','WMZ','MODBUSATTR','aktAZ: 6.40','aktAZ','6.40','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:21:42','DbRep','DBREP','state: connected','state','connected','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
-> dbd_st_FETCH_attrib for 6f09c30, key NUM_OF_PARAMS
-> execute_array in DBD::_::st for DBD::mysql::st (DBI::st=HASH(0x7e9b430)~0x8206af0 HASH(0x8206d60)) thr#1a97010
DBI::st=HASH(0x8206af0) trace level set to 0x100/2 (DBI @ 0x0/0) in DBI 1.637-ithread (pid 11847)
2018.11.13 18:21:45 1: SONOS4: Restore-Thread gestartet. Warte auf Arbeit...
2018.11.13 18:21:45 1: SONOS3: IsAlive-Thread gestartet. Warte 120 Sekunden und pruefe dann alle 30 Sekunden...
2018.11.13 18:21:45 1: SONOS2: LongJobs-Thread gestartet. Prüfe auf LongJobs...
2018.11.13 18:21:45 1: SONOS1: UPnP-Thread gestartet.
2018.11.13 18:21:42 3: DbRep DbRep - Connectiontest to db mysql:database=fhem;host=127.0.0.1;port=3307 successful
<- DESTROY= ( undef ) [1 items] at 93_DbLog.pm line 2199
Freeing 7 parameters, bind 0 fbind 0
-> DESTROY for DBD::mysql::st (DBI::st=HASH(0x828f0f8)~INNER) thr#1a97010
<- execute_array= ( 4 4 ) [2 items] at 93_DbLog.pm line 2079
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:21:12','SDM630','MODBUSSDM630M','Power_L3__W: 0','Power_L3__W','0','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:21:12','SDM630','MODBUSSDM630M','Power_L2__W: 469','Power_L2__W','469','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:21:12','SDM630','MODBUSSDM630M','Power_L1__W: 18','Power_L1__W','18','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:21:12','WMZ','MODBUSATTR','Durchfluss: 1050','Durchfluss','1050','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
-> dbd_st_FETCH_attrib for 6f09c30, key NUM_OF_PARAMS
-> execute_array in DBD::_::st for DBD::mysql::st (DBI::st=HASH(0x82886f0)~0x828f0f8 HASH(0x828f1d0)) thr#1a97010
DBI::st=HASH(0x828f0f8) trace level set to 0x100/2 (DBI @ 0x0/0) in DBI 1.637-ithread (pid 11825)
2018.11.13 18:21:12 3: DbRep DbRep - Connectiontest to database mysql:database=fhem;host=127.0.0.1;port=3307 with user fhem
PS: meine Logs laufen von oben nach unten ;-)
ZitatKannst Du mir noch eine tip geben bzgl. dem File Privileg des fhem users damit das dump erstellen klappt?
In phpmyAdmin finde ich nichts dergleichen, gibt es vielleicht einen SQL befehl den ich absetzen kann?
Schau mal im Anhang, dort siehst du es. Bei Benutzerkonten deinen DB-User auswählen und bei globalen Daten anhaken.
Der SQL-Befehl wäre:
GRANT FILE ON *.* TO 'fhem'@'%'
Den musst du als root bzw. User mit Grant-Recht ausführen.
Zitat
Hier jetzt ein auszug aus dem Log mit den nagepassten Modulen und den gesetzten Attributen - schaut ähnlich aus wie bei dir, ich frage mich wie ich hier nun einen Fehler erkennen soll...
Das schaue ich mir an. Die Frage ist ... tritt denn ein Fehler überhaupt auf ?
Also im Prinzip müsstest du verbose 3 einstellen und sobald eine Fehlermitteilung kommt den davor ! liegenden Trace posten. Das ist zumindest der Plan. ;)
Bei mir kommt kein Fehler, kann es deswegen auch nicht genau beschreiben.
hab einen...
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:47:13','SDM630','MODBUSSDM630M','Power_L1__W: 18','Power_L1__W','18','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
-> dbd_st_FETCH_attrib for 6f09c30, key NUM_OF_PARAMS
-> execute_array in DBD::_::st for DBD::mysql::st (DBI::st=HASH(0x8c08298)~0x8c09cb8 HASH(0x8b12030)) thr#1a97010
DBI::st=HASH(0x8c09cb8) trace level set to 0x100/2 (DBI @ 0x0/0) in DBI 1.637-ithread (pid 13495)
<- DESTROY= ( undef ) [1 items] at 93_DbLog.pm line 2199
Freeing 7 parameters, bind 0 fbind 0
-> DESTROY for DBD::mysql::st (DBI::st=HASH(0x8ba5748)~INNER) thr#1a97010
2018.11.13 18:47:11 2: DbLog DbLog -> Error table history - DBD::mysql::st execute_array failed: executing 5 generated 1 errors at ./FHEM/93_DbLog.pm line 2079.
<- execute_array= ( undef ) [1 items] at 93_DbLog.pm line 2079
!! ERROR: 2000000000 'executing 5 generated 1 errors' (err#1)
-- HandleSetErr err=2000000000, errstr='executing 5 generated 1 errors', state=undef, undef
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:46:43','SDM630','MODBUSSDM630M','Power_L3__W: 0','Power_L3__W','0','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:46:43','SDM630','MODBUSSDM630M','Power_L2__W: 469','Power_L2__W','469','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Sag mal, hast du einen Unique Index auf die history gesetzt ?
Wenn ich es richtig lese, wird dieser DAtensatz eingefügt:
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:46:43','SDM630','MODBUSSDM630M','Power_L2__W: 469','Power_L2__W','469','')
Der nächste geht schief:
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 18:46:43','SDM630','MODBUSSDM630M','Power_L3__W: 0','Power_L3__W','0','')
Die haben genau den gleichen Timestamp.
Und mach bitte im DbLog mal ein "set ... configCheck".
Ich muss gleich weg ... schaue nachher nochmal vorbei ...
Ähm, der Timestamp kann ja gleich sein - es geht um unterschiedliche Phasen des Drehstromzählers...
Einen Unique Index habe ich nicht (nicht bewusst) gesetzt...
Hier ein configCheck
Result of DbLog version check
Used DbLog version: 3.13.0
Recommendation: Your running version may be the current one. Please check for updates of DbLog periodically.
Result of configuration read check
Connection parameter store type: file
Connection parameter: Connection -> mysql:database=fhem;host=127.0.0.1;port=3307, User -> fhem, Password -> read o.k.
Result of connection check
Connection to database fhem successfully done.
Recommendation: settings o.k.
Result of encoding check
Encoding used by Client (connection): UTF8
Encoding used by DB fhem: UTF8
Recommendation: settings o.k.
Result of logmode check
Logmode of DbLog-device DbLog is: asynchronous
Recommendation: settings o.k.
Result of shutdown sequence preparation check
Attribute "shutdownWait" is set to:
Recommendation: Due to Reading "background_processing_time" is not available (you may set attribute "showproctime"), there is only a rough estimate to
set attribute "shutdownWait" to 2 seconds.
Result of plot generation method check
WARNING - at least one of your FHEMWEB devices have attribute "plotfork = 1" not set. This may cause blocking situations when creating plots.
WEB: plotfork=1
WEBphone: plotfork=0
WEBtablet: plotfork=0
WEBweatherstation: plotfork=0
Recommendation: You should set attribute "plotfork = 1" in relevant devices
Result of table 'history' check
Column width set in DB fhem.history: 'DEVICE' = 32, 'TYPE' = 32, 'EVENT' = 512, 'READING' = 32, 'VALUE' = 32, 'UNIT' = 32
Column width used by DbLog: 'DEVICE' = 64, 'TYPE' = 64, 'EVENT' = 512, 'READING' = 64, 'VALUE' = 128, 'UNIT' = 32
Recommendation: The relation between column width in table history and the field width used in device DbLog don't meet the requirements. Please make sure that the width of database field definition is equal or larger than the field width used by the module. Compare the given results.
Currently the default values for field width are:
DEVICE: 64
TYPE: 64
EVENT: 512
READING: 64
VALUE: 128
UNIT: 32
You can change the column width in database by a statement like 'alter table history modify VALUE varchar(128);' (example for changing field 'VALUE'). You can do it for example by executing 'sqlCmd' in DbRep or in a SQL-Editor of your choice. (switch DbLog to asynchron mode for non-blocking).
Alternatively the field width used by DbLog can be adjusted by setting attributes 'colEvent', 'colReading', 'colValue'. (pls. refer to commandref)
Result of table 'current' check
Column width set in DB fhem.current: 'DEVICE' = 32, 'TYPE' = 32, 'EVENT' = 512, 'READING' = 32, 'VALUE' = 32, 'UNIT' = 32
Column width used by DbLog: 'DEVICE' = 64, 'TYPE' = 64, 'EVENT' = 512, 'READING' = 64, 'VALUE' = 128, 'UNIT' = 32
Recommendation: The relation between column width in table current and the field width used in device DbLog don't meet the requirements. Please make sure that the width of database field definition is equal or larger than the field width used by the module. Compare the given results.
Currently the default values for field width are:
DEVICE: 64
TYPE: 64
EVENT: 512
READING: 64
VALUE: 128
UNIT: 32
You can change the column width in database by a statement like 'alter table current modify VALUE varchar(128);' (example for changing field 'VALUE'). You can do it for example by executing 'sqlCmd' in DbRep or in a SQL-Editor of your choice. (switch DbLog to asynchron mode for non-blocking).
Alternatively the field width used by DbLog can be adjusted by setting attributes 'colEvent', 'colReading', 'colValue'. (pls. refer to commandref)
Result of check 'Search_Idx' availability
Index 'Search_Idx' exists and contains recommended fields 'DEVICE', 'READING', 'TIMESTAMP'.
Recommendation: settings o.k.
Result of check 'Report_Idx' availability for DbRep-devices
At least one DbRep-device assigned to DbLog is used, but the recommended index 'Report_Idx' is missing.
Recommendation: You can create the index by executing statement 'CREATE INDEX Report_Idx ON `history` (TIMESTAMP, READING) USING BTREE;'
Depending on your database size this command may running a long time.
Please make sure the device 'DbLog' is operating in asynchronous mode to avoid FHEM from blocking when creating the index.
Note: If you have just created another index which covers the same fields and order as suggested (e.g. a primary key) you don't need to create the 'Report_Idx' as well !
Der Dump wurde wie erwartet nun schnell erstellt - hatte mich schon gewundert, die DS716+II sollte doch eigentlich genug Power haben für sowas..
2018.11.13 19:10:56 3: DbRep DbRep - Database dump finished successfully.
2018.11.13 19:10:56 3: DbRep DbRep - Finished backup of database fhem - total time used: 309 seconds
2018.11.13 19:10:56 1: PERL WARNING: Use of uninitialized value $fref in pattern match (m//) at ./FHEM/93_DbRep.pm line 9220.
2018.11.13 19:10:56 3: DbRep DbRep - Number of exported datasets: 11589275
2018.11.13 19:10:56 1: PERL WARNING: Use of uninitialized value $fref in pattern match (m//) at ./FHEM/93_DbRep.pm line 6835.
Da sind auch noch ein paar Warnings - und ähm, ich versuchte ja zweimal einen dump zu erstellen beim ersten mal ging das Ding in eine endlosschleife, beim zweiten mal gabs dann die meldung bzgl. FILE Privileg.
Der Dritte jetzt gerade lief durch.
Vielleicht kannst Du damit was anfangen und die endlosschleife abfangen.
Hier noch ein Fehler - wieder der SDM630 - mal schauen was ich da machen kann.
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 19:07:14','WMZ','MODBUSATTR','aktAZ: 6.42','aktAZ','6.42','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
-> dbd_st_FETCH_attrib for 6f09c30, key NUM_OF_PARAMS
-> execute_array in DBD::_::st for DBD::mysql::st (DBI::st=HASH(0x90570c0)~0x90712f8 HASH(0x906c738)) thr#1a97010
DBI::st=HASH(0x90712f8) trace level set to 0x100/2 (DBI @ 0x0/0) in DBI 1.637-ithread (pid 14828)
<- DESTROY= ( undef ) [1 items] at 93_DbLog.pm line 2199
Freeing 7 parameters, bind 0 fbind 0
-> DESTROY for DBD::mysql::st (DBI::st=HASH(0x93623b8)~INNER) thr#1a97010
2018.11.13 19:07:14 2: DbLog DbLog -> Error table history - DBD::mysql::st execute_array failed: executing 6 generated 1 errors at ./FHEM/93_DbLog.pm line 2079.
<- execute_array= ( undef ) [1 items] at 93_DbLog.pm line 2079
!! ERROR: 2000000000 'executing 6 generated 1 errors' (err#1)
-- HandleSetErr err=2000000000, errstr='executing 6 generated 1 errors', state=undef, undef
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 19:06:44','SDM630','MODBUSSDM630M','Power_L3__W: 0','Power_L3__W','0','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
<- dbd_st_execute returning imp_sth->row_num 1
Binding parameters: INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES ('2018-11-13 19:06:44','SDM630','MODBUSSDM630M','Power_L2__W: 467','Power_L2__W','467','')
>parse_params statement INSERT INTO history (TIMESTAMP, DEVICE, TYPE, EVENT, READING, VALUE, UNIT) VALUES (?,?,?,?,?,?,?)
mysql_st_internal_execute MYSQL_VERSION_ID 50172
<- dbd_st_free_result_sets
<- dbd_st_free_result_sets RC -1
>- dbd_st_free_result_sets
-> dbd_st_execute for 6f0a608
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Called: dbd_bind_ph
Eine ganz wichtige Erkenntnis kommt aus dem configCheck, deine DB ist nicht (mehr) richtig eingerichtet.
Die Spaltenbreiten stammen noch aus alter Zeit. Passe die erstmal dringend an die jetzigen Erfordernisse an.
Das betrifft alle Felder die im configCheck angemeckert werden in beiden Tabellen. Außer 'EVENT' und 'UNIT' musst du alle Felder in history und current anpassen.
Hier das Beispiel:
alter table history modify VALUE varchar(128);
Welche DbRep-Version hast du bei dir im Einsatz ?
Ein List vom DbRep Device...
Internals:
DATABASE fhem
DEF DbLog
LASTCMD dumpMySQL serverSide
MODEL Agent
NAME DbRep
NOTIFYDEV global,DbRep
NR 188
NTFY_ORDER 50-DbRep
ROLE Agent
STATE Database backup finished
TYPE DbRep
UTF8 1
VERSION 8.9.5
HELPER:
DBLOGDEVICE DbLog
IDRETRIES 3
MINTS 2018-09-30 21:36:08
DBREPCOL:
COLSET 1
DEVICE 64
EVENT 512
READING 64
TYPE 64
UNIT 32
VALUE 128
Helper:
DBLOG:
state:
DbLog:
TIME 1542132656.85175
VALUE Database backup finished
READINGS:
2018-11-13 19:10:56 DumpFileCreated ./fhem_history_2018_11_13_19_09.csv
2018-11-13 19:10:56 DumpRowsCurrent n.a.
2018-11-13 19:10:56 DumpRowsHistory 11589275
2018-11-13 19:10:56 background_processing_time 309.1530
2018-11-13 19:10:56 state Database backup finished
dbloghash:
COLUMNS field length used for Device: 64, Type: 64, Event: 512, Reading: 64, Value: 128, Unit: 32
CONFIGURATION ./db.conf
DEF ./db.conf WMZ.*|Lueftung.*:A.*|Power_L.*|R.*|V.*|Z.*|akt.*
MODE asynchronous
MODEL MYSQL
NAME DbLog
NR 164
NTFY_ORDER 50-DbLog
PID 11716
REGEXP WMZ.*|Lueftung.*:A.*|Power_L.*|R.*|V.*|Z.*|akt.*
STATE connected
TYPE DbLog
UTF8 1
VERSION 3.13.0
dbconn mysql:database=fhem;host=127.0.0.1;port=3307
dbuser fhem
HELPER:
COLSET 1
DEVICECOL 64
EVENTCOL 512
OLDSTATE connected
READINGCOL 64
TYPECOL 64
UNITCOL 32
VALUECOL 128
Helper:
DBLOG:
state:
DbLog:
TIME 1542142807.0025
VALUE DBD::mysql::st execute_array failed
READINGS:
2018-11-14 18:14:21 CacheUsage 0
2018-11-14 18:14:20 NextSync 2018-11-14 18:14:50 or if CacheUsage 500 reached
2018-11-10 14:41:48 countCurrent 767
2018-11-10 14:41:48 countHistory 10968723
2018-09-30 21:57:15 reduceLogState reduceLogNbl finished. Rows processed: 0, deleted: 0, time: 0.11sec
2018-11-14 18:14:21 state connected
cache:
index 12916
helper:
bm:
DbLog_Attr:
cnt 5
dmx -1000
dtot 0
dtotcnt 0
mTS 13.11. 18:21:09
max 5.29289245605469e-05
tot 0.000190019607543945
mAr:
set
DbLog
traceFlag
SQL
DbLog_Get:
cnt 8
dmx -1000
dtot 0
dtotcnt 0
mTS 13.11. 18:21:21
max 4.98294830322266e-05
tot 0.000261545181274414
mAr:
HASH(0x638e850)
DbLog
?
DbLog_Log:
cnt 78580
dmx -1000
dtot 0
dtotcnt 0
mTS 14.11. 17:44:28
max 0.0326840877532959
tot 112.483788490295
mAr:
HASH(0x638e850)
HASH(0x70c6c28)
DbLog_Set:
cnt 35
dmx -1000
dtot 0
dtotcnt 0
mTS 13.11. 19:22:56
max 0.0496408939361572
tot 0.0688180923461914
mAr:
HASH(0x638e850)
DbLog
configCheck
helper:
bm:
DbRep_Attr:
cnt 3
dmx -1000
dtot 0
dtotcnt 0
mTS 13.11. 20:15:37
max 0.00191211700439453
tot 0.0021202564239502
mAr:
set
DbRep
role
Agent
DbRep_Get:
cnt 8
dmx -1000
dtot 0
dtotcnt 0
mTS 13.11. 19:05:47
max 0.000117063522338867
tot 0.000555753707885742
mAr:
HASH(0x723c3e0)
DbRep
?
DbRep_Notify:
cnt 24
dmx -1000
dtot 0
dtotcnt 0
mTS 13.11. 19:05:47
max 0.00020289421081543
tot 0.00139307975769043
mAr:
HASH(0x723c3e0)
HASH(0x723c3e0)
DbRep_Set:
cnt 33
dmx -1000
dtot 0
dtotcnt 0
mTS 13.11. 19:05:47
max 0.0214500427246094
tot 0.0355830192565918
mAr:
HASH(0x723c3e0)
DbRep
dumpMySQL
serverSide
Attributes:
dumpFilesKeep 1
event-on-change-reading state
icon security
role Agent
room 99-Controller
timeout 1800
Ok, Du sagst die Felder stimmen nicht "mehr" mit den anforderungen überein, wie groß sollten die Felder den sein?
Beim einrichten habe ich mir per copy&paste die SQL befehle von irgendwo kopiert... Die frage ist jetzt wahrscheinlich welches HowTo ist aktuell...
Nabend,
danke ... die Warnungen kommen daher dass die Attribute für die ausgeführte Funktion nicht alle gesetzt sind. Ist aber auch nicht schlimm und ich werde die Warnungen in der nächsten Version eliminieren.
Zu den Feldgrößen. Aktuell die richtigen Größen sind die wie im configCheck angegeben.
Currently the default values for field width are:
DEVICE: 64
TYPE: 64
EVENT: 512
READING: 64
VALUE: 128
UNIT: 32
In der commandref habe ich auch den Link zu den aktuellen Einrichtungsskripten hinterlegt:
Der Code zur Anlage ist ebenfalls in den Scripten SVN -> contrib/dblog/db_create_<DBType>.sql enthalten.
Diese Quellen halte ich aktuell und dort siehst du die Größen.
D.h. du führst nacheinander aus:
alter table history modify DEVICE varchar(64);
alter table history modify TYPE varchar(64);
alter table history modify READING varchar(64);
alter table history modify VALUE varchar(128);
Wenn das für die history passiert ist, dann noch für die current Tabelle.
Gut wenn man MySQL/MariaDB hat, so geht es ganz simpel.
Ist die Anpassung erledigt schauen wir erneut wie es dann aussieht.
Der letzte Befehl
alter table history modify VALUE varchar(128);
läuft leider nicht durch...
https://www.dropbox.com/s/m5cio05pa5pntgl/Screenshot%202018-11-14%2019.47.16.png?dl=0
ist die Fehlermeldung.
Ich vermute das ist ein Timeout.
Setze den Befehl im DbRep mit
set DbRep sqlCmd alter ....
ab. Setze dort vorher das Attribut timeout auf z.B. 36000.
errortext
DBD::mysql::st execute failed: ALTER command denied to user 'fhem'@'localhost' for table 'history' at ./FHEM/93_DbRep.pm line 5565.
Edit:
Hab dem User fhem die rechte gegeben - jetzt läuft das comando...
Der User 'fhem'@'localhost' hat wieder nicht das benötigte Recht.
Ähnlich wie bei FILE in der Maske setzen. Dürfte das Recht ALTER in der Spalte Struktur sein.
Überschnitten ... :)
Ok, das wars...
ein aktueller configCheck:
Result of DbLog version check
Used DbLog version: 3.13.0
Recommendation: Your running version may be the current one. Please check for updates of DbLog periodically.
Result of configuration read check
Connection parameter store type: file
Connection parameter: Connection -> mysql:database=fhem;host=127.0.0.1;port=3307, User -> fhem, Password -> read o.k.
Result of connection check
Connection to database fhem successfully done.
Recommendation: settings o.k.
Result of encoding check
Encoding used by Client (connection): UTF8
Encoding used by DB fhem: UTF8
Recommendation: settings o.k.
Result of logmode check
Logmode of DbLog-device DbLog is: asynchronous
Recommendation: settings o.k.
Result of shutdown sequence preparation check
Attribute "shutdownWait" is set to:
Recommendation: Due to Reading "background_processing_time" is not available (you may set attribute "showproctime"), there is only a rough estimate to
set attribute "shutdownWait" to 2 seconds.
Result of plot generation method check
WARNING - at least one of your FHEMWEB devices have attribute "plotfork = 1" not set. This may cause blocking situations when creating plots.
WEB: plotfork=1
WEBphone: plotfork=0
WEBtablet: plotfork=0
WEBweatherstation: plotfork=0
Recommendation: You should set attribute "plotfork = 1" in relevant devices
Result of table 'history' check
Column width set in DB fhem.history: 'DEVICE' = 64, 'TYPE' = 64, 'EVENT' = 512, 'READING' = 64, 'VALUE' = 128, 'UNIT' = 32
Column width used by DbLog: 'DEVICE' = 64, 'TYPE' = 64, 'EVENT' = 512, 'READING' = 64, 'VALUE' = 128, 'UNIT' = 32
Recommendation: settings o.k.
Result of table 'current' check
Column width set in DB fhem.current: 'DEVICE' = 64, 'TYPE' = 64, 'EVENT' = 512, 'READING' = 64, 'VALUE' = 128, 'UNIT' = 32
Column width used by DbLog: 'DEVICE' = 64, 'TYPE' = 64, 'EVENT' = 512, 'READING' = 64, 'VALUE' = 128, 'UNIT' = 32
Recommendation: settings o.k.
Result of check 'Search_Idx' availability
Index 'Search_Idx' exists and contains recommended fields 'DEVICE', 'READING', 'TIMESTAMP'.
Recommendation: settings o.k.
Result of check 'Report_Idx' availability for DbRep-devices
At least one DbRep-device assigned to DbLog is used. Index 'Report_Idx' exists and contains recommended fields 'TIMESTAMP', 'READING'.
Recommendation: settings o.k.
ok. jetzt schauen wir wieder nach eventuell fehlerhaften Sätzen die gemeldet werden ...
Alles klar, nochmals vielen Dank für Deine hilfe...
Vielleicht kannst Du mir noch auf die sprünge helfen mit den Daten grundsätzlich - so eine hohe auflösung wie ich aktuell Logge brauche ich nach 24h eigentlich nicht mehr... Wenn also ein Tag vorbei ist könnte ich auf viele Einträge verzichten - ich denke alle 5 minuten ein Eintrag reicht mir.
Dazu ist ja eigentlich DbRep gedacht, oder? Ich hab DbRep glaube ich noch nicht so richtig verstanden.
Wie kann ich die History "ausdünnen"?
DbRep ist ein Werkzeugkoffer für die verschiedensten Anwendungen, so auch für das Löschen von Daten, zur Auswertung und tabellarischer Zusammenfassung von Werten, Backup und Restore, Datenexport, Infosystem zu DB-Variablen, Datenbanksynchronisation und etliches mehr.
Die Vorgehensweise ist so, dass man sich für sein vorhandenes Problem eine passende Funktion im DbRep sucht und das erstellte Device über die vielen möglichen Attribute nach seinen Bedürfnissen einstellt und die Funktion dann (regelmäßig) laufen lässt.
Für deine Anforderung gibt es verschiedene Möglichkeiten.
Zunächst vorhandene Dubletten löschen. Die hast du wahrscheinlich weil kein PK vorhanden ist.
Wenn du im DbRep die Attr so setzt :
timeDiffToNow = d:10
timeOlderThan = d:1
werden für die nachfolgenden Kommandos alles was älter als 1 Tag und neuer als 10 Tage ist, betrachtet.
set ... delDoublets adviceDelete
zeigt dir erstmal wieviel gelöscht werden würde. Mit "set delDoublets delete" wirfst du sie dann weg.
Dann gibt es
set ... delSeqDoublets ...
Das löscht auf spezielle Art und Weise Daten die noemalerweise logisch nicht benötigt werden, Wie genau das wirkt ist in der commandref ziemlich ausführlich dargestellt. Das können wir uns anschauen wenn du eine konkrete Anforderung hast.
Und es gibt noch das
set ... reduceLog
Ohne weiteren Zusatz behältst du immer den ersten Eintrag pro Stunde je Device & Reading.
Edit: Es gibt auch im Wiki etliche Beispiele die ich immer wieder erweitere wenn es meine Zeit erlaubt.
Guten Morgen Heiko,
nach anpassung der Feldgrößen innerhalb der DB verhält sich die Datenbank wieder unauffällig - läuft nun seit etwas mehr als 24Std. ohne weitere fehlereinträge im Log. Tausend Dank für Deine Hilfe!
Ich werde die nächsten Tage dazu nutzen das Logging einzuschränken sodass der Datenwust nicht zu groß wird, sinnvolle Daten aber behalten werden.
Hier komme ich mit Sicherheit noch mit der ein oder anderen frage ;-)
Na das hört sich doch gut an. :)
Lösche bitte das Attribut commitMode wieder. Das ist für den Support bzw. diesen Fehlerfall gut und hilfreich. Hat aber evtl. Nachteile für den normalen Betrieb.
Hab dich gerne unterstützt und war ja auch ein interessanter Fall.
Grüße,
Heiko