Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Einsteigerfragen
    4. Installationsprobleme iobroker

    NEWS

    • Wir empfehlen: Node.js 22.x

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker goes Matter ... Matter Adapter in Stable

    Installationsprobleme iobroker

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

      Hallo,

      ich habe bereits iobroker auf einem Raspi laufen und wollte iob jetzt auf einem neuen Raspi mit Bookworm installieren.

      leider bekomme ich mehrmal immer den gleichen fehler:

      npm ERR! code 6
      npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller
      npm ERR! command failed
      npm ERR! command sh -c node iobroker.js setup first
      npm ERR! Could not determine dns resolution order, fallback to "ipv4first": /opt/iobroker/iobroker-data/iobroker.json: Unexpected end of JSON input
      npm ERR! Could not determine dns resolution order, fallback to "ipv4first": /opt/iobroker/iobroker-data/iobroker.json: Unexpected end of JSON input
      npm ERR! Could not determine dns resolution order, fallback to "ipv4first": /opt/iobroker/iobroker-data/iobroker.json: Unexpected end of JSON input
      npm ERR! Cannot check config file: /opt/iobroker/iobroker-data/iobroker.json: Unexpected end of JSON input
      npm ERR! Uncaught Rejection: SyntaxError: /opt/iobroker/iobroker-data/iobroker.json: Unexpected end of JSON input
      npm ERR!     at JSON.parse (<anonymous>)
      npm ERR!     at Object.readFileSync (/opt/iobroker/node_modules/jsonfile/index.js:52:17)
      npm ERR!     at dbConnect (/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/dbConnection.js:63:39)
      npm ERR!     at /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/dbConnection.js:321:35
      npm ERR!     at new Promise (<anonymous>)
      npm ERR!     at dbConnectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/dbConnection.js:321:12)
      npm ERR!     at Setup.setupObjects (/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/setupSetup.js:271:96)
      npm ERR!     at Setup.setup (/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/setupSetup.js:1035:18)
      npm ERR!     at processCommand (/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup.js:536:19)
      npm ERR!     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      
      npm ERR! A complete log of this run can be found in: /home/ip/.npm/_logs/2023-11-26T19_31_05_578Z-debug-0.log
      
      

      Der Fehlerlog zeigt folgendes:

      0 verbose cli /usr/bin/node /usr/bin/npm
      1 info using npm@9.8.1
      2 info using node@v18.18.2
      3 timing npm:load:whichnode Completed in 8ms
      4 timing config:load:defaults Completed in 14ms
      5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 5ms
      6 timing config:load:builtin Completed in 8ms
      7 warn config production Use `--omit=dev` instead.
      8 timing config:load:cli Completed in 29ms
      9 timing config:load:env Completed in 3ms
      10 timing config:load:file:/opt/iobroker/.npmrc Completed in 11ms
      11 timing config:load:project Completed in 35ms
      12 timing config:load:file:/home/ip/.npmrc Completed in 2ms
      13 timing config:load:user Completed in 3ms
      14 timing config:load:file:/usr/etc/npmrc Completed in 1ms
      15 timing config:load:global Completed in 2ms
      16 timing config:load:setEnvs Completed in 8ms
      17 timing config:load Completed in 109ms
      18 timing npm:load:configload Completed in 110ms
      19 timing config:load:flatten Completed in 22ms
      20 timing npm:load:mkdirpcache Completed in 6ms
      21 timing npm:load:mkdirplogs Completed in 2ms
      22 verbose title npm i
      23 verbose argv "i" "--production" "--loglevel" "error" "--unsafe-perm"
      24 timing npm:load:setTitle Completed in 10ms
      25 timing npm:load:display Completed in 6ms
      26 verbose logfile logs-max:10 dir:/home/ip/.npm/_logs/2023-11-26T19_31_05_578Z-
      27 verbose logfile /home/ip/.npm/_logs/2023-11-26T19_31_05_578Z-debug-0.log
      28 timing npm:load:logFile Completed in 77ms
      29 timing npm:load:timers Completed in 0ms
      30 timing npm:load:configScope Completed in 1ms
      31 timing npm:load Completed in 360ms
      32 timing arborist:ctor Completed in 5ms
      33 timing arborist:ctor Completed in 1ms
      34 silly logfile start cleaning logs, removing 2 files
      35 silly logfile done cleaning log files
      36 timing idealTree:init Completed in 8124ms
      37 timing idealTree:userRequests Completed in 1ms
      38 silly idealTree buildDeps
      39 silly fetch manifest iobroker.js-controller@stable
      40 http fetch GET 200 https://registry.npmjs.org/iobroker.js-controller 1767ms (cache revalidated)
      41 silly fetch manifest iobroker.admin@stable
      42 http fetch GET 200 https://registry.npmjs.org/iobroker.admin 909ms (cache revalidated)
      43 silly fetch manifest iobroker.discovery@stable
      44 http fetch GET 200 https://registry.npmjs.org/iobroker.discovery 880ms (cache revalidated)
      45 silly fetch manifest iobroker.backitup@stable
      46 http fetch GET 200 https://registry.npmjs.org/iobroker.backitup 164ms (cache revalidated)
      47 silly placeDep ROOT iobroker.admin@6.10.1 REPLACE for: iobroker.inst@3.0.0 want: stable
      48 silly placeDep ROOT iobroker.backitup@2.8.7 REPLACE for: iobroker.inst@3.0.0 want: stable
      49 silly placeDep ROOT iobroker.discovery@4.2.0 REPLACE for: iobroker.inst@3.0.0 want: stable
      50 silly placeDep ROOT iobroker.js-controller@5.0.16 REPLACE for: iobroker.inst@3.0.0 want: stable
      51 timing idealTree:#root Completed in 4172ms
      52 silly fetch manifest fsevents@~2.3.2
      53 http fetch GET 200 https://registry.npmjs.org/fsevents 136ms (cache revalidated)
      54 silly placeDep node_modules/chokidar fsevents@2.3.3 OK for: chokidar@3.5.3 want: ~2.3.2
      55 timing idealTree:node_modules/chokidar Completed in 156ms
      56 timing idealTree:node_modules/iobroker.admin Completed in 1ms
      57 timing idealTree:node_modules/iobroker.backitup Completed in 0ms
      58 timing idealTree:node_modules/iobroker.discovery Completed in 0ms
      59 timing idealTree:node_modules/iobroker.js-controller Completed in 1ms
      60 timing idealTree:node_modules/chokidar/node_modules/fsevents Completed in 0ms
      61 timing idealTree:buildDeps Completed in 4341ms
      62 timing idealTree:fixDepFlags Completed in 58ms
      63 timing idealTree Completed in 12588ms
      64 timing reify:loadTrees Completed in 12594ms
      65 timing reify:diffTrees Completed in 51ms
      66 silly reify mark retired [ '/opt/iobroker/node_modules/fsevents' ]
      67 silly reify mark retired [ '/opt/iobroker/node_modules/iobroker.admin' ]
      68 silly reify mark retired [
      68 silly reify   '/opt/iobroker/node_modules/iobroker.js-controller',
      68 silly reify   '/opt/iobroker/node_modules/.bin/iobroker'
      68 silly reify ]
      69 silly reify mark retired [ '/opt/iobroker/node_modules/iobroker.backitup' ]
      70 silly reify mark retired [ '/opt/iobroker/node_modules/iobroker.discovery' ]
      71 silly reify moves {
      71 silly reify   '/opt/iobroker/node_modules/fsevents': '/opt/iobroker/node_modules/.fsevents-yNYMVUiI',
      71 silly reify   '/opt/iobroker/node_modules/iobroker.admin': '/opt/iobroker/node_modules/.iobroker.admin-TtUA2igk',
      71 silly reify   '/opt/iobroker/node_modules/iobroker.js-controller': '/opt/iobroker/node_modules/.iobroker.js-controller-7Q8bmsba',
      71 silly reify   '/opt/iobroker/node_modules/.bin/iobroker': '/opt/iobroker/node_modules/.bin/.iobroker-dBRdrK4k',
      71 silly reify   '/opt/iobroker/node_modules/iobroker.backitup': '/opt/iobroker/node_modules/.iobroker.backitup-ZZHwpo6A',
      71 silly reify   '/opt/iobroker/node_modules/iobroker.discovery': '/opt/iobroker/node_modules/.iobroker.discovery-Domn1CAP'
      71 silly reify }
      72 timing reify:retireShallow Completed in 34ms
      73 timing reify:createSparse Completed in 5ms
      74 timing reify:trashOmits Completed in 8ms
      75 timing reify:loadBundles Completed in 0ms
      76 verbose reify failed optional dependency /opt/iobroker/node_modules/chokidar/node_modules/fsevents
      77 silly reify mark deleted [ '/opt/iobroker/node_modules/chokidar/node_modules/fsevents' ]
      78 timing reifyNode:node_modules/chokidar/node_modules/fsevents Completed in 27ms
      79 timing reifyNode:node_modules/iobroker.js-controller Completed in 1198ms
      80 timing reifyNode:node_modules/iobroker.discovery Completed in 1314ms
      81 timing reifyNode:node_modules/iobroker.backitup Completed in 3852ms
      82 timing reifyNode:node_modules/iobroker.admin Completed in 8553ms
      83 timing reify:unpack Completed in 8558ms
      84 timing reify:unretire Completed in 26ms
      85 timing build:queue Completed in 10ms
      86 info run iobroker.js-controller@5.0.16 preinstall node_modules/iobroker.js-controller node build/lib/preinstallCheck.js
      87 info run iobroker.js-controller@5.0.16 preinstall { code: 0, signal: null }
      88 timing build:run:preinstall:node_modules/iobroker.js-controller Completed in 2949ms
      89 timing build:run:preinstall Completed in 2953ms
      90 timing build:link:node_modules/iobroker.js-controller Completed in 35ms
      91 timing build:link Completed in 36ms
      92 info run iobroker.js-controller@5.0.16 install node_modules/iobroker.js-controller node iobroker.js setup first
      93 info run iobroker.js-controller@5.0.16 install { code: 6, signal: null }
      94 timing reify:rollback:createSparse Completed in 655ms
      95 timing reify:rollback:retireShallow Completed in 5ms
      96 timing command:i Completed in 28976ms
      97 verbose stack Error: command failed
      97 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:53:27)
      97 verbose stack     at ChildProcess.emit (node:events:517:28)
      97 verbose stack     at maybeClose (node:internal/child_process:1098:16)
      97 verbose stack     at ChildProcess._handle.onexit (node:internal/child_process:303:5)
      98 verbose pkgid iobroker.js-controller@5.0.16
      99 verbose cwd /opt/iobroker
      100 verbose Linux 6.1.0-rpi6-rpi-v8
      101 verbose node v18.18.2
      102 verbose npm  v9.8.1
      103 error code 6
      104 error path /opt/iobroker/node_modules/iobroker.js-controller
      105 error command failed
      106 error command sh -c node iobroker.js setup first
      107 error Could not determine dns resolution order, fallback to "ipv4first": /opt/iobroker/iobroker-data/iobroker.json: Unexpected end of JSON input
      107 error Could not determine dns resolution order, fallback to "ipv4first": /opt/iobroker/iobroker-data/iobroker.json: Unexpected end of JSON input
      107 error Could not determine dns resolution order, fallback to "ipv4first": /opt/iobroker/iobroker-data/iobroker.json: Unexpected end of JSON input
      107 error Cannot check config file: /opt/iobroker/iobroker-data/iobroker.json: Unexpected end of JSON input
      107 error Uncaught Rejection: SyntaxError: /opt/iobroker/iobroker-data/iobroker.json: Unexpected end of JSON input
      107 error     at JSON.parse (<anonymous>)
      107 error     at Object.readFileSync (/opt/iobroker/node_modules/jsonfile/index.js:52:17)
      107 error     at dbConnect (/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/dbConnection.js:63:39)
      107 error     at /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/dbConnection.js:321:35
      107 error     at new Promise (<anonymous>)
      107 error     at dbConnectAsync (/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/dbConnection.js:321:12)
      107 error     at Setup.setupObjects (/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/setupSetup.js:271:96)
      107 error     at Setup.setup (/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup/setupSetup.js:1035:18)
      107 error     at processCommand (/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/lib/setup.js:536:19)
      107 error     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      108 verbose exit 6
      109 timing npm Completed in 31091ms
      110 verbose unfinished npm timer reify 1701027067668
      111 verbose unfinished npm timer reify:build 1701027088977
      112 verbose unfinished npm timer build 1701027088982
      113 verbose unfinished npm timer build:deps 1701027088984
      114 verbose unfinished npm timer build:run:install 1701027091986
      115 verbose unfinished npm timer build:run:install:node_modules/iobroker.js-controller 1701027091986
      116 verbose code 6
      117 error A complete log of this run can be found in: /home/ip/.npm/_logs/2023-11-26T19_31_05_578Z-debug-0.log
      
      

      Leider komme ich nicht weiter in der Ursachenfindung für die wiederholten Probleme.

      Andreas

      DJMarc75 crunchip 2 Replies Last reply Reply Quote 0
      • DJMarc75
        DJMarc75 @andi_grafa last edited by

        @andi_grafa sagte in Installationsprobleme iobroker:

        iob jetzt auf einem neuen Raspi mit Bookworm installieren

        und nach welcher Anleitung gemacht ?

        1 Reply Last reply Reply Quote 0
        • A
          andi_grafa last edited by

          @djmarc75 , sorry, das habe ich vergessen

          curl -sLf https://iobroker.net/install.sh | bash -

          Codierknecht 1 Reply Last reply Reply Quote 0
          • Codierknecht
            Codierknecht Developer Most Active @andi_grafa last edited by

            @andi_grafa
            Was hast Du da an OS installiert?

            Hast Du da "von Hand" schon ein Node draufgepackt?

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

              @codierknecht
              Ich habe bookworm neu installiert.
              Node ist nicht installiert, node -v brachte "Befehl nicht gefunden"

              1 Reply Last reply Reply Quote 0
              • crunchip
                crunchip Forum Testing Most Active @andi_grafa last edited by

                @andi_grafa sagte in Installationsprobleme iobroker:

                Could not determine dns resolution order, fallback to "ipv4first":

                liegt da möglicherweise ein Netzwerkproblem vor?

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

                  @crunchip
                  Netzwerproblem in welcher Hinsicht?

                  Das Raspi kann auf das Internet zugreifen, er wird remote bedient und hat somit Zugriff in das WWW.
                  Vielleicht kannst du noch etwas schreiben, wie du es genau meinst!?

                  Falls du die IPV4 Meldung meinst, wie könnte ich es überprüfen? Updates gehen, homematic konnte ich installieren und updaten...ein Zugriff sollte eigentlich möglich sein

                  Danke

                  amg_666 1 Reply Last reply Reply Quote 0
                  • amg_666
                    amg_666 @andi_grafa last edited by

                    @andi_grafa was sagt denn ifconfig ?

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

                      Mir ist leider ein Fehler unterlaufen, ich habe bezüglich npm auf dem falschen Raspi nachgesehen.

                      Auf dem betreffenden iobroker-Raspi ist npm 9.8.1 bereits installiert. ebenso wie node 18.18.2. iobroker ist momentan deinstalliert und alle iob Verzeichnisse wurden gelöscht.

                      @amg_666
                      es existiert wegen homematic bereits eine bridge, diese konfiguration hatte bisher (nur mit wlan) bereits auf dem alten Raspi funktioniert

                      ip@raspi-MUG:~ $ ifconfig
                      br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
                      inet 192.168.178.34 netmask 255.255.255.0 broadcast 192.168.178.255
                      inet6 fe80::ba27:ebff:fefa:f8d prefixlen 64 scopeid 0x20<link>
                      ether b8:27:eb:fa:0f:8d txqueuelen 1000 (Ethernet)
                      RX packets 142731 bytes 8191143 (7.8 MiB)
                      RX errors 0 dropped 0 overruns 0 frame 0
                      TX packets 11736 bytes 2480981 (2.3 MiB)
                      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

                      eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
                      ether b8:27:eb:fa:0f:8d txqueuelen 1000 (Ethernet)
                      RX packets 281382 bytes 18308181 (17.4 MiB)
                      RX errors 0 dropped 1680 overruns 0 frame 0
                      TX packets 112629 bytes 24380603 (23.2 MiB)
                      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

                      lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
                      inet 127.0.0.1 netmask 255.0.0.0
                      inet6 ::1 prefixlen 128 scopeid 0x10<host>
                      loop txqueuelen 1000 (Lokale Schleife)
                      RX packets 38 bytes 3586 (3.5 KiB)
                      RX errors 0 dropped 0 overruns 0 frame 0
                      TX packets 38 bytes 3586 (3.5 KiB)
                      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

                      lxcbr0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
                      inet 10.0.3.1 netmask 255.255.255.0 broadcast 10.0.3.255
                      ether 00:16:3e:00:00:00 txqueuelen 1000 (Ethernet)
                      RX packets 0 bytes 0 (0.0 B)
                      RX errors 0 dropped 0 overruns 0 frame 0
                      TX packets 0 bytes 0 (0.0 B)
                      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

                      vethpivccu: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
                      inet6 fe80::fcc0:6cff:fe51:c5 prefixlen 64 scopeid 0x20<link>
                      ether fe:c0:6c:51:00:c5 txqueuelen 1000 (Ethernet)
                      RX packets 81845 bytes 19689550 (18.7 MiB)
                      RX errors 0 dropped 0 overruns 0 frame 0
                      TX packets 269974 bytes 20867680 (19.9 MiB)
                      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

                      wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
                      ether b8:27:eb:af:5a:d8 txqueuelen 1000 (Ethernet)
                      RX packets 0 bytes 0 (0.0 B)
                      RX errors 0 dropped 0 overruns 0 frame 0
                      TX packets 0 bytes 0 (0.0 B)
                      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

                      wlan1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
                      ether 00:0c:43:00:b5:8d txqueuelen 1000 (Ethernet)
                      RX packets 0 bytes 0 (0.0 B)
                      RX errors 0 dropped 0 overruns 0 frame 0
                      TX packets 0 bytes 0 (0.0 B)
                      TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

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

                        hat niemand eine Idee, über einige Ideen würde ich mich freuen.

                        Andreas

                        crunchip 1 Reply Last reply Reply Quote 0
                        • crunchip
                          crunchip Forum Testing Most Active @andi_grafa last edited by

                          @andi_grafa sagte in Installationsprobleme iobroker:

                          über einige Ideen würde ich mich freuen.

                          @andi_grafa sagte in Installationsprobleme iobroker:

                          Auf dem betreffenden iobroker-Raspi ist npm 9.8.1 bereits installiert. ebenso wie node 18.18.2. iobroker ist momentan deinstalliert und alle iob Verzeichnisse wurden gelöscht.

                          dann setz neu auf, anschließend iobroker installieren.
                          nodejs kommt automatisch mit der iobroker Installation

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

                          Support us

                          ioBroker
                          Community Adapters
                          Donate

                          406
                          Online

                          32.0k
                          Users

                          80.4k
                          Topics

                          1.3m
                          Posts

                          5
                          11
                          620
                          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