Nur Text | Text mit Bildern

FHEM Forum

FHEM => Automatisierung => Thema gestartet von: Sidey am 24 Juni 2019, 23:32:29

Titel: DBLog - mit Version 4.1.1 nur noch Fehler
Beitrag von: Sidey am 24 Juni 2019, 23:32:29
Hi,

ich habe am Sonntag ein FHEM Update gemacht, dabei wurde auch das DBLog Modul von 4.1.0 auf 4.1.1 aktualisiert.

Seit dem habe ich massive Probleme.
Meine SQLite Datenbank war einige Zeit nach dem Update nicht mehr verwendbar.
Code Auswählen
Error: file is encrypted or is not a database

Die Daten stehen noch in der korrupten DB, allerdings wird die Datei nicht mehr als SQLite DB erkannt.
Ich habe mir dann erst mal eine neue Datenbank angelegt und die alte weggesichert.

Das lief auch ein paar Stunden, aber heute haben es keine Daten mehr in die Datenbank geschafft.
Also habe ich ein bisschen analysiert, verbose auf 5 gestellt und etliche Fehler im Logfile gefunden:

Die scheinen mir so kreuz und quer durch die Bank zu gehen.
List der LoggingDB Definiton:

Code Auswählen
Internals:
   COLUMNS    field length used for Device: 64, Type: 64, Event: 512, Reading: 64, Value: 128, Unit: 32
   CONFIGURATION /opt/fhem/db.conf
   DEF        /opt/fhem/db.conf  .*:.*(temp|temperature|measured-temp|desired-temp|actuator|humidity|humidity_absolute|dewpoint|tempdiff_avg_day|tempdiff|voltage|vorlauf|kessel|rücklauf|switch.|_counter_|light|rainNow|Distance|Relay|battery).*
   FUUID      5c4cb3c8-f33f-f610-81a8-b5c7e1780f83ea16
   FVERSION   93_DbLog.pm:v4.1.1-s19529/2019-06-02
   MODE       asynchronous
   MODEL      SQLITE
   NAME       LoggingDB
   NR         39
   NTFY_ORDER 50-LoggingDB
   PID        1192
   REGEXP     .*:.*(temp|temperature|measured-temp|desired-temp|actuator|humidity|humidity_absolute|dewpoint|tempdiff_avg_day|tempdiff|voltage|vorlauf|kessel|rücklauf|switch.|_counter_|light|rainNow|Distance|Relay|battery).*
   STATE      connected
   TYPE       DbLog
   dbconn     SQLite:dbname=/opt/fhem/fhem.db
   dbuser     
   HELPER:
     COLSET     1
     DEVICECOL  64
     EVENTCOL   512
     OLDSTATE   connected
     PACKAGE    main
     READINGCOL 64
     TYPECOL    64
     UNITCOL    32
     VALUECOL   128
     VERSION    4.1.1
   READINGS:
     2019-06-24 23:31:06   CacheUsage      3
     2019-06-24 23:30:54   NextSync        2019-06-24 23:31:24 or if CacheUsage 500 reached
     2016-12-04 22:03:11   countCurrent    44
     2017-07-19 22:00:40   countHistory    282613
     2018-04-10 23:07:27   reduceLogState  reduceLogNbl finished. Rows processed: 0, deleted: 0, updated: 0, time: 185.00sec
     2019-06-24 23:30:54   state           connected
     2019-05-19 21:01:40   userCommand     .indexes
     2019-05-19 21:01:41   userCommandResult DBD::SQLite::db selectrow_array failed: near ".": syntax error at ./FHEM/93_DbLog.pm line 872.

   cache:
     index      2976
Attributes:
   DbLogType  Current/History
   asyncMode  1
   commitMode basic_ta:off
   group      DB
   room       system
   useCharfilter 1
   userReadings attr dbLog userReadings DbFileSize:lastReduceLogResult.* { (split(' ',`du -m dbLog.db`))[0] }
   verbose    3

Code Auswählen

