Skip to content
  • Home
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo

Community Forum

  1. ioBroker Community Home
  2. Deutsch
  3. Tester
  4. Test Adapter Linux Control v1.x.x

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.2k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.9k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.2k

Test Adapter Linux Control v1.x.x

Geplant Angeheftet Gesperrt Verschoben Tester
adaptercontrolhardwarelinuxsteuern
675 Beiträge 70 Kommentatoren 171.7k Aufrufe 64 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • L Labersack

    @deta
    Wenn du in den Adaptereinstellungen unter Datenpunkte -> Control -> Shutdown aktivierst, hast du einen Datenpunkt, den du in einem Script/Flow verwenden kannst.

    D Offline
    D Offline
    deta
    Most Active
    schrieb am zuletzt editiert von
    #659

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

    @deta
    Wenn du in den Adaptereinstellungen unter Datenpunkte -> Control -> Shutdown aktivierst, hast du einen Datenpunkt, den du in einem Script/Flow verwenden kannst.

    Dachte ich auch aber nix
    646984a8-47b6-4d1d-9e62-603f271e6a78-image.png

    7baa30a8-b084-4aa2-80b8-c1e5194177ff-image.png

    f1465863-574b-4b57-b4b7-ef8373126818-image.png

    skvarelS 1 Antwort Letzte Antwort
    0
    • D deta

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

      @deta
      Wenn du in den Adaptereinstellungen unter Datenpunkte -> Control -> Shutdown aktivierst, hast du einen Datenpunkt, den du in einem Script/Flow verwenden kannst.

      Dachte ich auch aber nix
      646984a8-47b6-4d1d-9e62-603f271e6a78-image.png

      7baa30a8-b084-4aa2-80b8-c1e5194177ff-image.png

      f1465863-574b-4b57-b4b7-ef8373126818-image.png

      skvarelS Offline
      skvarelS Offline
      skvarel
      Developer
      schrieb am zuletzt editiert von
      #660

      @deta .. das ist merkwürdig. Bei dir fehlt das 'Control' Verzeichnis innerhalb von 'detlef-computer'.

      Bei mir sieht es so aus:

      3b31b890-2344-49b9-9543-afd0c25193aa-image.png

      f92480cd-06f4-483f-b29c-fba766b8259c-image.png

      1c598f45-69e8-4390-a13a-a3808731d3c4-image.png

      #TeamInventwo
      • vis-inventwo & vis-2-widgets-inventwo
      • vis-icontwo & vis-2-widgets-icontwo

      1 Antwort Letzte Antwort
      0
      • skvarelS Offline
        skvarelS Offline
        skvarel
        Developer
        schrieb am zuletzt editiert von skvarel
        #661

        Ich nutze allerdings die Version v1.1.6

        Ich kann mir aber nicht vorstellen, dass es daran liegt.

        8e8efb20-e6d0-451b-a7fd-756fa526e128-image.png

        #TeamInventwo
        • vis-inventwo & vis-2-widgets-inventwo
        • vis-icontwo & vis-2-widgets-icontwo

        1 Antwort Letzte Antwort
        0
        • D Offline
          D Offline
          deta
          Most Active
          schrieb am zuletzt editiert von
          #662

          Hab es auch jetzt mit der 1.1.6 probiert. Genau das selbe.
          Ich habe auch mal den root User eingetragen, das selbe..

          Keine anderen Daten...

          skvarelS 1 Antwort Letzte Antwort
          0
          • D deta

            Hab es auch jetzt mit der 1.1.6 probiert. Genau das selbe.
            Ich habe auch mal den root User eingetragen, das selbe..

            Keine anderen Daten...

            skvarelS Offline
            skvarelS Offline
            skvarel
            Developer
            schrieb am zuletzt editiert von
            #663

            @deta .. du hast aber Zugang über ssh (z.B. via Putty) zu dem Rechner?

            #TeamInventwo
            • vis-inventwo & vis-2-widgets-inventwo
            • vis-icontwo & vis-2-widgets-icontwo

            1 Antwort Letzte Antwort
            0
            • D Offline
              D Offline
              deta
              Most Active
              schrieb am zuletzt editiert von
              #664

              Fehler gefunden....
              Ich hatte noch keinen openssh Server auf dem Desktop installiert :disappointed:

              Jetzt geht es.
              Danke

              D 1 Antwort Letzte Antwort
              1
              • D deta

                Fehler gefunden....
                Ich hatte noch keinen openssh Server auf dem Desktop installiert :disappointed:

                Jetzt geht es.
                Danke

                D Offline
                D Offline
                denjo
                schrieb am zuletzt editiert von
                #665

                ich habe auch probleme mit dem Adapter

                über Putty kann ich ohne probleme zugreifen

                Mein IObroker ist bei allem auf aktuellen stand

                Node.js: v20.19.4
                JS Controller 7.0.6
                Adapter. 1.1.5

                
                host.iOBroker
                2025-08-13 20:44:20.577	info	"system.adapter.linux-control.0" disabled
                
                linux-control.0
                2025-08-13 20:44:06.264	error	Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                
                host.iOBroker
                2025-08-13 20:44:05.094	info	instance system.adapter.linux-control.0 in version "1.1.5" started with pid 3987
                
                host.iOBroker
                2025-08-13 20:43:34.740	info	Restart adapter system.adapter.linux-control.0 because enabled
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[14]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[14]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[14]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[14]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[14]: 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
                2025-08-13 20:43:34.740	error	Caught by controller[13]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[13]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[13]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[13]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[13]: 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
                2025-08-13 20:43:34.740	error	Caught by controller[12]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[12]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[12]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[12]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[12]: 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
                2025-08-13 20:43:34.740	error	Caught by controller[11]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[11]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[11]: ReplyError: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[11]: 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
                2025-08-13 20:43:34.740	error	Caught by controller[10]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[10]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[10]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[10]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[10]: 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
                2025-08-13 20:43:34.740	error	Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[9]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[9]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[9]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.740	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
                2025-08-13 20:43:34.740	error	Caught by controller[8]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[8]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[8]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[8]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[8]: 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
                2025-08-13 20:43:34.740	error	Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[7]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[7]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[7]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.740	error	Caught by controller[6]: 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
                2025-08-13 20:43:34.740	error	Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[5]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[5]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[5]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.739	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
                2025-08-13 20:43:34.739	error	Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[4]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[4]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[4]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[4]: 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
                2025-08-13 20:43:34.739	error	Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[3]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[3]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[3]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.739	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
                2025-08-13 20:43:34.739	error	Caught by controller[2]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[2]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[2]: ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.739	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
                2025-08-13 20:43:34.739	error	Caught by controller[1]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[1]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                
                host.iOBroker
                2025-08-13 20:43:34.739	error	Caught by controller[1]: ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                host.iOBroker
                2025-08-13 20:43:34.739	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
                2025-08-13 20:43:34.634	error	[needrestart] hyperion (192.168.178.67:22): error: Cannot find view "system", stack: Error: Cannot find view "system" at ObjectsInRedisClient._getObjectView (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:4272:19) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:4346:33)
                
                linux-control.0
                2025-08-13 20:43:34.595	error	Cannot find view "system" for search "state" : Connection is closed.
                
                linux-control.0
                2025-08-13 20:43:34.593	error	[servicesInfo] hyperion (192.168.178.67:22): error: DB closed, stack: Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:639:26) at Socket.emit (node:events:524:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:343:12)
                
                linux-control.0
                2025-08-13 20:43:34.554	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.554	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2025-08-13 20:43:34.554	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.553	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
                2025-08-13 20:43:34.515	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.515	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2025-08-13 20:43:34.515	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.514	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
                2025-08-13 20:43:34.480	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.480	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2025-08-13 20:43:34.479	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.479	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
                2025-08-13 20:43:34.464	error	Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.463	error	ReplyError: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" 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
                2025-08-13 20:43:34.463	error	unhandled promise rejection: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.463	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-Server
                2025-08-13 20:43:34.462	warn	States 127.0.0.1:45704 Error from InMemDB: Error: The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:324:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:242: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:524:28) at RedisHandler.emit (node:domain:489:12) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:483:21)
                
                linux-control.0
                2025-08-13 20:43:34.436	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.436	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2025-08-13 20:43:34.435	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.435	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
                2025-08-13 20:43:34.366	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.366	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2025-08-13 20:43:34.365	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.365	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
                2025-08-13 20:43:34.351	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.351	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2025-08-13 20:43:34.351	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.350	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
                2025-08-13 20:43:34.288	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.288	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2025-08-13 20:43:34.287	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.287	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
                2025-08-13 20:43:34.256	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.256	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2025-08-13 20:43:34.255	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.255	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
                2025-08-13 20:43:34.215	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.215	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2025-08-13 20:43:34.215	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.215	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
                2025-08-13 20:43:34.194	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.194	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                
                linux-control.0
                2025-08-13 20:43:34.145	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.145	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
                2025-08-13 20:43:34.138	error	ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" 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
                2025-08-13 20:43:34.138	error	unhandled promise rejection: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.138	error	Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                
                linux-control.0
                2025-08-13 20:43:34.137	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().
                
                crunchipC 1 Antwort Letzte Antwort
                0
                • D denjo

                  ich habe auch probleme mit dem Adapter

                  über Putty kann ich ohne probleme zugreifen

                  Mein IObroker ist bei allem auf aktuellen stand

                  Node.js: v20.19.4
                  JS Controller 7.0.6
                  Adapter. 1.1.5

                  
                  host.iOBroker
                  2025-08-13 20:44:20.577	info	"system.adapter.linux-control.0" disabled
                  
                  linux-control.0
                  2025-08-13 20:44:06.264	error	Object linux-control.0.command.host is invalid: obj.common.states has an invalid type! Expected "object", received "string"
                  
                  host.iOBroker
                  2025-08-13 20:44:05.094	info	instance system.adapter.linux-control.0 in version "1.1.5" started with pid 3987
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	info	Restart adapter system.adapter.linux-control.0 because enabled
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	instance system.adapter.linux-control.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[14]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[14]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[14]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[14]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[14]: 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
                  2025-08-13 20:43:34.740	error	Caught by controller[13]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[13]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[13]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[13]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[13]: 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
                  2025-08-13 20:43:34.740	error	Caught by controller[12]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[12]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[12]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[12]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[12]: 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
                  2025-08-13 20:43:34.740	error	Caught by controller[11]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[11]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[11]: ReplyError: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[11]: 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
                  2025-08-13 20:43:34.740	error	Caught by controller[10]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[10]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[10]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[10]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[10]: 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
                  2025-08-13 20:43:34.740	error	Caught by controller[9]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[9]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[9]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[9]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	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
                  2025-08-13 20:43:34.740	error	Caught by controller[8]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[8]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[8]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[8]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[8]: 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
                  2025-08-13 20:43:34.740	error	Caught by controller[7]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[7]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[7]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[7]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.740	error	Caught by controller[6]: 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
                  2025-08-13 20:43:34.740	error	Caught by controller[5]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[5]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[5]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[5]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	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
                  2025-08-13 20:43:34.739	error	Caught by controller[4]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[4]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[4]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[4]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[4]: 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
                  2025-08-13 20:43:34.739	error	Caught by controller[3]: at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[3]: at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[3]: at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[3]: Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	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
                  2025-08-13 20:43:34.739	error	Caught by controller[2]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[2]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[2]: ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	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
                  2025-08-13 20:43:34.739	error	Caught by controller[1]: at parseType (/opt/iobroker/node_modules/redis-parser/lib/parser.js:302:14)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[1]: at parseError (/opt/iobroker/node_modules/redis-parser/lib/parser.js:179:12)
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	error	Caught by controller[1]: ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  host.iOBroker
                  2025-08-13 20:43:34.739	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
                  2025-08-13 20:43:34.634	error	[needrestart] hyperion (192.168.178.67:22): error: Cannot find view "system", stack: Error: Cannot find view "system" at ObjectsInRedisClient._getObjectView (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:4272:19) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/src/lib/objects/objectsInRedisClient.ts:4346:33)
                  
                  linux-control.0
                  2025-08-13 20:43:34.595	error	Cannot find view "system" for search "state" : Connection is closed.
                  
                  linux-control.0
                  2025-08-13 20:43:34.593	error	[servicesInfo] hyperion (192.168.178.67:22): error: DB closed, stack: Error: DB closed at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:639:26) at Socket.emit (node:events:524:28) at Socket.emit (node:domain:489:12) at TCP.<anonymous> (node:net:343:12)
                  
                  linux-control.0
                  2025-08-13 20:43:34.554	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.554	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  linux-control.0
                  2025-08-13 20:43:34.554	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.553	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
                  2025-08-13 20:43:34.515	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.515	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  linux-control.0
                  2025-08-13 20:43:34.515	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.514	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
                  2025-08-13 20:43:34.480	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.480	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  linux-control.0
                  2025-08-13 20:43:34.479	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.479	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
                  2025-08-13 20:43:34.464	error	Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.463	error	ReplyError: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" 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
                  2025-08-13 20:43:34.463	error	unhandled promise rejection: Error The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.463	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-Server
                  2025-08-13 20:43:34.462	warn	States 127.0.0.1:45704 Error from InMemDB: Error: The pattern "linux-control.0.hyperion.services.systemd-fsck@dev-disk-by\x2dpartuuid-2f6f3587\x2d01.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StatesInMemoryServer.handleSubscribe (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/inMemFileDB.ts:324:59) at StatesInMemoryServer._subscribeForClient (file:///opt/iobroker/node_modules/@iobroker/db-states-file/src/lib/states/statesInMemFileDB.js:242: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:524:28) at RedisHandler.emit (node:domain:489:12) at Immediate._onImmediate (file:///opt/iobroker/node_modules/@iobroker/db-base/src/lib/redisHandler.ts:210:37) at processImmediate (node:internal/timers:483:21)
                  
                  linux-control.0
                  2025-08-13 20:43:34.436	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.436	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  linux-control.0
                  2025-08-13 20:43:34.435	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.435	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
                  2025-08-13 20:43:34.366	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.366	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  linux-control.0
                  2025-08-13 20:43:34.365	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.365	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
                  2025-08-13 20:43:34.351	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.351	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  linux-control.0
                  2025-08-13 20:43:34.351	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.350	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
                  2025-08-13 20:43:34.288	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.288	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  linux-control.0
                  2025-08-13 20:43:34.287	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.287	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
                  2025-08-13 20:43:34.256	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.256	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  linux-control.0
                  2025-08-13 20:43:34.255	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.255	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
                  2025-08-13 20:43:34.215	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.215	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  linux-control.0
                  2025-08-13 20:43:34.215	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.215	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
                  2025-08-13 20:43:34.194	error	The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.194	error	Error: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern at Module.pattern2RegEx (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/src/lib/common/tools.ts:2490:15) at StateRedisClient.subscribe (file:///opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:1127:27) at processTicksAndRejections (node:internal/process/task_queues:95:5)
                  
                  linux-control.0
                  2025-08-13 20:43:34.145	error	unhandled promise rejection: The pattern "io.linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.145	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
                  2025-08-13 20:43:34.138	error	ReplyError: Error The pattern "linux-control.0.hyperion.services.●.restart" 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
                  2025-08-13 20:43:34.138	error	unhandled promise rejection: Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.138	error	Error The pattern "linux-control.0.hyperion.services.●.restart" is not a valid ID pattern
                  
                  linux-control.0
                  2025-08-13 20:43:34.137	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().
                  
                  crunchipC Abwesend
                  crunchipC Abwesend
                  crunchip
                  Forum Testing Most Active
                  schrieb am zuletzt editiert von
                  #666

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

                  linux-control.0.hyperion.services.●.restart

                  Ist das Problem

                  umgestiegen von Proxmox auf Unraid

                  1 Antwort Letzte Antwort
                  0
                  • F Offline
                    F Offline
                    flispy
                    schrieb am zuletzt editiert von
                    #667

                    Moin,
                    leider bekomme ich neuerdings nur noch die Meldungen: "Host seems not to be online".
                    Ich habe den Adapter in Version 1.1.6 installiert.

                    Ping vom anderen Rechner bzw. Server auf den Host gehen ohne Probleme. Auch die ssh Verbindung von der iobroker shell zum betreffenden Host gehen ohne Probleme.

                    iputils-ping habe ich neu installiert.

                    Hat jemand eine Idee woran es liegen könnte?

                    F 1 Antwort Letzte Antwort
                    1
                    • F flispy

                      Moin,
                      leider bekomme ich neuerdings nur noch die Meldungen: "Host seems not to be online".
                      Ich habe den Adapter in Version 1.1.6 installiert.

                      Ping vom anderen Rechner bzw. Server auf den Host gehen ohne Probleme. Auch die ssh Verbindung von der iobroker shell zum betreffenden Host gehen ohne Probleme.

                      iputils-ping habe ich neu installiert.

                      Hat jemand eine Idee woran es liegen könnte?

                      F Offline
                      F Offline
                      flispy
                      schrieb am zuletzt editiert von
                      #668

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

                      Moin,
                      leider bekomme ich neuerdings nur noch die Meldungen: "Host seems not to be online".
                      Ich habe den Adapter in Version 1.1.6 installiert.

                      Ping vom anderen Rechner bzw. Server auf den Host gehen ohne Probleme. Auch die ssh Verbindung von der iobroker shell zum betreffenden Host gehen ohne Probleme.

                      iputils-ping habe ich neu installiert.

                      Hat jemand eine Idee woran es liegen könnte?

                      hab es lösen können. Ich musste folgendes ausführen
                      sudo setcap cap_net_raw+p /usr/bin/ping

                      M 1 Antwort Letzte Antwort
                      1
                      • F flispy

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

                        Moin,
                        leider bekomme ich neuerdings nur noch die Meldungen: "Host seems not to be online".
                        Ich habe den Adapter in Version 1.1.6 installiert.

                        Ping vom anderen Rechner bzw. Server auf den Host gehen ohne Probleme. Auch die ssh Verbindung von der iobroker shell zum betreffenden Host gehen ohne Probleme.

                        iputils-ping habe ich neu installiert.

                        Hat jemand eine Idee woran es liegen könnte?

                        hab es lösen können. Ich musste folgendes ausführen
                        sudo setcap cap_net_raw+p /usr/bin/ping

                        M Online
                        M Online
                        mading
                        schrieb am zuletzt editiert von
                        #669

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

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

                        Moin,
                        leider bekomme ich neuerdings nur noch die Meldungen: "Host seems not to be online".
                        Ich habe den Adapter in Version 1.1.6 installiert.

                        Ping vom anderen Rechner bzw. Server auf den Host gehen ohne Probleme. Auch die ssh Verbindung von der iobroker shell zum betreffenden Host gehen ohne Probleme.

                        iputils-ping habe ich neu installiert.

                        Hat jemand eine Idee woran es liegen könnte?

                        hab es lösen können. Ich musste folgendes ausführen
                        sudo setcap cap_net_raw+p /usr/bin/ping

                        Geht wieder, habe den Befehl auf dem iobroker ausgeführt. Danke!

                        1 Antwort Letzte Antwort
                        0
                        • F Offline
                          F Offline
                          Fichte
                          schrieb am zuletzt editiert von Fichte
                          #670

                          Hallo zusammen

                          Ich hab heut Trixie (Debian 13) unter Proxmox getestet und da erscheint diese Meldung

                          [getConnection] Host 'Name' (IP:Port) seems not to be online
                          

                          "Ping wird nicht mehr mit erhöhten Privilegien ausgeführt"
                          Quelle hier

                          Heisst unter einem anderen User außer root geht der befehl "Ping" nicht mehr.
                          Wird aber vom Adapter benötigt um zu schauem ob er online ist.

                          Abhilfe steht im Link und ist relativ einfach:

                          1. Anmelden
                          2. sudo nano /usr/lib/sysctl.d/50-default.conf
                          3. nach "net.ipv4.ping_group_range = .........." suchen und gegen "net.ipv4.ping_group_range = 1 1000" ersetzen.
                          4. Speichern und Neustarten

                          Liebe Grüße

                          NashraN wendy2702W M 3 Antworten Letzte Antwort
                          1
                          • F Fichte

                            Hallo zusammen

                            Ich hab heut Trixie (Debian 13) unter Proxmox getestet und da erscheint diese Meldung

                            [getConnection] Host 'Name' (IP:Port) seems not to be online
                            

                            "Ping wird nicht mehr mit erhöhten Privilegien ausgeführt"
                            Quelle hier

                            Heisst unter einem anderen User außer root geht der befehl "Ping" nicht mehr.
                            Wird aber vom Adapter benötigt um zu schauem ob er online ist.

                            Abhilfe steht im Link und ist relativ einfach:

                            1. Anmelden
                            2. sudo nano /usr/lib/sysctl.d/50-default.conf
                            3. nach "net.ipv4.ping_group_range = .........." suchen und gegen "net.ipv4.ping_group_range = 1 1000" ersetzen.
                            4. Speichern und Neustarten

                            Liebe Grüße

                            NashraN Offline
                            NashraN Offline
                            Nashra
                            Most Active Forum Testing
                            schrieb am zuletzt editiert von
                            #671

                            @fichte
                            danke für den Hinweis, Ping arbeitet wieder

                            Gruß Ralf
                            Mir egal, wer Dein Vater ist! Wenn ich hier angel, wird nicht übers Wasser gelaufen!!

                            Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                            1 Antwort Letzte Antwort
                            0
                            • F Fichte

                              Hallo zusammen

                              Ich hab heut Trixie (Debian 13) unter Proxmox getestet und da erscheint diese Meldung

                              [getConnection] Host 'Name' (IP:Port) seems not to be online
                              

                              "Ping wird nicht mehr mit erhöhten Privilegien ausgeführt"
                              Quelle hier

                              Heisst unter einem anderen User außer root geht der befehl "Ping" nicht mehr.
                              Wird aber vom Adapter benötigt um zu schauem ob er online ist.

                              Abhilfe steht im Link und ist relativ einfach:

                              1. Anmelden
                              2. sudo nano /usr/lib/sysctl.d/50-default.conf
                              3. nach "net.ipv4.ping_group_range = .........." suchen und gegen "net.ipv4.ping_group_range = 1 1000" ersetzen.
                              4. Speichern und Neustarten

                              Liebe Grüße

                              wendy2702W Online
                              wendy2702W Online
                              wendy2702
                              schrieb am zuletzt editiert von
                              #672

                              @fichte auch nach einem Restart ?

                              Bitte keine Fragen per PN, die gehören ins Forum!

                              Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                              F 1 Antwort Letzte Antwort
                              0
                              • wendy2702W wendy2702

                                @fichte auch nach einem Restart ?

                                F Offline
                                F Offline
                                Fichte
                                schrieb am zuletzt editiert von
                                #673

                                @wendy2702 Ja Punkt 4

                                1 Antwort Letzte Antwort
                                0
                                • F Fichte

                                  Hallo zusammen

                                  Ich hab heut Trixie (Debian 13) unter Proxmox getestet und da erscheint diese Meldung

                                  [getConnection] Host 'Name' (IP:Port) seems not to be online
                                  

                                  "Ping wird nicht mehr mit erhöhten Privilegien ausgeführt"
                                  Quelle hier

                                  Heisst unter einem anderen User außer root geht der befehl "Ping" nicht mehr.
                                  Wird aber vom Adapter benötigt um zu schauem ob er online ist.

                                  Abhilfe steht im Link und ist relativ einfach:

                                  1. Anmelden
                                  2. sudo nano /usr/lib/sysctl.d/50-default.conf
                                  3. nach "net.ipv4.ping_group_range = .........." suchen und gegen "net.ipv4.ping_group_range = 1 1000" ersetzen.
                                  4. Speichern und Neustarten

                                  Liebe Grüße

                                  M Online
                                  M Online
                                  mading
                                  schrieb am zuletzt editiert von
                                  #674

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

                                  Hallo zusammen

                                  Ich hab heut Trixie (Debian 13) unter Proxmox getestet und da erscheint diese Meldung

                                  [getConnection] Host 'Name' (IP:Port) seems not to be online
                                  

                                  "Ping wird nicht mehr mit erhöhten Privilegien ausgeführt"
                                  Quelle hier

                                  Heisst unter einem anderen User außer root geht der befehl "Ping" nicht mehr.
                                  Wird aber vom Adapter benötigt um zu schauem ob er online ist.

                                  Abhilfe steht im Link und ist relativ einfach:

                                  1. Anmelden
                                  2. sudo nano /usr/lib/sysctl.d/50-default.conf
                                  3. nach "net.ipv4.ping_group_range = .........." suchen und gegen "net.ipv4.ping_group_range = 1 1000" ersetzen.
                                  4. Speichern und Neustarten

                                  Liebe Grüße

                                  Muss das auf jedem server durchgeführt werden oder nur auf dem iob?

                                  wendy2702W 1 Antwort Letzte Antwort
                                  0
                                  • M mading

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

                                    Hallo zusammen

                                    Ich hab heut Trixie (Debian 13) unter Proxmox getestet und da erscheint diese Meldung

                                    [getConnection] Host 'Name' (IP:Port) seems not to be online
                                    

                                    "Ping wird nicht mehr mit erhöhten Privilegien ausgeführt"
                                    Quelle hier

                                    Heisst unter einem anderen User außer root geht der befehl "Ping" nicht mehr.
                                    Wird aber vom Adapter benötigt um zu schauem ob er online ist.

                                    Abhilfe steht im Link und ist relativ einfach:

                                    1. Anmelden
                                    2. sudo nano /usr/lib/sysctl.d/50-default.conf
                                    3. nach "net.ipv4.ping_group_range = .........." suchen und gegen "net.ipv4.ping_group_range = 1 1000" ersetzen.
                                    4. Speichern und Neustarten

                                    Liebe Grüße

                                    Muss das auf jedem server durchgeführt werden oder nur auf dem iob?

                                    wendy2702W Online
                                    wendy2702W Online
                                    wendy2702
                                    schrieb am zuletzt editiert von
                                    #675

                                    @mading nur auf dem wo der Linux Control Adapter läuft.

                                    Bitte keine Fragen per PN, die gehören ins Forum!

                                    Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.

                                    1 Antwort Letzte Antwort
                                    0
                                    Antworten
                                    • In einem neuen Thema antworten
                                    Anmelden zum Antworten
                                    • Älteste zuerst
                                    • Neuste zuerst
                                    • Meiste Stimmen


                                    Support us

                                    ioBroker
                                    Community Adapters
                                    Donate

                                    530

                                    Online

                                    32.4k

                                    Benutzer

                                    81.4k

                                    Themen

                                    1.3m

                                    Beiträge
                                    Community
                                    Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                                    ioBroker Community 2014-2025
                                    logo
                                    • Anmelden

                                    • Du hast noch kein Konto? Registrieren

                                    • Anmelden oder registrieren, um zu suchen
                                    • Erster Beitrag
                                      Letzter Beitrag
                                    0
                                    • Home
                                    • Aktuell
                                    • Tags
                                    • Ungelesen 0
                                    • Kategorien
                                    • Unreplied
                                    • Beliebt
                                    • GitHub
                                    • Docu
                                    • Hilfe