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

[RoddiEF]

@Homoran sagte in Test Adapter Linux Control v1.x.x:

dein Problem müsste hier zu suchen sein

error: linux-control.0 (693) [getConnection] Could not establish a connection to 'RPi->HA' (192.168.0.11:22)!
2026-01-13 12:36

Das kam daher das ich gleichzeitig den RPi, der da auftaucht, geupdatet sowie ein Reboot gemacht habe (was ich immer mache nach Updates) und er deshalb nicht erreichbar war. Kann mir also nicht Vorstellen das es daran liegen sollte.

[Homoran]

@RoddiEF und was läuft jetzt nicht?
Alle anderen Einträge im log sehen doch gut aus.

[RoddiEF]

@Homoran sagte in Test Adapter Linux Control v1.x.x:

@RoddiEF und was läuft jetzt nicht?
Alle anderen Einträge im log sehen doch gut aus.

Im Kern des ganzen ging es darum das der Adapter einen Fehler ins Log schreibt wenn er gestartet wird.
Daten liefert er ja, aber jeden Morgen (nach dem Backup vom ioBroker) bringt er den Fehler und das macht mich kirre im Kopf.

Edit: bild hinzugefügt

[Homoran]

@RoddiEF sagte in Test Adapter Linux Control v1.x.x:

das der Adapter einen Fehler ins Log schreibt wenn er gestartet wird.

wenn das alles ist, kannst du das ignorieren

[1Topf]

Hat zu meinem Problem niemand eine Idee? 😕

https://forum.iobroker.net/post/1316457

sagte in Test Adapter Linux Control v1.x.x:

Ich hab da auch mal ne Frage. Ich hab jetzt einen Raspi3 eingebunden, auf welchem 2 Kameras (Garten u. Hof) auf einem USB-Stick Bilder ablegen. Beide Ordner enthalten aktuell jeweils >20GB Daten. Wieso wird das nicht korrekt dargestellt? Hat da jemand eine Idee? Die Anzahl der Dateien hingegen stimmt.

[crunchip]

@1Topf sagte in Test Adapter Linux Control v1.x.x:

auf einem USB-Stick Bilder ablegen. Beide Ordner enthalten aktuell jeweils >20GB Daten

und wie sind die jeweils ins System eingebunden?

[1Topf]

@crunchip sagte in Test Adapter Linux Control v1.x.x:

und wie sind die jeweils ins System eingebunden?

Tja, mal kurz überlegen (is schon ne Weile her ...).
Auf dem Raspi3 läuft Debian GNU/Linux 12 (bookworm), raspios ohne GUI. Die Bilder werden von den Kameras per FTP auf den Raspi geschickt.
Der Stick ist normal 🤷‍♂️ eingebunden:

Dateisystem Größe Benutzt Verf. Verw% Eingehängt auf
/dev/sda1 __ 58G __ 50G _ 8,3G _ 86% _ /media/usbstick

Die beiden Ordner liegen unter /media/usbstick/Garten bzw. .../Hof.

Oder welche Info genau hättest Du gern?

[D3ltoroxp]

@crunchip sagte in Test Adapter Linux Control v1.x.x:

@D3ltoroxp die Frage ist eher, was da genau läuft auf deinen Systemen. Hat ja nichts mit den Befehlen zu tun.

Also das ist einmal nen LXC mit Mainsail / Klipper drauf und einmal ein PVE Host. Die beiden habe ich angelegt. Daraus erstellt er dann die DP's. Das ding lief auch schon mal. Ich befürchte seit irgendeinem Update läuft das bei mir nicht mehr richtig.

Wenn ich ihn starte dreht die Log komplett durch.

host.iobroker
2026-01-13 21:50:47.913	error	instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION)

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:105:5)

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[9]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27)

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[9]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15)

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[9]: Error: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[9]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[8]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[8]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[8]: ReplyError: Error The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[7]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[6]: at processTicksAndRejections (node:internal/process/task_queues:105:5)

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[6]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27)

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[6]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15)

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[6]: Error: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern

