Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 5.0.x jetzt für alle User im STABLE!

    NEWS

    • [erledigt] 15. 05. Wartungsarbeiten am ioBroker Forum

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    js-controller 5.0.x jetzt für alle User im STABLE!

    This topic has been deleted. Only users with topic management privileges can see it.
    • W
      Wildbill @mrjeschke last edited by Wildbill

      @fastfoot @Thomas-Braun @mrjeschke Im verlinkten Thread steht ja, dass es (momentan) ausreicht, wenn irgend ein Gerät auf der öffentlichen IP erreichbar ist. Das kann auch irgendein anderer Rechner im Netz sein, ein gewollter Webserver, ja sogar das Webinterface des Routes, einer Synology oder sonstwas. Es wird nur geprüft, ob auf der öffentlichen IP eine Antwort kommt. Deshalb ja auch die Vorschläge, das mittels Zertifikat oder Ähnlichem abzufangen, so dass nur die Meldung kommt, wenn es auch wirklich iobroker ist, der da wntwortet.
      Für den Moment also wohl einfach mal ignorieren…

      Gruss, Jürgen

      F 1 Reply Last reply Reply Quote 0
      • F
        fastfoot @Wildbill last edited by

        @wildbill

        und da läuft auch kein web server oder irgendwas anderes. Der Sicherheitscheck der Fritzbox zeigt alles als ok an

        was ist denn an da läuft nix falsch zu verstehen? Diese neue Funktion arbeitet schlicht fehlerhaft

        W 1 Reply Last reply Reply Quote 0
        • W
          Wildbill @fastfoot last edited by

          @fastfoot Es war nix persönlich gegen Dich, sondern der allgemeine Hinweis, dass es nicht iobroker sein muss, der da erreichbar ist, sondern eben irgendwas. Wenn bei Dir wirklich nix von außen erreichbar ist, die Meldung aber dennoch kommt, wäre jetzt wohl der Zeitpunkt, ein Issue aufzumachen, sofern es noch keins gibt, und es dort kund zu tun.
          Ich weiss auch nicht, ob nur die öffentlich IPv4 geprüft wird, oder auch die IPv6 oder vielleicht nur der Präfix. und manche Router, die bei IPv4 felsendicht sind, lassen bei IPv6 plötzlich so einiges durch. Ich denke da an einen TP-Link vor ein paar Jahren zurück. Der war im Standard bei IPv6 komplett ohne Firewall und liess einfach alles erst einmal durch.

          Gruss, Jürgen

          F 1 Reply Last reply Reply Quote 0
          • F
            fastfoot @Wildbill last edited by

            @wildbill Alles gut! Es wird gegen eine IPv4 geprüft die in meimem Fall(Kabel/DS-Lite) aber gar nicht erreichbar ist, das zeigen auch Tests im Browser und auf der Konsole. Issue wurde schon erstellt und durch Bluefox als fixed markiert.

            1 Reply Last reply Reply Quote 1
            • M
              MicyMic last edited by

              Hallo zusammen,

              mein IObroker lief bis vor kurzem sauber im docker container meiner synology nas.
              Nun habe ich das Update auf JS-contr5 gemacht, ohne mich vorab zu erkundigen.
              Danach war meine Konfiguration komplett weg.

              Problemstellung:

              • mein Backup lässt sich nicht einspielen (da nur mit JS-contr4 kompatibel, oder?)
              • ich habe keine Programmierkenntnisse, weiss auch nicht wie ich per ssh irgendein downgrade durchführen soll (also bitte schickt mir keine code zeilen :-D)

              Kann ich im Container Manager nicht einfach eine alte version hosten - wenn ja welche? oder gibt es die möglichkeit mein backup kompatibel zu machen?

              wäre super froh um rat!

              danke euch und beste grüße

              mcm1957 Marc Berg F 3 Replies Last reply Reply Quote 0
              • mcm1957
                mcm1957 @MicyMic last edited by mcm1957

                @micymic
                Kann nur zum Backup was sagen

                Backup erstellt mit js controller 4 lässt sich mit js-controller 4 oder 5 einspielen.

                Backup erstellt mit js-controller 5 lässt sich nur mit js-controller 5 einspielen.

                Es gibt aber m.W. einen neuen Container mit js-controller 5

                1 Reply Last reply Reply Quote 0
                • Marc Berg
                  Marc Berg Most Active @MicyMic last edited by

                  @micymic sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

                  Wie @mcm57 schon geschrieben hat, sind die Versionen soweit kompatibel. Wenn du sagst:

                  mein Backup lässt sich nicht einspielen (da nur mit JS-contr4 kompatibel, oder?)

                  Was konkret bedeutet das? Was geht wie und mit welcher Fehlermeldung nicht?

                  Und sage noch mehr zu deiner Umgebung: Hast du das ioBroker-Verzeichnis gemountet, auf welcher Image-Version bist du jetzt?

                  M 1 Reply Last reply Reply Quote 0
                  • M
                    MicyMic @Marc Berg last edited by

                    @mcm57 danke schon mal für die rückmeldung, das wär gut
                    @marc-berg hier ein paar infos zum system:
                    Node.js: v18.18.2
                    NPM: 9.8.1
                    Plattform: docker (official image - v9.0.1)
                    Betriebssystem: linux
                    Architektur: x64, 4 Kerne, AMD Ryzen Embedded R1600
                    js-controller: 5.0.12

                    zuvor hatte ich einen älteren js-controller. habe ohne drüber nachzudenken geupdated. nach dem reboot hatte ich eine leere iobroker installation. update einspielen per backitup geht bei "Started restore ..." nicht weiter... auch nach stunden nicht. Hatte bis vor ein paar monaten den iobroker auf einem raspberry. der umzug damals mit backitup hat geklappt. ich weiß nicht was ich falsch mache 😞

                    Thomas Braun 1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active @MicyMic last edited by

                      @micymic sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

                      update einspielen per backitup geht bei "Started restore ..." nicht weiter... auch nach stunden nicht.

                      Schalt den Popup/Skript-Blocker in deinem Browser aus.

                      M 1 Reply Last reply Reply Quote 0
                      • M
                        MicyMic @Thomas Braun last edited by

                        @thomas-braun hab nen pihole (auch im docker). gleiches problem wenn dieser aus ist:
                        "10.10.10.10 hat die Verbindung abgelehnt." kommt ausgegraut im hintergrund

                        Thomas Braun 1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @MicyMic last edited by

                          @micymic

                          Ist ein Thema in deinem Netzwerk. Der Backitup spannt an der Stelle einen eigenen Web-Server auf und blendet seine Meldungen dort ein. Bei dir funktioniert das nicht.

                          M 1 Reply Last reply Reply Quote 0
                          • M
                            MicyMic @Thomas Braun last edited by MicyMic

                            @thomas-braun okay danke, das könnte sein. eine idee wo das problem liegen könnte?

                            das backup liegt ebenfalls auf meinem synology server. zugriff funktioniert. es ist auch möglich ein backup vom jetzigen stand darauf zu speichern

                            Thomas Braun 1 Reply Last reply Reply Quote 0
                            • Thomas Braun
                              Thomas Braun Most Active @MicyMic last edited by

                              @micymic sagte in js-controller 5.0.x jetzt für alle User im STABLE!:

                              eine idee wo das problem liegen könnte?

                              Nö, ich weiß ja nicht was für 'Teufelszeug' da noch im Netzwerk herumspukt.

                              1 Reply Last reply Reply Quote 0
                              • F
                                fastfoot @MicyMic last edited by fastfoot

                                @micymic im 9er image gibt es einen Fehler der ein Restore verhindert, deshalb mache das von der Konsole iob restore filename. Falls du auch andere Backups hast(JS-Scrpte, etc.) dann kannst du die danach mit dem Backitup zurückspielen

                                Edit: An einer Lösung wird schon gearbeitet, Fehler ist identifiziert

                                M 1 Reply Last reply Reply Quote 0
                                • M
                                  MicyMic @fastfoot last edited by MicyMic

                                  @fastfoot hi und danke dir!

                                  ich bin leider kein itler nur ambitionierter anwender. mit dem raspberry wusste ich wie ich per konsole befehle eingebe. aber im docker container weiß ich das nicht. könntest du mir vllt. sagen wie ich vorgehen muss?

                                  mein letztes backup heißt "iobroker_2023_10_01-02_40_10_backupiobroker.tar.gz"

                                  F 1 Reply Last reply Reply Quote 0
                                  • F
                                    fastfoot @MicyMic last edited by

                                    @micymic ich habe keine Syno, aber im ContainerManager sollte es eine option geben um in die Konsole zu kommen

                                    cd /opt/iobroker