2019.06.24 23:20:25 5: DbLog LoggingDB -> DbLog_PushAsyncDone finished
2019.06.24 23:20:25 5: DbLog LoggingDB -> Start DbLog_PushAsyncDone
2019.06.24 23:20:25 5: DbLog LoggingDB -> DbLog_PushAsync finished

executing 2 generated 2 errors at ./FHEM/93_DbLog.pm line 2427.
2019.06.24 23:20:25 2: DbLog LoggingDB -> Error table history - DBD::SQLite::st execute_array failed: database disk image is malformed [err was 11 now 2000000000]
2019.06.24 23:20:25 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:20:01, Device: Temp1, Type: CUL_TCM97001, Event: dewpoint: 15.8, Reading: dewpoint, Value: 15.8, Unit:
2019.06.24 23:20:25 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:20:01, Device: Temp1, Type: CUL_TCM97001, Event: temperature: 26.1, Reading: temperature, Value: 26.1, Unit: °C
2019.06.24 23:20:25 5: DbLog LoggingDB -> Primary Key used in /opt/fhem/fhem.db.current: none
2019.06.24 23:20:25 5: DbLog LoggingDB -> Primary Key used in /opt/fhem/fhem.db.history: none
2019.06.24 23:20:25 4: DbLog LoggingDB -> Insert mode: Array
2019.06.24 23:20:25 4: DbLog LoggingDB -> AutoCommit mode: ON, Transaction mode: OFF
2019.06.24 23:20:25 5: DbLog LoggingDB -> DbLogType is: Current/History
2019.06.24 23:20:25 5: DbLog LoggingDB -> Start DbLog_PushAsync
2019.06.24 23:20:24 5: DbLog LoggingDB -> DbLog_PushAsync called with timeout: 86400
2019.06.24 23:20:24 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:20:01|Temp1|CUL_TCM97001|dewpoint: 15.8|dewpoint|15.8|
2019.06.24 23:20:24 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:20:01|Temp1|CUL_TCM97001|temperature: 26.1|temperature|26.1|°C
2019.06.24 23:20:24 4: DbLog LoggingDB -> DbLogType is: Current/History
2019.06.24 23:20:24 4: DbLog LoggingDB -> MemCache contains 2 entries to process
2019.06.24 23:20:24 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:20:24 4: DbLog LoggingDB -> ###      New database processing cycle - asynchronous        ###
2019.06.24 23:20:24 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:20:21 4: DbLog LoggingDB -> check Device: dg.WandHeizung , Event: state: Tem: 28.19 upt: 152961.00
2019.06.24 23:20:21 4: DbLog LoggingDB -> number of events received: 1 for device: dg.WandHeizung
2019.06.24 23:20:21 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:20:21 4: DbLog LoggingDB -> ###              start of new Logcycle                       ###
2019.06.24 23:20:21 4: DbLog LoggingDB -> ################################################################




Code Auswählen
2019.06.24 23:18:48 5: DbLog LoggingDB -> DbLog_PushAsyncDone finished
2019.06.24 23:18:48 5: DbLog LoggingDB -> Start DbLog_PushAsyncDone
2019.06.24 23:18:48 5: DbLog LoggingDB -> DbLog_PushAsync finished

