Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. System & Admin Upgrade "exited with code 25" Start-Schleife?

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    System & Admin Upgrade "exited with code 25" Start-Schleife?

    This topic has been deleted. Only users with topic management privileges can see it.
    • wendy2702
      wendy2702 @adarof last edited by

      @adarof mal ne Frage, hast du den Rechner mal neu gestartet?

      A 1 Reply Last reply Reply Quote 0
      • A
        adarof @wendy2702 last edited by

        @wendy2702 Ja, einmal nach dem Ubuntu Update und auch gerade bevor ich Deine Idee mit dem "npm install & iob stop & iob fix & iob start & iob update" gemacht habe

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

          @adarof

          iob stop all
          
          A 1 Reply Last reply Reply Quote 0
          • A
            adarof @Thomas Braun last edited by adarof

            @thomas-braun Danke, stopped das mehr als einfach "iob stop" ?

            Nun ist es wieder kaputt gegangen:

            hmersch@RoofServer:/opt/iobroker$ iob stop all
            The adapter "admin.0" was stopped.
            The adapter "history.0" was stopped.
            The adapter "javascript.0" was stopped.
            The adapter "email.0" was stopped.
            The adapter "sql.0" was stopped.
            The adapter "telegram.0" was stopped.
            The adapter "tr-064.0" was stopped.
            The adapter "hm-rpc.0" was stopped.
            The adapter "hm-rpc.1" was stopped.
            The adapter "hm-rega.0" was stopped.
            The adapter "ical.0" was stopped.
            The adapter "unifi.0" was stopped.
            The adapter "backitup.0" was stopped.
            The adapter "sonoff.0" was stopped.
            The adapter "hm-rpc.2" was stopped.
            The adapter "ping.0" was stopped.
            The adapter "homeconnect.0" was stopped.
            The adapter "mielecloudservice.0" was stopped.
            The adapter "wiegand-tcpip.0" was stopped.
            The adapter "nut.0" was stopped.
            The adapter "alexa2.0" was stopped.
            The adapter "modbus.0" was stopped.
            The adapter "modbus.1" was stopped.
            The adapter "tuya.0" was stopped.
            The adapter "evcc.0" was stopped.
            The adapter "lg-thinq.0" was stopped.
            The adapter "opendtu.0" was stopped.
            The adapter "device-watcher.0" was stopped.
            The adapter "discovery.0" was stopped.
            The adapter "web.0" was stopped.
            The adapter "mobile.0" was stopped.
            The adapter "vis.0" was stopped.
            The adapter "dwd.0" was stopped.
            The adapter "icons-material-png.0" was stopped.
            The adapter "icons-mfd-svg.0" was stopped.
            The adapter "vis-timeandweather.0" was stopped.
            The adapter "vis-fancyswitch.0" was stopped.
            The adapter "vis-hqwidgets.0" was stopped.
            The adapter "vis-metro.0" was stopped.
            The adapter "vis-colorpicker.0" was stopped.
            The adapter "icons-mfd-png.0" was stopped.
            The adapter "vis-jqui-mfd.0" was stopped.
            The adapter "flot.0" was stopped.
            The adapter "vis-history.0" was stopped.
            The adapter "vis-bars.0" was stopped.
            The adapter "icons-addictive-flavour-png.0" was stopped.
            The adapter "text2command.0" was stopped.
            The adapter "daswetter.0" was stopped.
            The adapter "vis-canvas-gauges.0" was stopped.
            The adapter "material.0" was stopped.
            The adapter "nina.0" was stopped.
            The adapter "vis-rgraph.0" was stopped.
            The adapter "rickshaw.0" was stopped.
            The adapter "simple-api.0" was stopped.
            The adapter "govee.0" was stopped.
            The adapter "easee.1" was stopped.
            The adapter "parser.0" was stopped.
            The adapter "vw-connect.0" was stopped.
            The adapter "statistics.0" was stopped.
            hmersch@RoofServer:/opt/iobroker$ iob stop all^C
            hmersch@RoofServer:/opt/iobroker$ iob stop all
             Cannot determine Lua scripts strategy: Connection is closed. ["cfg.o.system.host.RoofServer"]
            
            
            
            Uncaught Rejection: Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/opt/iobroker/node_modules/@iobroker/db-objects-jsonl/build/esm/index.js' imported from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/dbConnection.js
                at finalizeResolution (node:internal/modules/esm/resolve:283:11)
                at moduleResolve (node:internal/modules/esm/resolve:952:10)
                at defaultResolve (node:internal/modules/esm/resolve:1188:11)
                at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:642:12)
                at #cachedDefaultResolve (node:internal/modules/esm/loader:591:25)
                at ModuleLoader.resolve (node:internal/modules/esm/loader:574:38)
                at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:236:38)
                at ModuleLoader.import (node:internal/modules/esm/loader:539:34)
                at defaultImportModuleDynamicallyForModule (node:internal/modules/esm/utils:215:31)
                at importModuleDynamicallyCallback (node:internal/modules/esm/utils:254:12)
            hmersch@RoofServer:/opt/iobroker$
            hmersch@RoofServer:/opt/iobroker$
            hmersch@RoofServer:/opt/iobroker$
            hmersch@RoofServer:/opt/iobroker$ iob stop all
            node:internal/modules/cjs/loader:1215
              throw err;
              ^
            
            Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                at Module._resolveFilename (node:internal/modules/cjs/loader:1212:15)
                at Module._load (node:internal/modules/cjs/loader:1043:27)
                at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12)
                at node:internal/main/run_main_module:28:49 {
              code: 'MODULE_NOT_FOUND',
              requireStack: []
            }
            
            Node.js v20.19.2
            hmersch@RoofServer:/opt/iobroker$ iob stop all
            node:internal/modules/cjs/loader:1215
              throw err;
              ^
            
            Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                at Module._resolveFilename (node:internal/modules/cjs/loader:1212:15)
                at Module._load (node:internal/modules/cjs/loader:1043:27)
                at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12)
                at node:internal/main/run_main_module:28:49 {
              code: 'MODULE_NOT_FOUND',
              requireStack: []
            }
            
            Node.js v20.19.2
            
            A 1 Reply Last reply Reply Quote 0
            • A
              adarof @adarof last edited by adarof

              und ... ein paar sekunden später:

              hmersch@RoofServer:/opt/iobroker$ iob status
              iobroker is running on this host.
              
              
              Objects type: jsonl
              States  type: jsonl
              

              okay, davon kann ich dann "iob start admin.0" machen... oder auch nicht:

              hmersch@RoofServer:/opt/iobroker$ iob start admin.0
              node:internal/modules/cjs/loader:1215
                throw err;
                ^
              
              Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                  at Module._resolveFilename (node:internal/modules/cjs/loader:1212:15)
                  at Module._load (node:internal/modules/cjs/loader:1043:27)
                  at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12)
                  at node:internal/main/run_main_module:28:49 {
                code: 'MODULE_NOT_FOUND',
                requireStack: []
              }
              
              

              nun ist es wieder kaputt und ich müsste mit "npm install .." loslegen?

              Irgendwas ist da doch ganz ganz merkwürdig

              Da läuft auch noch jede Menge bzw wird gestartet:

              hmersch@RoofServer:/opt/iobroker$ ps aux |grep iobroker
              iobroker   16132 76.8  3.3 11995472 543668 ?     Rsl  21:16   0:40 iobroker.js-controller
              iobroker   16218 13.5  0.6 11741200 100672 ?     Sl   21:16   0:03 io.telegram.0
              iobroker   16265 34.5  2.1 12091024 356848 ?     Sl   21:16   0:05 io.admin.0
              iobroker   16287 16.5  0.6 11565564 103964 ?     Sl   21:16   0:01 io.history.0
              iobroker   16331 41.2  0.6 11561820 102412 ?     Sl   21:17   0:01 /usr/bin/node /opt/iobroker/node_modules/iobroker.ical/main.js --instance 0 --loglevel info
              iobroker   16342  113  0.9 11603300 156264 ?     Rl   21:17   0:02 /usr/bin/node /opt/iobroker/node_modules/iobroker.javascript/main.js --instance 0 --loglevel info
              iobroker   16349 94.0  0.5 11559260 93536 ?      Rl   21:17   0:01 /usr/bin/node /opt/iobroker/node_modules/iobroker.unifi/main.js --instance 0 --loglevel warn
              iobroker   16358  136  0.5 11538412 85436 ?      Rl   21:17   0:01 /usr/bin/node /opt/iobroker/node_modules/iobroker.email/build/main.js --instance 0 --loglevel info
              hmersch    16380  0.0  0.0   9608  2428 pts/0    S+   21:17   0:00 grep --color=auto iobroker
              
              

              Wer startet denn da noch was?

              Gibt es unterschiedliche Wege, wie der iobroker Prozess gestartet wird und ich gehe beide wenn ich hier "iob start" macht?

              Nach einem erneuten "iob stop all":

              hmersch@RoofServer:/opt/iobroker$ ps aux |grep iobroker
              iobroker   16941 34.7  5.1 2045780 834000 ?      Rl   21:19   0:43 npm install @iobroker-javascript.0/klf-200-api@npm:klf-200-api@latest
              hmersch    17589  0.0  0.0   9608  2348 pts/0    S+   21:21   0:00 grep --color=auto iobroker
              

              ...und dann wird neu gestartet. Das "iob stop all" scheint bei mir also nicht zu stoppen sondern zu restarten.

              Kann sich das jemand erklären?

              wendy2702 Thomas Braun 2 Replies Last reply Reply Quote 0
              • wendy2702
                wendy2702 @adarof last edited by wendy2702

                @adarof bei sauberer Installation bedeutet ein

                iob stop
                

                Das alles gestoppt wird.

                Wenn du den stoppst, schaust das alle Prozesse beendet sind, dann den Rechner mal neu startest und mal direkt das log anschaust.

                Edit: sieht fast so aus als wenn er die Adapter teilweise neu installiert. Vielleicht bist du auch nur zu ungeduldig

                A 2 Replies Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @adarof last edited by

                  @adarof

                  systemctl stop iobroker.service
                  
                  A 1 Reply Last reply Reply Quote 0
                  • A
                    adarof @wendy2702 last edited by

                    @wendy2702

                    hmersch@RoofServer:/opt/iobroker$ iob stop
                    hmersch@RoofServer:/opt/iobroker$ ps aux|grep iob
                    hmersch    18154  0.0  0.0   9476  2396 pts/0    S+   21:23   0:00 grep --color=auto iob
                    hmersch@RoofServer:/opt/iobroker$ ps aux|grep iob
                    hmersch    18156  0.0  0.0   9476  2352 pts/0    S+   21:23   0:00 grep --color=auto iob
                    

                    ... und nen reboot ...

                    hmersch@RoofServer:~$ ps aux|grep iob
                    iobroker    1429 77.2  3.4 12123260 557232 ?     Rsl  21:24   0:26 iobroker.js-controller
                    iobroker    2315 30.0  2.1 12082912 345432 ?     Rl   21:25   0:06 io.admin.0
                    iobroker    2362 14.5  0.6 11565428 106084 ?     Sl   21:25   0:02 io.history.0
                    iobroker    2540 37.5  1.0 11608208 164672 ?     Sl   21:25   0:02 /usr/bin/node /opt/iobroker/node_modules/iobroker.javascript/main.js --instance 0 --loglevel info
                    iobroker    2548 28.7  0.6 11560052 97652 ?      Sl   21:25   0:02 /usr/bin/node /opt/iobroker/node_modules/iobroker.email/build/main.js --instance 0 --loglevel info
                    iobroker    2563 48.5  0.5 11562508 96880 ?      Sl   21:25   0:01 /usr/bin/node /opt/iobroker/node_modules/iobroker.sql/main.js --instance 0 --loglevel info
                    iobroker    2601  0.0  0.0      0     0 ?        Z    21:25   0:00 [sh] <defunct>
                    hmersch     2605  0.0  0.0   9608  2216 pts/0    R+   21:25   0:00 grep --color=auto iob
                    

                    ... danach warten bis zum "absturz" und "iob logs"

                    Hm:

                    2025-05-27 21:27:41.438  - error: host.RoofServer Error: Could not determine controller directory
                        at getControllerDir (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:1833:11)
                        at Module.getPidsFileName (file:///opt/iobroker/node_modules/@iobroker/js-controller-common-db/build/esm/lib/common/tools.js:3368:22)
                        at Timeout._onTimeout (file:///opt/iobroker/node_modules/iobroker.js-controller/build/esm/main.js:2871:91)
                        at listOnTimeout (node:internal/timers:581:17)
                        at processTimers (node:internal/timers:519:7)
                    
                    
                    
                    1 Reply Last reply Reply Quote 0
                    • A
                      adarof @Thomas Braun last edited by adarof

                      @thomas-braun Ah, danke - logisch, ja! Kommt sich das in die Quere mit "iob start" - also werden dann 2 Instanzen auf /opt/iobroker gestartet? Kann ich vielleicht den iobroker.service falsch eingerichtet haben?

                      Aber auch wenn ich "systemctl stop iobroker.service" mache und danach "manuell" via "iob start" kommt es zum "Absturz" - und dabei sind immernoch "ADAPTER_ALREADY_RUNNING"-Meldungen im Log.
                      Irgendwas läuft da einfach doppelt

                      1 Reply Last reply Reply Quote 0
                      • A
                        adarof @wendy2702 last edited by

                        @wendy2702 Okay - vielleicht ... lass ich ihn dann mal über Nacht sich erholen. Mir fehlen gerade etwas auch die Ideen bzw das Hintergrundwissen um da bei fehlerhaften Verzeichniszugriffen, die aber eigentlich / kurz später da sind noch eine Idee zu haben.

                        Würde mich morgen melden und hoffen, dass Ihr weitere Ideen habt.
                        Dank Euch für heute abend

                        A 1 Reply Last reply Reply Quote 0
                        • A
                          adarof @adarof last edited by

                          Faszinierenderweise hat es noch 2 mal Neugestartet und seit dem läuft es.
                          Bin nun ein paar Tage unterwegs und werde danach das Neustartverhalten dann nochmal eingehender untersuchen.
                          Ob das dann noch was mit dem System- und/oder Admin Upgrade zu tun hat ... werden wir später sehen

                          Danke Euch erstmal

                          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

                          955
                          Online

                          31.7k
                          Users

                          79.7k
                          Topics

                          1.3m
                          Posts

                          3
                          38
                          505
                          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