iobroker m on -y
iobroker restore filename
container neustarten
                                    M 1 Reply Last reply Reply Quote 1
                                    • M
                                      MicyMic @fastfoot last edited by

                                      @fastfoot du bist ein gott. es hat funktioniert! besten dank!

                                      1 Reply Last reply Reply Quote 0
                                      • foxriver76
                                        foxriver76 Developer last edited by

                                        5.0.15 ist auf dem Weg ins latest

                                        • Problem behoben, dass das Memory Limit in Adapter nicht angezogen wurde
                                        • Die Statistik States von Instanzen werden jetzt resetted wenn die Instanz gestoppt wird (z. B. cputime)
                                        Feuersturm 1 Reply Last reply Reply Quote 2
                                        • Feuersturm
                                          Feuersturm @foxriver76 last edited by

                                          @foxriver76 Ich hab gerade mein Master Slave System aktualisiert

                                          Beim Master Update hatte ich folgende Warnung und folgenden Fehler. Das System wurde aber wohl erfolgreich aktualisiert und alle Instanzen wurden gestartet. Update vom Slave verlief ohne Auffälligkeiten.

                                          2023-10-27 20:17:15.788 - warn: web.0 (729) Timeout by termination of web-extensions!

                                          2023-10-27 20:17:20.657 - error: host.ioBrokerTestsystem Caught by controller[0]: Error: DB closed
