DbLog - Creating Push-Handle - Logeinträge bei deaktiviertem Device

Begonnen von SusisStrolch, 19 Januar 2018, 13:44:19

Vorheriges Thema - Nächstes Thema

SusisStrolch

Mein deaktiviertes DbLog-Device "mariadb10" produziert am laufenden Band Einträge im fhem-Log.
defmod mariadb10 DbLog ./contrib/dblog/MariaDB10.conf .*:.*
attr mariadb10 DbLogExclude .*
attr mariadb10 DbLogType Current/History
attr mariadb10 asyncMode 1
attr mariadb10 cacheEvents 2
attr mariadb10 colEvent 512
attr mariadb10 colReading 64
attr mariadb10 colValue 128
attr mariadb10 disable 1
attr mariadb10 event-on-change-reading CacheUsage,background_processing_time
attr mariadb10 group DbLog
attr mariadb10 icon security
attr mariadb10 room DbLog
attr mariadb10 showNotifyTime 1
attr mariadb10 showproctime 1
attr mariadb10 timeout 1800
attr mariadb10 verbose 3

setstate mariadb10 disconnected
setstate mariadb10 2017-12-11 17:34:14 CacheUsage 37
setstate mariadb10 2017-12-11 17:34:14 NextSync 2017-12-11 17:34:44 or if CacheUsage 500 reached
setstate mariadb10 2017-08-03 15:18:52 background_processing_time 1.8575
setstate mariadb10 2017-08-02 22:34:38 countCurrent 274
setstate mariadb10 2017-08-02 22:34:38 countHistory 116428051
setstate mariadb10 2017-12-11 17:34:13 notify_processing_time 0.0026
setstate mariadb10 2017-08-03 15:18:52 sql_processing_time 1.8427
setstate mariadb10 2018-01-19 13:43:24 state disconnected
setstate mariadb10 2017-07-28 10:56:55 userCommand CREATE INDEX Search_Idx ON `history` (DEVICE, READING, TIMESTAMP) USING BTREE;;
setstate mariadb10 2017-07-28 10:56:55 userCommandResult no result




2018.01.19 12:42:31.005 3: DbLog mariadb10: Creating Push-Handle to database mysql:database=fhem;host=192.168.254.20;port=3307 with user fhem
2018.01.19 12:42:36.005 3: DbLog mariadb10: Creating Push-Handle to database mysql:database=fhem;host=192.168.254.20;port=3307 with user fhem
2018.01.19 12:42:41.004 3: DbLog mariadb10: Creating Push-Handle to database mysql:database=fhem;host=192.168.254.20;port=3307 with user fhem
2018.01.19 12:42:46.005 3: DbLog mariadb10: Creating Push-Handle to database mysql:database=fhem;host=192.168.254.20;port=3307 with user fhem
2018.01.19 12:42:51.005 3: DbLog mariadb10: Creating Push-Handle to database mysql:database=fhem;host=192.168.254.20;port=3307 with user fhem

Synology DS1515+, 16GB RAM, 4x 6TB WD-Red
- Docker (FHEM), MariaDB, MariaDB10, Surveillance Station
Gateways: LCG miniCUL433, LCG miniCUL868, AVR-X4000, VU-Solo SE, Kodi
ESP8266: ESPEasy (S0-Counter, Temp/Hum), Sonoff TH, Sonoff 4ch

DS_Starter

Fixe ich im nächsten Release mit.
Habe gerade nachgeschaut. Das passiert wohl wenn das Device disabled ist UND die db nicht erreichbar ist.

Grüsse
Heiko
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

DS_Starter

Mit der angehängten V 3.6.5 sollte dein Problem nicht mehr auftreten.

Grüße
Heiko
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

SusisStrolch

Synology DS1515+, 16GB RAM, 4x 6TB WD-Red
- Docker (FHEM), MariaDB, MariaDB10, Surveillance Station
Gateways: LCG miniCUL433, LCG miniCUL868, AVR-X4000, VU-Solo SE, Kodi
ESP8266: ESPEasy (S0-Counter, Temp/Hum), Sonoff TH, Sonoff 4ch