[gelöst] Fehlersuche

matze1999 · 06 Mai 2022, 14:35:34

Hallo,

ich habe Warnungen und freezes im log, die ich gern nachverfolgen würde. allerdings fehlt mir der Ansatz, wie ich nach der Ursache suche. Wie würdet ihr vorgehen?

1.

Code Auswählen

2022.05.05 21:55:52 1: PERL WARNING: Argument "-5-" isn't numeric in subtraction (-) at ./FHEM/98_SVG.pm line 1368.
2022.05.05 21:55:52 1: stacktrace:
2022.05.05 21:55:52 1:     main::__ANON__                      called by ./FHEM/98_SVG.pm (1368)
2022.05.05 21:55:52 1:     main::SVG_getSteps                  called by ./FHEM/98_SVG.pm (1826)
2022.05.05 21:55:52 1:     main::SVG_render                    called by ./FHEM/98_SVG.pm (1227)
2022.05.05 21:55:52 1:     main::SVG_doShowLog                 called by ./FHEM/98_SVG.pm (1118)
2022.05.05 21:55:52 1:     main::SVG_showLog                   called by ./FHEM/01_FHEMWEB.pm (1012)
2022.05.05 21:55:52 1:     main::FW_answerCall                 called by ./FHEM/01_FHEMWEB.pm (608)
2022.05.05 21:55:52 1:     main::FW_Read                       called by fhem.pl (3931)
2022.05.05 21:55:52 1:     main::CallFn                        called by fhem.pl (780)

2.

Code Auswählen

2022.05.06 13:59:08 1: Perfmon: possible freeze starting at 13:59:07, delay is 1.022
2022.05.06 13:59:14 1: Perfmon: possible freeze starting at 13:59:13, delay is 1.319
2022.05.06 13:59:22 1: Perfmon: possible freeze starting at 13:59:21, delay is 1.295
2022.05.06 13:59:48 1: Perfmon: possible freeze starting at 13:59:47, delay is 1.308
2022.05.06 14:00:50 1: Perfmon: possible freeze starting at 14:00:49, delay is 1.103
2022.05.06 14:01:10 1: Perfmon: possible freeze starting at 14:01:09, delay is 1.409
2022.05.06 14:03:18 1: Perfmon: possible freeze starting at 14:03:17, delay is 1.282
2022.05.06 14:03:53 1: Perfmon: possible freeze starting at 14:03:52, delay is 1.347
2022.05.06 14:04:14 1: Perfmon: possible freeze starting at 14:04:13, delay is 1.403
2022.05.06 14:04:28 1: Perfmon: possible freeze starting at 14:04:27, delay is 1.171
2022.05.06 14:06:30 1: Perfmon: possible freeze starting at 14:06:29, delay is 1.52
2022.05.06 14:07:19 1: Perfmon: possible freeze starting at 14:07:18, delay is 1.297
2022.05.06 14:07:32 1: Perfmon: possible freeze starting at 14:07:31, delay is 1.19
2022.05.06 14:07:58 1: Perfmon: possible freeze starting at 14:07:57, delay is 1.413
2022.05.06 14:09:34 1: Perfmon: possible freeze starting at 14:09:33, delay is 1.135
2022.05.06 14:10:26 1: Perfmon: possible freeze starting at 14:10:25, delay is 1.397
2022.05.06 14:12:03 1: Perfmon: possible freeze starting at 14:12:02, delay is 1.263

3.

Code Auswählen

2022.05.06 12:40:59 1: PERL WARNING: Argument "AUTO" isn't numeric in division (/) at ./FHEM/70_DENON_AVR.pm line 1805.
2022.05.06 12:40:59 1: stacktrace:
2022.05.06 12:40:59 1:     main::__ANON__                      called by ./FHEM/70_DENON_AVR.pm (1805)
2022.05.06 12:40:59 1:     main::DENON_AVR_Parse               called by ./FHEM/70_DENON_AVR.pm (1589)
2022.05.06 12:40:59 1:     main::DENON_AVR_Read                called by fhem.pl (3931)
2022.05.06 12:40:59 1:     main::CallFn                        called by fhem.pl (780)

4.

Code Auswählen