host.iobroker
2026-01-13 21:50:47.913	error	Caught by controller[5]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[4]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[4]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[4]: ReplyError: Error The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[3]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[2]: at processTicksAndRejections (node:internal/process/task_queues:105:5)

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[2]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27)

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[2]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15)

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[2]: Error: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[2]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[1]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[1]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[1]: ReplyError: Error The pattern "linux-control.0.Mainsail.services.●.restart" is not a valid ID pattern

host.iobroker
2026-01-13 21:50:47.912	error	Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:

linux-control.0
2026-01-13 21:50:47.810	info	terminating

linux-control.0
2026-01-13 21:50:47.810	info	terminating

linux-control.0
2026-01-13 21:50:47.782	warn	Used invalid characters: linux-control.0.Mainsail.services.●.stop changed to linux-control.0.Mainsail.services._.stop

linux-control.0
2026-01-13 21:50:47.781	error	Error: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27) at processTicksAndRejections (node:internal/process/task_queues:105:5)

linux-control.0
2026-01-13 21:50:47.780	error	unhandled promise rejection: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern

linux-control.0
2026-01-13 21:50:47.780	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

linux-control.0
2026-01-13 21:50:47.779	warn	Used invalid characters: linux-control.0.Mainsail.services.●.start changed to linux-control.0.Mainsail.services._.start

linux-control.0
2026-01-13 21:50:47.778	warn	Used invalid characters: linux-control.0.Mainsail.services.●.restart changed to linux-control.0.Mainsail.services._.restart

linux-control.0
2026-01-13 21:50:47.736	warn	State "linux-control.0.Mainsail.services.●.description" has no existing object, this might lead to an error in future versions

linux-control.0
2026-01-13 21:50:47.734	warn	Used invalid characters: linux-control.0.Mainsail.services.●.description changed to linux-control.0.Mainsail.services._.description

linux-control.0
2026-01-13 21:50:47.687	warn	State "linux-control.0.Mainsail.services.●.running" has no existing object, this might lead to an error in future versions

linux-control.0
2026-01-13 21:50:47.686	warn	Used invalid characters: linux-control.0.Mainsail.services.●.running changed to linux-control.0.Mainsail.services._.running

linux-control.0
2026-01-13 21:50:47.642	warn	State "linux-control.0.Mainsail.services.●.active" has no existing object, this might lead to an error in future versions

linux-control.0
2026-01-13 21:50:47.638	warn	Used invalid characters: linux-control.0.Mainsail.services.●.active changed to linux-control.0.Mainsail.services._.active

linux-control.0
2026-01-13 21:50:47.593	warn	State "linux-control.0.Mainsail.services.●.load" has no existing object, this might lead to an error in future versions

linux-control.0
2026-01-13 21:50:47.591	warn	Used invalid characters: linux-control.0.Mainsail.services.●.load changed to linux-control.0.Mainsail.services._.load

linux-control.0
2026-01-13 21:50:47.589	error	ReplyError: Error The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)

linux-control.0
2026-01-13 21:50:47.589	error	unhandled promise rejection: Error The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern

linux-control.0
2026-01-13 21:50:47.589	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

host.iobroker
2026-01-13 21:50:47.588	warn	host.iobroker-Server States 127.0.0.1:44596 Error from InMemDB: Error: The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:323:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:240:14) at RedisHandler.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:380:26) at RedisHandler.emit (node:events:519:28) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:485:21) at process.callbackTrampoline (node:internal/async_hooks:130:17)

linux-control.0
2026-01-13 21:50:47.587	warn	Used invalid characters: linux-control.0.Mainsail.services.●.stop changed to linux-control.0.Mainsail.services._.stop

linux-control.0
2026-01-13 21:50:47.585	error	Error: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27) at processTicksAndRejections (node:internal/process/task_queues:105:5)

linux-control.0
2026-01-13 21:50:47.584	error	unhandled promise rejection: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern

linux-control.0
2026-01-13 21:50:47.584	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

linux-control.0
2026-01-13 21:50:47.583	warn	Used invalid characters: linux-control.0.Mainsail.services.●.start changed to linux-control.0.Mainsail.services._.start

