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

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Einsteigerfragen
  4. Installation
  5. Troubleshooting NodeJS update

NEWS

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

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

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

Troubleshooting NodeJS update

Geplant Angeheftet Gesperrt Verschoben Installation
nodejs 18nodejs update
504 Beiträge 60 Kommentatoren 148.4k Aufrufe 52 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.
  • gelberlemmyG gelberlemmy

    Moin moin,

    ich habe einmal mein NodeJS aus folgender Anleitung von 16 auf 18 geupdatet.

    https://forum.iobroker.net/topic/64032/update-nodejs-best-practise-supported-16-und-18

    Nun bekomme ich solche Fehlermeldungen in meinem System. Habe schon ein wenig gegoogelt, aber nix passendes gefunden. Hat da jemand einen Tipp für mich ?

    Gruß André

    host.IOBroker-Proxmox
    2023-07-01 14:18:03.996	error	instance system.adapter.amazon-dash.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.995	error	Caught by controller[0]: Node.js v18.16.1
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.995	error	Caught by controller[0]: }
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.995	error	Caught by controller[0]: code: 'ERR_DLOPEN_FAILED'
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.995	error	Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) {
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.995	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32)
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.970	error	Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.970	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14)
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.970	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/pcap/pcap.js:3:21)
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.970	error	Caught by controller[0]: at require (node:internal/modules/cjs/helpers:110:18)
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.970	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19)
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.970	error	Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12)
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.969	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32)
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.969	error	Caught by controller[0]: at Module._extensions..node (node:internal/modules/cjs/loader:1340:18)
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.969	error	Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.969	error	Caught by controller[0]: NODE_MODULE_VERSION 108. Please try re-compiling or re-installing
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.969	error	Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.969	error	Caught by controller[0]: was compiled against a different Node.js version using
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.968	error	Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/pcap/build/Release/pcap_binding.node'
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.968	error	Caught by controller[0]: ^
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.968	error	Caught by controller[0]: return process.dlopen(module, path.toNamespacedPath(filename));
    host.IOBroker-Proxmox
    2023-07-01 14:18:03.967	error	Caught by controller[0]: node:internal/modules/cjs/loader:1340
    
    Thomas BraunT Online
    Thomas BraunT Online
    Thomas Braun
    Most Active
    schrieb am zuletzt editiert von
    #146

    @gelberlemmy

    Installier den Adapter nochmal frisch.

    Linux-Werkzeugkasten:
    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
    NodeJS Fixer Skript:
    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

    gelberlemmyG 1 Antwort Letzte Antwort
    0
    • Thomas BraunT Thomas Braun

      @gelberlemmy

      Installier den Adapter nochmal frisch.

      gelberlemmyG Offline
      gelberlemmyG Offline
      gelberlemmy
      schrieb am zuletzt editiert von
      #147

      @thomas-braun sagte in Troubleshooting NodeJS update:

      @gelberlemmy

      Installier den Adapter nochmal frisch.

      Der DashButton Adapter läuft. Auch mein System läuft. Ich frage mich aber, was das für ganze Fehlermeldungen sind ?

      Thomas BraunT 1 Antwort Letzte Antwort
      0
      • gelberlemmyG gelberlemmy

        @thomas-braun sagte in Troubleshooting NodeJS update:

        @gelberlemmy

        Installier den Adapter nochmal frisch.

        Der DashButton Adapter läuft. Auch mein System läuft. Ich frage mich aber, was das für ganze Fehlermeldungen sind ?

        Thomas BraunT Online
        Thomas BraunT Online
        Thomas Braun
        Most Active
        schrieb am zuletzt editiert von
        #148

        @gelberlemmy sagte in Troubleshooting NodeJS update:

        Ich frage mich aber, was das für ganze Fehlermeldungen sind ?

        Welche? Frisch aus dem LogFile.

        Linux-Werkzeugkasten:
        https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
        NodeJS Fixer Skript:
        https://forum.iobroker.net/topic/68035/iob-node-fix-skript
        iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

        gelberlemmyG 1 Antwort Letzte Antwort
        0
        • Thomas BraunT Thomas Braun

          @gelberlemmy sagte in Troubleshooting NodeJS update:

          Ich frage mich aber, was das für ganze Fehlermeldungen sind ?

          Welche? Frisch aus dem LogFile.

          gelberlemmyG Offline
          gelberlemmyG Offline
          gelberlemmy
          schrieb am zuletzt editiert von
          #149

          @thomas-braun sagte in Troubleshooting NodeJS update:

          @gelberlemmy sagte in Troubleshooting NodeJS update:

          Ich frage mich aber, was das für ganze Fehlermeldungen sind ?

          Welche? Frisch aus dem LogFile.

          aus meinem Post

          Thomas BraunT 1 Antwort Letzte Antwort
          0
          • gelberlemmyG gelberlemmy

            @thomas-braun sagte in Troubleshooting NodeJS update:

            @gelberlemmy sagte in Troubleshooting NodeJS update:

            Ich frage mich aber, was das für ganze Fehlermeldungen sind ?

            Welche? Frisch aus dem LogFile.

            aus meinem Post

            Thomas BraunT Online
            Thomas BraunT Online
            Thomas Braun
            Most Active
            schrieb am zuletzt editiert von
            #150

            @gelberlemmy

            Ein Neustart des Adapters schaut nun wie aus?
            Bitte aus

            iob logs -watch | uniq
            

            ich mag nicht verkehrt herum lesen.

            Linux-Werkzeugkasten:
            https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
            NodeJS Fixer Skript:
            https://forum.iobroker.net/topic/68035/iob-node-fix-skript
            iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

            gelberlemmyG 1 Antwort Letzte Antwort
            0
            • gelberlemmyG gelberlemmy

              Moin moin,

              ich habe einmal mein NodeJS aus folgender Anleitung von 16 auf 18 geupdatet.

              https://forum.iobroker.net/topic/64032/update-nodejs-best-practise-supported-16-und-18

              Nun bekomme ich solche Fehlermeldungen in meinem System. Habe schon ein wenig gegoogelt, aber nix passendes gefunden. Hat da jemand einen Tipp für mich ?

              Gruß André

              host.IOBroker-Proxmox
              2023-07-01 14:18:03.996	error	instance system.adapter.amazon-dash.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.995	error	Caught by controller[0]: Node.js v18.16.1
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.995	error	Caught by controller[0]: }
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.995	error	Caught by controller[0]: code: 'ERR_DLOPEN_FAILED'
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.995	error	Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12) {
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.995	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32)
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.970	error	Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.970	error	Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1256:14)
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.970	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/pcap/pcap.js:3:21)
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.970	error	Caught by controller[0]: at require (node:internal/modules/cjs/helpers:110:18)
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.970	error	Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1143:19)
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.970	error	Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:960:12)
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.969	error	Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1119:32)
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.969	error	Caught by controller[0]: at Module._extensions..node (node:internal/modules/cjs/loader:1340:18)
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.969	error	Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.969	error	Caught by controller[0]: NODE_MODULE_VERSION 108. Please try re-compiling or re-installing
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.969	error	Caught by controller[0]: NODE_MODULE_VERSION 93. This version of Node.js requires
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.969	error	Caught by controller[0]: was compiled against a different Node.js version using
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.968	error	Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/pcap/build/Release/pcap_binding.node'
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.968	error	Caught by controller[0]: ^
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.968	error	Caught by controller[0]: return process.dlopen(module, path.toNamespacedPath(filename));
              host.IOBroker-Proxmox
              2023-07-01 14:18:03.967	error	Caught by controller[0]: node:internal/modules/cjs/loader:1340
              
              HomoranH Nicht stören
              HomoranH Nicht stören
              Homoran
              Global Moderator Administrators
              schrieb am zuletzt editiert von
              #151

              @gelberlemmy sagte in Troubleshooting NodeJS update:

              Error: The module '/opt/iobroker/node_modules/pcap/build/Release/pcap_binding.node'

              @gelberlemmy sagte in Troubleshooting NodeJS update:

              was compiled against a different Node.js version

              irgendwelche Systemdateien hin und herkopiert?

              kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.

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

              der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -

              1 Antwort Letzte Antwort
              0
              • Thomas BraunT Thomas Braun

                @gelberlemmy

                Ein Neustart des Adapters schaut nun wie aus?
                Bitte aus

                iob logs -watch | uniq
                

                ich mag nicht verkehrt herum lesen.

                gelberlemmyG Offline
                gelberlemmyG Offline
                gelberlemmy
                schrieb am zuletzt editiert von
                #152

                @thomas-braun sagte in Troubleshooting NodeJS update:

                @gelberlemmy

                Ein Neustart des Adapters schaut nun wie aus?
                Bitte aus

                iob logs -watch | uniq
                

                ich mag nicht verkehrt herum lesen.

                Habe einmal mein IOBroker neu gestartet. Log ist voller Errors. Aber fährt dann trotzdem normal alle Adapter hoch.

                host.IOBroker-Proxmox
                2023-07-01 21:23:12.703	info	Some obsolete host states deleted.
                host.IOBroker-Proxmox
                2023-07-01 21:23:12.697	info	Delete state "system.host.IOBroker-Proxmox.versions.npmNewestNext"
                host.IOBroker-Proxmox
                2023-07-01 21:23:12.690	info	Delete state "system.host.IOBroker-Proxmox.versions.npmNewest"
                host.IOBroker-Proxmox
                2023-07-01 21:23:12.684	info	Delete state "system.host.IOBroker-Proxmox.versions.npmCurrent"
                host.IOBroker-Proxmox
                2023-07-01 21:23:12.677	info	Delete state "system.host.IOBroker-Proxmox.versions.nodeNewestNext"
                host.IOBroker-Proxmox
                2023-07-01 21:23:12.619	info	Delete state "system.host.IOBroker-Proxmox.versions.nodeNewest"
                host.IOBroker-Proxmox
                2023-07-01 21:23:12.605	info	instance system.adapter.admin.0 started with pid 304
                host.IOBroker-Proxmox
                2023-07-01 21:23:12.360	info	starting 47 instances
                host.IOBroker-Proxmox
                2023-07-01 21:23:12.292	info	52 instances found
                host.IOBroker-Proxmox
                2023-07-01 21:23:12.291	info	Delete state "system.host.IOBroker-Proxmox.versions.nodeCurrent"
                host.IOBroker-Proxmox
                2023-07-01 21:23:11.037	info	added notifications configuration of host
                host.IOBroker-Proxmox
                2023-07-01 21:23:10.942	info	connected to Objects and States
                host.IOBroker-Proxmox
                2023-07-01 21:23:07.788	info	ip addresses: 192.168.171.35 fe80::a8d4:caff:fe76:9b25
                host.IOBroker-Proxmox
                2023-07-01 21:23:07.787	info	hostname: IOBroker-Proxmox, node: v18.16.1
                host.IOBroker-Proxmox
                2023-07-01 21:23:07.787	info	Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
                host.IOBroker-Proxmox
                2023-07-01 21:23:07.781	info	iobroker.js-controller version 5.0.5 js-controller starting
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.794	info	terminated
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.708	info	All instances are stopped.
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.708	info	instance system.adapter.ham.0 terminated with code 0 (NO_ERROR)
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.708	info	All instances are stopped.
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.707	info	instance system.adapter.history.0 terminated with code 0 (NO_ERROR)
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.629	info	instance system.adapter.shelly.1 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.629	warn	instance system.adapter.shelly.1 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.628	error	Caught by controller[0]: at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.628	error	Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.628	error	Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.628	error	Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.628	error	Caught by controller[0]: Error: DB closed
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.628	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:
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.599	info	instance system.adapter.shelly.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.599	warn	instance system.adapter.shelly.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.599	error	Caught by controller[0]: at processImmediate (node:internal/timers:447:9)
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.598	error	Caught by controller[0]: at runNextTicks (node:internal/process/task_queues:60:5)
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.598	error	Caught by controller[0]: at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.598	error	Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.598	error	Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.598	error	Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.598	error	Caught by controller[0]: Error: DB closed
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.598	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:
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.170	info	instance system.adapter.hue-extended.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.170	warn	instance system.adapter.hue-extended.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.170	info	instance system.adapter.zigbee.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.170	warn	instance system.adapter.zigbee.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.103	info	instance system.adapter.javascript.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.102	warn	instance system.adapter.javascript.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.055	info	instance system.adapter.jarvis.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.055	warn	instance system.adapter.jarvis.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.054	info	instance system.adapter.zwave2.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:54.054	warn	instance system.adapter.zwave2.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.988	info	instance system.adapter.alexa2.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.988	warn	instance system.adapter.alexa2.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.938	info	instance system.adapter.admin.1 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.938	warn	instance system.adapter.admin.1 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.896	info	instance system.adapter.admin.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.896	warn	instance system.adapter.admin.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.895	info	instance system.adapter.amazon-dash.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.895	warn	instance system.adapter.amazon-dash.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.819	info	instance system.adapter.energiefluss.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.819	warn	instance system.adapter.energiefluss.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.778	info	instance system.adapter.accuweather.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.778	warn	instance system.adapter.accuweather.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.745	info	instance system.adapter.senec.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.745	warn	instance system.adapter.senec.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.745	info	instance system.adapter.worx.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.745	warn	instance system.adapter.worx.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.650	info	instance system.adapter.proxmox.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.650	warn	instance system.adapter.proxmox.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.620	info	instance system.adapter.web.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.619	warn	instance system.adapter.web.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.589	info	instance system.adapter.trashschedule.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.589	warn	instance system.adapter.trashschedule.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.589	info	instance system.adapter.text2command.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.589	warn	instance system.adapter.text2command.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.501	info	instance system.adapter.sourceanalytix.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.500	warn	instance system.adapter.sourceanalytix.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.470	info	instance system.adapter.pushsafer.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.470	warn	instance system.adapter.pushsafer.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.439	info	instance system.adapter.octoprint.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.439	warn	instance system.adapter.octoprint.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.439	info	instance system.adapter.iot.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.438	warn	instance system.adapter.iot.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.356	info	instance system.adapter.info.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.356	warn	instance system.adapter.info.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.326	info	instance system.adapter.homeconnect.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.326	warn	instance system.adapter.homeconnect.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.325	info	instance system.adapter.fb-checkpresence.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.325	warn	instance system.adapter.fb-checkpresence.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.149	info	instance system.adapter.enocean.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.148	warn	instance system.adapter.enocean.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.070	info	instance system.adapter.discovery.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:53.070	warn	instance system.adapter.discovery.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.989	info	instance system.adapter.device-reminder.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.988	warn	instance system.adapter.device-reminder.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.988	info	instance system.adapter.cloud.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.988	warn	instance system.adapter.cloud.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.909	info	instance system.adapter.backitup.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.909	warn	instance system.adapter.backitup.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.869	info	instance system.adapter.alarm.2 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.869	warn	instance system.adapter.alarm.2 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.839	info	instance system.adapter.alarm.1 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.839	warn	instance system.adapter.alarm.1 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.839	info	instance system.adapter.alarm.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.839	warn	instance system.adapter.alarm.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.746	info	instance system.adapter.tr-064.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.746	warn	instance system.adapter.tr-064.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.716	info	instance system.adapter.samsung.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.716	warn	instance system.adapter.samsung.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.685	info	instance system.adapter.nut.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.685	warn	instance system.adapter.nut.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.685	info	instance system.adapter.sonoff.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.684	warn	instance system.adapter.sonoff.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.595	info	instance system.adapter.netatmo.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.595	warn	instance system.adapter.netatmo.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.564	info	instance system.adapter.mqtt.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.564	warn	instance system.adapter.mqtt.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.515	info	instance system.adapter.hmip.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.515	warn	instance system.adapter.hmip.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.515	info	instance system.adapter.telegram.1 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.514	warn	instance system.adapter.telegram.1 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.437	info	instance system.adapter.telegram.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.437	warn	instance system.adapter.telegram.0 terminated due to SIGTERM
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.396	info	instance system.adapter.email.0 terminated with code null ()
                host.IOBroker-Proxmox
                2023-07-01 21:22:52.395	warn	instance system.adapter.email.0 terminated due to SIGTERM
                
                shelly.1
                2023-07-01 21:22:48.051	error	DB closed
                
                shelly.0
                2023-07-01 21:22:47.944	error	DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                
                hue-extended.0
                2023-07-01 21:22:47.658	error	unhandled promise rejection: 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:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12) at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9)
                
                hue-extended.0
                2023-07-01 21:22:47.658	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().
                
                hue-extended.0
                2023-07-01 21:22:47.657	error	unhandled promise rejection: 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:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12)
                
                hue-extended.0
                2023-07-01 21:22:47.658	error	Error: DB closed
                
                hue-extended.0
                2023-07-01 21:22:47.658	error	DB closed
                
                hue-extended.0
                2023-07-01 21:22:47.657	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().
                
                hue-extended.0
                2023-07-01 21:22:47.656	error	unhandled promise rejection: 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:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12)
                
                hue-extended.0
                2023-07-01 21:22:47.657	error	Error: DB closed
                
                hue-extended.0
                2023-07-01 21:22:47.657	error	DB closed
                
                hue-extended.0
                2023-07-01 21:22:47.656	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().
                
                hue-extended.0
                2023-07-01 21:22:47.655	error	unhandled promise rejection: 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:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12)
                
                hue-extended.0
                2023-07-01 21:22:47.656	error	Error: DB closed
                
                hue-extended.0
                2023-07-01 21:22:47.656	error	DB closed
                
                hue-extended.0
                2023-07-01 21:22:47.654	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().
                
                hue-extended.0
                2023-07-01 21:22:47.654	error	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:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12)
                
                hue-extended.0
                2023-07-01 21:22:47.655	error	Error: DB closed
                
                hue-extended.0
                2023-07-01 21:22:47.655	error	DB closed
                
                hue-extended.0
                2023-07-01 21:22:47.654	error	unhandled promise rejection: DB closed
                
                hue-extended.0
                2023-07-01 21:22:47.654	error	DB closed
                
                shelly.0
                2023-07-01 21:22:47.930	error	Error: DB closed
                
                shelly.0
                2023-07-01 21:22:46.742	error	unhandled promise rejection: DB closed
                
                shelly.0
                2023-07-01 21:22:46.741	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().
                
                shelly.1
                2023-07-01 21:22:48.050	error	Error: DB closed
                
                shelly.1
                2023-07-01 21:22:46.721	error	unhandled promise rejection: DB closed
                
                shelly.1
                2023-07-01 21:22:46.721	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().
                
                Thomas BraunT 1 Antwort Letzte Antwort
                0
                • gelberlemmyG gelberlemmy

                  @thomas-braun sagte in Troubleshooting NodeJS update:

                  @gelberlemmy

                  Ein Neustart des Adapters schaut nun wie aus?
                  Bitte aus

                  iob logs -watch | uniq
                  

                  ich mag nicht verkehrt herum lesen.

                  Habe einmal mein IOBroker neu gestartet. Log ist voller Errors. Aber fährt dann trotzdem normal alle Adapter hoch.

                  host.IOBroker-Proxmox
                  2023-07-01 21:23:12.703	info	Some obsolete host states deleted.
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:12.697	info	Delete state "system.host.IOBroker-Proxmox.versions.npmNewestNext"
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:12.690	info	Delete state "system.host.IOBroker-Proxmox.versions.npmNewest"
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:12.684	info	Delete state "system.host.IOBroker-Proxmox.versions.npmCurrent"
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:12.677	info	Delete state "system.host.IOBroker-Proxmox.versions.nodeNewestNext"
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:12.619	info	Delete state "system.host.IOBroker-Proxmox.versions.nodeNewest"
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:12.605	info	instance system.adapter.admin.0 started with pid 304
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:12.360	info	starting 47 instances
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:12.292	info	52 instances found
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:12.291	info	Delete state "system.host.IOBroker-Proxmox.versions.nodeCurrent"
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:11.037	info	added notifications configuration of host
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:10.942	info	connected to Objects and States
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:07.788	info	ip addresses: 192.168.171.35 fe80::a8d4:caff:fe76:9b25
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:07.787	info	hostname: IOBroker-Proxmox, node: v18.16.1
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:07.787	info	Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
                  host.IOBroker-Proxmox
                  2023-07-01 21:23:07.781	info	iobroker.js-controller version 5.0.5 js-controller starting
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.794	info	terminated
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.708	info	All instances are stopped.
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.708	info	instance system.adapter.ham.0 terminated with code 0 (NO_ERROR)
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.708	info	All instances are stopped.
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.707	info	instance system.adapter.history.0 terminated with code 0 (NO_ERROR)
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.629	info	instance system.adapter.shelly.1 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.629	warn	instance system.adapter.shelly.1 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.628	error	Caught by controller[0]: at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.628	error	Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.628	error	Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.628	error	Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.628	error	Caught by controller[0]: Error: DB closed
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.628	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:
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.599	info	instance system.adapter.shelly.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.599	warn	instance system.adapter.shelly.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.599	error	Caught by controller[0]: at processImmediate (node:internal/timers:447:9)
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.598	error	Caught by controller[0]: at runNextTicks (node:internal/process/task_queues:60:5)
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.598	error	Caught by controller[0]: at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.598	error	Caught by controller[0]: at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.598	error	Caught by controller[0]: at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.598	error	Caught by controller[0]: at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.598	error	Caught by controller[0]: Error: DB closed
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.598	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:
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.170	info	instance system.adapter.hue-extended.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.170	warn	instance system.adapter.hue-extended.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.170	info	instance system.adapter.zigbee.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.170	warn	instance system.adapter.zigbee.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.103	info	instance system.adapter.javascript.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.102	warn	instance system.adapter.javascript.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.055	info	instance system.adapter.jarvis.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.055	warn	instance system.adapter.jarvis.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.054	info	instance system.adapter.zwave2.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:54.054	warn	instance system.adapter.zwave2.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.988	info	instance system.adapter.alexa2.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.988	warn	instance system.adapter.alexa2.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.938	info	instance system.adapter.admin.1 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.938	warn	instance system.adapter.admin.1 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.896	info	instance system.adapter.admin.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.896	warn	instance system.adapter.admin.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.895	info	instance system.adapter.amazon-dash.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.895	warn	instance system.adapter.amazon-dash.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.819	info	instance system.adapter.energiefluss.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.819	warn	instance system.adapter.energiefluss.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.778	info	instance system.adapter.accuweather.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.778	warn	instance system.adapter.accuweather.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.745	info	instance system.adapter.senec.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.745	warn	instance system.adapter.senec.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.745	info	instance system.adapter.worx.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.745	warn	instance system.adapter.worx.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.650	info	instance system.adapter.proxmox.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.650	warn	instance system.adapter.proxmox.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.620	info	instance system.adapter.web.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.619	warn	instance system.adapter.web.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.589	info	instance system.adapter.trashschedule.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.589	warn	instance system.adapter.trashschedule.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.589	info	instance system.adapter.text2command.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.589	warn	instance system.adapter.text2command.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.501	info	instance system.adapter.sourceanalytix.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.500	warn	instance system.adapter.sourceanalytix.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.470	info	instance system.adapter.pushsafer.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.470	warn	instance system.adapter.pushsafer.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.439	info	instance system.adapter.octoprint.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.439	warn	instance system.adapter.octoprint.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.439	info	instance system.adapter.iot.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.438	warn	instance system.adapter.iot.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.356	info	instance system.adapter.info.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.356	warn	instance system.adapter.info.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.326	info	instance system.adapter.homeconnect.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.326	warn	instance system.adapter.homeconnect.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.325	info	instance system.adapter.fb-checkpresence.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.325	warn	instance system.adapter.fb-checkpresence.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.149	info	instance system.adapter.enocean.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.148	warn	instance system.adapter.enocean.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.070	info	instance system.adapter.discovery.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:53.070	warn	instance system.adapter.discovery.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.989	info	instance system.adapter.device-reminder.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.988	warn	instance system.adapter.device-reminder.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.988	info	instance system.adapter.cloud.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.988	warn	instance system.adapter.cloud.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.909	info	instance system.adapter.backitup.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.909	warn	instance system.adapter.backitup.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.869	info	instance system.adapter.alarm.2 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.869	warn	instance system.adapter.alarm.2 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.839	info	instance system.adapter.alarm.1 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.839	warn	instance system.adapter.alarm.1 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.839	info	instance system.adapter.alarm.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.839	warn	instance system.adapter.alarm.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.746	info	instance system.adapter.tr-064.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.746	warn	instance system.adapter.tr-064.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.716	info	instance system.adapter.samsung.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.716	warn	instance system.adapter.samsung.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.685	info	instance system.adapter.nut.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.685	warn	instance system.adapter.nut.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.685	info	instance system.adapter.sonoff.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.684	warn	instance system.adapter.sonoff.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.595	info	instance system.adapter.netatmo.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.595	warn	instance system.adapter.netatmo.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.564	info	instance system.adapter.mqtt.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.564	warn	instance system.adapter.mqtt.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.515	info	instance system.adapter.hmip.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.515	warn	instance system.adapter.hmip.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.515	info	instance system.adapter.telegram.1 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.514	warn	instance system.adapter.telegram.1 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.437	info	instance system.adapter.telegram.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.437	warn	instance system.adapter.telegram.0 terminated due to SIGTERM
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.396	info	instance system.adapter.email.0 terminated with code null ()
                  host.IOBroker-Proxmox
                  2023-07-01 21:22:52.395	warn	instance system.adapter.email.0 terminated due to SIGTERM
                  
                  shelly.1
                  2023-07-01 21:22:48.051	error	DB closed
                  
                  shelly.0
                  2023-07-01 21:22:47.944	error	DB closed at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                  
                  hue-extended.0
                  2023-07-01 21:22:47.658	error	unhandled promise rejection: 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:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12) at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24) at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25) at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40) at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34) at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:447:9)
                  
                  hue-extended.0
                  2023-07-01 21:22:47.658	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().
                  
                  hue-extended.0
                  2023-07-01 21:22:47.657	error	unhandled promise rejection: 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:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12)
                  
                  hue-extended.0
                  2023-07-01 21:22:47.658	error	Error: DB closed
                  
                  hue-extended.0
                  2023-07-01 21:22:47.658	error	DB closed
                  
                  hue-extended.0
                  2023-07-01 21:22:47.657	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().
                  
                  hue-extended.0
                  2023-07-01 21:22:47.656	error	unhandled promise rejection: 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:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12)
                  
                  hue-extended.0
                  2023-07-01 21:22:47.657	error	Error: DB closed
                  
                  hue-extended.0
                  2023-07-01 21:22:47.657	error	DB closed
                  
                  hue-extended.0
                  2023-07-01 21:22:47.656	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().
                  
                  hue-extended.0
                  2023-07-01 21:22:47.655	error	unhandled promise rejection: 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:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12)
                  
                  hue-extended.0
                  2023-07-01 21:22:47.656	error	Error: DB closed
                  
                  hue-extended.0
                  2023-07-01 21:22:47.656	error	DB closed
                  
                  hue-extended.0
                  2023-07-01 21:22:47.654	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().
                  
                  hue-extended.0
                  2023-07-01 21:22:47.654	error	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:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:322:12)
                  
                  hue-extended.0
                  2023-07-01 21:22:47.655	error	Error: DB closed
                  
                  hue-extended.0
                  2023-07-01 21:22:47.655	error	DB closed
                  
                  hue-extended.0
                  2023-07-01 21:22:47.654	error	unhandled promise rejection: DB closed
                  
                  hue-extended.0
                  2023-07-01 21:22:47.654	error	DB closed
                  
                  shelly.0
                  2023-07-01 21:22:47.930	error	Error: DB closed
                  
                  shelly.0
                  2023-07-01 21:22:46.742	error	unhandled promise rejection: DB closed
                  
                  shelly.0
                  2023-07-01 21:22:46.741	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().
                  
                  shelly.1
                  2023-07-01 21:22:48.050	error	Error: DB closed
                  
                  shelly.1
                  2023-07-01 21:22:46.721	error	unhandled promise rejection: DB closed
                  
                  shelly.1
                  2023-07-01 21:22:46.721	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().
                  
                  Thomas BraunT Online
                  Thomas BraunT Online
                  Thomas Braun
                  Most Active
                  schrieb am zuletzt editiert von
                  #153

                  @gelberlemmy sagte in Troubleshooting NodeJS update:

                  ich mag nicht verkehrt herum lesen.

                  Linux-Werkzeugkasten:
                  https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                  NodeJS Fixer Skript:
                  https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                  iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                  gelberlemmyG 1 Antwort Letzte Antwort
                  0
                  • Thomas BraunT Thomas Braun

                    @gelberlemmy sagte in Troubleshooting NodeJS update:

                    ich mag nicht verkehrt herum lesen.

                    gelberlemmyG Offline
                    gelberlemmyG Offline
                    gelberlemmy
                    schrieb am zuletzt editiert von
                    #154

                    @thomas-braun so jetzt aber. Ich hoffe ich habe alles mitbekommen.

                    2023-07-01 21:43:53.082  - warn: shelly.0 (556) redis get shelly.0.SHUNI-1#349454790800#1.Relay0.Timer, error - DB closed
                    2023-07-01 21:43:53.165  - info: hue-extended.0 (832) terminating
                    2023-07-01 21:43:53.170  - warn: shelly.0 (556) get state error: Connection is closed.
                    2023-07-01 21:43:53.218  - info: hue-extended.0 (832) terminating with timeout
                    2023-07-01 21:43:53.298  - warn: shelly.0 (556) get state error: Connection is closed.
                    2023-07-01 21:43:53.301  - error: shelly.0 (556) 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().
                    2023-07-01 21:43:53.306  - error: shelly.0 (556) unhandled promise rejection: DB closed
                    2023-07-01 21:43:53.772  - error: shelly.0 (556) Error: DB closed
                        at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                        at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                        at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                        at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                    2023-07-01 21:43:53.772  - error: shelly.0 (556) DB closed
                    2023-07-01 21:43:53.796  - warn: shelly.0 (556) redis get shelly.0.SHSW-25#3494546A140D#1.Relay1.Timer, error - Connection is closed.
                    2023-07-01 21:43:53.796  - warn: shelly.0 (556) redis get shelly.0.SHUNI-1#349454790800#1.Relay1.Timer, error - Connection is closed.
                    2023-07-01 21:43:54.091  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.095  - warn: shelly.1 (631) get state error: Connection is closed.
                    2023-07-01 21:43:54.130  - info: host.IOBroker-Proxmox stopInstance system.adapter.admin.0 killing pid 304
                    2023-07-01 21:43:54.133  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.146  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.147  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.148  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.149  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.150  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.151  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.152  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.153  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.154  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.184  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.185  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.186  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.187  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.197  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.198  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.199  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.200  - warn: zigbee.0 (592) get state error: Connection is closed.
                    2023-07-01 21:43:54.132  - info: host.IOBroker-Proxmox stopInstance system.adapter.admin.1 killing pid 331
                    2023-07-01 21:43:54.134  - info: host.IOBroker-Proxmox stopInstance system.adapter.email.0 killing pid 338
                    2023-07-01 21:43:54.160  - info: host.IOBroker-Proxmox stopInstance system.adapter.javascript.0 killing pid 384
                    2023-07-01 21:43:54.160  - info: host.IOBroker-Proxmox stopInstance system.adapter.telegram.0 killing pid 395
                    2023-07-01 21:43:54.160  - info: host.IOBroker-Proxmox stopInstance system.adapter.telegram.1 killing pid 406
                    2023-07-01 21:43:54.175  - info: host.IOBroker-Proxmox stopInstance system.adapter.alexa2.0 killing pid 421
                    2023-07-01 21:43:54.200  - info: host.IOBroker-Proxmox stopInstance system.adapter.ham.0 killing pid 440
                    2023-07-01 21:43:54.214  - info: host.IOBroker-Proxmox stopInstance system.adapter.hmip.0 killing pid 451
                    2023-07-01 21:43:54.217  - info: host.IOBroker-Proxmox stopInstance system.adapter.mqtt.0 killing pid 497
                    2023-07-01 21:43:54.217  - info: host.IOBroker-Proxmox stopInstance system.adapter.netatmo.0 killing pid 548
                    2023-07-01 21:43:54.217  - info: host.IOBroker-Proxmox stopInstance system.adapter.shelly.0 killing pid 556
                    2023-07-01 21:43:54.217  - info: host.IOBroker-Proxmox stopInstance system.adapter.sonoff.0 killing pid 573
                    2023-07-01 21:43:54.218  - info: host.IOBroker-Proxmox stopInstance system.adapter.zigbee.0 killing pid 592
                    2023-07-01 21:43:54.218  - info: host.IOBroker-Proxmox stopInstance system.adapter.nut.0 killing pid 605
                    2023-07-01 21:43:54.218  - info: host.IOBroker-Proxmox stopInstance system.adapter.samsung.0 killing pid 624
                    2023-07-01 21:43:54.219  - info: host.IOBroker-Proxmox stopInstance system.adapter.shelly.1 killing pid 631
                    2023-07-01 21:43:54.219  - info: host.IOBroker-Proxmox stopInstance system.adapter.tr-064.0 killing pid 650
                    2023-07-01 21:43:54.222  - info: host.IOBroker-Proxmox stopInstance system.adapter.alarm.0 killing pid 665
                    2023-07-01 21:43:54.225  - info: host.IOBroker-Proxmox stopInstance system.adapter.alarm.1 killing pid 688
                    2023-07-01 21:43:54.225  - info: host.IOBroker-Proxmox stopInstance system.adapter.alarm.2 killing pid 699
                    2023-07-01 21:43:54.227  - info: host.IOBroker-Proxmox stopInstance system.adapter.amazon-dash.0 killing pid 719
                    2023-07-01 21:43:54.227  - info: host.IOBroker-Proxmox stopInstance system.adapter.backitup.0 killing pid 743
                    2023-07-01 21:43:54.228  - info: host.IOBroker-Proxmox stopInstance system.adapter.cloud.0 killing pid 754
                    2023-07-01 21:43:54.230  - info: host.IOBroker-Proxmox stopInstance system.adapter.device-reminder.0 killing pid 765
                    2023-07-01 21:43:54.269  - info: host.IOBroker-Proxmox stopInstance system.adapter.discovery.0 killing pid 776
                    2023-07-01 21:43:54.269  - info: host.IOBroker-Proxmox stopInstance system.adapter.enocean.0 killing pid 791
                    2023-07-01 21:43:54.272  - info: host.IOBroker-Proxmox stopInstance system.adapter.fb-checkpresence.0 killing pid 802
                    2023-07-01 21:43:54.272  - info: host.IOBroker-Proxmox stopInstance system.adapter.homeconnect.0 killing pid 813
                    2023-07-01 21:43:54.272  - info: host.IOBroker-Proxmox stopInstance system.adapter.hue-extended.0 killing pid 832
                    2023-07-01 21:43:54.273  - info: host.IOBroker-Proxmox stopInstance system.adapter.info.0 killing pid 843
                    2023-07-01 21:43:54.276  - info: host.IOBroker-Proxmox stopInstance system.adapter.iot.0 killing pid 858
                    2023-07-01 21:43:54.278  - info: host.IOBroker-Proxmox stopInstance system.adapter.octoprint.0 killing pid 885
                    2023-07-01 21:43:54.280  - info: host.IOBroker-Proxmox stopInstance system.adapter.pushsafer.0 killing pid 904
                    2023-07-01 21:43:54.282  - info: host.IOBroker-Proxmox stopInstance system.adapter.sourceanalytix.0 killing pid 924
                    2023-07-01 21:43:54.284  - info: host.IOBroker-Proxmox stopInstance system.adapter.text2command.0 killing pid 939
                    2023-07-01 21:43:54.285  - info: host.IOBroker-Proxmox stopInstance system.adapter.trashschedule.0 killing pid 954
                    2023-07-01 21:43:54.285  - info: host.IOBroker-Proxmox stopInstance system.adapter.web.0 killing pid 969
                    2023-07-01 21:43:54.285  - info: host.IOBroker-Proxmox stopInstance system.adapter.zwave2.0 killing pid 980
                    2023-07-01 21:43:54.285  - info: host.IOBroker-Proxmox stopInstance system.adapter.proxmox.0 killing pid 987
                    2023-07-01 21:43:54.367  - info: host.IOBroker-Proxmox stopInstance system.adapter.worx.0 killing pid 1002
                    2023-07-01 21:43:54.367  - info: host.IOBroker-Proxmox stopInstance system.adapter.senec.0 killing pid 1013
                    2023-07-01 21:43:54.441  - info: host.IOBroker-Proxmox stopInstance system.adapter.accuweather.0 killing pid 1028
                    2023-07-01 21:43:54.442  - info: host.IOBroker-Proxmox stopInstance system.adapter.jarvis.0 killing pid 1039
                    2023-07-01 21:43:54.464  - info: host.IOBroker-Proxmox stopInstance system.adapter.energiefluss.0 killing pid 1050
                    2023-07-01 21:43:54.097  - error: shelly.1 (631) 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().
                    2023-07-01 21:43:54.098  - error: shelly.1 (631) unhandled promise rejection: DB closed
                    2023-07-01 21:43:55.069  - error: shelly.1 (631) Error: DB closed
                        at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                        at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                        at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                        at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                    2023-07-01 21:43:55.069  - error: shelly.1 (631) DB closed
                    2023-07-01 21:43:59.300  - warn: host.IOBroker-Proxmox instance system.adapter.admin.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.300  - info: host.IOBroker-Proxmox instance system.adapter.admin.0 terminated with code null ()
                    2023-07-01 21:43:59.348  - warn: host.IOBroker-Proxmox instance system.adapter.admin.1 terminated due to SIGTERM
                    2023-07-01 21:43:59.348  - info: host.IOBroker-Proxmox instance system.adapter.admin.1 terminated with code null ()
                    2023-07-01 21:43:59.419  - warn: host.IOBroker-Proxmox instance system.adapter.email.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.419  - info: host.IOBroker-Proxmox instance system.adapter.email.0 terminated with code null ()
                    2023-07-01 21:43:59.419  - warn: host.IOBroker-Proxmox instance system.adapter.telegram.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.420  - info: host.IOBroker-Proxmox instance system.adapter.telegram.0 terminated with code null ()
                    2023-07-01 21:43:59.467  - warn: host.IOBroker-Proxmox instance system.adapter.telegram.1 terminated due to SIGTERM
                    2023-07-01 21:43:59.467  - info: host.IOBroker-Proxmox instance system.adapter.telegram.1 terminated with code null ()
                    2023-07-01 21:43:59.498  - warn: host.IOBroker-Proxmox instance system.adapter.alexa2.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.499  - info: host.IOBroker-Proxmox instance system.adapter.alexa2.0 terminated with code null ()
                    2023-07-01 21:43:59.587  - warn: host.IOBroker-Proxmox instance system.adapter.hmip.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.587  - info: host.IOBroker-Proxmox instance system.adapter.hmip.0 terminated with code null ()
                    2023-07-01 21:43:59.588  - warn: host.IOBroker-Proxmox instance system.adapter.mqtt.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.588  - info: host.IOBroker-Proxmox instance system.adapter.mqtt.0 terminated with code null ()
                    2023-07-01 21:43:59.619  - warn: host.IOBroker-Proxmox instance system.adapter.netatmo.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.619  - info: host.IOBroker-Proxmox instance system.adapter.netatmo.0 terminated with code null ()
                    2023-07-01 21:43:59.650  - error: host.IOBroker-Proxmox 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:
                    2023-07-01 21:43:59.650  - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed
                    2023-07-01 21:43:59.650  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    2023-07-01 21:43:59.651  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-07-01 21:43:59.651  - error: host.IOBroker-Proxmox Caught by controller[0]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                    2023-07-01 21:43:59.651  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                    2023-07-01 21:43:59.651  - warn: host.IOBroker-Proxmox instance system.adapter.shelly.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.651  - info: host.IOBroker-Proxmox instance system.adapter.shelly.0 terminated with code null ()
                    2023-07-01 21:43:59.737  - warn: host.IOBroker-Proxmox instance system.adapter.sonoff.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.737  - info: host.IOBroker-Proxmox instance system.adapter.sonoff.0 terminated with code null ()
                    2023-07-01 21:43:59.737  - warn: host.IOBroker-Proxmox instance system.adapter.nut.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.737  - info: host.IOBroker-Proxmox instance system.adapter.nut.0 terminated with code null ()
                    2023-07-01 21:43:59.768  - warn: host.IOBroker-Proxmox instance system.adapter.samsung.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.768  - info: host.IOBroker-Proxmox instance system.adapter.samsung.0 terminated with code null ()
                    2023-07-01 21:43:59.816  - warn: host.IOBroker-Proxmox instance system.adapter.tr-064.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.816  - info: host.IOBroker-Proxmox instance system.adapter.tr-064.0 terminated with code null ()
                    2023-07-01 21:43:59.892  - warn: host.IOBroker-Proxmox instance system.adapter.alarm.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.893  - info: host.IOBroker-Proxmox instance system.adapter.alarm.0 terminated with code null ()
                    2023-07-01 21:43:59.893  - warn: host.IOBroker-Proxmox instance system.adapter.alarm.1 terminated due to SIGTERM
                    2023-07-01 21:43:59.893  - info: host.IOBroker-Proxmox instance system.adapter.alarm.1 terminated with code null ()
                    2023-07-01 21:43:59.936  - warn: host.IOBroker-Proxmox instance system.adapter.alarm.2 terminated due to SIGTERM
                    2023-07-01 21:43:59.937  - info: host.IOBroker-Proxmox instance system.adapter.alarm.2 terminated with code null ()
                    2023-07-01 21:43:59.984  - warn: host.IOBroker-Proxmox instance system.adapter.amazon-dash.0 terminated due to SIGTERM
                    2023-07-01 21:43:59.984  - info: host.IOBroker-Proxmox instance system.adapter.amazon-dash.0 terminated with code null ()
                    2023-07-01 21:44:00.214  - warn: host.IOBroker-Proxmox instance system.adapter.backitup.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.215  - info: host.IOBroker-Proxmox instance system.adapter.backitup.0 terminated with code null ()
                    2023-07-01 21:44:00.216  - warn: host.IOBroker-Proxmox instance system.adapter.cloud.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.216  - info: host.IOBroker-Proxmox instance system.adapter.cloud.0 terminated with code null ()
                    2023-07-01 21:44:00.265  - warn: host.IOBroker-Proxmox instance system.adapter.device-reminder.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.265  - info: host.IOBroker-Proxmox instance system.adapter.device-reminder.0 terminated with code null ()
                    2023-07-01 21:44:00.326  - warn: host.IOBroker-Proxmox instance system.adapter.discovery.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.326  - info: host.IOBroker-Proxmox instance system.adapter.discovery.0 terminated with code null ()
                    2023-07-01 21:44:00.326  - warn: host.IOBroker-Proxmox instance system.adapter.enocean.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.327  - info: host.IOBroker-Proxmox instance system.adapter.enocean.0 terminated with code null ()
                    2023-07-01 21:44:00.383  - warn: host.IOBroker-Proxmox instance system.adapter.fb-checkpresence.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.384  - info: host.IOBroker-Proxmox instance system.adapter.fb-checkpresence.0 terminated with code null ()
                    2023-07-01 21:44:00.415  - warn: host.IOBroker-Proxmox instance system.adapter.homeconnect.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.415  - info: host.IOBroker-Proxmox instance system.adapter.homeconnect.0 terminated with code null ()
                    2023-07-01 21:44:00.497  - warn: host.IOBroker-Proxmox instance system.adapter.hue-extended.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.497  - info: host.IOBroker-Proxmox instance system.adapter.hue-extended.0 terminated with code null ()
                    2023-07-01 21:44:00.497  - warn: host.IOBroker-Proxmox instance system.adapter.info.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.497  - info: host.IOBroker-Proxmox instance system.adapter.info.0 terminated with code null ()
                    2023-07-01 21:44:00.528  - warn: host.IOBroker-Proxmox instance system.adapter.iot.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.528  - info: host.IOBroker-Proxmox instance system.adapter.iot.0 terminated with code null ()
                    2023-07-01 21:44:00.557  - warn: host.IOBroker-Proxmox instance system.adapter.octoprint.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.557  - info: host.IOBroker-Proxmox instance system.adapter.octoprint.0 terminated with code null ()
                    2023-07-01 21:44:00.645  - warn: host.IOBroker-Proxmox instance system.adapter.pushsafer.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.645  - info: host.IOBroker-Proxmox instance system.adapter.pushsafer.0 terminated with code null ()
                    2023-07-01 21:44:00.646  - warn: host.IOBroker-Proxmox instance system.adapter.sourceanalytix.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.646  - info: host.IOBroker-Proxmox instance system.adapter.sourceanalytix.0 terminated with code null ()
                    2023-07-01 21:44:00.676  - warn: host.IOBroker-Proxmox instance system.adapter.text2command.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.676  - info: host.IOBroker-Proxmox instance system.adapter.text2command.0 terminated with code null ()
                    2023-07-01 21:44:00.707  - warn: host.IOBroker-Proxmox instance system.adapter.trashschedule.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.707  - info: host.IOBroker-Proxmox instance system.adapter.trashschedule.0 terminated with code null ()
                    2023-07-01 21:44:00.800  - warn: host.IOBroker-Proxmox instance system.adapter.web.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.801  - info: host.IOBroker-Proxmox instance system.adapter.web.0 terminated with code null ()
                    2023-07-01 21:44:00.801  - warn: host.IOBroker-Proxmox instance system.adapter.zwave2.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.801  - info: host.IOBroker-Proxmox instance system.adapter.zwave2.0 terminated with code null ()
                    2023-07-01 21:44:00.831  - warn: host.IOBroker-Proxmox instance system.adapter.proxmox.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.832  - info: host.IOBroker-Proxmox instance system.adapter.proxmox.0 terminated with code null ()
                    2023-07-01 21:44:00.861  - warn: host.IOBroker-Proxmox instance system.adapter.worx.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.861  - info: host.IOBroker-Proxmox instance system.adapter.worx.0 terminated with code null ()
                    2023-07-01 21:44:00.958  - warn: host.IOBroker-Proxmox instance system.adapter.senec.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.958  - info: host.IOBroker-Proxmox instance system.adapter.senec.0 terminated with code null ()
                    2023-07-01 21:44:00.958  - warn: host.IOBroker-Proxmox instance system.adapter.accuweather.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.958  - info: host.IOBroker-Proxmox instance system.adapter.accuweather.0 terminated with code null ()
                    2023-07-01 21:44:00.986  - warn: host.IOBroker-Proxmox instance system.adapter.energiefluss.0 terminated due to SIGTERM
                    2023-07-01 21:44:00.987  - info: host.IOBroker-Proxmox instance system.adapter.energiefluss.0 terminated with code null ()
                    2023-07-01 21:44:01.070  - warn: host.IOBroker-Proxmox instance system.adapter.javascript.0 terminated due to SIGTERM
                    2023-07-01 21:44:01.071  - info: host.IOBroker-Proxmox instance system.adapter.javascript.0 terminated with code null ()
                    2023-07-01 21:44:01.071  - warn: host.IOBroker-Proxmox instance system.adapter.zigbee.0 terminated due to SIGTERM
                    2023-07-01 21:44:01.071  - info: host.IOBroker-Proxmox instance system.adapter.zigbee.0 terminated with code null ()
                    2023-07-01 21:44:01.100  - warn: host.IOBroker-Proxmox instance system.adapter.jarvis.0 terminated due to SIGTERM
                    2023-07-01 21:44:01.100  - info: host.IOBroker-Proxmox instance system.adapter.jarvis.0 terminated with code null ()
                    2023-07-01 21:44:01.444  - error: host.IOBroker-Proxmox 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:
                    2023-07-01 21:44:01.444  - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed
                    2023-07-01 21:44:01.445  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                    2023-07-01 21:44:01.445  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                    2023-07-01 21:44:01.445  - error: host.IOBroker-Proxmox Caught by controller[0]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                    2023-07-01 21:44:01.445  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                    2023-07-01 21:44:01.445  - warn: host.IOBroker-Proxmox instance system.adapter.shelly.1 terminated due to SIGTERM
                    2023-07-01 21:44:01.445  - info: host.IOBroker-Proxmox instance system.adapter.shelly.1 terminated with code null ()
                    2023-07-01 21:44:01.474  - info: host.IOBroker-Proxmox instance system.adapter.ham.0 terminated with code 0 (NO_ERROR)
                    2023-07-01 21:44:01.508  - info: host.IOBroker-Proxmox instance system.adapter.history.0 terminated with code 0 (NO_ERROR)
                    2023-07-01 21:44:01.508  - info: host.IOBroker-Proxmox All instances are stopped.
                    2023-07-01 21:44:01.645  - info: host.IOBroker-Proxmox terminated
                    2023-07-01 21:44:13.180  - info: host.IOBroker-Proxmox iobroker.js-controller version 5.0.5 js-controller starting
                    2023-07-01 21:44:13.191  - info: host.IOBroker-Proxmox Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
                    2023-07-01 21:44:13.192  - info: host.IOBroker-Proxmox hostname: IOBroker-Proxmox, node: v18.16.1
                    2023-07-01 21:44:13.193  - info: host.IOBroker-Proxmox ip addresses: 192.168.171.35 fe80::a8d4:caff:fe76:9b25
                    2023-07-01 21:44:15.377  - info: host.IOBroker-Proxmox connected to Objects and States
                    2023-07-01 21:44:15.472  - info: host.IOBroker-Proxmox added notifications configuration of host
                    2023-07-01 21:44:16.711  - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.nodeCurrent"
                    2023-07-01 21:44:16.713  - info: host.IOBroker-Proxmox 52 instances found
                    2023-07-01 21:44:16.799  - info: host.IOBroker-Proxmox starting 47 instances
                    2023-07-01 21:44:16.985  - info: host.IOBroker-Proxmox instance system.adapter.admin.0 started with pid 304
                    2023-07-01 21:44:17.000  - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.nodeNewest"
                    2023-07-01 21:44:17.006  - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.nodeNewestNext"
                    2023-07-01 21:44:17.012  - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.npmCurrent"
                    2023-07-01 21:44:17.018  - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.npmNewest"
                    2023-07-01 21:44:17.024  - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.npmNewestNext"
                    2023-07-01 21:44:17.029  - info: host.IOBroker-Proxmox Some obsolete host states deleted.
                    2023-07-01 21:44:19.599  - info: admin.0 (304) starting. Version 6.5.9 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.1, js-controller: 5.0.5
                    2023-07-01 21:44:19.765  - info: admin.0 (304) requesting all states
                    2023-07-01 21:44:19.766  - info: admin.0 (304) requesting all objects
                    2023-07-01 21:44:22.115  - info: admin.0 (304) Request actual repository...
                    2023-07-01 21:44:23.321  - info: host.IOBroker-Proxmox instance system.adapter.admin.1 started with pid 355
                    2023-07-01 21:44:24.625  - info: admin.0 (304) received all objects
                    2023-07-01 21:44:25.318  - info: admin.0 (304) Secure socket.io server listening on port 8081
                    2023-07-01 21:44:25.334  - info: admin.0 (304) https server listening on port 8081
                    2023-07-01 21:44:25.335  - info: admin.0 (304) Use link "https://127.0.0.1:8081" to configure.
                    2023-07-01 21:44:25.376  - info: host.IOBroker-Proxmox instance system.adapter.email.0 started with pid 362
                    2023-07-01 21:44:26.648  - info: host.IOBroker-Proxmox Updating repository "Alternativ latest" under "http://iobroker.live/repo/sources-dist-latest.json"
                    2023-07-01 21:44:29.259  - info: admin.0 (304) Repository received successfully.
                    2023-07-01 21:44:30.667  - info: host.IOBroker-Proxmox instance system.adapter.history.0 started with pid 392
                    2023-07-01 21:44:31.973  - info: admin.1 (355) starting. Version 6.5.9 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.1, js-controller: 5.0.5
                    2023-07-01 21:44:32.192  - info: admin.1 (355) requesting all states
                    2023-07-01 21:44:32.199  - info: admin.1 (355) requesting all objects
                    2023-07-01 21:44:32.676  - info: email.0 (362) starting. Version 1.2.0 in /opt/iobroker/node_modules/iobroker.email, node: v18.16.1, js-controller: 5.0.5
                    2023-07-01 21:44:31.973  - info: admin.1 (355) starting. Version 6.5.9 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.1, js-controller: 5.0.5
                    2023-07-01 21:44:32.192  - info: admin.1 (355) requesting all states
                    2023-07-01 21:44:32.199  - info: admin.1 (355) requesting all objects
                    2023-07-01 21:44:32.676  - info: email.0 (362) starting. Version 1.2.0 in /opt/iobroker/node_modules/iobroker.email, node: v18.16.1, js-controller: 5.0.5
                    2023-07-01 21:44:35.881  - info: host.IOBroker-Proxmox instance system.adapter.javascript.0 started with pid 423
                    2023-07-01 21:44:37.586  - info: admin.1 (355) received all objects
                    2023-07-01 21:44:38.014  - info: host.IOBroker-Proxmox instance system.adapter.telegram.0 started with pid 430
                    2023-07-01 21:44:38.216  - info: admin.1 (355) Request actual repository...
                    2023-07-01 21:44:38.721  - info: admin.1 (355) socket.io server listening on port 8088
                    2023-07-01 21:44:38.744  - info: admin.1 (355) http server listening on port 8088
                    2023-07-01 21:44:38.744  - info: admin.1 (355) Use link "http://127.0.0.1:8088" to configure.
                    2023-07-01 21:44:39.198  - info: host.IOBroker-Proxmox Updating repository "Alternativ latest" under "http://iobroker.live/repo/sources-dist-latest.json"
                    2023-07-01 21:44:39.425  - info: history.0 (392) starting. Version 2.2.4 in /opt/iobroker/node_modules/iobroker.history, node: v18.16.1, js-controller: 5.0.5
                    2023-07-01 21:44:39.762  - info: history.0 (392) enabled logging of alias.0.Steckdosen.Steckdose Datenschrank.value_electric_w_consumed (Count=1), Alias=false
                    2023-07-01 21:44:39.769  - info: history.0 (392) enabled logging of alias.0.Steckdosen.Steckdose_Geschirrspüler.Power (Count=2), Alias=false
                    2023-07-01 21:44:39.770  - info: history.0 (392) enabled logging of alias.0.Steckdosen.Steckdose_Trockner.ENERGY_Power (Count=3), Alias=false
                    2023-07-01 21:44:39.771  - info: history.0 (392) enabled logging of shelly.0.SHPLG-S#9D8C29#1.Relay0.Power (Count=4), Alias=false
                    2023-07-01 21:44:39.772  - info: history.0 (392) enabled logging of sonoff.0.Trockner.ENERGY_Power (Count=5), Alias=false
                    2023-07-01 21:44:39.772  - info: history.0 (392) enabled logging of fb-checkpresence.0.Nadine (Count=6), Alias=false
                    2023-07-01 21:44:39.773  - info: history.0 (392) enabled logging of fb-checkpresence.0.Andre (Count=7), Alias=false
                    2023-07-01 21:44:37.586  - info: admin.1 (355) received all objects
                    2023-07-01 21:44:38.014  - info: host.IOBroker-Proxmox instance system.adapter.telegram.0 started with pid 430
                    
                    
                    
                    Thomas BraunT 1 Antwort Letzte Antwort
                    0
                    • gelberlemmyG gelberlemmy

                      @thomas-braun so jetzt aber. Ich hoffe ich habe alles mitbekommen.

                      2023-07-01 21:43:53.082  - warn: shelly.0 (556) redis get shelly.0.SHUNI-1#349454790800#1.Relay0.Timer, error - DB closed
                      2023-07-01 21:43:53.165  - info: hue-extended.0 (832) terminating
                      2023-07-01 21:43:53.170  - warn: shelly.0 (556) get state error: Connection is closed.
                      2023-07-01 21:43:53.218  - info: hue-extended.0 (832) terminating with timeout
                      2023-07-01 21:43:53.298  - warn: shelly.0 (556) get state error: Connection is closed.
                      2023-07-01 21:43:53.301  - error: shelly.0 (556) 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().
                      2023-07-01 21:43:53.306  - error: shelly.0 (556) unhandled promise rejection: DB closed
                      2023-07-01 21:43:53.772  - error: shelly.0 (556) Error: DB closed
                          at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                          at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                          at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                      2023-07-01 21:43:53.772  - error: shelly.0 (556) DB closed
                      2023-07-01 21:43:53.796  - warn: shelly.0 (556) redis get shelly.0.SHSW-25#3494546A140D#1.Relay1.Timer, error - Connection is closed.
                      2023-07-01 21:43:53.796  - warn: shelly.0 (556) redis get shelly.0.SHUNI-1#349454790800#1.Relay1.Timer, error - Connection is closed.
                      2023-07-01 21:43:54.091  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.095  - warn: shelly.1 (631) get state error: Connection is closed.
                      2023-07-01 21:43:54.130  - info: host.IOBroker-Proxmox stopInstance system.adapter.admin.0 killing pid 304
                      2023-07-01 21:43:54.133  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.146  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.147  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.148  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.149  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.150  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.151  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.152  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.153  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.154  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.184  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.185  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.186  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.187  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.197  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.198  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.199  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.200  - warn: zigbee.0 (592) get state error: Connection is closed.
                      2023-07-01 21:43:54.132  - info: host.IOBroker-Proxmox stopInstance system.adapter.admin.1 killing pid 331
                      2023-07-01 21:43:54.134  - info: host.IOBroker-Proxmox stopInstance system.adapter.email.0 killing pid 338
                      2023-07-01 21:43:54.160  - info: host.IOBroker-Proxmox stopInstance system.adapter.javascript.0 killing pid 384
                      2023-07-01 21:43:54.160  - info: host.IOBroker-Proxmox stopInstance system.adapter.telegram.0 killing pid 395
                      2023-07-01 21:43:54.160  - info: host.IOBroker-Proxmox stopInstance system.adapter.telegram.1 killing pid 406
                      2023-07-01 21:43:54.175  - info: host.IOBroker-Proxmox stopInstance system.adapter.alexa2.0 killing pid 421
                      2023-07-01 21:43:54.200  - info: host.IOBroker-Proxmox stopInstance system.adapter.ham.0 killing pid 440
                      2023-07-01 21:43:54.214  - info: host.IOBroker-Proxmox stopInstance system.adapter.hmip.0 killing pid 451
                      2023-07-01 21:43:54.217  - info: host.IOBroker-Proxmox stopInstance system.adapter.mqtt.0 killing pid 497
                      2023-07-01 21:43:54.217  - info: host.IOBroker-Proxmox stopInstance system.adapter.netatmo.0 killing pid 548
                      2023-07-01 21:43:54.217  - info: host.IOBroker-Proxmox stopInstance system.adapter.shelly.0 killing pid 556
                      2023-07-01 21:43:54.217  - info: host.IOBroker-Proxmox stopInstance system.adapter.sonoff.0 killing pid 573
                      2023-07-01 21:43:54.218  - info: host.IOBroker-Proxmox stopInstance system.adapter.zigbee.0 killing pid 592
                      2023-07-01 21:43:54.218  - info: host.IOBroker-Proxmox stopInstance system.adapter.nut.0 killing pid 605
                      2023-07-01 21:43:54.218  - info: host.IOBroker-Proxmox stopInstance system.adapter.samsung.0 killing pid 624
                      2023-07-01 21:43:54.219  - info: host.IOBroker-Proxmox stopInstance system.adapter.shelly.1 killing pid 631
                      2023-07-01 21:43:54.219  - info: host.IOBroker-Proxmox stopInstance system.adapter.tr-064.0 killing pid 650
                      2023-07-01 21:43:54.222  - info: host.IOBroker-Proxmox stopInstance system.adapter.alarm.0 killing pid 665
                      2023-07-01 21:43:54.225  - info: host.IOBroker-Proxmox stopInstance system.adapter.alarm.1 killing pid 688
                      2023-07-01 21:43:54.225  - info: host.IOBroker-Proxmox stopInstance system.adapter.alarm.2 killing pid 699
                      2023-07-01 21:43:54.227  - info: host.IOBroker-Proxmox stopInstance system.adapter.amazon-dash.0 killing pid 719
                      2023-07-01 21:43:54.227  - info: host.IOBroker-Proxmox stopInstance system.adapter.backitup.0 killing pid 743
                      2023-07-01 21:43:54.228  - info: host.IOBroker-Proxmox stopInstance system.adapter.cloud.0 killing pid 754
                      2023-07-01 21:43:54.230  - info: host.IOBroker-Proxmox stopInstance system.adapter.device-reminder.0 killing pid 765
                      2023-07-01 21:43:54.269  - info: host.IOBroker-Proxmox stopInstance system.adapter.discovery.0 killing pid 776
                      2023-07-01 21:43:54.269  - info: host.IOBroker-Proxmox stopInstance system.adapter.enocean.0 killing pid 791
                      2023-07-01 21:43:54.272  - info: host.IOBroker-Proxmox stopInstance system.adapter.fb-checkpresence.0 killing pid 802
                      2023-07-01 21:43:54.272  - info: host.IOBroker-Proxmox stopInstance system.adapter.homeconnect.0 killing pid 813
                      2023-07-01 21:43:54.272  - info: host.IOBroker-Proxmox stopInstance system.adapter.hue-extended.0 killing pid 832
                      2023-07-01 21:43:54.273  - info: host.IOBroker-Proxmox stopInstance system.adapter.info.0 killing pid 843
                      2023-07-01 21:43:54.276  - info: host.IOBroker-Proxmox stopInstance system.adapter.iot.0 killing pid 858
                      2023-07-01 21:43:54.278  - info: host.IOBroker-Proxmox stopInstance system.adapter.octoprint.0 killing pid 885
                      2023-07-01 21:43:54.280  - info: host.IOBroker-Proxmox stopInstance system.adapter.pushsafer.0 killing pid 904
                      2023-07-01 21:43:54.282  - info: host.IOBroker-Proxmox stopInstance system.adapter.sourceanalytix.0 killing pid 924
                      2023-07-01 21:43:54.284  - info: host.IOBroker-Proxmox stopInstance system.adapter.text2command.0 killing pid 939
                      2023-07-01 21:43:54.285  - info: host.IOBroker-Proxmox stopInstance system.adapter.trashschedule.0 killing pid 954
                      2023-07-01 21:43:54.285  - info: host.IOBroker-Proxmox stopInstance system.adapter.web.0 killing pid 969
                      2023-07-01 21:43:54.285  - info: host.IOBroker-Proxmox stopInstance system.adapter.zwave2.0 killing pid 980
                      2023-07-01 21:43:54.285  - info: host.IOBroker-Proxmox stopInstance system.adapter.proxmox.0 killing pid 987
                      2023-07-01 21:43:54.367  - info: host.IOBroker-Proxmox stopInstance system.adapter.worx.0 killing pid 1002
                      2023-07-01 21:43:54.367  - info: host.IOBroker-Proxmox stopInstance system.adapter.senec.0 killing pid 1013
                      2023-07-01 21:43:54.441  - info: host.IOBroker-Proxmox stopInstance system.adapter.accuweather.0 killing pid 1028
                      2023-07-01 21:43:54.442  - info: host.IOBroker-Proxmox stopInstance system.adapter.jarvis.0 killing pid 1039
                      2023-07-01 21:43:54.464  - info: host.IOBroker-Proxmox stopInstance system.adapter.energiefluss.0 killing pid 1050
                      2023-07-01 21:43:54.097  - error: shelly.1 (631) 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().
                      2023-07-01 21:43:54.098  - error: shelly.1 (631) unhandled promise rejection: DB closed
                      2023-07-01 21:43:55.069  - error: shelly.1 (631) Error: DB closed
                          at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                          at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                          at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                          at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                      2023-07-01 21:43:55.069  - error: shelly.1 (631) DB closed
                      2023-07-01 21:43:59.300  - warn: host.IOBroker-Proxmox instance system.adapter.admin.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.300  - info: host.IOBroker-Proxmox instance system.adapter.admin.0 terminated with code null ()
                      2023-07-01 21:43:59.348  - warn: host.IOBroker-Proxmox instance system.adapter.admin.1 terminated due to SIGTERM
                      2023-07-01 21:43:59.348  - info: host.IOBroker-Proxmox instance system.adapter.admin.1 terminated with code null ()
                      2023-07-01 21:43:59.419  - warn: host.IOBroker-Proxmox instance system.adapter.email.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.419  - info: host.IOBroker-Proxmox instance system.adapter.email.0 terminated with code null ()
                      2023-07-01 21:43:59.419  - warn: host.IOBroker-Proxmox instance system.adapter.telegram.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.420  - info: host.IOBroker-Proxmox instance system.adapter.telegram.0 terminated with code null ()
                      2023-07-01 21:43:59.467  - warn: host.IOBroker-Proxmox instance system.adapter.telegram.1 terminated due to SIGTERM
                      2023-07-01 21:43:59.467  - info: host.IOBroker-Proxmox instance system.adapter.telegram.1 terminated with code null ()
                      2023-07-01 21:43:59.498  - warn: host.IOBroker-Proxmox instance system.adapter.alexa2.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.499  - info: host.IOBroker-Proxmox instance system.adapter.alexa2.0 terminated with code null ()
                      2023-07-01 21:43:59.587  - warn: host.IOBroker-Proxmox instance system.adapter.hmip.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.587  - info: host.IOBroker-Proxmox instance system.adapter.hmip.0 terminated with code null ()
                      2023-07-01 21:43:59.588  - warn: host.IOBroker-Proxmox instance system.adapter.mqtt.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.588  - info: host.IOBroker-Proxmox instance system.adapter.mqtt.0 terminated with code null ()
                      2023-07-01 21:43:59.619  - warn: host.IOBroker-Proxmox instance system.adapter.netatmo.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.619  - info: host.IOBroker-Proxmox instance system.adapter.netatmo.0 terminated with code null ()
                      2023-07-01 21:43:59.650  - error: host.IOBroker-Proxmox 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:
                      2023-07-01 21:43:59.650  - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed
                      2023-07-01 21:43:59.650  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                      2023-07-01 21:43:59.651  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                      2023-07-01 21:43:59.651  - error: host.IOBroker-Proxmox Caught by controller[0]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                      2023-07-01 21:43:59.651  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                      2023-07-01 21:43:59.651  - warn: host.IOBroker-Proxmox instance system.adapter.shelly.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.651  - info: host.IOBroker-Proxmox instance system.adapter.shelly.0 terminated with code null ()
                      2023-07-01 21:43:59.737  - warn: host.IOBroker-Proxmox instance system.adapter.sonoff.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.737  - info: host.IOBroker-Proxmox instance system.adapter.sonoff.0 terminated with code null ()
                      2023-07-01 21:43:59.737  - warn: host.IOBroker-Proxmox instance system.adapter.nut.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.737  - info: host.IOBroker-Proxmox instance system.adapter.nut.0 terminated with code null ()
                      2023-07-01 21:43:59.768  - warn: host.IOBroker-Proxmox instance system.adapter.samsung.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.768  - info: host.IOBroker-Proxmox instance system.adapter.samsung.0 terminated with code null ()
                      2023-07-01 21:43:59.816  - warn: host.IOBroker-Proxmox instance system.adapter.tr-064.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.816  - info: host.IOBroker-Proxmox instance system.adapter.tr-064.0 terminated with code null ()
                      2023-07-01 21:43:59.892  - warn: host.IOBroker-Proxmox instance system.adapter.alarm.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.893  - info: host.IOBroker-Proxmox instance system.adapter.alarm.0 terminated with code null ()
                      2023-07-01 21:43:59.893  - warn: host.IOBroker-Proxmox instance system.adapter.alarm.1 terminated due to SIGTERM
                      2023-07-01 21:43:59.893  - info: host.IOBroker-Proxmox instance system.adapter.alarm.1 terminated with code null ()
                      2023-07-01 21:43:59.936  - warn: host.IOBroker-Proxmox instance system.adapter.alarm.2 terminated due to SIGTERM
                      2023-07-01 21:43:59.937  - info: host.IOBroker-Proxmox instance system.adapter.alarm.2 terminated with code null ()
                      2023-07-01 21:43:59.984  - warn: host.IOBroker-Proxmox instance system.adapter.amazon-dash.0 terminated due to SIGTERM
                      2023-07-01 21:43:59.984  - info: host.IOBroker-Proxmox instance system.adapter.amazon-dash.0 terminated with code null ()
                      2023-07-01 21:44:00.214  - warn: host.IOBroker-Proxmox instance system.adapter.backitup.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.215  - info: host.IOBroker-Proxmox instance system.adapter.backitup.0 terminated with code null ()
                      2023-07-01 21:44:00.216  - warn: host.IOBroker-Proxmox instance system.adapter.cloud.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.216  - info: host.IOBroker-Proxmox instance system.adapter.cloud.0 terminated with code null ()
                      2023-07-01 21:44:00.265  - warn: host.IOBroker-Proxmox instance system.adapter.device-reminder.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.265  - info: host.IOBroker-Proxmox instance system.adapter.device-reminder.0 terminated with code null ()
                      2023-07-01 21:44:00.326  - warn: host.IOBroker-Proxmox instance system.adapter.discovery.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.326  - info: host.IOBroker-Proxmox instance system.adapter.discovery.0 terminated with code null ()
                      2023-07-01 21:44:00.326  - warn: host.IOBroker-Proxmox instance system.adapter.enocean.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.327  - info: host.IOBroker-Proxmox instance system.adapter.enocean.0 terminated with code null ()
                      2023-07-01 21:44:00.383  - warn: host.IOBroker-Proxmox instance system.adapter.fb-checkpresence.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.384  - info: host.IOBroker-Proxmox instance system.adapter.fb-checkpresence.0 terminated with code null ()
                      2023-07-01 21:44:00.415  - warn: host.IOBroker-Proxmox instance system.adapter.homeconnect.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.415  - info: host.IOBroker-Proxmox instance system.adapter.homeconnect.0 terminated with code null ()
                      2023-07-01 21:44:00.497  - warn: host.IOBroker-Proxmox instance system.adapter.hue-extended.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.497  - info: host.IOBroker-Proxmox instance system.adapter.hue-extended.0 terminated with code null ()
                      2023-07-01 21:44:00.497  - warn: host.IOBroker-Proxmox instance system.adapter.info.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.497  - info: host.IOBroker-Proxmox instance system.adapter.info.0 terminated with code null ()
                      2023-07-01 21:44:00.528  - warn: host.IOBroker-Proxmox instance system.adapter.iot.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.528  - info: host.IOBroker-Proxmox instance system.adapter.iot.0 terminated with code null ()
                      2023-07-01 21:44:00.557  - warn: host.IOBroker-Proxmox instance system.adapter.octoprint.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.557  - info: host.IOBroker-Proxmox instance system.adapter.octoprint.0 terminated with code null ()
                      2023-07-01 21:44:00.645  - warn: host.IOBroker-Proxmox instance system.adapter.pushsafer.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.645  - info: host.IOBroker-Proxmox instance system.adapter.pushsafer.0 terminated with code null ()
                      2023-07-01 21:44:00.646  - warn: host.IOBroker-Proxmox instance system.adapter.sourceanalytix.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.646  - info: host.IOBroker-Proxmox instance system.adapter.sourceanalytix.0 terminated with code null ()
                      2023-07-01 21:44:00.676  - warn: host.IOBroker-Proxmox instance system.adapter.text2command.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.676  - info: host.IOBroker-Proxmox instance system.adapter.text2command.0 terminated with code null ()
                      2023-07-01 21:44:00.707  - warn: host.IOBroker-Proxmox instance system.adapter.trashschedule.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.707  - info: host.IOBroker-Proxmox instance system.adapter.trashschedule.0 terminated with code null ()
                      2023-07-01 21:44:00.800  - warn: host.IOBroker-Proxmox instance system.adapter.web.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.801  - info: host.IOBroker-Proxmox instance system.adapter.web.0 terminated with code null ()
                      2023-07-01 21:44:00.801  - warn: host.IOBroker-Proxmox instance system.adapter.zwave2.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.801  - info: host.IOBroker-Proxmox instance system.adapter.zwave2.0 terminated with code null ()
                      2023-07-01 21:44:00.831  - warn: host.IOBroker-Proxmox instance system.adapter.proxmox.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.832  - info: host.IOBroker-Proxmox instance system.adapter.proxmox.0 terminated with code null ()
                      2023-07-01 21:44:00.861  - warn: host.IOBroker-Proxmox instance system.adapter.worx.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.861  - info: host.IOBroker-Proxmox instance system.adapter.worx.0 terminated with code null ()
                      2023-07-01 21:44:00.958  - warn: host.IOBroker-Proxmox instance system.adapter.senec.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.958  - info: host.IOBroker-Proxmox instance system.adapter.senec.0 terminated with code null ()
                      2023-07-01 21:44:00.958  - warn: host.IOBroker-Proxmox instance system.adapter.accuweather.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.958  - info: host.IOBroker-Proxmox instance system.adapter.accuweather.0 terminated with code null ()
                      2023-07-01 21:44:00.986  - warn: host.IOBroker-Proxmox instance system.adapter.energiefluss.0 terminated due to SIGTERM
                      2023-07-01 21:44:00.987  - info: host.IOBroker-Proxmox instance system.adapter.energiefluss.0 terminated with code null ()
                      2023-07-01 21:44:01.070  - warn: host.IOBroker-Proxmox instance system.adapter.javascript.0 terminated due to SIGTERM
                      2023-07-01 21:44:01.071  - info: host.IOBroker-Proxmox instance system.adapter.javascript.0 terminated with code null ()
                      2023-07-01 21:44:01.071  - warn: host.IOBroker-Proxmox instance system.adapter.zigbee.0 terminated due to SIGTERM
                      2023-07-01 21:44:01.071  - info: host.IOBroker-Proxmox instance system.adapter.zigbee.0 terminated with code null ()
                      2023-07-01 21:44:01.100  - warn: host.IOBroker-Proxmox instance system.adapter.jarvis.0 terminated due to SIGTERM
                      2023-07-01 21:44:01.100  - info: host.IOBroker-Proxmox instance system.adapter.jarvis.0 terminated with code null ()
                      2023-07-01 21:44:01.444  - error: host.IOBroker-Proxmox 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:
                      2023-07-01 21:44:01.444  - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed
                      2023-07-01 21:44:01.445  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                      2023-07-01 21:44:01.445  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                      2023-07-01 21:44:01.445  - error: host.IOBroker-Proxmox Caught by controller[0]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                      2023-07-01 21:44:01.445  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                      2023-07-01 21:44:01.445  - warn: host.IOBroker-Proxmox instance system.adapter.shelly.1 terminated due to SIGTERM
                      2023-07-01 21:44:01.445  - info: host.IOBroker-Proxmox instance system.adapter.shelly.1 terminated with code null ()
                      2023-07-01 21:44:01.474  - info: host.IOBroker-Proxmox instance system.adapter.ham.0 terminated with code 0 (NO_ERROR)
                      2023-07-01 21:44:01.508  - info: host.IOBroker-Proxmox instance system.adapter.history.0 terminated with code 0 (NO_ERROR)
                      2023-07-01 21:44:01.508  - info: host.IOBroker-Proxmox All instances are stopped.
                      2023-07-01 21:44:01.645  - info: host.IOBroker-Proxmox terminated
                      2023-07-01 21:44:13.180  - info: host.IOBroker-Proxmox iobroker.js-controller version 5.0.5 js-controller starting
                      2023-07-01 21:44:13.191  - info: host.IOBroker-Proxmox Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
                      2023-07-01 21:44:13.192  - info: host.IOBroker-Proxmox hostname: IOBroker-Proxmox, node: v18.16.1
                      2023-07-01 21:44:13.193  - info: host.IOBroker-Proxmox ip addresses: 192.168.171.35 fe80::a8d4:caff:fe76:9b25
                      2023-07-01 21:44:15.377  - info: host.IOBroker-Proxmox connected to Objects and States
                      2023-07-01 21:44:15.472  - info: host.IOBroker-Proxmox added notifications configuration of host
                      2023-07-01 21:44:16.711  - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.nodeCurrent"
                      2023-07-01 21:44:16.713  - info: host.IOBroker-Proxmox 52 instances found
                      2023-07-01 21:44:16.799  - info: host.IOBroker-Proxmox starting 47 instances
                      2023-07-01 21:44:16.985  - info: host.IOBroker-Proxmox instance system.adapter.admin.0 started with pid 304
                      2023-07-01 21:44:17.000  - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.nodeNewest"
                      2023-07-01 21:44:17.006  - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.nodeNewestNext"
                      2023-07-01 21:44:17.012  - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.npmCurrent"
                      2023-07-01 21:44:17.018  - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.npmNewest"
                      2023-07-01 21:44:17.024  - info: host.IOBroker-Proxmox Delete state "system.host.IOBroker-Proxmox.versions.npmNewestNext"
                      2023-07-01 21:44:17.029  - info: host.IOBroker-Proxmox Some obsolete host states deleted.
                      2023-07-01 21:44:19.599  - info: admin.0 (304) starting. Version 6.5.9 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.1, js-controller: 5.0.5
                      2023-07-01 21:44:19.765  - info: admin.0 (304) requesting all states
                      2023-07-01 21:44:19.766  - info: admin.0 (304) requesting all objects
                      2023-07-01 21:44:22.115  - info: admin.0 (304) Request actual repository...
                      2023-07-01 21:44:23.321  - info: host.IOBroker-Proxmox instance system.adapter.admin.1 started with pid 355
                      2023-07-01 21:44:24.625  - info: admin.0 (304) received all objects
                      2023-07-01 21:44:25.318  - info: admin.0 (304) Secure socket.io server listening on port 8081
                      2023-07-01 21:44:25.334  - info: admin.0 (304) https server listening on port 8081
                      2023-07-01 21:44:25.335  - info: admin.0 (304) Use link "https://127.0.0.1:8081" to configure.
                      2023-07-01 21:44:25.376  - info: host.IOBroker-Proxmox instance system.adapter.email.0 started with pid 362
                      2023-07-01 21:44:26.648  - info: host.IOBroker-Proxmox Updating repository "Alternativ latest" under "http://iobroker.live/repo/sources-dist-latest.json"
                      2023-07-01 21:44:29.259  - info: admin.0 (304) Repository received successfully.
                      2023-07-01 21:44:30.667  - info: host.IOBroker-Proxmox instance system.adapter.history.0 started with pid 392
                      2023-07-01 21:44:31.973  - info: admin.1 (355) starting. Version 6.5.9 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.1, js-controller: 5.0.5
                      2023-07-01 21:44:32.192  - info: admin.1 (355) requesting all states
                      2023-07-01 21:44:32.199  - info: admin.1 (355) requesting all objects
                      2023-07-01 21:44:32.676  - info: email.0 (362) starting. Version 1.2.0 in /opt/iobroker/node_modules/iobroker.email, node: v18.16.1, js-controller: 5.0.5
                      2023-07-01 21:44:31.973  - info: admin.1 (355) starting. Version 6.5.9 in /opt/iobroker/node_modules/iobroker.admin, node: v18.16.1, js-controller: 5.0.5
                      2023-07-01 21:44:32.192  - info: admin.1 (355) requesting all states
                      2023-07-01 21:44:32.199  - info: admin.1 (355) requesting all objects
                      2023-07-01 21:44:32.676  - info: email.0 (362) starting. Version 1.2.0 in /opt/iobroker/node_modules/iobroker.email, node: v18.16.1, js-controller: 5.0.5
                      2023-07-01 21:44:35.881  - info: host.IOBroker-Proxmox instance system.adapter.javascript.0 started with pid 423
                      2023-07-01 21:44:37.586  - info: admin.1 (355) received all objects
                      2023-07-01 21:44:38.014  - info: host.IOBroker-Proxmox instance system.adapter.telegram.0 started with pid 430
                      2023-07-01 21:44:38.216  - info: admin.1 (355) Request actual repository...
                      2023-07-01 21:44:38.721  - info: admin.1 (355) socket.io server listening on port 8088
                      2023-07-01 21:44:38.744  - info: admin.1 (355) http server listening on port 8088
                      2023-07-01 21:44:38.744  - info: admin.1 (355) Use link "http://127.0.0.1:8088" to configure.
                      2023-07-01 21:44:39.198  - info: host.IOBroker-Proxmox Updating repository "Alternativ latest" under "http://iobroker.live/repo/sources-dist-latest.json"
                      2023-07-01 21:44:39.425  - info: history.0 (392) starting. Version 2.2.4 in /opt/iobroker/node_modules/iobroker.history, node: v18.16.1, js-controller: 5.0.5
                      2023-07-01 21:44:39.762  - info: history.0 (392) enabled logging of alias.0.Steckdosen.Steckdose Datenschrank.value_electric_w_consumed (Count=1), Alias=false
                      2023-07-01 21:44:39.769  - info: history.0 (392) enabled logging of alias.0.Steckdosen.Steckdose_Geschirrspüler.Power (Count=2), Alias=false
                      2023-07-01 21:44:39.770  - info: history.0 (392) enabled logging of alias.0.Steckdosen.Steckdose_Trockner.ENERGY_Power (Count=3), Alias=false
                      2023-07-01 21:44:39.771  - info: history.0 (392) enabled logging of shelly.0.SHPLG-S#9D8C29#1.Relay0.Power (Count=4), Alias=false
                      2023-07-01 21:44:39.772  - info: history.0 (392) enabled logging of sonoff.0.Trockner.ENERGY_Power (Count=5), Alias=false
                      2023-07-01 21:44:39.772  - info: history.0 (392) enabled logging of fb-checkpresence.0.Nadine (Count=6), Alias=false
                      2023-07-01 21:44:39.773  - info: history.0 (392) enabled logging of fb-checkpresence.0.Andre (Count=7), Alias=false
                      2023-07-01 21:44:37.586  - info: admin.1 (355) received all objects
                      2023-07-01 21:44:38.014  - info: host.IOBroker-Proxmox instance system.adapter.telegram.0 started with pid 430
                      
                      
                      
                      Thomas BraunT Online
                      Thomas BraunT Online
                      Thomas Braun
                      Most Active
                      schrieb am zuletzt editiert von
                      #155

                      @gelberlemmy

                      Und wo siehst du da konkret ein Problem?

                      Linux-Werkzeugkasten:
                      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                      NodeJS Fixer Skript:
                      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                      gelberlemmyG 1 Antwort Letzte Antwort
                      0
                      • Thomas BraunT Thomas Braun

                        @gelberlemmy

                        Und wo siehst du da konkret ein Problem?

                        gelberlemmyG Offline
                        gelberlemmyG Offline
                        gelberlemmy
                        schrieb am zuletzt editiert von
                        #156

                        @thomas-braun da es dort sehr viele "Errors" beim Hochfahren gibt, macht mich stutzig....

                        crunchipC 1 Antwort Letzte Antwort
                        0
                        • gelberlemmyG gelberlemmy

                          @thomas-braun da es dort sehr viele "Errors" beim Hochfahren gibt, macht mich stutzig....

                          crunchipC Offline
                          crunchipC Offline
                          crunchip
                          Forum Testing Most Active
                          schrieb am zuletzt editiert von
                          #157

                          @gelberlemmy davon ist aber kein log dabei
                          wofür ist der 2te admin?

                          umgestiegen von Proxmox auf Unraid

                          gelberlemmyG 1 Antwort Letzte Antwort
                          0
                          • crunchipC crunchip

                            @gelberlemmy davon ist aber kein log dabei
                            wofür ist der 2te admin?

                            gelberlemmyG Offline
                            gelberlemmyG Offline
                            gelberlemmy
                            schrieb am zuletzt editiert von
                            #158

                            @crunchip für iorboker.pro. Sonst kann ich nicht auf alle Adapetereinstellungen von der Ferne zugreifen

                            Thomas BraunT 1 Antwort Letzte Antwort
                            0
                            • gelberlemmyG gelberlemmy

                              @crunchip für iorboker.pro. Sonst kann ich nicht auf alle Adapetereinstellungen von der Ferne zugreifen

                              Thomas BraunT Online
                              Thomas BraunT Online
                              Thomas Braun
                              Most Active
                              schrieb am zuletzt editiert von
                              #159

                              @gelberlemmy
                              Nach

                              2023-07-01 21:44:13.180  - info: host.IOBroker-Proxmox iobroker.js-controller version 5.0.5 js-controller starting
                              

                              seh ich nur INFO.

                              Linux-Werkzeugkasten:
                              https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                              NodeJS Fixer Skript:
                              https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                              iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                              gelberlemmyG 2 Antworten Letzte Antwort
                              0
                              • Thomas BraunT Thomas Braun

                                @gelberlemmy
                                Nach

                                2023-07-01 21:44:13.180  - info: host.IOBroker-Proxmox iobroker.js-controller version 5.0.5 js-controller starting
                                

                                seh ich nur INFO.

                                gelberlemmyG Offline
                                gelberlemmyG Offline
                                gelberlemmy
                                schrieb am zuletzt editiert von
                                #160

                                @thomas-braun sagte in Troubleshooting NodeJS update:

                                @gelberlemmy
                                Nach

                                2023-07-01 21:44:13.180  - info: host.IOBroker-Proxmox iobroker.js-controller version 5.0.5 js-controller starting
                                

                                seh ich nur INFO.

                                ach Mensch, ist der falsche Teil des Logs... Warte

                                crunchipC 1 Antwort Letzte Antwort
                                0
                                • Thomas BraunT Thomas Braun

                                  @gelberlemmy
                                  Nach

                                  2023-07-01 21:44:13.180  - info: host.IOBroker-Proxmox iobroker.js-controller version 5.0.5 js-controller starting
                                  

                                  seh ich nur INFO.

                                  gelberlemmyG Offline
                                  gelberlemmyG Offline
                                  gelberlemmy
                                  schrieb am zuletzt editiert von
                                  #161

                                  @thomas-braun

                                  023-07-01 22:09:15.913  - info: host.IOBroker-Proxmox instance system.adapter.admin.1 terminated with code 0 (NO_ERROR)
                                  2023-07-01 22:09:15.942  - warn: host.IOBroker-Proxmox instance system.adapter.sonoff.0 terminated due to SIGTERM
                                  2023-07-01 22:09:15.942  - info: host.IOBroker-Proxmox instance system.adapter.sonoff.0 terminated with code null ()
                                  2023-07-01 22:09:16.015  - warn: host.IOBroker-Proxmox instance system.adapter.homeconnect.0 terminated due to SIGTERM
                                  2023-07-01 22:09:16.015  - info: host.IOBroker-Proxmox instance system.adapter.homeconnect.0 terminated with code null ()
                                  2023-07-01 22:09:16.015  - warn: host.IOBroker-Proxmox instance system.adapter.hue-extended.0 terminated due to SIGTERM
                                  2023-07-01 22:09:16.015  - info: host.IOBroker-Proxmox instance system.adapter.hue-extended.0 terminated with code null ()
                                  2023-07-01 22:09:16.057  - warn: host.IOBroker-Proxmox instance system.adapter.zigbee.0 terminated due to SIGTERM
                                  2023-07-01 22:09:16.057  - info: host.IOBroker-Proxmox instance system.adapter.zigbee.0 terminated with code null ()
                                  2023-07-01 22:09:16.838  - warn: host.IOBroker-Proxmox instance system.adapter.javascript.0 terminated due to SIGTERM
                                  2023-07-01 22:09:16.838  - info: host.IOBroker-Proxmox instance system.adapter.javascript.0 terminated with code null ()
                                  2023-07-01 22:09:17.016  - error: host.IOBroker-Proxmox 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:
                                  2023-07-01 22:09:17.017  - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed
                                  2023-07-01 22:09:17.017  - error: host.IOBroker-Proxmox Caught by controller[0]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                                  2023-07-01 22:09:17.017  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                                  2023-07-01 22:09:17.017  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Object.onceWrapper (node:events:628:26)
                                  2023-07-01 22:09:17.017  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Socket.emit (node:events:513:28)
                                  2023-07-01 22:09:17.017  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Socket.emit (node:domain:489:12)
                                  2023-07-01 22:09:17.018  - error: host.IOBroker-Proxmox Caught by controller[0]:     at TCP.<anonymous> (node:net:322:12)
                                  2023-07-01 22:09:17.018  - warn: host.IOBroker-Proxmox instance system.adapter.nut.0 terminated due to SIGTERM
                                  2023-07-01 22:09:17.018  - info: host.IOBroker-Proxmox instance system.adapter.nut.0 terminated with code null ()
                                  2023-07-01 22:09:17.081  - error: host.IOBroker-Proxmox 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:
                                  2023-07-01 22:09:17.081  - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed
                                  2023-07-01 22:09:17.081  - error: host.IOBroker-Proxmox Caught by controller[0]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                                  2023-07-01 22:09:17.081  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                                  2023-07-01 22:09:17.082  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Object.onceWrapper (node:events:628:26)
                                  2023-07-01 22:09:17.082  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Socket.emit (node:events:513:28)
                                  2023-07-01 22:09:17.082  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Socket.emit (node:domain:489:12)
                                  2023-07-01 22:09:17.082  - error: host.IOBroker-Proxmox Caught by controller[0]:     at TCP.<anonymous> (node:net:322:12)
                                  2023-07-01 22:09:17.082  - warn: host.IOBroker-Proxmox instance system.adapter.netatmo.0 terminated due to SIGTERM
                                  2023-07-01 22:09:17.082  - info: host.IOBroker-Proxmox instance system.adapter.netatmo.0 terminated with code null ()
                                  2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox 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:
                                  2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed
                                  2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                                  2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                                  2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                                  2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                                  2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]:     at runNextTicks (node:internal/process/task_queues:60:5)
                                  2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]:     at processImmediate (node:internal/timers:447:9)
                                  2023-07-01 22:09:17.083  - warn: host.IOBroker-Proxmox instance system.adapter.shelly.0 terminated due to SIGTERM
                                  2023-07-01 22:09:17.084  - info: host.IOBroker-Proxmox instance system.adapter.shelly.0 terminated with code null ()
                                  2023-07-01 22:09:17.112  - error: host.IOBroker-Proxmox 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:
                                  2023-07-01 22:09:17.112  - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed
                                  2023-07-01 22:09:17.112  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                                  2023-07-01 22:09:17.112  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                                  2023-07-01 22:09:17.112  - error: host.IOBroker-Proxmox Caught by controller[0]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                                  2023-07-01 22:09:17.113  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                                  2023-07-01 22:09:17.113  - warn: host.IOBroker-Proxmox instance system.adapter.shelly.1 terminated due to SIGTERM
                                  2023-07-01 22:09:17.113  - info: host.IOBroker-Proxmox instance system.adapter.shelly.1 terminated with code null ()
                                  2023-07-01 22:09:17.163  - warn: host.IOBroker-Proxmox instance system.adapter.fb-checkpresence.0 terminated due to SIGTERM
                                  2023-07-01 22:09:17.163  - info: host.IOBroker-Proxmox instance system.adapter.fb-checkpresence.0 terminated with code null ()
                                  2023-07-01 22:09:17.190  - info: host.IOBroker-Proxmox instance system.adapter.history.0 terminated with code 0 (NO_ERROR)
                                  
                                  Thomas BraunT 1 Antwort Letzte Antwort
                                  0
                                  • gelberlemmyG gelberlemmy

                                    @thomas-braun

                                    023-07-01 22:09:15.913  - info: host.IOBroker-Proxmox instance system.adapter.admin.1 terminated with code 0 (NO_ERROR)
                                    2023-07-01 22:09:15.942  - warn: host.IOBroker-Proxmox instance system.adapter.sonoff.0 terminated due to SIGTERM
                                    2023-07-01 22:09:15.942  - info: host.IOBroker-Proxmox instance system.adapter.sonoff.0 terminated with code null ()
                                    2023-07-01 22:09:16.015  - warn: host.IOBroker-Proxmox instance system.adapter.homeconnect.0 terminated due to SIGTERM
                                    2023-07-01 22:09:16.015  - info: host.IOBroker-Proxmox instance system.adapter.homeconnect.0 terminated with code null ()
                                    2023-07-01 22:09:16.015  - warn: host.IOBroker-Proxmox instance system.adapter.hue-extended.0 terminated due to SIGTERM
                                    2023-07-01 22:09:16.015  - info: host.IOBroker-Proxmox instance system.adapter.hue-extended.0 terminated with code null ()
                                    2023-07-01 22:09:16.057  - warn: host.IOBroker-Proxmox instance system.adapter.zigbee.0 terminated due to SIGTERM
                                    2023-07-01 22:09:16.057  - info: host.IOBroker-Proxmox instance system.adapter.zigbee.0 terminated with code null ()
                                    2023-07-01 22:09:16.838  - warn: host.IOBroker-Proxmox instance system.adapter.javascript.0 terminated due to SIGTERM
                                    2023-07-01 22:09:16.838  - info: host.IOBroker-Proxmox instance system.adapter.javascript.0 terminated with code null ()
                                    2023-07-01 22:09:17.016  - error: host.IOBroker-Proxmox 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:
                                    2023-07-01 22:09:17.017  - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed
                                    2023-07-01 22:09:17.017  - error: host.IOBroker-Proxmox Caught by controller[0]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                                    2023-07-01 22:09:17.017  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                                    2023-07-01 22:09:17.017  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Object.onceWrapper (node:events:628:26)
                                    2023-07-01 22:09:17.017  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Socket.emit (node:events:513:28)
                                    2023-07-01 22:09:17.017  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Socket.emit (node:domain:489:12)
                                    2023-07-01 22:09:17.018  - error: host.IOBroker-Proxmox Caught by controller[0]:     at TCP.<anonymous> (node:net:322:12)
                                    2023-07-01 22:09:17.018  - warn: host.IOBroker-Proxmox instance system.adapter.nut.0 terminated due to SIGTERM
                                    2023-07-01 22:09:17.018  - info: host.IOBroker-Proxmox instance system.adapter.nut.0 terminated with code null ()
                                    2023-07-01 22:09:17.081  - error: host.IOBroker-Proxmox 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:
                                    2023-07-01 22:09:17.081  - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed
                                    2023-07-01 22:09:17.081  - error: host.IOBroker-Proxmox Caught by controller[0]:     at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
                                    2023-07-01 22:09:17.081  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
                                    2023-07-01 22:09:17.082  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Object.onceWrapper (node:events:628:26)
                                    2023-07-01 22:09:17.082  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Socket.emit (node:events:513:28)
                                    2023-07-01 22:09:17.082  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Socket.emit (node:domain:489:12)
                                    2023-07-01 22:09:17.082  - error: host.IOBroker-Proxmox Caught by controller[0]:     at TCP.<anonymous> (node:net:322:12)
                                    2023-07-01 22:09:17.082  - warn: host.IOBroker-Proxmox instance system.adapter.netatmo.0 terminated due to SIGTERM
                                    2023-07-01 22:09:17.082  - info: host.IOBroker-Proxmox instance system.adapter.netatmo.0 terminated with code null ()
                                    2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox 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:
                                    2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed
                                    2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                                    2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                                    2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                                    2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                                    2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]:     at runNextTicks (node:internal/process/task_queues:60:5)
                                    2023-07-01 22:09:17.083  - error: host.IOBroker-Proxmox Caught by controller[0]:     at processImmediate (node:internal/timers:447:9)
                                    2023-07-01 22:09:17.083  - warn: host.IOBroker-Proxmox instance system.adapter.shelly.0 terminated due to SIGTERM
                                    2023-07-01 22:09:17.084  - info: host.IOBroker-Proxmox instance system.adapter.shelly.0 terminated with code null ()
                                    2023-07-01 22:09:17.112  - error: host.IOBroker-Proxmox 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:
                                    2023-07-01 22:09:17.112  - error: host.IOBroker-Proxmox Caught by controller[0]: Error: DB closed
                                    2023-07-01 22:09:17.112  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.sendCommand (/opt/iobroker/node_modules/ioredis/built/redis/index.js:636:24)
                                    2023-07-01 22:09:17.112  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Redis.get (/opt/iobroker/node_modules/ioredis/built/commander.js:122:25)
                                    2023-07-01 22:09:17.112  - error: host.IOBroker-Proxmox Caught by controller[0]:     at StateRedisClient.setState (/opt/iobroker/node_modules/@iobroker/db-states-redis/src/lib/states/statesInRedisClient.ts:726:40)
                                    2023-07-01 22:09:17.113  - error: host.IOBroker-Proxmox Caught by controller[0]:     at Shelly._setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:7591:34)
                                    2023-07-01 22:09:17.113  - warn: host.IOBroker-Proxmox instance system.adapter.shelly.1 terminated due to SIGTERM
                                    2023-07-01 22:09:17.113  - info: host.IOBroker-Proxmox instance system.adapter.shelly.1 terminated with code null ()
                                    2023-07-01 22:09:17.163  - warn: host.IOBroker-Proxmox instance system.adapter.fb-checkpresence.0 terminated due to SIGTERM
                                    2023-07-01 22:09:17.163  - info: host.IOBroker-Proxmox instance system.adapter.fb-checkpresence.0 terminated with code null ()
                                    2023-07-01 22:09:17.190  - info: host.IOBroker-Proxmox instance system.adapter.history.0 terminated with code 0 (NO_ERROR)
                                    
                                    Thomas BraunT Online
                                    Thomas BraunT Online
                                    Thomas Braun
                                    Most Active
                                    schrieb am zuletzt editiert von
                                    #162

                                    @gelberlemmy

                                    Das ist ein shut down? Auch nicht ungewöhnlich.

                                    Linux-Werkzeugkasten:
                                    https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                    NodeJS Fixer Skript:
                                    https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                    iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                    gelberlemmyG 1 Antwort Letzte Antwort
                                    0
                                    • gelberlemmyG gelberlemmy

                                      @thomas-braun sagte in Troubleshooting NodeJS update:

                                      @gelberlemmy
                                      Nach

                                      2023-07-01 21:44:13.180  - info: host.IOBroker-Proxmox iobroker.js-controller version 5.0.5 js-controller starting
                                      

                                      seh ich nur INFO.

                                      ach Mensch, ist der falsche Teil des Logs... Warte

                                      crunchipC Offline
                                      crunchipC Offline
                                      crunchip
                                      Forum Testing Most Active
                                      schrieb am zuletzt editiert von
                                      #163

                                      @gelberlemmy sagte in Troubleshooting NodeJS update:

                                      ist der falsche Teil des Logs

                                      is nicht der falsche Teil, nur zu wenig, die Adapterstarts kommen doch erst nach und nach

                                      umgestiegen von Proxmox auf Unraid

                                      gelberlemmyG 1 Antwort Letzte Antwort
                                      0
                                      • Thomas BraunT Thomas Braun

                                        @gelberlemmy

                                        Das ist ein shut down? Auch nicht ungewöhnlich.

                                        gelberlemmyG Offline
                                        gelberlemmyG Offline
                                        gelberlemmy
                                        schrieb am zuletzt editiert von
                                        #164

                                        @thomas-braun sagte in Troubleshooting NodeJS update:

                                        @gelberlemmy

                                        Das ist ein shut down? Auch nicht ungewöhnlich.

                                        Nein ein Neustart

                                        Thomas BraunT 1 Antwort Letzte Antwort
                                        0
                                        • gelberlemmyG gelberlemmy

                                          @thomas-braun sagte in Troubleshooting NodeJS update:

                                          @gelberlemmy

                                          Das ist ein shut down? Auch nicht ungewöhnlich.

                                          Nein ein Neustart

                                          Thomas BraunT Online
                                          Thomas BraunT Online
                                          Thomas Braun
                                          Most Active
                                          schrieb am zuletzt editiert von Thomas Braun
                                          #165

                                          @gelberlemmy

                                          Das kann aber nicht sein, SIGTERM ist das Signal für das Beenden eines Prozesses.

                                          Ein Neustart hat auch mehr als 52 Zeilen im Log.

                                          Linux-Werkzeugkasten:
                                          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                                          NodeJS Fixer Skript:
                                          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                                          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                                          gelberlemmyG 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

                                          800

                                          Online

                                          32.4k

                                          Benutzer

                                          81.5k

                                          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