executing 8 generated 1 errors at ./FHEM/93_DbLog.pm line 2427.
2019.06.24 23:18:48 2: DbLog LoggingDB -> Error table history - DBD::SQLite::st execute_array failed: database disk image is malformed [err was 11 now 2000000000]
2019.06.24 23:18:48 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:18:48, Device: Buienradar, Type: BUIENRADAR, Event: rainNow: 0.000 mm/h, Reading: rainNow, Value: 0.000 mm/h, Unit:
2019.06.24 23:18:48 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:18:42, Device: wc.Heizung_Weather, Type: CUL_HM, Event: measured-temp: 24.6, Reading: measured-temp, Value: 24.6, Unit:
2019.06.24 23:18:48 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:18:42, Device: wc.Heizung_Clima, Type: CUL_HM, Event: measured-temp: 24.6, Reading: measured-temp, Value: 24.6, Unit:
2019.06.24 23:18:48 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:18:42, Device: wc.Heizung_Clima, Type: CUL_HM, Event: desired-temp: 12.0, Reading: desired-temp, Value: 12.0, Unit:
2019.06.24 23:18:48 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:18:40, Device: bad.th, Type: CUL_TX, Event: dewpoint: 16.1, Reading: dewpoint, Value: 16.1, Unit:
2019.06.24 23:18:48 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:18:40, Device: bad.th, Type: CUL_TX, Event: humidity: 59.0, Reading: humidity, Value: 59.0, Unit: %
2019.06.24 23:18:48 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:18:39, Device: bad.th, Type: CUL_TX, Event: Averagehumidity: 59.2488179366101, Reading: Averagehumidity, Value: 59.2488179366101, Unit:
2019.06.24 23:18:48 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:18:39, Device: bad.th, Type: CUL_TX, Event: temperature: 24.7, Reading: temperature, Value: 24.7, Unit: °C
2019.06.24 23:18:48 5: DbLog LoggingDB -> Primary Key used in /opt/fhem/fhem.db.current: none
2019.06.24 23:18:48 5: DbLog LoggingDB -> Primary Key used in /opt/fhem/fhem.db.history: none
2019.06.24 23:18:48 4: DbLog LoggingDB -> Insert mode: Array
2019.06.24 23:18:48 4: DbLog LoggingDB -> AutoCommit mode: ON, Transaction mode: OFF
2019.06.24 23:18:48 5: DbLog LoggingDB -> DbLogType is: Current/History
2019.06.24 23:18:48 5: DbLog LoggingDB -> Start DbLog_PushAsync
2019.06.24 23:18:48 5: DbLog LoggingDB -> DbLog_PushAsync called with timeout: 86400
2019.06.24 23:18:48 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:18:48|Buienradar|BUIENRADAR|rainNow: 0.000 mm/h|rainNow|0.000 mm/h|
2019.06.24 23:18:48 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:18:42|wc.Heizung_Weather|CUL_HM|measured-temp: 24.6|measured-temp|24.6|
2019.06.24 23:18:48 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:18:42|wc.Heizung_Clima|CUL_HM|measured-temp: 24.6|measured-temp|24.6|
2019.06.24 23:18:48 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:18:42|wc.Heizung_Clima|CUL_HM|desired-temp: 12.0|desired-temp|12.0|
2019.06.24 23:18:48 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:18:40|bad.th|CUL_TX|dewpoint: 16.1|dewpoint|16.1|
2019.06.24 23:18:48 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:18:40|bad.th|CUL_TX|humidity: 59.0|humidity|59.0|%
2019.06.24 23:18:48 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:18:39|bad.th|CUL_TX|Averagehumidity: 59.2488179366101|Averagehumidity|59.2488179366101|
2019.06.24 23:18:48 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:18:39|bad.th|CUL_TX|temperature: 24.7|temperature|24.7|°C
2019.06.24 23:18:48 4: DbLog LoggingDB -> DbLogType is: Current/History
2019.06.24 23:18:48 4: DbLog LoggingDB -> MemCache contains 8 entries to process
2019.06.24 23:18:48 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:18:48 4: DbLog LoggingDB -> ###      New database processing cycle - asynchronous        ###
2019.06.24 23:18:48 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:18:48 4: DbLog LoggingDB -> check Device: Buienradar , Event: rainMax: 0.000
2019.06.24 23:18:48 4: DbLog LoggingDB -> added event - Timestamp: 2019-06-24 23:18:48, Device: Buienradar, Type: BUIENRADAR, Event: rainNow: 0.000 mm/h, Reading: rainNow, Value: 0.000 mm/h, Unit:
2019.06.24 23:18:48 5: DbLog LoggingDB -> parsed Event: Buienradar , Event: rainNow: 0.000 mm/h
2019.06.24 23:18:48 4: DbLog LoggingDB -> check Device: Buienradar , Event: rainNow: 0.000 mm/h
2019.06.24 23:18:48 4: DbLog LoggingDB -> number of events received: 2 for device: Buienradar
2019.06.24 23:18:48 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:18:48 4: DbLog LoggingDB -> ###              start of new Logcycle                       ###
2019.06.24 23:18:48 4: DbLog LoggingDB -> ################################################################


