Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[mrMuppet]

Systemdata	Bitte Ausfüllen
Hardwaresystem:	Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz (4 cores), FreeNAS. FreeBSD.
Arbeitsspeicher:	32GB
Festplattenart:	HDD
Betriebssystem:	FreeBSD 11.2
Node-Version:	v10.16.3
Nodejs-Version:	v10.16.3
NPM-Version:	6.11.3
Installationsart:	Skript
Image genutzt:	Nein

Ich hab es endlich geschafft den Skript auch auf meinem FreeNAS-System ans laufen zu bekommen. Leider macht anscheinend der "Systeminformation"-Adapter anscheinend Probleme:

host.iobroker-v3	2019-10-29 01:05:11.099	error	instance system.adapter.info.0 terminated with code 0 (OK)
host.iobroker-v3	2019-10-29 01:05:11.099	error	Caught by controller[1]: at Pipe._handle.close (net.js:606:12)
host.iobroker-v3	2019-10-29 01:05:11.099	error	Caught by controller[1]: at Socket.emit (events.js:198:13)
host.iobroker-v3	2019-10-29 01:05:11.099	error	Caught by controller[1]: at Socket.stream.socket.on (internal/child_process.js:389:11)
host.iobroker-v3	2019-10-29 01:05:11.099	error	Caught by controller[1]: at maybeClose (internal/child_process.js:982:16)
host.iobroker-v3	2019-10-29 01:05:11.099	error	Caught by controller[1]: at ChildProcess.emit (events.js:198:13)
host.iobroker-v3	2019-10-29 01:05:11.099	error	Caught by controller[1]: at ChildProcess.exithandler (child_process.js:285:7)
host.iobroker-v3	2019-10-29 01:05:11.099	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.info/node_modules/systeminformation/lib/cpu.js:651:19
host.iobroker-v3	2019-10-29 01:05:11.099	error	Caught by controller[1]: at Array.forEach (<anonymous>)
host.iobroker-v3	2019-10-29 01:05:11.099	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.info/node_modules/systeminformation/lib/cpu.js:654:50
host.iobroker-v3	2019-10-29 01:05:11.099	error	Caught by controller[1]: TypeError: Cannot read property 'replace' of undefined
host.iobroker-v3	2019-10-29 01:05:11.098	error	Caught by controller[0]: at Pipe._handle.close (net.js:606:12)
host.iobroker-v3	2019-10-29 01:05:11.098	error	Caught by controller[0]: at Socket.emit (events.js:198:13)
host.iobroker-v3	2019-10-29 01:05:11.098	error	Caught by controller[0]: at Socket.stream.socket.on (internal/child_process.js:389:11)
host.iobroker-v3	2019-10-29 01:05:11.098	error	Caught by controller[0]: at maybeClose (internal/child_process.js:982:16)
host.iobroker-v3	2019-10-29 01:05:11.098	error	Caught by controller[0]: at ChildProcess.emit (events.js:198:13)
host.iobroker-v3	2019-10-29 01:05:11.098	error	Caught by controller[0]: at ChildProcess.exithandler (child_process.js:285:7)
host.iobroker-v3	2019-10-29 01:05:11.098	error	Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.info/node_modules/systeminformation/lib/cpu.js:353:31
host.iobroker-v3	2019-10-29 01:05:11.098	error	Caught by controller[0]: TypeError: Cannot read property 'split' of undefined
host.iobroker-v3	2019-10-29 01:05:10.007	info	instance system.adapter.info.0 started with pid 55673
discovery.0	2019-10-29 01:05:06.314	info	starting. Version 1.3.0 in /opt/iobroker/node_modules/iobroker.discovery, node: v10.16.3

Interessanterweise funktioniert die Darstellung der Info-Seite über die IOBroker-Oberfläche
(links Taste Info) problemlos. Dort wird auch der CPU erkannt:

iobroker-v3
Betriebssystem
freebsd
Architektur
x64
CPUs
4
Geschwindigkeit
3392 MHz
Modell
Intel(R) Core(TM) i3-4130 CPU @ 3.40GHz
RAM
31.92 GB

Aber auch unter Instanzen wird der Adapter immer mit rot angezeigt.