linux-control.0
2026-01-13 21:50:47.582	warn	Used invalid characters: linux-control.0.Mainsail.services.●.restart changed to linux-control.0.Mainsail.services._.restart

linux-control.0
2026-01-13 21:50:47.539	warn	State "linux-control.0.Mainsail.services.●.description" has no existing object, this might lead to an error in future versions

linux-control.0
2026-01-13 21:50:47.538	warn	Used invalid characters: linux-control.0.Mainsail.services.●.description changed to linux-control.0.Mainsail.services._.description

linux-control.0
2026-01-13 21:50:47.492	warn	State "linux-control.0.Mainsail.services.●.running" has no existing object, this might lead to an error in future versions

linux-control.0
2026-01-13 21:50:47.490	warn	Used invalid characters: linux-control.0.Mainsail.services.●.running changed to linux-control.0.Mainsail.services._.running

linux-control.0
2026-01-13 21:50:47.443	warn	State "linux-control.0.Mainsail.services.●.active" has no existing object, this might lead to an error in future versions

linux-control.0
2026-01-13 21:50:47.442	warn	Used invalid characters: linux-control.0.Mainsail.services.●.active changed to linux-control.0.Mainsail.services._.active

linux-control.0
2026-01-13 21:50:47.399	warn	State "linux-control.0.Mainsail.services.●.load" has no existing object, this might lead to an error in future versions

linux-control.0
2026-01-13 21:50:47.398	warn	Used invalid characters: linux-control.0.Mainsail.services.●.load changed to linux-control.0.Mainsail.services._.load

linux-control.0
2026-01-13 21:50:47.396	error	ReplyError: Error The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12) at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)

linux-control.0
2026-01-13 21:50:47.396	error	unhandled promise rejection: Error The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern

linux-control.0
2026-01-13 21:50:47.395	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

host.iobroker
2026-01-13 21:50:47.395	warn	host.iobroker-Server States 127.0.0.1:44596 Error from InMemDB: Error: The pattern "linux-control.0.Mainsail.services.●.stop" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:323:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:240:14) at RedisHandler.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-states-jsonl/src/lib/states/statesInMemServerRedis.js:380:26) at RedisHandler.emit (node:events:519:28) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:485:21) at process.callbackTrampoline (node:internal/async_hooks:130:17)

linux-control.0
2026-01-13 21:50:47.390	warn	Used invalid characters: linux-control.0.Mainsail.services.●.stop changed to linux-control.0.Mainsail.services._.stop

linux-control.0
2026-01-13 21:50:47.389	error	Error: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2507:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1124:27) at processTicksAndRejections (node:internal/process/task_queues:105:5)

linux-control.0
2026-01-13 21:50:47.338	error	unhandled promise rejection: The pattern "io.linux-control.0.Mainsail.services.●.start" is not a valid ID pattern

linux-control.0
2026-01-13 21:50:47.338	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

linux-control.0
2026-01-13 21:50:47.310	warn	Used invalid characters: linux-control.0.Mainsail.services.●.start changed to linux-control.0.Mainsail.services._.start

linux-control.0
2026-01-13 21:50:47.309	warn	Terminated (UNCAUGHT_EXCEPTION): Without reason

Das ist aktiv.

[crunchip]

@D3ltoroxp sagte in Test Adapter Linux Control v1.x.x:

befürchte seit irgendeinem Update

https://github.com/mainsail-crew/MainsailOS/releases/tag/2.2.2
Musst du halt mal vergleichen

@D3ltoroxp sagte in Test Adapter Linux Control v1.x.x:

Das ist aktiv

Vllt mal die Service ausschließen für deinen PI

[D3ltoroxp]

@crunchip Mit dem Update meinte ich vom Linux Control Adapter. Hab jetzt mal alles deaktiviert, bis auf den oberen Block Infos zum Host. Die Log ist recht sauber und ruhig. Funktionieren dann einfach die anderen Optionen nicht am System. Wie gesagt, beides mal Linux was da werkelt, einmal Proxmox Host und einmal nen LXC mit Mainsail.