Code Auswählen

2019.06.24 23:17:46 5: DbLog LoggingDB -> DbLog_PushAsyncDone finished
2019.06.24 23:17:46 5: DbLog LoggingDB -> Start DbLog_PushAsyncDone
2019.06.24 23:17:46 5: DbLog LoggingDB -> DbLog_PushAsync finished

executing 19 generated 3 errors at ./FHEM/93_DbLog.pm line 2427.
2019.06.24 23:17:45 2: DbLog LoggingDB -> Error table history - DBD::SQLite::st execute_array failed: database disk image is malformed [err was 11 now 2000000000]
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:41, Device: Temp1, Type: CUL_TCM97001, Event: dewpoint: 15.9, Reading: dewpoint, Value: 15.9, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:41, Device: Temp1, Type: CUL_TCM97001, Event: humidity: 53, Reading: humidity, Value: 53, Unit: %
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:41, Device: Temp1, Type: CUL_TCM97001, Event: temperature: 26.2, Reading: temperature, Value: 26.2, Unit: °C
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:19, Device: dg.Heizung2_Weather, Type: CUL_HM, Event: measured-temp: 25.9, Reading: measured-temp, Value: 25.9, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:19, Device: dg.Heizung2_Clima, Type: CUL_HM, Event: measured-temp: 25.9, Reading: measured-temp, Value: 25.9, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:19, Device: dg.Heizung2_Clima, Type: CUL_HM, Event: desired-temp: 17.0, Reading: desired-temp, Value: 17.0, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:19, Device: dg.Heizung2, Type: CUL_HM, Event: measured-temp: 25.9, Reading: measured-temp, Value: 25.9, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:19, Device: dg.Heizung2, Type: CUL_HM, Event: desired-temp: 17.0, Reading: desired-temp, Value: 17.0, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:19, Device: dg.Heizung2, Type: CUL_HM, Event: batteryLevel: 2.9, Reading: batteryLevel, Value: 2.9, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:19, Device: dg.Heizung2, Type: CUL_HM, Event: battery: ok, Reading: battery, Value: ok, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:19, Device: dg.Heizung2, Type: CUL_HM, Event: actuator: 0, Reading: actuator, Value: 0, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:16, Device: dg.Heizung1_Weather, Type: CUL_HM, Event: measured-temp: 26.4, Reading: measured-temp, Value: 26.4, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:16, Device: dg.Heizung1_Clima, Type: CUL_HM, Event: measured-temp: 26.4, Reading: measured-temp, Value: 26.4, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:16, Device: dg.Heizung1_Clima, Type: CUL_HM, Event: desired-temp: 17.0, Reading: desired-temp, Value: 17.0, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:16, Device: dg.Heizung1, Type: CUL_HM, Event: measured-temp: 26.4, Reading: measured-temp, Value: 26.4, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:16, Device: dg.Heizung1, Type: CUL_HM, Event: desired-temp: 17.0, Reading: desired-temp, Value: 17.0, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:16, Device: dg.Heizung1, Type: CUL_HM, Event: batteryLevel: 2.4, Reading: batteryLevel, Value: 2.4, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:16, Device: dg.Heizung1, Type: CUL_HM, Event: battery: ok, Reading: battery, Value: ok, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:17:16, Device: dg.Heizung1, Type: CUL_HM, Event: actuator: 0, Reading: actuator, Value: 0, Unit:
2019.06.24 23:17:45 5: DbLog LoggingDB -> Primary Key used in /opt/fhem/fhem.db.current: none
2019.06.24 23:17:45 5: DbLog LoggingDB -> Primary Key used in /opt/fhem/fhem.db.history: none
2019.06.24 23:17:45 4: DbLog LoggingDB -> Insert mode: Array
2019.06.24 23:17:45 4: DbLog LoggingDB -> AutoCommit mode: ON, Transaction mode: OFF
2019.06.24 23:17:45 5: DbLog LoggingDB -> DbLogType is: Current/History
2019.06.24 23:17:45 5: DbLog LoggingDB -> Start DbLog_PushAsync
2019.06.24 23:17:45 5: DbLog LoggingDB -> DbLog_PushAsync called with timeout: 86400
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:41|Temp1|CUL_TCM97001|dewpoint: 15.9|dewpoint|15.9|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:41|Temp1|CUL_TCM97001|humidity: 53|humidity|53|%
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:41|Temp1|CUL_TCM97001|temperature: 26.2|temperature|26.2|°C
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:19|dg.Heizung2_Weather|CUL_HM|measured-temp: 25.9|measured-temp|25.9|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:19|dg.Heizung2_Clima|CUL_HM|measured-temp: 25.9|measured-temp|25.9|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:19|dg.Heizung2_Clima|CUL_HM|desired-temp: 17.0|desired-temp|17.0|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:19|dg.Heizung2|CUL_HM|measured-temp: 25.9|measured-temp|25.9|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:19|dg.Heizung2|CUL_HM|desired-temp: 17.0|desired-temp|17.0|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:19|dg.Heizung2|CUL_HM|batteryLevel: 2.9|batteryLevel|2.9|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:19|dg.Heizung2|CUL_HM|battery: ok|battery|ok|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:19|dg.Heizung2|CUL_HM|actuator: 0|actuator|0|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:16|dg.Heizung1_Weather|CUL_HM|measured-temp: 26.4|measured-temp|26.4|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:16|dg.Heizung1_Clima|CUL_HM|measured-temp: 26.4|measured-temp|26.4|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:16|dg.Heizung1_Clima|CUL_HM|desired-temp: 17.0|desired-temp|17.0|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:16|dg.Heizung1|CUL_HM|measured-temp: 26.4|measured-temp|26.4|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:16|dg.Heizung1|CUL_HM|desired-temp: 17.0|desired-temp|17.0|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:16|dg.Heizung1|CUL_HM|batteryLevel: 2.4|batteryLevel|2.4|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:16|dg.Heizung1|CUL_HM|battery: ok|battery|ok|
2019.06.24 23:17:45 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:17:16|dg.Heizung1|CUL_HM|actuator: 0|actuator|0|
2019.06.24 23:17:45 4: DbLog LoggingDB -> DbLogType is: Current/History
2019.06.24 23:17:45 4: DbLog LoggingDB -> MemCache contains 19 entries to process
2019.06.24 23:17:45 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:17:45 4: DbLog LoggingDB -> ###      New database processing cycle - asynchronous        ###
2019.06.24 23:17:45 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:17:42 4: DbLog LoggingDB -> check Device: HMLAN1 , Event: loadLvl: low
2019.06.24 23:17:42 4: DbLog LoggingDB -> number of events received: 1 for device: HMLAN1
2019.06.24 23:17:42 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:17:42 4: DbLog LoggingDB -> ###              start of new Logcycle                       ###
2019.06.24 23:17:42 4: DbLog LoggingDB -> ################################################################