2022.05.06 03:03:23 1: PERL WARNING: Argument "set 60" isn't numeric in numeric lt (<) at FHEM/Color.pm line 508.
2022.05.06 03:03:23 1: eval: {Color::devStateIcon($name,'rgb','rgb','pct','state')}
2022.05.06 03:03:23 1: stacktrace:
2022.05.06 03:03:23 1:     main::__ANON__                      called by FHEM/Color.pm (508)
2022.05.06 03:03:23 1:     Color::devStateIcon                 called by (eval 3546899) (1)
2022.05.06 03:03:23 1:     (eval)                              called by ./FHEM/01_FHEMWEB.pm (3002)
2022.05.06 03:03:23 1:     main::FW_dev2image                  called by ./FHEM/01_FHEMWEB.pm (3328)
2022.05.06 03:03:23 1:     main::FW_devState                   called by ./FHEM/01_FHEMWEB.pm (3190)
2022.05.06 03:03:23 1:     main::FW_Notify                     called by fhem.pl (3931)
2022.05.06 03:03:23 1:     main::CallFn                        called by fhem.pl (3843)
2022.05.06 03:03:23 1:     main::DoTrigger                     called by fhem.pl (4946)
2022.05.06 03:03:23 1:     main::readingsEndUpdate             called by fhem.pl (5129)
2022.05.06 03:03:23 1:     main::readingsSingleUpdate          called by ./FHEM/10_MQTT2_DEVICE.pm (428)
2022.05.06 03:03:23 1:     main::MQTT2_DEVICE_Set              called by fhem.pl (3926)
2022.05.06 03:03:23 1:     main::CallFn                        called by fhem.pl (1955)
2022.05.06 03:03:23 1:     main::DoSet                         called by fhem.pl (1987)
2022.05.06 03:03:23 1:     main::CommandSet                    called by fhem.pl (1272)
2022.05.06 03:03:23 1:     main::AnalyzeCommand                called by fhem.pl (1123)
2022.05.06 03:03:23 1:     main::AnalyzeCommandChain           called by ./FHEM/98_DOIF.pm (2046)
2022.05.06 03:03:23 1:     main::ParseCommandsDoIf             called by ./FHEM/98_DOIF.pm (2465)
2022.05.06 03:03:23 1:     main::DOIF_cmd                      called by ./FHEM/98_DOIF.pm (2721)
2022.05.06 03:03:23 1:     main::DOIF_Trigger                  called by ./FHEM/98_DOIF.pm (2959)
2022.05.06 03:03:23 1:     main::DOIF_Notify                   called by fhem.pl (3931)
2022.05.06 03:03:23 1:     main::CallFn                        called by fhem.pl (3843)
2022.05.06 03:03:23 1:     main::DoTrigger                     called by fhem.pl (4946)
2022.05.06 03:03:23 1:     main::readingsEndUpdate             called by ./FHEM/31_HUEDevice.pm (1986)
2022.05.06 03:03:23 1:     main::HUEDevice_Parse               called by ./FHEM/30_HUEBridge.pm (169)
2022.05.06 03:03:23 1:     main::HUEBridge_Read                called by fhem.pl (3931)
2022.05.06 03:03:23 1:     main::CallFn                        called by fhem.pl (780)

matze1999

Beta-User · 06 Mai 2022, 14:51:55

Ad 1:

Zitat von: Beta-User am 01 April 2022, 12:37:10
Keine Ahnung, aber im Forum mit "isn't numeric in numeric gt (>) at ./FHEM/98_SVG.pm" findet sich z.B. https://forum.fhem.de/index.php/topic,124142.msg1187499.html#msg1187499...

Anders gesagt: Du must die zum plotten abgefragten Werte ggf. in "richtige Nummern" verwandeln, Texte oder leere Felder gehen nicht.

Ad 2:
Irgendjemand hat "freezemon" erfunden. Meine Vermutung: u.a. weil Perfmon etwas "schweigsam" ist...

Ad 3:
Bitte selber suchen und/oder ggf. die Frage separat im passenden Forumsbereich posten...

Ad 4:
https://forum.fhem.de/index.php/topic,124191.msg1187606.html#msg1187606

matze1999 · 10 Mai 2022, 11:18:09

Hallo,

Fehler 1 ist weg, ich hatte bei einem plot wirklich bei range min,max "-5-" drinstehen.

Fehler 2 ist nach dem Neuaufsetzen des Systems weg.

Fehler 3 ist nach Neuaufsetzen des Systems weg, aber dafür das neu

Fehler 4 weg, mit neuer Color.pm von hier

matze1999

FHEM Forum