Objects Datenbank

wrod

@thomas-braun Danke. Ich bekomme derzeit immer noch keine Objekte angezeigt. Das liegt dann wohl nicht am Speicher ...

Thomas Braun

@wrod Schau im LogFile, ob da was steht.

wrod

@thomas-braun Danke.
Ich habe dort mehrere Warnungen, u.a.:

backitup.1
2021-11-24 08:59:30.612 warn Source cannot be reached: Error: EACCES: permission denied, scandir '/opt/iobroker/backups'

aber auch:

influxdb.0
2021-11-24 08:59:53.291 warn Error on writePoint("{"value":"20210429-101611/v1.10.4-g3f94cd7","time":"2021-11-24T07:59:43.248Z","from":"system.adapter.shelly.0","q":0,"ack":true}): Error: {"error":"timeout"} / "{"error":"timeout"}\n"

und

influxdb.0
2021-11-24 08:59:53.315 warn Error on writePoint("{"value":"2D02:44:43","time":"2021-11-24T07:59:43.291Z","from":"system.adapter.shelly.0","q":0,"ack":true}): Error: {"error":"timeout"} / "{"error":"timeout"}\n"

Ich habe auch mal geschaut, welche Verzeichnisse besonders groß sind (du -sh):

Das ist einmal "/home" und darin "Iobroker" mit 593 M sowie "/opt", darin "iobroker" (744M) und darin "iobroker-data" (309M) und "node.modules" (403M).

Asgothian

@wrod

Es könnte sein das du Probleme mit den Rechten hast. Mach doch mal bitte

iobroker fix

auf der Konsole.

A.

wrod

@asgothian Danke.
Nach

iobroker stop
iobroker -fox
iobroker start

habe ich das gleiche Bild. Log gibt nun aber zwei Fehler:

admin.0
2021-11-24 09:28:42.070 error error
admin.0
2021-11-24 09:28:42.060 error failed connection to socket.io from ::ffff:192.168.220.60:

und:

admin.0
2021-11-24 09:30:53.101 warn Cannot parse "undefined"
admin.0
2021-11-24 09:30:52.956 error error
admin.0
2021-11-24 09:30:52.944 warn Cannot parse "undefined"

Thomas Braun

@wrod

Nicht
iobroker -fox
sondern

iobroker fix

wrod

@thomas-braun sorry. Das war mein Typo hier. Nein auch

iobroker fix

ändert nichts.

wrod

@wrod Noch eine Info: Objekte werden nicht aufgelistet. Die "Objekte"-Seite meldet aber oben rechts 1452 Objekte mit 1192 Zuständen (was mir beides sehr hoch zu sein scheint, aber ich kann das sonicht kontrollieren). Kann es sein, dass einige doppelt /mehrfach angelegt wurden?

wrod

@thomas-braun
Ich habe immer noch einen leeren Objektbaum, obwohl oben rechts eine hohe Zahl an Objekten und Zuständen angezeigt wird:

Gleichzeitig zeigt Hosts keine Speicherüberlastung an:

Hier einmal der Beginn bei einem Neutstart des Hosts (rückwärts):

web.0
	2021-11-24 14:27:19.488	info	<==Disconnect system.user.admin from ::ffff:192.168.220.64 flot
web.0
	2021-11-24 14:27:19.293	warn	State "web.0.info.connection" has no existing object, this might lead to an error in future versions
web.0
	2021-11-24 14:27:18.579	info	==>Connected system.user.admin from ::ffff:192.168.220.64
web.0
	2021-11-24 14:27:18.576	info	==>Connected system.user.admin from ::ffff:192.168.220.64
info.0
	2021-11-24 14:27:18.415	info	cpu Temp res = {"main":66.604,"cores":[],"max":66.604,"socket":[],"chipset":null}
web.0
	2021-11-24 14:27:18.250	info	http server listening on port 8082
web.0
	2021-11-24 14:27:18.212	info	socket.io server listening on port 8082
info.0
	2021-11-24 14:27:18.012	info	State value to set for "info.0.sysinfo.cpu.info.cache-l3" has to be type "number" but received type "string"
info.0
	2021-11-24 14:27:17.990	info	State value to set for "info.0.sysinfo.cpu.info.cache-l2" has to be type "number" but received type "string"
info.0
	2021-11-24 14:27:17.975	info	State value to set for "info.0.sysinfo.cpu.info.cache-l1i" has to be type "number" but received type "string"
info.0
	2021-11-24 14:27:17.961	info	State value to set for "info.0.sysinfo.cpu.info.cache-l1d" has to be type "number" but received type "string"
info.0
	2021-11-24 14:27:17.807	info	State value to set for "info.0.sysinfo.cpu.info.speed" has to be type "string" but received type "number"
web.0
	2021-11-24 14:27:17.443	info	starting. Version 3.4.9 in /opt/iobroker/node_modules/iobroker.web, node: v14.17.5, js-controller: 3.3.18
host.raspberrypi
	2021-11-24 14:27:16.173	info	instance system.adapter.shelly.0 started with pid 14008
info.0
	2021-11-24 14:27:16.123	info	Reading/updating systemdata.
info.0
	2021-11-24 14:27:15.872	info	starting. Version 1.9.8 in /opt/iobroker/node_modules/iobroker.info, node: v14.17.5, js-controller: 3.3.18
host.raspberrypi
	2021-11-24 14:27:12.149	info	instance system.adapter.web.0 started with pid 13985
javascript.0
	2021-11-24 14:27:11.636	info	script.js.Heizungen_soll_auf_Absenk_(abends): registered 0 subscriptions and 1 schedule
javascript.0
	2021-11-24 14:27:11.615	info	Start javascript script.js.Heizungen_soll_auf_Absenk_(abends)
javascript.0
	2021-11-24 14:27:11.609	info	script.js.ShellyTempkorrigieren: registered 0 subscriptions and 0 schedules
javascript.0
	2021-11-24 14:27:11.572	info	Start javascript script.js.ShellyTempkorrigieren
javascript.0
	2021-11-24 14:27:11.570	info	script.js.Temp2IoT: registered 0 subscriptions and 1 schedule
javascript.0
	2021-11-24 14:27:11.267	info	Start javascript script.js.Temp2IoT
discovery.0
	2021-11-24 14:27:10.870	info	starting. Version 2.7.3 in /opt/iobroker/node_modules/iobroker.discovery, node: v14.17.5, js-controller: 3.3.18
javascript.0
	2021-11-24 14:27:10.571	info	received all states
javascript.0
	2021-11-24 14:27:10.494	info	received all objects
admin.0
	2021-11-24 14:27:09.468	warn	Cannot parse "undefined"
admin.0
	2021-11-24 14:27:09.406	error	error
admin.0
	2021-11-24 14:27:09.402	warn	Cannot parse "undefined"
admin.0
	2021-11-24 14:27:09.209	warn	Cannot parse "undefined"
admin.0
	2021-11-24 14:27:08.303	error	error
admin.0
	2021-11-24 14:27:08.292	warn	Cannot parse "undefined"
host.raspberrypi
	2021-11-24 14:27:08.161	info	instance system.adapter.info.0 started with pid 13963
javascript.0
	2021-11-24 14:27:08.093	info	requesting all objects
javascript.0
	2021-11-24 14:27:08.089	info	requesting all states
admin.0
	2021-11-24 14:27:07.683	info	Use link "https://localhost:8081" to configure.
admin.0
	2021-11-24 14:27:07.680	info	https server listening on port 8081
javascript.0
	2021-11-24 14:27:07.657	info	starting. Version 5.2.13 in /opt/iobroker/node_modules/iobroker.javascript, node: v14.17.5, js-controller: 3.3.18
ping.0
	2021-11-24 14:27:04.631	info	starting. Version 1.5.0 in /opt/iobroker/node_modules/iobroker.ping, node: v14.17.5, js-controller: 3.3.18
admin.0
	2021-11-24 14:27:04.214	info	received all objects
host.raspberrypi
	2021-11-24 14:27:04.126	info	instance system.adapter.discovery.0 started with pid 13931
admin.0
	2021-11-24 14:27:01.284	info	requesting all objects
admin.0
	2021-11-24 14:27:01.282	info	requesting all states
admin.0
	2021-11-24 14:27:00.891	info	starting. Version 5.1.25 in /opt/iobroker/node_modules/iobroker.admin, node: v14.17.5, js-controller: 3.3.18
host.raspberrypi
	2021-11-24 14:27:00.083	info	instance system.adapter.ping.0 started with pid 13912
host.raspberrypi
	2021-11-24 14:26:56.931	info	instance system.adapter.javascript.0 started with pid 13901
host.raspberrypi
	2021-11-24 14:26:52.135	info	instance system.adapter.admin.0 started with pid 13894
host.raspberrypi
	2021-11-24 14:26:51.876	info	starting 12 instances
host.raspberrypi
	2021-11-24 14:26:51.758	info	17 instances found
host.raspberrypi
	2021-11-24 14:26:50.577	info	added notifications configuration of host
host.raspberrypi
	2021-11-24 14:26:50.521	info	connected to Objects and States
host.raspberrypi
	2021-11-24 14:26:49.459	info	ip addresses: 192.168.220.41 fe80::9f1d:34c9:26d:a669
host.raspberrypi
	2021-11-24 14:26:49.458	info	hostname: raspberrypi, node: v14.17.5
host.raspberrypi
	2021-11-24 14:26:49.457	info	Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
host.raspberrypi
	2021-11-24 14:26:49.446	info	iobroker.js-controller version 3.3.18 js-controller starting
host.raspberrypi
	2021-11-24 14:26:44.318	info	terminated
host.raspberrypi
	2021-11-24 14:26:44.217	info	All instances are stopped.
host.raspberrypi
	2021-11-24 14:26:44.217	info	instance system.adapter.backitup.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
host.raspberrypi
	2021-11-24 14:26:44.216	info	All instances are stopped.
host.raspberrypi
	2021-11-24 14:26:44.215	info	instance system.adapter.ble.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
host.raspberrypi
	2021-11-24 14:26:44.082	info	All instances are stopped.
host.raspberrypi
	2021-11-24 14:26:44.081	info	instance system.adapter.fritzdect.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
host.raspberrypi
	2021-11-24 14:26:44.080	info	All instances are stopped.
host.raspberrypi
	2021-11-24 14:26:44.079	info	instance system.adapter.influxdb.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
host.raspberrypi
	2021-11-24 14:26:44.076	info	instance system.adapter.shelly.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
host.raspberrypi
	2021-11-24 14:26:43.839	info	instance system.adapter.web.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
host.raspberrypi
	2021-11-24 14:26:43.838	info	instance system.adapter.info.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
host.raspberrypi
	2021-11-24 14:26:43.837	info	instance system.adapter.ping.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
host.raspberrypi
	2021-11-24 14:26:43.619	info	instance system.adapter.javascript.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
host.raspberrypi
	2021-11-24 14:26:43.615	info	instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
host.raspberrypi
	2021-11-24 14:26:42.784	info	instance system.adapter.iqontrol.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
host.raspberrypi
	2021-11-24 14:26:42.781	info	instance system.adapter.discovery.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
host.raspberrypi
	2021-11-24 14:26:42.595	info	stopInstance system.adapter.backitup.0 killing pid 10980
host.raspberrypi
	2021-11-24 14:26:42.595	info	stopInstance system.adapter.ble.0 killing pid 10647
host.raspberrypi
	2021-11-24 14:26:42.594	info	stopInstance system.adapter.fritzdect.0 killing pid 10487
host.raspberrypi
	2021-11-24 14:26:42.594	info	stopInstance system.adapter.shelly.0 killing pid 10293
host.raspberrypi
	2021-11-24 14:26:42.593	info	stopInstance system.adapter.web.0 killing pid 10235
host.raspberrypi
	2021-11-24 14:26:42.592	info	stopInstance system.adapter.info.0 killing pid 10209
host.raspberrypi
	2021-11-24 14:26:42.592	info	stopInstance system.adapter.ping.0 killing pid 10162
host.raspberrypi
	2021-11-24 14:26:42.591	info	stopInstance system.adapter.javascript.0 killing pid 10155
host.raspberrypi
	2021-11-24 14:26:42.589	info	stopInstance system.adapter.admin.0 killing pid 10140
ping.0
	2021-11-24 14:26:41.566	info	Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
influxdb.0
	2021-11-24 14:26:41.458	info	Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
host.raspberrypi
	2021-11-24 14:26:41.462	info	stopInstance system.adapter.backitup.0 send kill signal
host.raspberrypi
	2021-11-24 14:26:41.461	info	stopInstance system.adapter.ble.0 send kill signal
host.raspberrypi
	2021-11-24 14:26:41.460	info	stopInstance system.adapter.fritzdect.0 send kill signal
host.raspberrypi
	2021-11-24 14:26:41.455	info	stopInstance system.adapter.iqontrol.0 send kill signal
host.raspberrypi
	2021-11-24 14:26:41.454	info	stopInstance system.adapter.shelly.0 send kill signal
host.raspberrypi
	2021-11-24 14:26:41.454	info	stopInstance system.adapter.web.0 send kill signal
host.raspberrypi
	2021-11-24 14:26:41.453	info	stopInstance system.adapter.info.0 send kill signal
host.raspberrypi
	2021-11-24 14:26:41.452	info	stopInstance system.adapter.discovery.0 send kill signal
host.raspberrypi
	2021-11-24 14:26:41.451	info	stopInstance system.adapter.ping.0 send kill signal
host.raspberrypi
	2021-11-24 14:26:41.450	info	stopInstance system.adapter.javascript.0 send kill signal
host.raspberrypi
	2021-11-24 14:26:41.445	info	stopInstance system.adapter.admin.0 send kill signal

MOD_EDIT: Code in code-tags gesetzt!

===

=====
Woran kann das liegen=

wrod

@wrod Plötzlich geht alles wieder - ich kann nicht erkennen, warum.

Dennoch eine Frage: Inwiefern ist es möglich/sinnvoll, Objekte per Hand zu löschen, die man nicht unbedingt braucht - sprich: inwiefern läuft man Gefahr, damit die Funktion selbst zu stören, weil sie vielleicht intern gebraucht werden?

Thomas Braun

@wrod

Bei mir:
Objekte: 6053, Zustände: 5351

Und keine Aussetzer.
Objekte werden wieder hergestellt, wenn die Adapter/Instanzen neugestartet werden. Bringt dir also so oder so nix.

Community Forum

NEWS

Objects Datenbank

Support us

528

32.9k

83.0k

1.3m