Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Iobroker startet nicht mehr

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Iobroker startet nicht mehr

    This topic has been deleted. Only users with topic management privileges can see it.
    • H
      Hoss0305 last edited by

      @Thomas-Braun

      Wie geschrieben, bekomme ich das ioBroker WebUI nicht gestartet. Dieses Problem trat heute Vormittag ohne jegliches Zutun auf. Vor einer zur nächsten Minute war ein Zugriff nicht mehr möglich.

      Wenn ich den Befehl

      node node_modules/iobroker.js-controller/controller.js --logs
      

      eingebe, erhalte ich

      pi@ioBroker-Pi:/opt/iobroker $ node node_modules/iobroker.js-controller/controller.js --logs
      - info: host.ioBroker-Pi iobroker.js-controller version 3.2.16 js-contr                        oller starting
      - info: host.ioBroker-Pi Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
      - info: host.ioBroker-Pi hostname: ioBroker-Pi, node: v12.22.1
      - info: host.ioBroker-Pi ip addresses: 192.168.123.61 2a02:2f4:484e:af00:dbf8:12ef:9fbf:4984 fe80::ee08:c96b:c94e:f438
      - info: host.ioBroker-Pi-Server  Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
      - error: host.ioBroker-Pi No connection to databases possible, restart
      - info: host.ioBroker-Pi iobroker _restart
      

      Kann mir da irgend jemand helfen, woran es liegen könnte, dass ich das ioBroker WebUI nicht gestartet bekomme.

      Glasfaser 1 Reply Last reply Reply Quote 0
      • Glasfaser
        Glasfaser @Hoss0305 last edited by

        @hoss0305 sagte in Iobroker startet nicht mehr:

        • info: host.ioBroker-Pi-Server
          Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001

        Der Port 9001 wird schon auf deinem System genutzt , deshalb startet ioBroker nicht

        H 1 Reply Last reply Reply Quote 0
        • H
          Hoss0305 @Glasfaser last edited by

          @glasfaser
          Wie kann ich denn ermitteln, wodurch der Port 9001 belegt ist, das System hat doch zuvor immer funktioniert.

          Glasfaser 1 Reply Last reply Reply Quote 0
          • Glasfaser
            Glasfaser @Hoss0305 last edited by

            @hoss0305

            https://forum.iobroker.net/topic/43839/gelöst-ich-bekomme-den-iobroker-auf-nuc-nicht-ans-laufen?_=1617990930977

            H 1 Reply Last reply Reply Quote 0
            • H
              Hoss0305 @Glasfaser last edited by

              @glasfaser
              Wenn ich mit

              netstat
              

              da rangehe, erhalte ich:

              pi@ioBroker-Pi:/opt/iobroker $ netstat
              Aktive Internetverbindungen (ohne Server)
              Proto Recv-Q Send-Q Local Address           Foreign Address         State
              tcp        0      0 localhost:49308         localhost:9001          VERBUNDEN
              tcp        0      0 ioBroker-Pi-WLAN.:45890 FR-PAR-ANX-R009.te:5938 VERBUNDEN
              tcp        0      0 localhost:9001          localhost:49308         VERBUNDEN
              tcp        0      0 localhost:44256         localhost:9000          VERBUNDEN
              tcp        0      0 localhost:49310         localhost:9001          VERBUNDEN
              tcp        0      0 localhost:9000          localhost:44258         VERBUNDEN
              tcp        0    240 ioBroker-Pi-WLAN.fr:ssh MININT-91OJ9JA.fr:54023 VERBUNDEN
              tcp        0      0 localhost:9000          localhost:44256         VERBUNDEN
              tcp        0      0 localhost:9001          localhost:49310         VERBUNDEN
              tcp        0      0 localhost:44258         localhost:9000          VERBUNDEN
              Aktive Sockets in der UNIX-Dom▒ne (ohne Server)
              Proto RefCnt Flags       Type       State         I-Node   Pfad
              unix  2      [ ]         DGRAM                    10511    /run/systemd/journal/syslog
              unix  14     [ ]         DGRAM                    10535    /run/systemd/journal/dev-log
              unix  2      [ ]         DGRAM                    14650    /var/run/wpa_supplicant/wlan0
              unix  2      [ ]         DGRAM                    14655    /var/run/wpa_supplicant/p2p-dev-wlan0
              unix  3      [ ]         DGRAM                    10446    /run/systemd/notify
              unix  2      [ ]         DGRAM                    16602    /run/user/1000/systemd/notify
              unix  7      [ ]         DGRAM                    10465    /run/systemd/journal/socket
              unix  2      [ ]         DGRAM                    15598
              unix  3      [ ]         STREAM     VERBUNDEN     12767    /var/run/dbus/system_bus_socket
              unix  3      [ ]         STREAM     VERBUNDEN     15875    /run/systemd/journal/stdout
              unix  3      [ ]         STREAM     VERBUNDEN     15053
              unix  3      [ ]         STREAM     VERBUNDEN     15071
              unix  3      [ ]         STREAM     VERBUNDEN     15605
              unix  3      [ ]         STREAM     VERBUNDEN     6135
              unix  3      [ ]         STREAM     VERBUNDEN     12193
              unix  3      [ ]         STREAM     VERBUNDEN     12764    /var/run/dbus/system_bus_socket
              unix  3      [ ]         STREAM     VERBUNDEN     6137     /run/systemd/journal/stdout
              unix  3      [ ]         STREAM     VERBUNDEN     13764    /run/systemd/journal/stdout
              unix  3      [ ]         STREAM     VERBUNDEN     15536
              unix  3      [ ]         STREAM     VERBUNDEN     14281    /var/run/dbus/system_bus_socket
              unix  2      [ ]         DGRAM                    15540
              unix  2      [ ]         DGRAM                    14511
              unix  2      [ ]         DGRAM                    15706
              unix  3      [ ]         STREAM     VERBUNDEN     14561
              unix  3      [ ]         STREAM     VERBUNDEN     15974
              unix  3      [ ]         STREAM     VERBUNDEN     13928    /var/run/dbus/system_bus_socket
              unix  3      [ ]         STREAM     VERBUNDEN     15973
              unix  2      [ ]         DGRAM                    10664
              unix  3      [ ]         STREAM     VERBUNDEN     15549    /run/systemd/journal/stdout
              unix  3      [ ]         DGRAM                    5963
              unix  3      [ ]         DGRAM                    10668
              unix  3      [ ]         STREAM     VERBUNDEN     12651
              unix  3      [ ]         DGRAM                    5962
              unix  3      [ ]         STREAM     VERBUNDEN     10660
              unix  3      [ ]         STREAM     VERBUNDEN     5452     /run/systemd/journal/stdout
              unix  3      [ ]         STREAM     VERBUNDEN     13569    /run/systemd/journal/stdout
              unix  2      [ ]         DGRAM                    5960
              unix  3      [ ]         DGRAM                    10667
              unix  3      [ ]         STREAM     VERBUNDEN     12548
              unix  3      [ ]         STREAM     VERBUNDEN     14041    /var/run/dbus/system_bus_socket
              unix  3      [ ]         STREAM     VERBUNDEN     12649
              unix  2      [ ]         DGRAM                    12900
              unix  3      [ ]         STREAM     VERBUNDEN     12788
              unix  3      [ ]         STREAM     VERBUNDEN     16608
              unix  2      [ ]         DGRAM                    12646
              unix  2      [ ]         DGRAM                    5340
              unix  2      [ ]         DGRAM                    12550
              unix  3      [ ]         STREAM     VERBUNDEN     14736    /run/systemd/journal/stdout
              unix  3      [ ]         STREAM     VERBUNDEN     17451    /var/run/dbus/system_bus_socket
              unix  3      [ ]         STREAM     VERBUNDEN     12648
              unix  3      [ ]         STREAM     VERBUNDEN     12902
              unix  3      [ ]         STREAM     VERBUNDEN     14497    /run/systemd/journal/stdout
              unix  3      [ ]         DGRAM                    16605
              unix  3      [ ]         STREAM     VERBUNDEN     12761
              unix  3      [ ]         STREAM     VERBUNDEN     12762
              unix  3      [ ]         STREAM     VERBUNDEN     12713
              unix  2      [ ]         DGRAM                    16587
              unix  3      [ ]         STREAM     VERBUNDEN     12719
              unix  3      [ ]         DGRAM                    16604
              unix  3      [ ]         STREAM     VERBUNDEN     5973
              unix  3      [ ]         STREAM     VERBUNDEN     12765    /var/run/dbus/system_bus_socket
              unix  2      [ ]         DGRAM                    17432
              unix  3      [ ]         STREAM     VERBUNDEN     12763    /var/run/dbus/system_bus_socket
              unix  3      [ ]         STREAM     VERBUNDEN     16579
              unix  3      [ ]         STREAM     VERBUNDEN     17439    /run/systemd/journal/stdout
              unix  2      [ ]         DGRAM                    16584
              unix  2      [ ]         DGRAM                    8572
              unix  3      [ ]         DGRAM                    5965
              unix  2      [ ]         STREAM     VERBUNDEN     16494
              unix  3      [ ]         STREAM     VERBUNDEN     12896
              unix  3      [ ]         DGRAM                    10448
              unix  3      [ ]         STREAM     VERBUNDEN     13937    /var/run/dbus/system_bus_socket
              unix  3      [ ]         DGRAM                    5964
              unix  3      [ ]         DGRAM                    10449
              unix  3      [ ]         STREAM     VERBUNDEN     12766    /var/run/dbus/system_bus_socket
              unix  2      [ ]         DGRAM                    13863
              unix  2      [ ]         DGRAM                    13869
              unix  2      [ ]         DGRAM                    13847
              unix  3      [ ]         STREAM     VERBUNDEN     13754
              unix  3      [ ]         STREAM     VERBUNDEN     13465
              unix  3      [ ]         STREAM     VERBUNDEN     13758    /run/systemd/journal/stdout
              unix  3      [ ]         STREAM     VERBUNDEN     12489    /run/systemd/journal/stdout
              unix  3      [ ]         STREAM     VERBUNDEN     26289
              unix  3      [ ]         STREAM     VERBUNDEN     12464    /run/systemd/journal/stdout
              unix  3      [ ]         STREAM     VERBUNDEN     13686
              unix  3      [ ]         STREAM     VERBUNDEN     13567
              unix  3      [ ]         STREAM     VERBUNDEN     27060    /run/systemd/journal/stdout
              unix  3      [ ]         STREAM     VERBUNDEN     13687    /run/systemd/journal/stdout
              unix  2      [ ]         DGRAM                    13929
              unix  3      [ ]         STREAM     VERBUNDEN     13860
              

              Da kann ich aber leider immer noch nicht erkennen, wodurch der Port belegt ist, sorry, bin leider noch nicht ganz so fit mit dem System.

              1 Reply Last reply Reply Quote 0
              • Glasfaser
                Glasfaser last edited by Glasfaser

                @hoss0305

                Zeige mal

                iobroker status
                iobroker list instances
                ps auxww|grep io
                
                1 Reply Last reply Reply Quote 0
                • H
                  Hoss0305 last edited by

                  So, hier die Codezeilen entsprechend Deinen Anfragen

                  pi@ioBroker-Pi:/opt/iobroker $ iobroker status
                  iobroker is running on this host.
                  
                  
                  Objects type: file
                  States  type: file
                  pi@ioBroker-Pi:/opt/iobroker $ iobroker list instances
                  
                  
                  + instance is alive
                  pi@ioBroker-Pi:/opt/iobroker $ ps auxww|grep io
                  root        11  0.0  0.0      0     0 ?        S    20:23   0:00 [migration/0]
                  root        14  0.0  0.0      0     0 ?        S    20:23   0:00 [migration/1]
                  root        19  0.0  0.0      0     0 ?        S    20:23   0:00 [migration/2]
                  root        24  0.0  0.0      0     0 ?        S    20:23   0:00 [migration/3]
                  root        56  0.0  0.0      0     0 ?        I<   20:23   0:00 [rpciod]
                  root        58  0.0  0.0      0     0 ?        I<   20:23   0:00 [xprtiod]
                  root        60  0.0  0.0      0     0 ?        I<   20:23   0:00 [nfsiod]
                  root        63  0.0  0.0      0     0 ?        I<   20:23   0:00 [DWC Notificatio]
                  message+   321  0.0  0.3   6652  3552 ?        Ss   20:23   0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
                  avahi      356  0.0  0.2   5772  2624 ?        Ss   20:23   0:00 avahi-daemon: running [ioBroker-Pi.local]
                  iobroker   569  2.7  5.2 138676 49524 ?        Ssl  20:23   0:07 iobroker.js-controller
                  pi         745  0.0  0.1   4900  1592 pts/0    S+   20:28   0:00 grep --color=auto io
                  
                  
                  1 Reply Last reply Reply Quote 0
                  • Glasfaser
                    Glasfaser last edited by

                    @hoss0305

                    Hast du deine Pi mal neu gestartet ?

                    Zeige mal

                    which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
                    
                    H 1 Reply Last reply Reply Quote 0
                    • H
                      Hoss0305 @Glasfaser last edited by

                      @glasfaser
                      Ja, diverse Male, auch schon längere Zeit vom Netzstrom getrennt und dann wieder in Betrieb genommen, ohne jegliche Veränderungen.

                      pi@ioBroker-Pi:/opt/iobroker $ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
                      /usr/bin/nodejs
                      v12.22.1
                      /usr/bin/node
                      v12.22.1
                      /usr/bin/npm
                      6.14.12
                      nodejs:
                        Installiert:           12.22.1-1nodesource1
                        Installationskandidat: 12.22.1-1nodesource1
                        Versionstabelle:
                       *** 12.22.1-1nodesource1 500
                              500 https://deb.nodesource.com/node_12.x buster/main armhf Packages
                              100 /var/lib/dpkg/status
                           10.24.0~dfsg-1~deb10u1 500
                              500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
                      
                      
                      1 Reply Last reply Reply Quote 0
                      • Glasfaser
                        Glasfaser last edited by Glasfaser

                        @hoss0305

                        Hast du da was abgeschnitten , die Ausgabe fehlt von deinen vorhandenen Instanzen .

                        pi@ioBroker-Pi:/opt/iobroker $ iobroker list instances
                        
                        H 1 Reply Last reply Reply Quote 0
                        • H
                          Hoss0305 @Glasfaser last edited by

                          @glasfaser sagte in Iobroker startet nicht mehr:

                          iobroker list instances

                          Nö, habe ich nicht. Da steht nur:

                          pi@ioBroker-Pi:/opt/iobroker $ iobroker list instances
                          
                          
                          + instance is alive
                          
                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @Hoss0305 last edited by

                            @hoss0305

                            iobroker status
                            
                            H 1 Reply Last reply Reply Quote 0
                            • H
                              Hoss0305 @Thomas Braun last edited by

                              @thomas-braun sagte in Iobroker startet nicht mehr:

                              iobroker status

                              pi@ioBroker-Pi:/opt/iobroker $ iobroker status
                              iobroker is running on this host.
                              
                              
                              Objects type: file
                              States  type: file
                              
                              Thomas Braun 1 Reply Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @Hoss0305 last edited by

                                @hoss0305

                                iobroker start admin
                                
                                H 1 Reply Last reply Reply Quote 0
                                • H
                                  Hoss0305 @Thomas Braun last edited by

                                  @thomas-braun sagte in Iobroker startet nicht mehr:

                                  iobroker start admin

                                  Nach Eingabe von

                                  iobroker start Admin
                                  

                                  erscheint

                                  pi@ioBroker-Pi:/opt/iobroker $ iobroker start admin
                                  Cannot find any instances of "admin"!
                                  
                                  Thomas Braun 1 Reply Last reply Reply Quote 0
                                  • Thomas Braun
                                    Thomas Braun Most Active @Hoss0305 last edited by

                                    @hoss0305

                                    iobroker list adapters
                                    
                                    H 1 Reply Last reply Reply Quote 0
                                    • H
                                      Hoss0305 @Thomas Braun last edited by

                                      @thomas-braun sagte in Iobroker startet nicht mehr:

                                      iobroker list adapters

                                      pi@ioBroker-Pi:/opt/iobroker $ iobroker list adapters
                                      pi@ioBroker-Pi:/opt/iobroker $
                                      
                                      

                                      Da wird nichts angezeigt!

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

                                        @hoss0305

                                        Installiere es nochmal:

                                        cd /opt/iobroker
                                        sudo -H -u iobroker npm install iobroker.js-controller
                                        
                                        H 1 Reply Last reply Reply Quote 0
                                        • H
                                          Hoss0305 @Thomas Braun last edited by

                                          @thomas-braun sagte in Iobroker startet nicht mehr:

                                          cd /opt/iobroker
                                          sudo -H -u iobroker npm install iobroker.js-controller

                                          pi@ioBroker-Pi:/opt/iobroker $ cd /opt/iobroker
                                          pi@ioBroker-Pi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller
                                          npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
                                          
                                          > iobroker.js-controller@3.2.16 preinstall /opt/iobroker/node_modules/iobroker.js-controller
                                          > node lib/preinstallCheck.js
                                          
                                          NPM version: 6.14.12
                                          
                                          > iobroker.js-controller@3.2.16 install /opt/iobroker/node_modules/iobroker.js-controller
                                          > node iobroker.js setup first
                                          
                                          object system.certificates updated
                                          object _design/system updated
                                          npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (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"})
                                          
                                          + iobroker.js-controller@3.2.16
                                          updated 1 package in 63.863s
                                          
                                          81 packages are looking for funding
                                            run `npm fund` for details
                                          
                                          
                                          
                                             ╭───────────────────────────────────────────────────────────────╮
                                             │                                                               │
                                             │     New major version of npm available! 6.14.12 -> 7.9.0      │
                                             │   Changelog: https://github.com/npm/cli/releases/tag/v7.9.0   │
                                             │               Run npm install -g npm to update!               │
                                             │                                                               │
                                             ╰───────────────────────────────────────────────────────────────╯
                                          

                                          des Weiteren habe ich npm geupdatet

                                          pi@ioBroker-Pi:/opt/iobroker $ sudo npm install -g npm
                                          /usr/bin/npm -> /usr/lib/node_modules/npm/bin/npm-cli.js
                                          /usr/bin/npx -> /usr/lib/node_modules/npm/bin/npx-cli.js
                                          + npm@7.9.0
                                          added 58 packages from 23 contributors, removed 241 packages and updated 194 packages in 29.898s
                                          

                                          aber das ioBroker WebUI startet immer noch nicht

                                          pi@ioBroker-Pi:/opt/iobroker $ iobroker list adapters
                                          pi@ioBroker-Pi:/opt/iobroker $
                                          

                                          Auch hier keine Veränderungen

                                          mikeal created this issue in request/request

                                          open Request’s Past, Present and Future #3142

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

                                            @hoss0305

                                            Nie npm manuell updaten! Insbesondere nicht auf npm@7

                                            H 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

                                            697
                                            Online

                                            31.7k
                                            Users

                                            79.7k
                                            Topics

                                            1.3m
                                            Posts

                                            error iobroker startet nicht status
                                            10
                                            97
                                            9446
                                            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