Net-Tools update auf 1.0.1 Fehler
-
-
Ich hab heute morgen mal den Adapter neu suchen lassen und dabei stürzte der Adapter dann auch mal kurzfristig ab und es gab einige fehler und warnungen. Das gleiche wiederholt sich auch bei weiteren versuchen.
Es fehlen geräte und gelöschte bzw Geräte die ich in der Fritzbox umbenannt habe werden nicht (zumindest) automatisch gefunden853 Log-Größe: 203.5 KB Zeit Nachricht net-tools.0 2024-01-21 12:09:12.893 info Port scan finished net-tools.0 2024-01-21 12:09:11.856 warn License Key is invalid net-tools.0 2024-01-21 12:09:10.728 info Scanning for open ports (20, 21, 22, 23, 25, 53, 80, 110, 119, 123, 143, 161, 162, 194, 443, 445, 3306, 3389, 5900, 6379, 8080, 8443, 9090, 9200, 9999) at localhost, please wait net-tools.0 2024-01-21 12:09:10.462 info starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.net-tools, node: v18.19.0, js-controller: 5.0.17 host.iobroker 2024-01-21 12:09:08.144 info instance system.adapter.net-tools.0 started with pid 24532 host.iobroker 2024-01-21 12:08:38.035 info Restart adapter system.adapter.net-tools.0 because enabled host.iobroker 2024-01-21 12:08:38.034 error instance system.adapter.net-tools.0 terminated with code 6 (UNCAUGHT_EXCEPTION) net-tools.0 2024-01-21 12:08:37.922 info Default value for state "net-tools.0.2462ab541893.time" could not be set: DB closed net-tools.0 2024-01-21 12:08:37.920 warn get state error: Connection is closed. net-tools.0 2024-01-21 12:08:37.919 warn Could not perform strict object check of state net-tools.0.2462ab541893.time: DB closed net-tools.0 2024-01-21 12:08:37.911 warn redis get net-tools.0.2462ab541893.time, error - Connection is closed. net-tools.0 2024-01-21 12:08:37.898 info terminating net-tools.0 2024-01-21 12:08:37.802 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.801 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.651 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.506 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.461 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.460 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.459 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.458 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.457 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.457 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.456 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.455 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.453 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.452 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.451 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.450 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.448 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.447 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.445 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.444 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.442 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.441 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.438 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.436 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.435 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.435 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.433 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.432 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.432 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.431 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.430 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.429 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.428 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.427 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.426 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.425 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.425 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.424 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.423 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.421 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.420 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.419 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.418 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.418 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.417 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 12:08:37.396 warn Terminated (UNCAUGHT_EXCEPTION): Without reason net-tools.0 2024-01-21 12:08:37.394 info terminating net-tools.0 2024-01-21 12:08:37.050 error Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 12:08:37.048 error TypeError: Cannot read properties of undefined (reading 'stateAlive') at /opt/iobroker/node_modules/iobroker.net-tools/main.js:523:35 at ChildProcess.<anonymous> (/opt/iobroker/node_modules/iobroker.net-tools/lib/ping.js:144:15) at ChildProcess.emit (node:events:517:28) at ChildProcess._handle.onexit (node:internal/child_process:292:12) net-tools.0 2024-01-21 12:08:37.047 error uncaught exception: Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 12:08:37.044 error Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 12:08:37.043 error TypeError: Cannot read properties of undefined (reading 'stateAlive') at /opt/iobroker/node_modules/iobroker.net-tools/main.js:523:35 at ChildProcess.<anonymous> (/opt/iobroker/node_modules/iobroker.net-tools/lib/ping.js:144:15) at ChildProcess.emit (node:events:517:28) at ChildProcess._handle.onexit (node:internal/child_process:292:12) net-tools.0 2024-01-21 12:08:37.041 error uncaught exception: Cannot read properties of undefined (reading 'stateAlive') discovery.0 2024-01-21 12:08:12.374 info Discovery finished discovery.0 2024-01-21 12:08:12.179 info Discovery finished. Found new or modified 13 instances net-tools.0 2024-01-21 12:07:01.161 warn Unknown message origin: 1777722 discovery.0 2024-01-21 12:04:35.882 info Found 43 addresses discovery.0 2024-01-21 12:04:35.720 info Done discovering ping devices. 42 packages received discovery.0 2024-01-21 12:04:09.872 info Discovering ping devices... net-tools.0 2024-01-21 12:04:08.806 error Error: No outstanding message, can't send a new one admin.0 2024-01-21 12:03:54.291 warn net-tools has an invalid jsonConfig: [{"instancePath":"/items/_deviceManager","schemaPath":"#/properties/items/patternProperties/%5E.%2B/allOf/8/then/additionalProperties","keyword":"additionalProperties","params":{"additionalProperty":"innerStyle"},"message":"must NOT have additional properties"}] host.iobroker 2024-01-21 12:00:10.219 info instance system.adapter.ical.0 terminated with code 0 (NO_ERROR) ical.0 2024-01-21 12:00:10.057 warn get state error: Connection is closed. -
@teletapi sagte in Net-Tools update auf 1.0.1 Fehler:
Es fehlen geräte und gelöschte bzw Geräte die ich in der Fritzbox umbenannt habe werden nicht (zumindest) automatisch gefunden
Das Geräte Fehlen kann daran liegen das sie nicht auf den Ping reagieren. Es gab auch früher Meldungen das Geräte nicht gefunden wurden obwohl sie per Ping erreichbar sind. Dieses Problem betrifft auch drn Ping Adapter und die Ursache hab ich bisher nicht finden können.
Hier hilft es nur die Geräte von Hand an zu legen.Warum gelöschte Geräte nicht gefunden werden können ergibt für mich erst mal keinen Sinn. Das muss ich versuchen Nach zu stellen.
Da Geräte mit ihrer Mac im Adapter angelegt werden hat der Name keinen Einfluss. Es kann sein das der Name nicht in den Adapter übernommen wird, dennoch sollte es weiterhin im Adapter zu sehen sein, wenn es nicht gelöscht wurde.
Die Fehlermeldungen sehe ich mir an.
-
Ja ich lösch den Adapter jetzt, das hier macht irgendwie so garkeinen Sinn
2999+ Log-Größe: 54.1 KB Zeit Nachricht admin.0 2024-01-21 15:03:27.368 info <== Disconnect system.user.admin from ::ffff:192.168.178.63 admin.0 2024-01-21 15:02:18.027 info ==> Connected system.user.admin from ::ffff:192.168.178.63 net-tools.0 2024-01-21 15:01:32.871 info Port scan finished net-tools.0 2024-01-21 15:01:31.880 warn License Key is invalid net-tools.0 2024-01-21 15:01:30.741 info Scanning for open ports (20, 21, 22, 23, 25, 53, 80, 110, 119, 123, 143, 161, 162, 194, 443, 445, 3306, 3389, 5900, 6379, 8080, 8443, 9090, 9200, 9999) at localhost, please wait net-tools.0 2024-01-21 15:01:30.553 info starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.net-tools, node: v18.19.0, js-controller: 5.0.17 host.iobroker 2024-01-21 15:01:28.059 info instance system.adapter.net-tools.0 started with pid 50632 host.iobroker 2024-01-21 15:00:57.972 info Restart adapter system.adapter.net-tools.0 because enabled host.iobroker 2024-01-21 15:00:57.971 error instance system.adapter.net-tools.0 terminated with code 6 (UNCAUGHT_EXCEPTION) net-tools.0 2024-01-21 15:00:57.824 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.822 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.821 warn Could not perform strict object check of state net-tools.0.2462ab541893.rps: DB closed net-tools.0 2024-01-21 15:00:57.821 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.820 warn Could not perform strict object check of state net-tools.0.2462ab541893.time: DB closed net-tools.0 2024-01-21 15:00:57.819 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.819 warn Could not perform strict object check of state net-tools.0.aafe8b6946e4.rps: DB closed net-tools.0 2024-01-21 15:00:57.818 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.818 warn Could not perform strict object check of state net-tools.0.aafe8b6946e4.time: DB closed net-tools.0 2024-01-21 15:00:57.817 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.817 warn Could not perform strict object check of state net-tools.0.aafe8b6946e4.alive: DB closed net-tools.0 2024-01-21 15:00:57.816 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.816 warn Could not perform strict object check of state net-tools.0.c45bbe556fde.rps: DB closed net-tools.0 2024-01-21 15:00:57.815 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.814 warn Could not perform strict object check of state net-tools.0.c45bbe556fde.time: DB closed net-tools.0 2024-01-21 15:00:57.814 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.813 warn Could not perform strict object check of state net-tools.0.c45bbe556fde.alive: DB closed net-tools.0 2024-01-21 15:00:57.812 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.812 warn Could not perform strict object check of state net-tools.0.308398a2f258.rps: DB closed net-tools.0 2024-01-21 15:00:57.811 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.810 warn Could not perform strict object check of state net-tools.0.308398a2f258.time: DB closed net-tools.0 2024-01-21 15:00:57.810 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.809 warn Could not perform strict object check of state net-tools.0.308398a2f258.alive: DB closed net-tools.0 2024-01-21 15:00:57.808 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.808 warn Could not perform strict object check of state net-tools.0.b48a0ac70e0e.rps: DB closed net-tools.0 2024-01-21 15:00:57.807 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.806 warn Could not perform strict object check of state net-tools.0.b48a0ac70e0e.time: DB closed net-tools.0 2024-01-21 15:00:57.805 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.804 warn Could not perform strict object check of state net-tools.0.b48a0ac70e0e.alive: DB closed net-tools.0 2024-01-21 15:00:57.804 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.803 warn Could not perform strict object check of state net-tools.0.70039f01361f.rps: DB closed net-tools.0 2024-01-21 15:00:57.802 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.802 warn Could not perform strict object check of state net-tools.0.70039f01361f.time: DB closed net-tools.0 2024-01-21 15:00:57.800 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.798 warn Could not perform strict object check of state net-tools.0.70039f01361f.alive: DB closed net-tools.0 2024-01-21 15:00:57.797 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.797 warn Could not perform strict object check of state net-tools.0.ec94cb7b5908.rps: DB closed net-tools.0 2024-01-21 15:00:57.796 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.795 warn Could not perform strict object check of state net-tools.0.ec94cb7b5908.time: DB closed net-tools.0 2024-01-21 15:00:57.795 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.794 warn Could not perform strict object check of state net-tools.0.ec94cb7b5908.alive: DB closed net-tools.0 2024-01-21 15:00:57.793 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.792 warn Could not perform strict object check of state net-tools.0.d85ed3f769e8.rps: DB closed net-tools.0 2024-01-21 15:00:57.792 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.791 warn Could not perform strict object check of state net-tools.0.d85ed3f769e8.time: DB closed net-tools.0 2024-01-21 15:00:57.790 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.790 warn Could not perform strict object check of state net-tools.0.d85ed3f769e8.alive: DB closed net-tools.0 2024-01-21 15:00:57.789 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.788 warn Could not perform strict object check of state net-tools.0.c45bbe5536ee.rps: DB closed net-tools.0 2024-01-21 15:00:57.788 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.787 warn Could not perform strict object check of state net-tools.0.c45bbe5536ee.time: DB closed net-tools.0 2024-01-21 15:00:57.786 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.785 warn Could not perform strict object check of state net-tools.0.c45bbe5536ee.alive: DB closed net-tools.0 2024-01-21 15:00:57.785 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.784 warn Could not perform strict object check of state net-tools.0.4827e22eda50.rps: DB closed net-tools.0 2024-01-21 15:00:57.783 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.783 warn Could not perform strict object check of state net-tools.0.4827e22eda50.time: DB closed net-tools.0 2024-01-21 15:00:57.782 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.781 warn Could not perform strict object check of state net-tools.0.4827e22eda50.alive: DB closed net-tools.0 2024-01-21 15:00:57.758 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.758 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.758 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.757 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.757 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.757 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.756 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.756 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.755 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.755 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.755 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.754 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.754 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.754 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.753 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.753 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.753 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.752 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.752 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.752 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.751 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.751 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.751 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.750 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.750 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.749 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.749 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.749 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.748 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.748 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.747 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.747 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.746 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.745 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.744 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.743 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.743 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.742 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.741 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.740 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.739 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.739 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.738 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.737 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.736 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.735 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.734 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.733 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.733 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.732 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.731 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.730 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.729 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.728 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.727 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.727 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.726 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.725 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.724 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.723 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.722 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.711 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.710 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.709 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.709 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.708 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.707 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.707 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.706 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.705 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.705 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.704 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.704 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.703 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.703 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.702 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.701 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.701 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.700 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.699 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.699 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.699 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.698 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.698 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.698 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.697 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.695 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.694 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.694 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.694 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.693 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.693 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.693 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.692 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.692 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.691 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.691 warn get state error: Connection is closed. net-tools.0 2024-01-21 15:00:57.645 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.644 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.643 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.642 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.642 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.641 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.640 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.640 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.639 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.638 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.637 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.637 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.636 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.635 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.634 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.634 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.633 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.632 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.631 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.631 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.629 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.629 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.628 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.627 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.626 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.626 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.625 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.624 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.624 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.623 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.622 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.621 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.621 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.620 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.619 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.619 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.618 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.617 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.616 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.615 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.614 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.613 warn setTimeout called, but adapter is shutting down net-tools.0 2024-01-21 15:00:57.593 info terminating net-tools.0 2024-01-21 15:00:57.021 warn Terminated (UNCAUGHT_EXCEPTION): Without reason net-tools.0 2024-01-21 15:00:57.019 info terminating net-tools.0 2024-01-21 15:00:56.980 error Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.979 error uncaught exception: Cannot read properties of undefined (reading 'stateAlive') at /opt/iobroker/node_modules/iobroker.net-tools/main.js:523:35 at ChildProcess.<anonymous> (/opt/iobroker/node_modules/iobroker.net-tools/lib/ping.js:144:15) at ChildProcess.emit (node:events:517:28) at ChildProcess._handle.onexit (node:internal/child_process:292:12) net-tools.0 2024-01-21 15:00:56.978 error Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.979 error TypeError: Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.977 error uncaught exception: Cannot read properties of undefined (reading 'stateAlive') at /opt/iobroker/node_modules/iobroker.net-tools/main.js:523:35 at ChildProcess.<anonymous> (/opt/iobroker/node_modules/iobroker.net-tools/lib/ping.js:144:15) at ChildProcess.emit (node:events:517:28) at ChildProcess._handle.onexit (node:internal/child_process:292:12) net-tools.0 2024-01-21 15:00:56.976 error Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.977 error TypeError: Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.975 error uncaught exception: Cannot read properties of undefined (reading 'stateAlive') at /opt/iobroker/node_modules/iobroker.net-tools/main.js:523:35 at ChildProcess.<anonymous> (/opt/iobroker/node_modules/iobroker.net-tools/lib/ping.js:144:15) at ChildProcess.emit (node:events:517:28) at ChildProcess._handle.onexit (node:internal/child_process:292:12) net-tools.0 2024-01-21 15:00:56.974 error Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.975 error TypeError: Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.973 error uncaught exception: Cannot read properties of undefined (reading 'stateAlive') at /opt/iobroker/node_modules/iobroker.net-tools/main.js:523:35 at ChildProcess.<anonymous> (/opt/iobroker/node_modules/iobroker.net-tools/lib/ping.js:144:15) at ChildProcess.emit (node:events:517:28) at ChildProcess._handle.onexit (node:internal/child_process:292:12) net-tools.0 2024-01-21 15:00:56.972 error Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.973 error TypeError: Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.971 error uncaught exception: Cannot read properties of undefined (reading 'stateAlive') at /opt/iobroker/node_modules/iobroker.net-tools/main.js:523:35 at ChildProcess.<anonymous> (/opt/iobroker/node_modules/iobroker.net-tools/lib/ping.js:144:15) at ChildProcess.emit (node:events:517:28) at ChildProcess._handle.onexit (node:internal/child_process:292:12) net-tools.0 2024-01-21 15:00:56.970 error Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.971 error TypeError: Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.969 error TypeError: Cannot read properties of undefined (reading 'stateAlive') at /opt/iobroker/node_modules/iobroker.net-tools/main.js:523:35 at ChildProcess.<anonymous> (/opt/iobroker/node_modules/iobroker.net-tools/lib/ping.js:144:15) at ChildProcess.emit (node:events:517:28) at ChildProcess._handle.onexit (node:internal/child_process:292:12) net-tools.0 2024-01-21 15:00:56.969 error uncaught exception: Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.968 error TypeError: Cannot read properties of undefined (reading 'stateAlive') at /opt/iobroker/node_modules/iobroker.net-tools/main.js:523:35 at ChildProcess.<anonymous> (/opt/iobroker/node_modules/iobroker.net-tools/lib/ping.js:144:15) at ChildProcess.emit (node:events:517:28) at ChildProcess._handle.onexit (node:internal/child_process:292:12) net-tools.0 2024-01-21 15:00:56.967 error uncaught exception: Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.968 error Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.966 error Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.966 error TypeError: Cannot read properties of undefined (reading 'stateAlive') at /opt/iobroker/node_modules/iobroker.net-tools/main.js:523:35 at ChildProcess.<anonymous> (/opt/iobroker/node_modules/iobroker.net-tools/lib/ping.js:144:15) at ChildProcess.emit (node:events:517:28) at ChildProcess._handle.onexit (node:internal/child_process:292:12) net-tools.0 2024-01-21 15:00:56.965 error uncaught exception: Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.964 error TypeError: Cannot read properties of undefined (reading 'stateAlive') at /opt/iobroker/node_modules/iobroker.net-tools/main.js:523:35 at ChildProcess.<anonymous> (/opt/iobroker/node_modules/iobroker.net-tools/lib/ping.js:144:15) at ChildProcess.emit (node:events:517:28) at ChildProcess._handle.onexit (node:internal/child_process:292:12) net-tools.0 2024-01-21 15:00:56.964 error uncaught exception: Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.964 error Cannot read properties of undefined (reading 'stateAlive') net-tools.0 2024-01-21 15:00:56.963 error Cannot read properties of undefined (reading 'stateAlive') -
Morjen, ich denke ich weiß jetzt woher die Fehler und warnungen kommen.
Ich hab heute morgen gesehen das der "Net-tools" Adapter in der version 1.03 vorhanden ist und hab den nochmal installiert, eigentlich wollte ich damit nur schauen ob ich vielleicht einen fehler bei der Installation über die Katze ein Fehler gemacht habe. Nach der Installation blieben die Fehler und Warnungen aber die gleichen.Dabei hab ich im Protocol aber gesehen das der Discovery Adapter scheinbar immer mit reagiert wenn ich die Gerätesuche im Net-Tools adapter starte.
Dann hab ich nochmal bei den Instanzen geschaut und da fielen mir die beiden Adapter "Ping" und "Discovery" auf und habe diese einfach mal gestoppt und dann den Net-tools Adapter laufen lassen neu gestartet und die Geräte suche laufen lassen, dabei wurden alle Geräte gefunden. Seiddem hat der Adapter keinen fehler mehr gezeigtDen Ping Adapter habe ich mittlerweile wieder aktiviert und beide Adapter mal unabhängig voneinander neu gestartet das scheint den Net-tools Adapter aber nicht zu stören. Dürfte dann also der "Discovery Adapter" sein der hier in Verbindung mit dem Net-tools Adapter Probleme macht.
Sobald ich dann die Gerätesuche im Net-tools Adapter starte startet auch der Discovery Adapter neu und die Fehler sind wieder da
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: iobroker Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.5 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 10:46:21 up 34 min, 1 user, load average: 1.39, 1.25, 1.20 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Mon 2024-01-22 10:46:21 CET Universal time: Mon 2024-01-22 09:46:21 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input render netdev lpadmin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 7.8G 2.3G 3.7G 1.0M 1.7G 5.3G Swap: 99M 0B 99M Total: 7.9G 2.3G 3.8G 7811 M total memory 2343 M used memory 3335 M active memory 583 M inactive memory 3727 M free memory 121 M buffer memory 1619 M swap cache 99 M total swap 0 M used swap 99 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 59G 9.2G 47G 17% / devtmpfs devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 1.6G 1.2M 1.6G 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda1 vfat 255M 31M 225M 13% /boot tmpfs tmpfs 782M 16K 782M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Mon Jan 22 10:12:17 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=D8:3A:DD:13:A5:D1 vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 console=tty1 root=PARTUUID=2c0392e1-02 rootfstype=ext4 fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Mon Jan 22 10:12:19 2024] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none. [Mon Jan 22 10:12:19 2024] VFS: Mounted root (ext4 filesystem) readonly on device 8:2. [Mon Jan 22 10:12:20 2024] EXT4-fs (sda2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,noatime `-/boot /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 1.9G /var/ 1.1G /var/log/journal/a9f1eae0dc5a48ddbf0e2a62c2227673 1.1G /var/log/journal 1.1G /var/log 619M /var/lib Archived and active journals take up 1.0G in the file system. /opt/iobroker/backups: 1.8G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 352M /opt/iobroker/iobroker-data/ 181M /opt/iobroker/iobroker-data/files 77M /opt/iobroker/iobroker-data/backup-objects 72M /opt/iobroker/iobroker-data/node-red 71M /opt/iobroker/iobroker-data/node-red/node_modules The five largest files in iobroker-data are: 33M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js.map 22M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js.map 15M /opt/iobroker/iobroker-data/objects.jsonl 8.5M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js 8.3M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.c05ba1d3.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': find: '/dev/serial/by-id/': No such file or directory *** NodeJS-Installation *** /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.0-1nodesource1 Candidate: 18.19.0-1nodesource1 Version table: *** 18.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.17 admin: 6.13.15 javascript: 7.7.0 Adapters from github: 2 Adapter State + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alexa2.0 : alexa2 : iobroker - enabled system.adapter.alias-manager.0 : alias-manager : iobroker - disabled + system.adapter.backitup.0 : backitup : iobroker - enabled + system.adapter.cloud.0 : cloud : iobroker - enabled system.adapter.discovery.0 : discovery : iobroker - disabled + system.adapter.energiefluss-erweitert.0 : energiefluss-erweitert: iobroker - enabled + system.adapter.fritzdect.0 : fritzdect : iobroker - enabled + system.adapter.hm-rega.0 : hm-rega : iobroker - enabled + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 18701 + system.adapter.hm-rpc.1 : hm-rpc : iobroker - enabled, port: 12001 + system.adapter.hm-rpc.2 : hm-rpc : iobroker - enabled, port: 12010 + system.adapter.hm-rpc.3 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.hue.0 : hue : iobroker - enabled, port: 443 system.adapter.ical.0 : ical : iobroker - enabled + system.adapter.influxdb.0 : influxdb : iobroker - enabled, port: 8086 + system.adapter.info.0 : info : iobroker - enabled + system.adapter.iot.0 : iot : iobroker - enabled + system.adapter.jarvis.0 : jarvis : iobroker - enabled + system.adapter.javascript.0 : javascript : iobroker - enabled + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.net-tools.0 : net-tools : iobroker - enabled + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.nuki.0 : nuki : iobroker - enabled + system.adapter.opendtu.0 : opendtu : iobroker - enabled + system.adapter.philips-tv.0 : philips-tv : iobroker - enabled system.adapter.ping.0 : ping : iobroker - disabled + system.adapter.rpi2.0 : rpi2 : iobroker - enabled + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : iobroker - enabled, port: 8087, bind: 192.168.178.82, run as: admin + system.adapter.socketio.0 : socketio : iobroker - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : iobroker - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.sourceanalytix.0 : sourceanalytix : iobroker - enabled + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.tr-064.0 : tr-064 : iobroker - enabled + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : iobroker - enabled, port: 18701 + system.adapter.hm-rpc.1 : hm-rpc : iobroker - enabled, port: 12001 + system.adapter.hm-rpc.2 : hm-rpc : iobroker - enabled, port: 12010 + system.adapter.hm-rpc.3 : hm-rpc : iobroker - enabled, port: 0 + system.adapter.hue.0 : hue : iobroker - enabled, port: 443 + system.adapter.influxdb.0 : influxdb : iobroker - enabled, port: 8086 + system.adapter.mqtt.0 : mqtt : iobroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.node-red.0 : node-red : iobroker - enabled, port: 1880, bind: 0.0.0.0 + system.adapter.shelly.0 : shelly : iobroker - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : iobroker - enabled, port: 8087, bind: 192.168.178.82, run as: admin + system.adapter.socketio.0 : socketio : iobroker - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : iobroker - enabled, port: 1886, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : iobroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): beta Installed ioBroker-Instances Used repository: beta Adapter "admin" : 6.13.15 , installed 6.13.15 Adapter "alexa2" : 3.26.3 , installed 3.26.3 Adapter "alias-manager": 1.2.6 , installed 1.2.6 Adapter "backitup" : 2.10.4 , installed 2.10.4 Adapter "cloud" : 4.4.1 , installed 4.4.1 Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "fritzdect" : 2.5.9 , installed 2.5.9 Adapter "hm-rega" : 4.0.0 , installed 4.0.0 Adapter "hm-rpc" : 1.16.0 , installed 1.16.0 Adapter "hue" : 3.10.2 , installed 3.10.2 Adapter "ical" : 1.14.0 , installed 1.14.0 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "info" : 2.0.0 , installed 2.0.0 Adapter "iot" : 2.0.11 , installed 2.0.11 Adapter "jarvis" : 3.1.8 , installed 3.1.9-beta.3 Adapter "javascript" : 7.7.0 , installed 7.7.0 Controller "js-controller": 5.0.17 , installed 5.0.17 Adapter "mqtt" : 5.2.0 , installed 5.2.0 Adapter "net-tools" : 1.0.3 , installed 1.0.3 Adapter "node-red" : 5.1.0 , installed 5.1.0 Adapter "nuki" : 1.6.0 , installed 1.6.0 Adapter "opendtu" : 1.0.1 , installed 1.0.1 Adapter "philips-tv" : 0.5.3 , installed 0.5.3 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "rpi2" : 1.3.2 , installed 1.3.2 Adapter "shelly" : 6.7.0 , installed 6.7.0 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 6.6.0 Adapter "sonoff" : 3.0.3 , installed 3.0.3 Adapter "sourceanalytix": 0.4.14 , installed 0.4.14 Adapter "telegram" : 3.0.1 , installed 3.0.1 Adapter "tr-064" : 4.2.18 , installed 4.2.18 Adapter "web" : 6.2.3 , installed 6.2.3 Adapter "ws" : 2.5.10 , installed 2.5.10 Objects and States Please stand by - This may take a while Objects: 10033 States: 10104 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian bullseye-updates InRelease Hit:3 http://security.debian.org/debian-security bullseye-security InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Hit:5 https://apt.grafana.com stable InRelease Hit:6 https://repos.influxdata.com/debian stable InRelease Hit:7 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 192.168.178.82:12010 0.0.0.0:* LISTEN 1001 17711 1371/io.hm-rpc.2 tcp 0 0 192.168.178.82:12001 0.0.0.0:* LISTEN 1001 16319 1349/io.hm-rpc.1 tcp 0 0 192.168.178.82:8087 0.0.0.0:* LISTEN 1001 19209 1936/io.simple-api. tcp 0 0 192.168.178.82:18701 0.0.0.0:* LISTEN 1001 17018 1328/io.hm-rpc.0 tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 16412 540/cupsd tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 11882 576/sshd: /usr/sbin tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 14752 657/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 12133 657/iobroker.js-con tcp 0 0 192.168.178.82:2001 0.0.0.0:* LISTEN 1001 17184 1425/io.hm-rpc.3 tcp 0 0 0.0.0.0:8400 0.0.0.0:* LISTEN 1001 23289 1856/io.jarvis.0 tcp 0 0 0.0.0.0:1880 0.0.0.0:* LISTEN 1001 17603 1247/node-red tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1001 18758 1561/io.shelly.0 tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 116 15492 558/mosquitto tcp 0 0 0.0.0.0:1886 0.0.0.0:* LISTEN 1001 18120 1498/io.sonoff.0 tcp 0 0 192.168.178.82:9092 0.0.0.0:* LISTEN 1001 24733 1922/io.nuki.0 tcp6 0 0 :::3000 :::* LISTEN 117 14648 656/grafana tcp6 0 0 :::8081 :::* LISTEN 1001 15817 1079/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 21540 1656/io.web.0 tcp6 0 0 :::8084 :::* LISTEN 1001 24693 2164/io.socketio.0 tcp6 0 0 :::8086 :::* LISTEN 999 11946 549/influxd tcp6 0 0 ::1:631 :::* LISTEN 0 16411 540/cupsd tcp6 0 0 :::22 :::* LISTEN 0 11884 576/sshd: /usr/sbin tcp6 0 0 :::1883 :::* LISTEN 116 15493 558/mosquitto udp 0 0 0.0.0.0:631 0.0.0.0:* 0 11920 617/cups-browsed udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 11257 401/avahi-daemon: r udp 0 0 0.0.0.0:48832 0.0.0.0:* 108 11259 401/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 14641 461/dhcpcd udp6 0 0 :::546 :::* 0 14661 461/dhcpcd udp6 0 0 :::5353 :::* 108 11258 401/avahi-daemon: r udp6 0 0 :::53051 :::* 108 11260 401/avahi-daemon: r *** Log File - Last 25 Lines *** 2024-01-22 10:39:04.632 - info: host.iobroker stopInstance system.adapter.net-tools.0 (force=false, process=true) 2024-01-22 10:39:04.766 - info: net-tools.0 (8472) Got terminate signal TERMINATE_YOURSELF 2024-01-22 10:39:04.771 - info: host.iobroker stopInstance system.adapter.net-tools.0 send kill signal 2024-01-22 10:39:04.772 - info: net-tools.0 (8472) terminating 2024-01-22 10:39:04.774 - info: net-tools.0 (8472) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-01-22 10:39:05.276 - info: net-tools.0 (8472) terminating 2024-01-22 10:39:05.434 - info: host.iobroker instance system.adapter.net-tools.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2024-01-22 10:39:07.862 - info: host.iobroker instance system.adapter.net-tools.0 started with pid 8574 2024-01-22 10:39:10.364 - info: net-tools.0 (8574) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.net-tools, node: v18.19.0, js-controller: 5.0.17 2024-01-22 10:39:10.579 - info: net-tools.0 (8574) License Key is valid 2024-01-22 10:39:10.587 - info: net-tools.0 (8574) Scanning for open ports (20, 21, 22, 23, 25, 53, 80, 110, 119, 123, 143, 161, 162, 194, 443, 445, 3306, 3389, 5900, 6379, 8080, 8443, 9090, 9200, 9999) at localhost, please wait 2024-01-22 10:39:13.207 - info: net-tools.0 (8574) Port scan finished -
@teletapi das ist gut zu wissen. Der discovery adapter ist als dependency eingetragen und sollte so bei bedarf mit installiert werden, falls er nich da ist. Gestartet wird er Automatisch wenn er nicht läuft.
Da muss ich also noch zusätzlich Warnmeldungen einbauen. -
@teletapi said in Net-Tools update auf 1.0.1 Fehler:
Morjen, ich denke ich weiß jetzt woher die Fehler und warnungen kommen.
Den Ping Adapter habe ich mittlerweile wieder aktiviert und beide Adapter mal unabhängig voneinander neu gestartet das scheint den Net-tools Adapter aber nicht zu stören.
Ping und net-tools sollten sich in keiner Weise gegenseitig beeinflussen.
Dürfte dann also der "Discovery Adapter" sein der hier in Verbindung mit dem Net-tools Adapter Probleme macht.
Sobald ich dann die Gerätesuche im Net-tools Adapter starte startet auch der Discovery Adapter neu und die Fehler sind wieder da
Da meines Wissens nach net-tools die Funktion(en) des discovery Adapters zur Gerätesuche verwendet ist dieses Verhalten logisch erklärbar. Genau aus diesem Grunde setzt ja net-tools auch die INstallation von discovery voraus.
-
@mcm57 Das war mir natürlich so nicht ganz bewusst und hab ich erst im Nachgang einigermaßen verstanden. Die Fehler die dann dabei entstehen versteh ich halt nicht...... Wie ich sovieles noch immer nicht verstehe was alle Adapter,abhängigkeiten usw. angeht. Da bin ich ganz auf euer aller Hilfe angewiesen
-
@teletapi said in Net-Tools update auf 1.0.1 Fehler:
@mcm57 Das war mir natürlich so nicht ganz bewusst und hab ich erst im Nachgang einigermaßen verstanden. Die Fehler die dann dabei entstehen versteh ich halt nicht...... Wie ich sovieles noch immer nicht verstehe was alle Adapter,abhängigkeiten usw. angeht. Da bin ich ganz auf euer aller Hilfe angewiesen
Ja passt schon.
Jey-Cee wird sich die Fehler garantiert zeitnahe ansehen.
-
@mcm57 danke das du es noch mal etwas klarer Formuliert hast.
Selbstverständlich schaue ich mir das an.