2023-10-27 20:17:20.659 - error: host.ioBrokerTestsystem Caught by controller[0]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2023-10-27 20:17:20.660 - error: host.ioBrokerTestsystem Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2023-10-27 20:17:20.662 - error: host.ioBrokerTestsystem Caught by controller[0]: at Object.onceWrapper (node:events:632:26)
2023-10-27 20:17:20.663 - error: host.ioBrokerTestsystem Caught by controller[0]: at Socket.emit (node:events:517:28)
2023-10-27 20:17:20.664 - error: host.ioBrokerTestsystem Caught by controller[0]: at Socket.emit (node:domain:489:12)
2023-10-27 20:17:20.666 - error: host.ioBrokerTestsystem Caught by controller[0]: at TCP. (node:net:350:12)

                                          Vollständiges Log Master vom update

                                          2023-10-27 20:17:10.679 - info: host.ioBrokerTestsystem Controller will upgrade itself to version 5.0.15
2023-10-27 20:17:11.905 - info: ical.4 (47222) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:12.486 - info: host.ioBrokerTestsystem instance system.adapter.ical.4 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:14.950 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Stopping controller
2023-10-27 20:17:15.077 - info: fully-tablet-control.0 (574) Adapter Fully Tablet Control stopped...
2023-10-27 20:17:15.099 - info: admin.0 (330) terminating http server on port 8081
2023-10-27 20:17:15.115 - info: host.ioBrokerTestsystem received SIGTERM
2023-10-27 20:17:15.107 - info: backitup.0 (545) cleaned everything up...
2023-10-27 20:17:15.125 - info: info.0 (597) cleaned everything up...
2023-10-27 20:17:15.163 - info: javascript.0 (367) Stop script script.js.Skripte.Beschattung_Rolladen
2023-10-27 20:17:15.101 - info: trashschedule.0 (20672) cleaned everything up...
2023-10-27 20:17:15.167 - info: javascript.0 (367) Stop script script.js.Skripte.Kalender.ical_0_ToHtmlTable
2023-10-27 20:17:15.169 - info: javascript.0 (367) Stop script script.js.Skripte.Kalender.ical_2_ToHtmlTable
2023-10-27 20:17:15.175 - info: javascript.0 (367) Stop script script.js.Skripte.Kalender.ical_3_ToHtmlTable
2023-10-27 20:17:15.177 - info: javascript.0 (367) Stop script script.js.Skripte.Kalender.ical_4_ToHtmlTable
2023-10-27 20:17:15.180 - info: javascript.0 (367) Stop script script.js.Skripte.Kalender.muellkalender
2023-10-27 20:17:15.182 - info: javascript.0 (367) Stop script script.js.Skripte.Netzwerk.Unifi_Vouchers
2023-10-27 20:17:15.124 - info: vis-inventwo.0 (722) cleaned everything up...
2023-10-27 20:17:15.132 - info: unifi.0 (526) cleaned everything up...
2023-10-27 20:17:15.152 - info: hm-rpc.0 (407) xmlrpc -> 192.168.178.84:2010/ init ["http://192.168.178.77:2010",""]
2023-10-27 20:17:15.111 - info: valloxmv.0 (650) cleaned everything up...
2023-10-27 20:17:15.233 - info: hm-rpc.0 (407) Disconnected
2023-10-27 20:17:15.124 - info: host.ioBrokerTestsystem stopInstance system.adapter.admin.0 (force=false, process=true)
2023-10-27 20:17:15.127 - info: host.ioBrokerTestsystem stopInstance system.adapter.influxdb.0 (force=false, process=true)
2023-10-27 20:17:15.129 - info: host.ioBrokerTestsystem stopInstance system.adapter.javascript.0 (force=false, process=true)
2023-10-27 20:17:15.132 - info: host.ioBrokerTestsystem stopInstance system.adapter.scenes.0 (force=false, process=true)
2023-10-27 20:17:15.134 - info: host.ioBrokerTestsystem stopInstance system.adapter.scheduler.0 (force=false, process=false)
2023-10-27 20:17:15.143 - info: host.ioBrokerTestsystem stopInstance system.adapter.telegram.0 (force=false, process=false)
2023-10-27 20:17:15.146 - info: host.ioBrokerTestsystem stopInstance system.adapter.fritzbox.0 (force=false, process=true)
2023-10-27 20:17:15.156 - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rega.0 (force=false, process=true)
2023-10-27 20:17:15.158 - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rpc.0 (force=false, process=true)
2023-10-27 20:17:15.160 - info: host.ioBrokerTestsystem stopInstance system.adapter.hue.0 (force=false, process=false)
2023-10-27 20:17:15.162 - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.0 (force=false, process=false)
2023-10-27 20:17:15.165 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.ical.0
2023-10-27 20:17:15.173 - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.1 (force=false, process=false)
2023-10-27 20:17:15.175 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.ical.1
2023-10-27 20:17:15.177 - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.2 (force=false, process=false)
2023-10-27 20:17:15.178 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.ical.2
2023-10-27 20:17:15.190 - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.3 (force=false, process=false)
2023-10-27 20:17:15.192 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.ical.3
2023-10-27 20:17:15.194 - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.4 (force=false, process=false)
2023-10-27 20:17:15.196 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.ical.4
2023-10-27 20:17:15.198 - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.5 (force=false, process=false)
2023-10-27 20:17:15.199 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.ical.5
2023-10-27 20:17:15.201 - info: host.ioBrokerTestsystem stopInstance system.adapter.mqtt.0 (force=false, process=false)
2023-10-27 20:17:15.203 - info: host.ioBrokerTestsystem stopInstance system.adapter.openweathermap.0 (force=false, process=false)
2023-10-27 20:17:15.205 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.openweathermap.0
2023-10-27 20:17:15.207 - info: host.ioBrokerTestsystem stopInstance system.adapter.samsung-community.0 (force=false, process=false)
2023-10-27 20:17:15.208 - info: host.ioBrokerTestsystem stopInstance system.adapter.spotify-premium.0 (force=false, process=false)
2023-10-27 20:17:15.210 - info: host.ioBrokerTestsystem stopInstance system.adapter.tr-064.0 (force=false, process=true)
2023-10-27 20:17:15.212 - info: host.ioBrokerTestsystem stopInstance system.adapter.unifi.0 (force=false, process=true)
2023-10-27 20:17:15.214 - info: host.ioBrokerTestsystem stopInstance system.adapter.backitup.0 (force=false, process=true)
2023-10-27 20:17:15.216 - info: host.ioBrokerTestsystem stopInstance system.adapter.benchmark.0 (force=false, process=false)
2023-10-27 20:17:15.218 - info: host.ioBrokerTestsystem stopInstance system.adapter.daswetter.0 (force=false, process=false)
2023-10-27 20:17:15.220 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.daswetter.0
2023-10-27 20:17:15.223 - info: host.ioBrokerTestsystem stopInstance system.adapter.device-watcher.0 (force=false, process=false)
2023-10-27 20:17:15.224 - info: host.ioBrokerTestsystem stopInstance system.adapter.dwd.0 (force=false, process=false)
2023-10-27 20:17:15.227 - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.dwd.0
2023-10-27 20:17:15.228 - info: host.ioBrokerTestsystem stopInstance system.adapter.fully-tablet-control.0 (force=false, process=true)
2023-10-27 20:17:15.231 - info: host.ioBrokerTestsystem stopInstance system.adapter.info.0 (force=false, process=true)
2023-10-27 20:17:15.233 - info: host.ioBrokerTestsystem stopInstance system.adapter.nina.0 (force=false, process=true)
2023-10-27 20:17:15.235 - info: host.ioBrokerTestsystem stopInstance system.adapter.proxmox.0 (force=false, process=true)
2023-10-27 20:17:15.238 - info: host.ioBrokerTestsystem stopInstance system.adapter.rainbird.0 (force=false, process=false)
2023-10-27 20:17:15.240 - info: host.ioBrokerTestsystem stopInstance system.adapter.sayit.0 (force=false, process=false)
2023-10-27 20:17:15.241 - info: host.ioBrokerTestsystem stopInstance system.adapter.simple-api.0 (force=false, process=false)
2023-10-27 20:17:15.243 - info: host.ioBrokerTestsystem stopInstance system.adapter.socketio.0 (force=false, process=false)
2023-10-27 20:17:15.244 - info: host.ioBrokerTestsystem stopInstance system.adapter.tankerkoenig.0 (force=false, process=true)
2023-10-27 20:17:15.246 - info: host.ioBrokerTestsystem stopInstance system.adapter.trashschedule.0 (force=false, process=true)
2023-10-27 20:17:15.247 - info: host.ioBrokerTestsystem stopInstance system.adapter.valloxmv.0 (force=false, process=true)
2023-10-27 20:17:15.249 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-widgets-energy.0 (force=false, process=false)
2023-10-27 20:17:15.251 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-widgets-gauges.0 (force=false, process=false)
2023-10-27 20:17:15.252 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-widgets-jaeger-design.0 (force=false, process=false)
2023-10-27 20:17:15.253 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-widgets-material.0 (force=false, process=false)
2023-10-27 20:17:15.255 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2.0 (force=false, process=true)
2023-10-27 20:17:15.256 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-fancyswitch.0 (force=false, process=false)
2023-10-27 20:17:15.258 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-google-fonts.0 (force=false, process=false)
2023-10-27 20:17:15.260 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-history.0 (force=false, process=false)
2023-10-27 20:17:15.261 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-inventwo.0 (force=false, process=true)
2023-10-27 20:17:15.263 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-jqui-mfd.0 (force=false, process=false)
2023-10-27 20:17:15.264 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-justgage.0 (force=false, process=false)
2023-10-27 20:17:15.265 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-map.0 (force=false, process=false)
2023-10-27 20:17:15.267 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-materialdesign.0 (force=false, process=false)
2023-10-27 20:17:15.269 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-timeandweather.0 (force=false, process=false)
2023-10-27 20:17:15.270 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis.0 (force=false, process=false)
2023-10-27 20:17:15.272 - info: host.ioBrokerTestsystem stopInstance system.adapter.web.0 (force=false, process=true)
2023-10-27 20:17:15.274 - info: host.ioBrokerTestsystem stopInstance system.adapter.worx.0 (force=false, process=false)
2023-10-27 20:17:15.276 - info: host.ioBrokerTestsystem stopInstance system.adapter.echarts.0 (force=false, process=true)
2023-10-27 20:17:15.410 - info: admin.0 (330) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.413 - info: javascript.0 (367) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.421 - info: hm-rpc.0 (407) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.429 - info: unifi.0 (526) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.428 - info: backitup.0 (545) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.445 - info: info.0 (597) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.448 - info: fully-tablet-control.0 (574) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.424 - info: tr-064.0 (519) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.479 - info: proxmox.0 (618) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.486 - info: trashschedule.0 (20672) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.494 - info: valloxmv.0 (650) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.418 - info: hm-rega.0 (400) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.514 - info: vis-inventwo.0 (722) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.497 - info: vis-2.0 (47097) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.457 - info: nina.0 (609) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.483 - info: tankerkoenig.0 (633) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.549 - info: echarts.0 (736) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.577 - info: proxmox.0 (618) terminating
2023-10-27 20:17:15.578 - info: nina.0 (609) terminating
2023-10-27 20:17:15.582 - info: nina.0 (609) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.582 - info: proxmox.0 (618) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.596 - info: tankerkoenig.0 (633) terminating
2023-10-27 20:17:15.601 - info: tankerkoenig.0 (633) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.600 - info: influxdb.0 (337) terminating
2023-10-27 20:17:15.608 - info: influxdb.0 (337) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.501 - info: web.0 (729) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.615 - info: unifi.0 (526) terminating
2023-10-27 20:17:15.599 - info: backitup.0 (545) terminating
2023-10-27 20:17:15.619 - info: unifi.0 (526) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.616 - info: javascript.0 (367) terminating
2023-10-27 20:17:15.615 - info: trashschedule.0 (20672) terminating
2023-10-27 20:17:15.601 - info: fully-tablet-control.0 (574) terminating
2023-10-27 20:17:15.600 - info: tr-064.0 (519) terminating
2023-10-27 20:17:15.626 - info: valloxmv.0 (650) terminating
2023-10-27 20:17:15.595 - info: vis-2.0 (47097) terminating
2023-10-27 20:17:15.621 - info: vis-inventwo.0 (722) terminating
2023-10-27 20:17:15.630 - info: valloxmv.0 (650) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.626 - info: hm-rpc.0 (407) terminating
2023-10-27 20:17:15.620 - info: backitup.0 (545) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.667 - info: vis-inventwo.0 (722) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.621 - info: info.0 (597) terminating
2023-10-27 20:17:15.671 - info: javascript.0 (367) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.601 - info: admin.0 (330) terminating
2023-10-27 20:17:15.707 - info: info.0 (597) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.716 - info: admin.0 (330) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.664 - info: trashschedule.0 (20672) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.642 - info: tr-064.0 (519) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.419 - info: fritzbox.0 (385) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.723 - info: fritzbox.0 (385) terminating
2023-10-27 20:17:15.746 - info: fritzbox.0 (385) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.699 - info: vis-2.0 (47097) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.636 - info: fully-tablet-control.0 (574) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.788 - warn: web.0 (729) Timeout by termination of web-extensions!
2023-10-27 20:17:15.720 - info: hm-rpc.0 (407) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:15.807 - info: web.0 (729) terminated http server on port 8082
2023-10-27 20:17:15.865 - info: host.ioBrokerTestsystem stopInstance system.adapter.admin.0 send kill signal
2023-10-27 20:17:15.886 - info: host.ioBrokerTestsystem stopInstance system.adapter.javascript.0 send kill signal
2023-10-27 20:17:15.888 - info: host.ioBrokerTestsystem stopInstance system.adapter.scenes.0 send kill signal
2023-10-27 20:17:15.889 - info: host.ioBrokerTestsystem stopInstance system.adapter.fritzbox.0 send kill signal
2023-10-27 20:17:15.891 - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rega.0 send kill signal
2023-10-27 20:17:15.893 - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rpc.0 send kill signal
2023-10-27 20:17:15.895 - info: host.ioBrokerTestsystem stopInstance system.adapter.tr-064.0 send kill signal
2023-10-27 20:17:15.896 - info: host.ioBrokerTestsystem stopInstance system.adapter.unifi.0 send kill signal
2023-10-27 20:17:15.898 - info: host.ioBrokerTestsystem stopInstance system.adapter.backitup.0 send kill signal
2023-10-27 20:17:15.900 - info: host.ioBrokerTestsystem stopInstance system.adapter.fully-tablet-control.0 send kill signal
2023-10-27 20:17:15.901 - info: host.ioBrokerTestsystem stopInstance system.adapter.info.0 send kill signal
2023-10-27 20:17:15.903 - info: host.ioBrokerTestsystem stopInstance system.adapter.nina.0 send kill signal
2023-10-27 20:17:15.905 - info: host.ioBrokerTestsystem stopInstance system.adapter.proxmox.0 send kill signal
2023-10-27 20:17:15.907 - info: host.ioBrokerTestsystem stopInstance system.adapter.tankerkoenig.0 send kill signal
2023-10-27 20:17:15.908 - info: host.ioBrokerTestsystem stopInstance system.adapter.trashschedule.0 send kill signal
2023-10-27 20:17:15.910 - info: host.ioBrokerTestsystem stopInstance system.adapter.valloxmv.0 send kill signal
2023-10-27 20:17:15.912 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2.0 send kill signal
2023-10-27 20:17:15.914 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-inventwo.0 send kill signal
2023-10-27 20:17:15.915 - info: host.ioBrokerTestsystem stopInstance system.adapter.web.0 send kill signal
2023-10-27 20:17:15.917 - info: host.ioBrokerTestsystem stopInstance system.adapter.echarts.0 send kill signal
2023-10-27 20:17:15.413 - info: scenes.0 (374) Got terminate signal TERMINATE_YOURSELF
2023-10-27 20:17:15.902 - info: scenes.0 (374) terminating
2023-10-27 20:17:15.917 - info: scenes.0 (374) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:16.017 - info: fully-tablet-control.0 (574) terminating
2023-10-27 20:17:16.022 - info: hm-rega.0 (400) terminating
2023-10-27 20:17:16.021 - info: proxmox.0 (618) terminating
2023-10-27 20:17:16.026 - info: hm-rega.0 (400) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:16.031 - info: backitup.0 (545) terminating
2023-10-27 20:17:16.031 - info: vis-2.0 (47097) terminating
2023-10-27 20:17:16.018 - info: javascript.0 (367) terminating
2023-10-27 20:17:16.036 - info: info.0 (597) terminating
2023-10-27 20:17:16.039 - info: nina.0 (609) terminating
2023-10-27 20:17:16.040 - info: vis-inventwo.0 (722) terminating
2023-10-27 20:17:16.039 - info: unifi.0 (526) terminating
2023-10-27 20:17:16.040 - info: trashschedule.0 (20672) terminating
2023-10-27 20:17:16.049 - info: tr-064.0 (519) terminating
2023-10-27 20:17:16.045 - info: valloxmv.0 (650) terminating
2023-10-27 20:17:16.047 - info: echarts.0 (736) terminating
2023-10-27 20:17:16.054 - info: tankerkoenig.0 (633) terminating
2023-10-27 20:17:16.063 - info: admin.0 (330) terminating
2023-10-27 20:17:16.055 - info: web.0 (729) terminating
2023-10-27 20:17:16.063 - info: web.0 (729) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:16.070 - info: web.0 (729) terminating
2023-10-27 20:17:16.053 - info: echarts.0 (736) Terminated (NO_ERROR): Without reason
2023-10-27 20:17:16.118 - info: fritzbox.0 (385) terminating
2023-10-27 20:17:16.104 - info: scenes.0 (374) terminating
2023-10-27 20:17:16.357 - info: hm-rpc.0 (407) terminating
2023-10-27 20:17:16.589 - info: echarts.0 (736) terminating with timeout
2023-10-27 20:17:16.590 - info: hm-rega.0 (400) terminating with timeout
2023-10-27 20:17:16.589 - info: vis-2.0 (47097) terminating with timeout
2023-10-27 20:17:16.686 - info: javascript.0 (367) terminating with timeout
2023-10-27 20:17:16.712 - info: info.0 (597) terminating with timeout
2023-10-27 20:17:16.721 - info: admin.0 (330) terminating with timeout
2023-10-27 20:17:16.742 - info: tr-064.0 (519) terminating with timeout
2023-10-27 20:17:16.753 - info: fritzbox.0 (385) terminating with timeout
2023-10-27 20:17:16.770 - info: vis-inventwo.0 (722) terminating with timeout
2023-10-27 20:17:16.828 - info: web.0 (729) terminating with timeout
2023-10-27 20:17:16.857 - info: hm-rega.0 (400) terminating
2023-10-27 20:17:16.899 - info: scenes.0 (374) terminating with timeout
2023-10-27 20:17:17.048 - info: host.ioBrokerTestsystem instance system.adapter.nina.0 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:17.054 - info: host.ioBrokerTestsystem stopInstance system.adapter.admin.0 killing pid 330
2023-10-27 20:17:17.131 - info: host.ioBrokerTestsystem stopInstance system.adapter.javascript.0 killing pid 367
2023-10-27 20:17:17.134 - info: host.ioBrokerTestsystem stopInstance system.adapter.scenes.0 killing pid 374
2023-10-27 20:17:17.136 - info: host.ioBrokerTestsystem stopInstance system.adapter.fritzbox.0 killing pid 385
2023-10-27 20:17:17.138 - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rega.0 killing pid 400
2023-10-27 20:17:17.140 - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rpc.0 killing pid 407
2023-10-27 20:17:17.142 - info: host.ioBrokerTestsystem stopInstance system.adapter.info.0 killing pid 597
2023-10-27 20:17:17.147 - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2.0 killing pid 47097
2023-10-27 20:17:17.149 - info: host.ioBrokerTestsystem stopInstance system.adapter.web.0 killing pid 729
2023-10-27 20:17:17.151 - info: host.ioBrokerTestsystem stopInstance system.adapter.echarts.0 killing pid 736
2023-10-27 20:17:17.572 - info: host.ioBrokerTestsystem instance system.adapter.proxmox.0 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:18.218 - info: host.ioBrokerTestsystem instance system.adapter.unifi.0 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:18.416 - info: host.ioBrokerTestsystem instance system.adapter.backitup.0 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:18.419 - info: host.ioBrokerTestsystem instance system.adapter.tankerkoenig.0 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:18.501 - info: host.ioBrokerTestsystem instance system.adapter.influxdb.0 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:19.577 - info: host.ioBrokerTestsystem instance system.adapter.fully-tablet-control.0 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:19.580 - info: host.ioBrokerTestsystem instance system.adapter.valloxmv.0 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:19.675 - info: host.ioBrokerTestsystem instance system.adapter.trashschedule.0 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:19.822 - info: host.ioBrokerTestsystem instance system.adapter.tr-064.0 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:19.825 - info: host.ioBrokerTestsystem instance system.adapter.vis-inventwo.0 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:19.826 - info: host.ioBrokerTestsystem All instances are stopped.
2023-10-27 20:17:20.311 - info: host.ioBrokerTestsystem instance system.adapter.javascript.0 terminated with code 0 (NO_ERROR)
2023-10-27 20:17:20.313 - info: host.ioBrokerTestsystem All instances are stopped.
2023-10-27 20:17:20.315 - warn: host.ioBrokerTestsystem instance system.adapter.fritzbox.0 terminated due to SIGTERM
2023-10-27 20:17:20.316 - info: host.ioBrokerTestsystem instance system.adapter.fritzbox.0 terminated with code null ()
2023-10-27 20:17:20.318 - info: host.ioBrokerTestsystem All instances are stopped.
2023-10-27 20:17:20.361 - warn: host.ioBrokerTestsystem instance system.adapter.hm-rega.0 terminated due to SIGTERM
2023-10-27 20:17:20.362 - info: host.ioBrokerTestsystem instance system.adapter.hm-rega.0 terminated with code null ()
2023-10-27 20:17:20.364 - info: host.ioBrokerTestsystem All instances are stopped.
2023-10-27 20:17:20.507 - warn: host.ioBrokerTestsystem instance system.adapter.hm-rpc.0 terminated due to SIGTERM
2023-10-27 20:17:20.509 - info: host.ioBrokerTestsystem instance system.adapter.hm-rpc.0 terminated with code null ()
2023-10-27 20:17:20.510 - info: host.ioBrokerTestsystem All instances are stopped.
2023-10-27 20:17:20.512 - warn: host.ioBrokerTestsystem instance system.adapter.web.0 terminated due to SIGTERM
2023-10-27 20:17:20.513 - info: host.ioBrokerTestsystem instance system.adapter.web.0 terminated with code null ()
2023-10-27 20:17:20.515 - info: host.ioBrokerTestsystem All instances are stopped.
2023-10-27 20:17:20.603 - warn: host.ioBrokerTestsystem instance system.adapter.echarts.0 terminated due to SIGTERM
2023-10-27 20:17:20.605 - info: host.ioBrokerTestsystem instance system.adapter.echarts.0 terminated with code null ()
2023-10-27 20:17:20.607 - info: host.ioBrokerTestsystem All instances are stopped.
2023-10-27 20:17:20.608 - warn: host.ioBrokerTestsystem instance system.adapter.info.0 terminated due to SIGTERM
2023-10-27 20:17:20.609 - info: host.ioBrokerTestsystem instance system.adapter.info.0 terminated with code null ()
2023-10-27 20:17:20.612 - info: host.ioBrokerTestsystem All instances are stopped.
2023-10-27 20:17:20.657 - error: host.ioBrokerTestsystem Caught by controller[0]: Error: DB closed
2023-10-27 20:17:20.659 - error: host.ioBrokerTestsystem Caught by controller[0]: at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25)
2023-10-27 20:17:20.660 - error: host.ioBrokerTestsystem Caught by controller[0]: at Socket. (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20)
2023-10-27 20:17:20.662 - error: host.ioBrokerTestsystem Caught by controller[0]: at Object.onceWrapper (node:events:632:26)
2023-10-27 20:17:20.663 - error: host.ioBrokerTestsystem Caught by controller[0]: at Socket.emit (node:events:517:28)
2023-10-27 20:17:20.664 - error: host.ioBrokerTestsystem Caught by controller[0]: at Socket.emit (node:domain:489:12)
2023-10-27 20:17:20.666 - error: host.ioBrokerTestsystem Caught by controller[0]: at TCP. (node:net:350:12)
2023-10-27 20:17:20.667 - warn: host.ioBrokerTestsystem instance system.adapter.admin.0 terminated due to SIGTERM
2023-10-27 20:17:20.668 - info: host.ioBrokerTestsystem instance system.adapter.admin.0 terminated with code null ()
2023-10-27 20:17:20.670 - info: host.ioBrokerTestsystem All instances are stopped.
2023-10-27 20:17:20.828 - warn: host.ioBrokerTestsystem instance system.adapter.scenes.0 terminated due to SIGTERM
2023-10-27 20:17:20.829 - info: host.ioBrokerTestsystem instance system.adapter.scenes.0 terminated with code null ()
2023-10-27 20:17:20.831 - info: host.ioBrokerTestsystem All instances are stopped.
2023-10-27 20:17:20.834 - warn: host.ioBrokerTestsystem instance system.adapter.vis-2.0 terminated due to SIGTERM
2023-10-27 20:17:20.836 - info: host.ioBrokerTestsystem instance system.adapter.vis-2.0 terminated with code null ()
2023-10-27 20:17:20.839 - info: host.ioBrokerTestsystem All instances are stopped.
2023-10-27 20:17:20.995 - info: host.ioBrokerTestsystem terminated
2023-10-27 20:17:25.609 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Successfully stopped js-controller
2023-10-27 20:17:25.628 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Server is running on http://localhost:8081
2023-10-27 20:18:26.655 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Final information delivered
2023-10-27 20:18:26.787 - info: host.ioBrokerTestsystem [CONTROLLER_AUTO_UPGRADE] Successfully started js-controller
2023-10-27 20:18:30.077 - info: host.ioBrokerTestsystem iobroker.js-controller version 5.0.15 js-controller starting
2023-10-27 20:18:30.089 - info: host.ioBrokerTestsystem Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker

                                          1 Reply Last reply Reply Quote 0
                                          • M
                                            mpl1338 last edited by

                                            Screenshot 2023-10-28 212034.png

                                            Plattform
                                            linux
                                            Betriebssystem
                                            linux
                                            Architektur
                                            x64
                                            CPUs
                                            2
                                            Geschwindigkeit
                                            3600 MHz
                                            Modell
                                            Intel(R) Core(TM) i3-8109U CPU @ 3.00GHz
                                            RAM
                                            5.16 GB
                                            System-Betriebszeit
                                            12 T. 00:16:02
                                            Node.js
                                            v18.18.2
                                            time
                                            1698520878074
                                            timeOffset
                                            -120
                                            NPM
                                            9.8.1
                                            Anzahl der Adapter
                                            596
                                            Datenträgergröße
                                            28 GB
                                            freier Festplattenspeicher
                                            14.66 GB
                                            Aktive Instanzen
                                            36
                                            Pfad
                                            /opt/iobroker/
                                            Betriebszeit
                                            19:20:45
                                            Hostname
                                            iobroker

                                            Was passt nicht?

                                            und btw: Screenshot 2023-10-28 212227.png

                                            könnte man hier mal das Change log nutzen oder einen Link anstelle des Textes setzen?

                                            "see CHANGELOG.md" ist nicht gerade der korrekte Text für einen Changelog.

                                            Thomas Braun foxriver76 2 Replies 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

                                            742
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            js-controller stable upgrade
                                            82
                                            509
                                            98171
                                            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