Code Auswählen
2019.06.24 23:16:42 5: DbLog LoggingDB -> DbLog_PushAsyncDone finished
2019.06.24 23:16:42 5: DbLog LoggingDB -> Start DbLog_PushAsyncDone
2019.06.24 23:16:42 5: DbLog LoggingDB -> DbLog_PushAsync finished

2019.06.24 23:16:42 2: DbLog LoggingDB -> Error table history - DBD::SQLite::st execute_array failed: executing 6 generated 1 errors at ./FHEM/93_DbLog.pm line 2427.
2019.06.24 23:16:42 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:16:39, Device: wc.Heizung_Weather, Type: CUL_HM, Event: measured-temp: 24.6, Reading: measured-temp, Value: 24.6, Unit:
2019.06.24 23:16:42 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:16:39, Device: wc.Heizung_Clima, Type: CUL_HM, Event: measured-temp: 24.6, Reading: measured-temp, Value: 24.6, Unit:
2019.06.24 23:16:42 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:16:39, Device: wc.Heizung_Clima, Type: CUL_HM, Event: desired-temp: 12.0, Reading: desired-temp, Value: 12.0, Unit:
2019.06.24 23:16:42 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:16:18, Device: Buienradar, Type: BUIENRADAR, Event: rainNow: 0.000 mm/h, Reading: rainNow, Value: 0.000 mm/h, Unit:
2019.06.24 23:16:42 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:16:15, Device: au.licht, Type: TWILIGHT, Event: twilight_weather: 5.9, Reading: twilight_weather, Value: 5.9, Unit:
2019.06.24 23:16:42 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:16:15, Device: au.licht, Type: TWILIGHT, Event: twilight: 5.9, Reading: twilight, Value: 5.9, Unit:
2019.06.24 23:16:42 5: DbLog LoggingDB -> Primary Key used in /opt/fhem/fhem.db.current: none
2019.06.24 23:16:42 5: DbLog LoggingDB -> Primary Key used in /opt/fhem/fhem.db.history: none
2019.06.24 23:16:42 4: DbLog LoggingDB -> Insert mode: Array
2019.06.24 23:16:42 4: DbLog LoggingDB -> AutoCommit mode: ON, Transaction mode: OFF
2019.06.24 23:16:42 5: DbLog LoggingDB -> DbLogType is: Current/History
2019.06.24 23:16:42 5: DbLog LoggingDB -> Start DbLog_PushAsync
2019.06.24 23:16:42 5: DbLog LoggingDB -> DbLog_PushAsync called with timeout: 86400
2019.06.24 23:16:42 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:16:39|wc.Heizung_Weather|CUL_HM|measured-temp: 24.6|measured-temp|24.6|
2019.06.24 23:16:42 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:16:39|wc.Heizung_Clima|CUL_HM|measured-temp: 24.6|measured-temp|24.6|
2019.06.24 23:16:42 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:16:39|wc.Heizung_Clima|CUL_HM|desired-temp: 12.0|desired-temp|12.0|
2019.06.24 23:16:42 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:16:18|Buienradar|BUIENRADAR|rainNow: 0.000 mm/h|rainNow|0.000 mm/h|
2019.06.24 23:16:42 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:16:15|au.licht|TWILIGHT|twilight_weather: 5.9|twilight_weather|5.9|
2019.06.24 23:16:42 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:16:15|au.licht|TWILIGHT|twilight: 5.9|twilight|5.9|
2019.06.24 23:16:42 4: DbLog LoggingDB -> DbLogType is: Current/History
2019.06.24 23:16:42 4: DbLog LoggingDB -> MemCache contains 6 entries to process
2019.06.24 23:16:42 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:16:42 4: DbLog LoggingDB -> ###      New database processing cycle - asynchronous        ###
2019.06.24 23:16:42 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: lastReadout: 426 values captured in 0.95 s
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_84_F3_EB_B0_B7_46: ESP-S20-3-8 (WLAN, 6 / 5 Mbit/s, -80)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_BC_DD_C2_23_43_CD: ESPMYSGateway (WLAN, 49 / 2 Mbit/s, -83)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_9C_32_CE_CD_B0_5B: CDB05B000000 (WLAN, 72 / 72 Mbit/s, -71)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_44_00_49_E6_31_C9: amazon-FIRETV (WLAN, 130 / 144 Mbit/s, -71)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_BC_DD_C2_94_44_61: ESP-ShellyV1-2-5 (WLAN, 54 / 47 Mbit/s, -71)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_D0_77_14_35_89_64: Android-42 (WLAN, 86 / 104 Mbit/s, -72)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_84_F3_EB_A8_20_C2: ESP-SBasic-01-4 (WLAN, 1 / 1 Mbit/s, -80)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_F0_81_73_50_57_CA: amazon-188d407a9 (WLAN, 72 / 58 Mbit/s, -74)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_B0_FC_0D_FA_8C_37: amazon-803c6d7d2 (WLAN, 72 / 63 Mbit/s, -64)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_48_4B_AA_56_E2_5F: iPhone-von-Sven (WLAN, 144 / 104 Mbit/s, -71)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_B8_27_EB_57_D8_BD: pi2
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_00_A0_96_DC_8E_94: Sony-TV (WLAN, 72 / 72 Mbit/s, -67)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: box_rateUp: 6.960
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_BC_DD_C2_94_17_BE: Shelly1-1 (WLAN, 57 / 1 Mbit/s, -56)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_B8_27_EB_16_A6_AA: fhem-pi
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_BC_76_5E_95_F8_49: Galaxy-Tab-A-2016 (WLAN, 433 / 433 Mbit/s, -63)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_00_15_5D_0B_56_0A: dmsserver
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_CC_CE_1E_DB_30_5D: fritz7490
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_34_51_C9_D2_81_B9: iPad-von-Sven-2 (WLAN, 65 / 64 Mbit/s, -61)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_EC_FA_BC_0E_0B_7C: ESP-RGB-2 (WLAN, 65 / 48 Mbit/s, -75)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_BC_AE_C5_97_1C_4F: Thor
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_78_D6_F0_D4_BD_6E: android-9891d33592e502f1 (WLAN, 64 / 40 Mbit/s, -69)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: box_rateDown: 741.168
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_EC_FA_BC_13_56_B8: ESP-S20-1-0 (WLAN, 57 / 7 Mbit/s, -53)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_DC_4F_22_2B_D7_BA: ESP-S20-2-2 (WLAN, 51 / 4 Mbit/s, -76)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_88_44_77_91_4B_C5: Honor-6X (WLAN, 72 / 10 Mbit/s, -53)
2019.06.24 23:16:42 4: DbLog LoggingDB -> check Device: fb7590 , Event: mac_44_4E_6D_3B_10_89: fritz.box
2019.06.24 23:16:42 4: DbLog LoggingDB -> number of events received: 28 for device: fb7590
2019.06.24 23:16:42 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:16:42 4: DbLog LoggingDB -> ###              start of new Logcycle                       ###


