Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 4.0 jetzt im BETA/LATEST!

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    js-controller 4.0 jetzt im BETA/LATEST!

    This topic has been deleted. Only users with topic management privileges can see it.
    • O
      oFbEQnpoLKKl6mbY5e13 @Thomas Braun last edited by

      @thomas-braun
      Wie gesagt, das Problem konnte durch iobroker fix behoben werden.

      # ls -l /opt/iobroker/node_modules/iobroker.vis/www/widgets/fritzdect/css/style.css
-rw-rw-rw- 1 iobroker iobroker 70 Feb 21 11:05 /opt/iobroker/node_modules/iobroker.vis/www/widgets/fritzdect/css/style.css
      1 Reply Last reply Reply Quote 0
      • S
        saeft_2003 Most Active @apollon77 last edited by saeft_2003

        @apollon77 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

        @saeft_2003 naja mit 630MB frei ist dann die Frage wie gross denn so das Backup ist wenn es tut? bzw wieviele Daten sind es denn die da gesichert werden

        Das backup hat 90MB.

        edit: ich habe ohne den ram zu erhöhen ein Backup manuell gestartet das lief ohne Probleme durch.

        1 Reply Last reply Reply Quote 0
        • apollon77
          apollon77 @oFbEQnpoLKKl6mbY5e13 last edited by

          @ofbeqnpolkkl6mby5e13 sagte in js-controller 4.0 jetzt im BETA/LATEST!:

          Nur hätte ich mir das alles sparen können, weil mein ursprüngliches Problem weiterhin existiert...

          ??

          O 1 Reply Last reply Reply Quote 0
          • O
            oFbEQnpoLKKl6mbY5e13 @apollon77 last edited by

            @apollon77

            Restore mit VIS v1.4.12 geht mindestens bei mir nicht und hat mit JS-Controller nichts zu tun. Das Problem, weshalb ich auf einen älteren Stand wollte, ist aber Off-Topic.

            Danke für die Hilfe!

            1 Reply Last reply Reply Quote 0
            • apollon77
              apollon77 @saeft_2003 last edited by

              @saeft_2003 Kannst du mir mal einen gefallen tun?

              Mach mal eine Shell auf mit "top", dann drücke "Shift-M" - das sortiert dir die EInträge nach RAM nutzung. Dnan am besten davon nen Screenshot

              Jetzt bitte mal zwei Dinge tun:
              1.) in einer zweiten Shell ein "iob backup" ausführen
              2.) Backup über BackItUp manuell starten

              Und bei beiden Dingen bitte mal das "top" beobachten ... Wo steigt der RAM Verbrauch an und wenn ja in welchem prozess?

              Vllt kommen wir so ein bissl dahinter

              M 1 Reply Last reply Reply Quote 0
              • M
                Marty56 @apollon77 last edited by

                @apollon77
                Ich habe meine zweite iobroker Instanz (Raspberry 3) ohne Probleme umgestellt.
                Dort hatte ich früher die States auf redis umgestellt und würde jetzt gern auf JSONL migrieren.

                iobroker status
iobroker is running on this host.


Objects type: jsonl
States  type: redis

                Ist das unproblematisch?

                apollon77 1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 @Marty56 last edited by

                  @marty56 Na klar, einfach per iob setup custom machen

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    Marty56 @apollon77 last edited by

                    @apollon77 Danke. Hat unproblematisch geklappt.

                    1 Reply Last reply Reply Quote 1
                    • E
                      e-i-k-e last edited by e-i-k-e

                      Aktualisiere gerade ein Slave von 4.0.10 auf 4.0.15.
                      Habe es nun bereits mit sudo -H -u iobroker npm install iobroker.js-controller versucht.

                      Bei den anderen Geräten hatte ich dieses Problem nicht.
                      Was kann ich tun?

                      pi@raspberrypi-display2:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller

> iobroker.js-controller@4.0.10 preinstall /opt/iobroker/node_modules/iobroker.js-controller
> node lib/preinstallCheck.js

NPM version: 6.14.16

> iobroker.js-controller@4.0.10 install /opt/iobroker/node_modules/iobroker.js-controller
> node iobroker.js setup first

