Hauptmenü

LogDB Fehler

Begonnen von Flanders, 28 November 2022, 15:33:10

Vorheriges Thema - Nächstes Thema

Flanders

Hallo,

nachdem ich das Logging in die MariaDB aktiviert habe tauchen folgende Fehlermeldungen im Status des Logdevices auf:


bLog logdb -> Error table history - DBD::mysql::st execute_array failed: Data too long for column 'READING' at row 1 [err was 1406 now 2000000000]
executing 33 generated 3 errors at ./FHEM/93_DbLog.pm line 2909.

2022.11.28 15:20:07.513 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 501 generated 41 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 15:20:08.648 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 561 generated 41 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 15:20:27.127 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 746 generated 66 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 15:20:28.413 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 750 generated 66 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 15:20:30.682 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 756 generated 68 errors at ./FHEM/93_DbLog.pm line 2909.


Wie kann ich das beheben?

Greets

Flanders

OK Spaltengröße für READING habe ich über phpmyadmin vergrößert...

Der Fehler

DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 756 generated 68 errors at ./FHEM/93_DbLog.pm line 2909.

bleibt aber. Der taucht immer weiter auf....


Greets

DS_Starter

Wahrscheinlich nicht groß genug. Ein

set ... configCheck

gibt dir sicherlich einen Hinweis.
ESXi@NUC+Debian+MariaDB, PV: SMA, Victron MPII+Pylontech+CerboGX
Maintainer: SSCam, SSChatBot, SSCal, SSFile, DbLog/DbRep, Log2Syslog, SolarForecast,Watches, Dashboard, PylonLowVoltage
Kaffeekasse: https://www.paypal.me/HMaaz
Contrib: https://svn.fhem.de/trac/browser/trunk/fhem/contrib/DS_Starter

Flanders

Der Fehler mit der zu kleinen Spalte erscheint nicht mehr, jetzt ist es vermutlich eine andere Ursache??!

2022.11.28 16:10:39.927 5: DbLog logdb -> MemCache contains: 2022-11-28 16:10:12|logdb|DBLOG|state: DBD::mysql::st execute_array failed: executing 501 generated 41 errors at ./FHEM/93_DbLog.pm line 2909.

Greets

DS_Starter

Da hast du den eigenen Fehlerevent des state Readings loggen lassen. Entweder den Regex im DEF anpassen oder z.B. das Attr excludeDevs nutzen um im Umkehrschluss Devices vom Logging auszuschließen. Zumindest für das eigene DbLog Device ist es oft sinnvoll.

Wenn du alles eingestellt hast, dann mit  set ... purgeCache  den Cache leeren oder einfachen FHEM restarten.
ESXi@NUC+Debian+MariaDB, PV: SMA, Victron MPII+Pylontech+CerboGX
Maintainer: SSCam, SSChatBot, SSCal, SSFile, DbLog/DbRep, Log2Syslog, SolarForecast,Watches, Dashboard, PylonLowVoltage
Kaffeekasse: https://www.paypal.me/HMaaz
Contrib: https://svn.fhem.de/trac/browser/trunk/fhem/contrib/DS_Starter

Flanders

Hallo,

daran lag es nicht, Neustart gemacht, Fehlermeldung kommt trotzdem!

Ich habe mal versucht über
excludeDevs echo,echodevice,dblog,log
diese Geräte auszuschließen, da ich den Verdacht hatte, dass diese  den Fehler verursachen...

Das Log ist voll mit diesen Fehlern:


2022.11.28 16:40:13.172 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 599 generated 47 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:40:34.739 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 6999 generated 585 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:40:45.110 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 7004 generated 585 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:40:53.962 1: Perfmon: possible freeze starting at 16:40:51, delay is 2.961
2022.11.28 16:40:59.145 1: Perfmon: possible freeze starting at 16:40:57, delay is 2.145
2022.11.28 16:41:01.500 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 7135 generated 606 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:41:03.891 1: Perfmon: possible freeze starting at 16:41:00, delay is 3.891
2022.11.28 16:41:06.185 1: Perfmon: possible freeze starting at 16:41:04, delay is 2.185
2022.11.28 16:41:11.280 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 501 generated 28 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:41:12.732 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 542 generated 37 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:41:17.282 1: Perfmon: possible freeze starting at 16:41:16, delay is 1.282
2022.11.28 16:41:37.615 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 7746 generated 646 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:41:49.198 1: Perfmon: possible freeze starting at 16:41:48, delay is 1.198
2022.11.28 16:41:49.240 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 7752 generated 646 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:41:53.353 1: Perfmon: possible freeze starting at 16:41:51, delay is 2.352
2022.11.28 16:42:00.490 1: Perfmon: possible freeze starting at 16:41:57, delay is 3.49
2022.11.28 16:42:05.875 1: Perfmon: possible freeze starting at 16:42:01, delay is 4.875
2022.11.28 16:42:06.730 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 501 generated 40 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:42:09.568 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 608 generated 46 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:42:39.058 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 8496 generated 706 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:42:51.474 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 8503 generated 706 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:42:53.614 1: Perfmon: possible freeze starting at 16:42:51, delay is 2.614
2022.11.28 16:43:05.870 1: Perfmon: possible freeze starting at 16:42:58, delay is 7.87
2022.11.28 16:43:06.742 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 501 generated 41 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:43:08.126 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 571 generated 41 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:43:33.551 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 9219 generated 768 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:43:47.344 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 9273 generated 770 errors at ./FHEM/93_DbLog.pm line 2909.
2022.11.28 16:43:53.436 1: Perfmon: possible freeze starting at 16:43:51, delay is 2.436
2022.11.28 16:44:06.706 2: DbLog logdb -> Error table history - DBD::mysql::st execute_array failed: executing 9453 generated 790 errors at ./FHEM/93_DbLog.pm line 2909.

DS_Starter

Das Attr useCharfilter = 1 setzen und restart.
ESXi@NUC+Debian+MariaDB, PV: SMA, Victron MPII+Pylontech+CerboGX
Maintainer: SSCam, SSChatBot, SSCal, SSFile, DbLog/DbRep, Log2Syslog, SolarForecast,Watches, Dashboard, PylonLowVoltage
Kaffeekasse: https://www.paypal.me/HMaaz
Contrib: https://svn.fhem.de/trac/browser/trunk/fhem/contrib/DS_Starter