Code Auswählen

2019.06.24 23:14:06 5: DbLog LoggingDB -> DbLog_PushAsyncDone finished
2019.06.24 23:14:06 5: DbLog LoggingDB -> Start DbLog_PushAsyncDone
2019.06.24 23:14:06 5: DbLog LoggingDB -> DbLog_PushAsync finished

2019.06.24 23:14:06 2: DbLog LoggingDB -> Error table history - DBD::SQLite::st execute_array failed: executing 7 generated 1 errors at ./FHEM/93_DbLog.pm line 2427.
2019.06.24 23:14:06 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:14:00, Device: sz.heizung, Type: CUL_HM, Event: measured-temp: 25.3, Reading: measured-temp, Value: 25.3, Unit:
2019.06.24 23:14:06 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:14:00, Device: sz.heizung, Type: CUL_HM, Event: desired-temp: off, Reading: desired-temp, Value: off, Unit:
2019.06.24 23:14:06 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:14:00, Device: sz.heizung, Type: CUL_HM, Event: actuator: 0, Reading: actuator, Value: 0, Unit:
2019.06.24 23:14:06 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:13:48, Device: Buienradar, Type: BUIENRADAR, Event: rainNow: 0.000 mm/h, Reading: rainNow, Value: 0.000 mm/h, Unit:
2019.06.24 23:14:06 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:13:46, Device: kz.temp, Type: OREGON, Event: batteryState: low, Reading: batteryState, Value: low, Unit:
2019.06.24 23:14:06 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:13:46, Device: kz.temp, Type: OREGON, Event: temperature: 23.8, Reading: temperature, Value: 23.8, Unit: °C
2019.06.24 23:14:06 5: DbLog LoggingDB -> processing event Timestamp: 2019-06-24 23:13:44, Device: bad.Fenster, Type: CUL_HM, Event: battery: ok, Reading: battery, Value: ok, Unit:
2019.06.24 23:14:06 5: DbLog LoggingDB -> Primary Key used in /opt/fhem/fhem.db.current: none
2019.06.24 23:14:06 5: DbLog LoggingDB -> Primary Key used in /opt/fhem/fhem.db.history: none
2019.06.24 23:14:06 4: DbLog LoggingDB -> Insert mode: Array
2019.06.24 23:14:06 4: DbLog LoggingDB -> AutoCommit mode: ON, Transaction mode: OFF
2019.06.24 23:14:06 5: DbLog LoggingDB -> DbLogType is: Current/History
2019.06.24 23:14:06 5: DbLog LoggingDB -> Start DbLog_PushAsync
2019.06.24 23:14:06 5: DbLog LoggingDB -> DbLog_PushAsync called with timeout: 86400
2019.06.24 23:14:06 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:14:00|sz.heizung|CUL_HM|measured-temp: 25.3|measured-temp|25.3|
2019.06.24 23:14:06 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:14:00|sz.heizung|CUL_HM|desired-temp: off|desired-temp|off|
2019.06.24 23:14:06 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:14:00|sz.heizung|CUL_HM|actuator: 0|actuator|0|
2019.06.24 23:14:06 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:13:48|Buienradar|BUIENRADAR|rainNow: 0.000 mm/h|rainNow|0.000 mm/h|
2019.06.24 23:14:06 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:13:46|kz.temp|OREGON|batteryState: low|batteryState|low|
2019.06.24 23:14:06 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:13:46|kz.temp|OREGON|temperature: 23.8|temperature|23.8|°C
2019.06.24 23:14:06 5: DbLog LoggingDB -> MemCache contains: 2019-06-24 23:13:44|bad.Fenster|CUL_HM|battery: ok|battery|ok|
2019.06.24 23:14:06 4: DbLog LoggingDB -> DbLogType is: Current/History
2019.06.24 23:14:06 4: DbLog LoggingDB -> MemCache contains 7 entries to process
2019.06.24 23:14:06 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:14:06 4: DbLog LoggingDB -> ###      New database processing cycle - asynchronous        ###
2019.06.24 23:14:06 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:14:00 4: DbLog LoggingDB -> check Device: fl.LichtDach , Event: state: Sta: on rss: -68.00 upt: 15820
2019.06.24 23:14:00 4: DbLog LoggingDB -> number of events received: 1 for device: fl.LichtDach
2019.06.24 23:14:00 4: DbLog LoggingDB -> ################################################################
2019.06.24 23:14:00 4: DbLog LoggingDB -> ###              start of new Logcycle                       ###
2019.06.24 23:14:00 4: DbLog LoggingDB -> ################################################################