No connection to objects 192.168.3.100:6379[redis]
/opt/iobroker/node_modules/standard-as-callback/built/index.js:6
        throw e;
        ^

Error: Connection is 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 (events.js:520:26)
    at Socket.emit (events.js:400:28)
    at TCP.<anonymous> (net.js:686:12)
Emitted 'error' event on ScanStream instance at:
    at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22
    at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23)
    at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! iobroker.js-controller@4.0.10 install: `node iobroker.js setup first`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the iobroker.js-controller@4.0.10 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2022-02-21T20_58_28_730Z-debug.l

                      Keine Ahnung was jetzt los ist.. 😲

                      pi@raspberrypi-display2:~ $ iobroker stop
pi@raspberrypi-display2:~ $ iobroker fix
library: loaded
Library version=2022-02-10
ioBroker is not installed in /opt/iobroker! Cannot fix anything...
                      apollon77 2 Replies Last reply Reply Quote 0
                      • apollon77
                        apollon77 @e-i-k-e last edited by

                        @e-i-k-e Wie geht es dem Redis? Steht ggf etwas im Redis log? Ich hab das gefühl das sich der beendet mittendrin.

                        E 1 Reply Last reply Reply Quote 0
                        • E
                          e-i-k-e @apollon77 last edited by

                          @apollon77

                          Hast du zufällig den Pfad parat?

                          Ich habe den kompletten Container inkl. Reids mal neu gestartet. Keine Änderung.

                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @e-i-k-e last edited by

                            @e-i-k-e

                            less -R /var/log/redis/redis-server.log

                            und

                            systemctl status redis

                            anschauen.

                            E 1 Reply Last reply Reply Quote 1
                            • Diginix
                              Diginix last edited by Diginix

                              @AlCalzone @apollon77
                              Hab eben per CLI admin, web und ws aktualisiert und dann ist der js-controller mal wieder RAM technisch eskaliert mit über 2 GB. Hat sich dann aber ohne mein Zutun wieder stabilisiert. Wahrs. reichten die 6 GB RAM der VM gerade so aus.

                                            total        used        free      shared  buff/cache   available
Mem:           5941        4407         131           1        1402        1242
Swap:             0           0           0

                              4737ce9d-6927-41f3-a9c8-aba20b0ba606-image.png

                              f03fd880-06cb-48c8-9bb8-f0174972d891-image.png

                              apollon77 3 Replies Last reply Reply Quote 0
                              • E
                                e-i-k-e @Thomas Braun last edited by

                                @thomas-braun

                                Danke.

                                Im Log steht immer das gleiche, nichts auffälliges.

                                11670:C 20 Feb 2022 22:13:49.210 * DB saved on disk
11670:C 20 Feb 2022 22:13:49.228 * RDB: 7 MB of memory used by copy-on-write
139:M 20 Feb 2022 22:13:49.345 * Background saving terminated with success
139:M 20 Feb 2022 22:15:49.680 * 10000 changes in 60 seconds. Saving...
139:M 20 Feb 2022 22:15:49.698 * Background saving started by pid 11703
11703:C 20 Feb 2022 22:16:04.583 * DB saved on disk
11703:C 20 Feb 2022 22:16:04.601 * RDB: 14 MB of memory used by copy-on-write
139:M 20 Feb 2022 22:16:04.688 * Background saving terminated with success
139:M 20 Feb 2022 22:18:21.814 * 10000 changes in 60 seconds. Saving...

                                pi@ioBroker-Rock:~$ systemctl status redis