Das ganze kommt mir seltsam vor, dass die Fehler auf einmal so vielfältig sind.

Grüße Sidey
Titel: Antw:DBLog - mit Version 4.1.1 nur noch Fehler
Beitrag von: DS_Starter am 25 Juni 2019, 00:12:23
Hallo Sidey,

die Aktualisierung des Moduls ist mit Sicherheit nicht die Ursache des Fehlers, weil die Änderungen von 4.1.0 zu 4.1.1 nur minimal. Betrifft nur die Behandlung des Wertes 0 wenn Mininterval angegeben ist und somit nur die Behandlung der Events aber nicht der Schreibroutinen o.ä. was fehleranfällig wäre.

Und es gibt eigentlich nur einen Fehler:

Code Auswählen
2019.06.24 23:20:25 2: DbLog LoggingDB -> Error table history - DBD::SQLite::st execute_array failed: database disk image is malformed [err was 11 now 2000000000]

Aber der ist schwerwiegend, deswegen kommt auch nichts mehr in die DB. Die weiteren Logangaben sind im Prinzip nur Informationen die helfen.

Wenn du eine korrupte DB hast wie im vorliegenden Fall, kannst du mit einem DbRep-Device und dem Befehl

set <name> repairSQLite

versuchen die DB zu reparieren.

Die Gründe für eine korrupte SQLIte können äußerst vielfältig sein -> https://www.sqlite.org/howtocorrupt.html

Grüße,
Heiko
Nur Text | Text mit Bildern