* redis-server.service - Advanced key-value store
     Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
     Active: active (running) since Mon 2022-02-21 22:27:17 CET; 46min ago
       Docs: http://redis.io/documentation,
             man:redis-server(1)
    Process: 114 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS)
   Main PID: 135 (redis-server)
      Tasks: 4 (limit: 18952)
     Memory: 1.7G
        CPU: 6min 39.212s
     CGroup: /system.slice/redis-server.service
             `-135 /usr/bin/redis-server 0.0.0.0:6379

                                Fünf weitere Slave laufen aber auch problemlos mit dem Master und der Redis DB.

                                M apollon77 2 Replies Last reply Reply Quote 0
                                • M
                                  Marty56 @e-i-k-e last edited by

                                  Ich beobachte einen seltsamen Effekt, den ich nicht verstehe.

                                  Ich habe iob mit dem Update auf von js-controller 4 von Objects type: jsonl
                                  States type: redis auf Objects type: jsonl States type: jsonl umgestellt, was auch ohne Probleme geklappt hat und einige Stunden stabil lief.

                                  Dann hatte ich mir gedacht, dass ich redis ausschalte, um ein bisschen Speicher zu sparen. Diese Änderung führte zu einer dramatischen Instabilität. Iob konnte kein Web Interface mehr anzeigen, die über SSH gestartet Console hat mich nach einigen Sekunden wieder rausgeschmissen und Debmatic ist auch nicht mehr gestartet. Ansonsten habe ich noch NextPVR installiert. Debmatic und NextPVR haben keine Abhängigkeiten von redis.
                                  Es wirkt so, als ob es dennoch Prozesse gibt, die immer noch redis Verfügbarkeit benötigen und wenn sie die nicht bekommen, das System extrem belasten.

                                  Gottseidank konnte ich in der kurzen Zeitspanne, in der die Console funktioniert hat, den redis Server wieder via SSH einschalten und jetzt läuft es wieder stabil.

                                  Hat jemand eine Idee? Kann man irgendwie herausbekommen, wer den Redis Server benutzt?

                                  M arteck apollon77 3 Replies Last reply Reply Quote 0
                                  • M
                                    Marty56 @Marty56 last edited by Marty56

                                    gelöscht

                                    F 1 Reply Last reply Reply Quote 0
                                    • F
                                      Fortune95 @Marty56 last edited by

                                      @apollon77

                                      Node.js: v14.19.0
                                      js-controller: 4.0.15

                                      Habe gerade folgendes nach einem Neustart des Shelly Adapters im Log gefunden:

                                      2022-02-22 06:12:00.875 - error: shelly.0 (15030) uncaught exception: This socket has been ended by the other party
2022-02-22 06:12:00.876 - error: shelly.0 (15030) Error: This socket has been ended by the other party
at Socket.writeAfterFIN [as write] (net.js:468:14)
at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:300:10)
at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14)
at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9)
at writeOrBuffer (internal/streams/writable.js:358:12)
at Writable.write (internal/streams/writable.js:303:10)
at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22)
at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64)
at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5)
at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11)
2022-02-22 06:12:00.877 - error: shelly.0 (15030) Exception-Code: EPIPE: This socket has been ended by the other party
2022-02-22 06:12:00.880 - error: shelly.0 (15030) uncaught exception: This socket has been ended by the other party
2022-02-22 06:12:00.880 - error: shelly.0 (15030) Error: This socket has been ended by the other party
at Socket.writeAfterFIN [as write] (net.js:468:14)
at writeVarByteInt (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:804:17)
at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:302:3)
at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14)
at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9)
at writeOrBuffer (internal/streams/writable.js:358:12)
at Writable.write (internal/streams/writable.js:303:10)
at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22)
at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64)
at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5)
2022-02-22 06:12:00.880 - error: shelly.0 (15030) Exception-Code: EPIPE: This socket has been ended by the other party
2022-02-22 06:12:00.881 - error: shelly.0 (15030) uncaught exception: This socket has been ended by the other party
2022-02-22 06:12:00.881 - error: shelly.0 (15030) Error: This socket has been ended by the other party
at Socket.writeAfterFIN [as write] (net.js:468:14)
at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:303:10)
at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14)
at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9)
at writeOrBuffer (internal/streams/writable.js:358:12)
at Writable.write (internal/streams/writable.js:303:10)
at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22)
at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64)
at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5)
at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11)
2022-02-22 06:12:00.881 - error: shelly.0 (15030) Exception-Code: EPIPE: This socket has been ended by the other party
2022-02-22 06:12:00.882 - error: shelly.0 (15030) uncaught exception: This socket has been ended by the other party
2022-02-22 06:12:00.882 - error: shelly.0 (15030) Error: This socket has been ended by the other party
at Socket.writeAfterFIN [as write] (net.js:468:14)
at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:305:10)
at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14)
at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9)
at writeOrBuffer (internal/streams/writable.js:358:12)
at Writable.write (internal/streams/writable.js:303:10)
at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22)
at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64)
at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5)
at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11)
2022-02-22 06:12:00.882 - error: shelly.0 (15030) Exception-Code: EPIPE: This socket has been ended by the other party
2022-02-22 06:12:00.883 - warn: shelly.0 (15030) Terminated (UNCAUGHT_EXCEPTION): Without reason
2022-02-22 06:12:00.950 - error: host.iobroker Caught by controller[1]: Error: This socket has been ended by the other party
2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at Socket.writeAfterFIN [as write] (net.js:468:14)
2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:300:10)
2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14)
2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9)
2022-02-22 06:12:00.955 - error: host.iobroker Caught by controller[1]: at writeOrBuffer (internal/streams/writable.js:358:12)
2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at Writable.write (internal/streams/writable.js:303:10)
2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22)
2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64)
2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5)
2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[1]: at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11)
2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[2]: Error: This socket has been ended by the other party
2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[2]: at Socket.writeAfterFIN [as write] (net.js:468:14)
2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[2]: at writeVarByteInt (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:804:17)
2022-02-22 06:12:00.956 - error: host.iobroker Caught by controller[2]: at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:302:3)
2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14)
2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9)
2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (internal/streams/writable.js:358:12)
2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at Writable.write (internal/streams/writable.js:303:10)
2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22)
2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64)
2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5)
2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: Error: This socket has been ended by the other party
2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at Socket.writeAfterFIN [as write] (net.js:468:14)
2022-02-22 06:12:00.957 - error: host.iobroker Caught by controller[2]: at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:303:10)
2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14)
2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9)
2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (internal/streams/writable.js:358:12)
2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at Writable.write (internal/streams/writable.js:303:10)
2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22)
2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64)
2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5)
2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[2]: at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11)
2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[3]: Error: This socket has been ended by the other party
2022-02-22 06:12:00.958 - error: host.iobroker Caught by controller[3]: at Socket.writeAfterFIN [as write] (net.js:468:14)
2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at connack (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:305:10)
2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at generate (/opt/iobroker/node_modules/mqtt-connection/node_modules/mqtt-packet/writeToStream.js:32:14)
2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at Writable.write [as _write] (/opt/iobroker/node_modules/mqtt-connection/lib/writeToStream.js:13:9)
2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at writeOrBuffer (internal/streams/writable.js:358:12)
2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at Writable.write (internal/streams/writable.js:303:10)
2022-02-22 06:12:00.959 - error: host.iobroker Caught by controller[3]: at Connection.Duplexify._write (/opt/iobroker/node_modules/duplexify/index.js:208:22)
2022-02-22 06:12:00.961 - error: host.iobroker Caught by controller[3]: at doWrite (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:428:64)
2022-02-22 06:12:00.961 - error: host.iobroker Caught by controller[3]: at writeOrBuffer (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:417:5)
2022-02-22 06:12:00.962 - error: host.iobroker Caught by controller[3]: at Connection.Writable.write (/opt/iobroker/node_modules/duplexify/node_modules/readable-stream/lib/_stream_writable.js:334:11)
2022-02-22 06:12:00.962 - error: host.iobroker instance system.adapter.shelly.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
                                      apollon77 1 Reply Last reply Reply Quote 0
                                      • apollon77
                                        apollon77 @Diginix last edited by

                                        @diginix welche nodejs Version nutzt du?

                                        1 Reply Last reply Reply Quote 0
                                        • apollon77
                                          apollon77 @Diginix last edited by apollon77

                                          @diginix hast du bitte mal das log dieser Updates und paar mins davor und danach bitte? Auch: wie genau wurden die Updates ausgeführt? Einzeln? Uplgrade all?

                                          Diginix 1 Reply Last reply Reply Quote 0
                                          • apollon77
                                            apollon77 @e-i-k-e last edited by

                                            @e-i-k-e und das log ist vom Update Zeitraum? Ja komisch. Dann Versuchs nochmal bitte

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            842
                                            Online

                                            31.7k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            70
                                            747
                                            167375
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo