Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Iobroker Installation hängt bei creating conf/iobroker.json

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    Iobroker Installation hängt bei creating conf/iobroker.json

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

      Die Ausgabe sieht so aus:

      [09:58:55] openhabian@openHABianPi:/opt/iobroker$ sudo rm /opt/iobroker/ -R
[09:59:09] openhabian@openHABianPi:/opt/iobroker$ la -l
total 0
[09:59:12] openhabian@openHABianPi:/opt/iobroker$ ls -l                            total 0
[10:00:21] openhabian@openHABianPi:/opt/iobroker$ sudo npm install iobroker.js-controller@stable --production --save
path.js:1167
          cwd = process.cwd();
                        ^

Error: ENOENT: no such file or directory, uv_cwd
    at Object.resolve (path.js:1167:25)
    at Function.Module._resolveLookupPaths (module.js:424:17)
    at Function.Module._resolveFilename (module.js:541:20)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at /usr/local/lib/node_modules/npm/bin/npm-cli.js:19:21
    at Object. <anonymous>(/usr/local/lib/node_modules/npm/bin/npm-cli.js:92:3)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
[10:01:07] openhabian@openHABianPi:/opt/iobroker$</anonymous>
      1 Reply Last reply Reply Quote 0
      • apollon77
        apollon77 last edited by

        Ist das Verzeichnis echt noch da nach dem Befehl oben ?! hmmm ….

        Auch ls -la mit Total 0" kommt mir komisch vor. Stell mal sicher das /opt/iobroker wirklich noch da ist 🙂

        Ansonsten versuch mal

        sudo npm install iobroker.js-controller --production --save
        1 Reply Last reply Reply Quote 0
        • echoDave
          echoDave last edited by

          jop das dir war weg, ist mir dann auch aufgefallen.

          habe es angelegt und hier die neue Ausgabe:

          [10:13:17] openhabian@openHABianPi:/opt$ sudo mkdir iobroker
[sudo] password for openhabian:
[10:13:28] openhabian@openHABianPi:/opt$ ls
afterfirstboot.lock  iobroker    openHABian-install-successful
FireMotD             openhabian  vc
[10:13:30] openhabian@openHABianPi:/opt$ cd iobroker/
[10:13:35] openhabian@openHABianPi:/opt/iobroker$ sudo npm cache clean -f
npm WARN using --force I sure hope you know what you are doing.
[10:13:51] openhabian@openHABianPi:/opt/iobroker$ sudo npm install iobroker.js-controller@stable --production --save
npm WARN deprecated localhost.daplie.me-certificates@1.3.5: this package has been deprecated

> unix-dgram@0.2.3 install /opt/iobroker/node_modules/unix-dgram
> node-gyp rebuild

gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/8.10.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/node_modules/unix-dgram/.node-gyp"
make: Entering directory '/opt/iobroker/node_modules/unix-dgram/build'
  CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.o
  SOLINK_MODULE(target) Release/obj.target/unix_dgram.node
  COPY Release/unix_dgram.node
make: Leaving directory '/opt/iobroker/node_modules/unix-dgram/build'

> ursa@0.9.4 install /opt/iobroker/node_modules/ursa
> node-gyp rebuild

gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/8.10.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/node_modules/ursa/.node-gyp"
make: Entering directory '/opt/iobroker/node_modules/ursa/build'
  CXX(target) Release/obj.target/ursaNative/src/ursaNative.o
  SOLINK_MODULE(target) Release/obj.target/ursaNative.node
  COPY Release/ursaNative.node
make: Leaving directory '/opt/iobroker/node_modules/ursa/build'

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

Cannot write file. Not critical: Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../../../killall.sh'
creating conf/iobroker.json
fs.js:885
  return binding.mkdir(pathModule._makeLong(path),
                 ^

Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../../../iobroker-data/'
    at Object.fs.mkdirSync (fs.js:885:18)
    at mkpathSync (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup.js:23:24)
    at Setup.setup (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup.js:154:13)
    at /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:630:27
    at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:662:15)
    at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:3105:5)
    at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1:100)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/package.json'
npm WARN iobroker No description
npm WARN iobroker No repository field.
npm WARN iobroker No README data
npm WARN iobroker No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! iobroker.js-controller@1.2.3 install: `node iobroker.js setup first`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the iobroker.js-controller@1.2.3 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2018-03-20T09_16_20_813Z-debug.log
[10:16:21] openhabian@openHABianPi:/opt/iobroker$ ls -l
total 12
drwxr-xr-x 3 root root 12288 Mar 20 10:16 node_modules</anonymous>
          1 Reply Last reply Reply Quote 0
          • apollon77
            apollon77 last edited by

            Hm … permission denied.mach mal ein

            chmod 777 /opt/iobroker

            und vorher wieder leer machen

            dann?

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

              dann hängt er wieder beim creating.

              der opt ordner gehört openhab:openhabian, hängt das vllt damit zusammen?

              [11:05:31] openhabian@openHABianPi:/opt$ sudo rm iobroker/ -dR
[sudo] password for openhabian:
[11:05:54] openhabian@openHABianPi:/opt$ ls
afterfirstboot.lock  FireMotD  openhabian  openHABian-install-successful  vc
[11:05:56] openhabian@openHABianPi:/opt$ sudo mkdir iobroker
[11:06:05] openhabian@openHABianPi:/opt$ sudo chmod 777 /opt/iobroker
[11:06:20] openhabian@openHABianPi:/opt$ ls -l
total 20
-rw-rw-r-- 1 openhab openhabian   91 Dec 20 22:16 afterfirstboot.lock
drwxrwxr-x 5 openhab openhabian 4096 Dec 20 22:10 FireMotD
drwxrwxrwx 2 root    root       4096 Mar 20 11:06 iobroker
drwxrwxr-x 8 openhab openhabian 4096 Feb  7 08:24 openhabian
-rw-rw-r-- 1 openhab openhabian    0 Dec 20 22:16 openHABian-install-successful
drwxrwxr-x 7 openhab openhabian 4096 Apr 10  2017 vc
[11:06:32] openhabian@openHABianPi:/opt$ cd iobroker/
[11:06:40] openhabian@openHABianPi:/opt/iobroker$ sudo npm install iobroker.js-controller --production --save
npm WARN deprecated localhost.daplie.me-certificates@1.3.5: this package has been deprecated
npm WARN lifecycle iobroker.js-controller@1.3.0~preinstall: cannot run in wd %s %s (wd=%s) iobroker.js-controller@1.3.0 node lib/preinstall_check.js /opt/iobroker/node_modules/.staging/iobroker.js-controller-a76002ca

> unix-dgram@0.2.3 install /opt/iobroker/node_modules/unix-dgram
> node-gyp rebuild

gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/8.10.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/node_modules/unix-dgram/.node-gyp"
make: Entering directory '/opt/iobroker/node_modules/unix-dgram/build'
  CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.o
  SOLINK_MODULE(target) Release/obj.target/unix_dgram.node
  COPY Release/unix_dgram.node
make: Leaving directory '/opt/iobroker/node_modules/unix-dgram/build'

> ursa@0.9.4 install /opt/iobroker/node_modules/ursa
> node-gyp rebuild

gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/8.10.0"
gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/node_modules/ursa/.node-gyp"
make: Entering directory '/opt/iobroker/node_modules/ursa/build'
  CXX(target) Release/obj.target/ursaNative/src/ursaNative.o
  SOLINK_MODULE(target) Release/obj.target/ursaNative.node
  COPY Release/ursaNative.node
make: Leaving directory '/opt/iobroker/node_modules/ursa/build'

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

creating conf/iobroker.json
              1 Reply Last reply Reply Quote 0
              • echoDave
                echoDave last edited by

                Ich habe es jetzt unter meinem Ubuntuserver zum laufen gebracht, kommt wohl mit irgendwas auf dem Raspi nicht zurecht.

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

                  Hänge mich hier mal dran, da ich dasselbe Problem habe. Bekomme iobroker partout nicht auf meinem RPi2 (Stretch) installiert.

                  Stretch Image installiert, danach piVCCU, (OH2 war installiert, jedoch wieder gelöscht), FHEM läuft.

                  Habe nodejs in mehreren Versionen installiert, jedes Mal ohne Erfolg 😞

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

                    Es scheint wohl ein Rechtsproblem zu sein.

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

                      Ich habe vorher chmod 777 /opt/iobroker gemacht, von daher sollten die Rechte doch korrekt vergeben worden sein, oder nicht?

                      Ggf. wie kann ich das überprüfen? Bin kein Linuxcrack 😉

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

                        EIne Frage von mir:

                        Wenn das dort "hängt" und Du checks im ioBroker-verzeichnis:

                        • existing das Verzeichnis iobroker-data?

                        • existiert das angegebene File dort?

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

                          Also habe gerade nachgeschaut, das Verzeichnis iobroker-data existiert und darin enthalten ist ein File iobroker.json (3KB)

                          Ich musste den Prozess mit Strg + C abbrechen, weil sich gar nichts mehr tat, auf der Console.

                          ` > pi@raspberrypi:/opt/iobroker $ iobroker start

                          Starting iobroker controller daemon…

                          iobroker controller daemon started. PID: 7870

                          pi@raspberrypi:/opt/iobroker $ iobroker status

                          iobroker is not running `

                          ` > pi@raspberrypi:/opt/iobroker $ sudo chmod 777 /opt/iobroker

                          pi@raspberrypi:/opt/iobroker $ sudo npm install iobroker.js-controller –production --save

                          npm WARN lifecycle iobroker.js-controller@1.4.2~preinstall: cannot run in wd %s %s (wd=%s) iobroker.js-controller@1.4.2 node lib/preinstall_check.js /opt/iobroker/node_modules/.staging/iobroker.js-controller-a76002ca

                          iobroker.js-controller@1.4.2 install /opt/iobroker/node_modules/iobroker.js-controller

                          node iobroker.js setup first

                          Cannot write file. Not critical: Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../../../killall.sh'

                          iobroker.inst@1.1.2 /opt/iobroker

                          └── iobroker.js-controller@1.4.2

                          pi@raspberrypi:/opt/iobroker $ iobroker start

                          Starting iobroker controller daemon...

                          /opt/iobroker/node_modules/daemonize2/lib/daemonize.js:136

                          throw new Error(msg.error);

                          ^

                          Error: Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/iobroker.js-controller/lib/states/../../../../iobroker-data/backup-objects/'

                          at Error (native)

                          at Object.fs.mkdirSync (fs.js:932:18)

                          at new StatesInMemory (/opt/iobroker/node_modules/iobroker.js-controller/lib/states/statesInMemServer.js:109:16)

                          at createStates (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:186:12)

                          at init (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:2543:14)

                          at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.js-controller/controller.js:2624:1)

                          at Module._compile (module.js:577:32)

                          at Object.Module._extensions..js (module.js:586:10)

                          at Module.load (module.js:494:32)

                          at tryModuleLoad (module.js:453:12)

                          at ChildProcess. <anonymous>(/opt/iobroker/node_modules/daemonize2/lib/daemonize.js:136:19)

                          at emitTwo (events.js:106:13)

                          at ChildProcess.emit (events.js:191:7)

                          at process.nextTick (internal/child_process.js:787:12)

                          at _combinedTickCallback (internal/process/next_tick.js:73:7)

                          at process._tickCallback (internal/process/next_tick.js:104:9)

                          pi@raspberrypi:/opt/iobroker $ ls -l

                          total 32

                          drwxr-xr-x 2 root root 4096 Jun 12 21:53 iobroker-data

                          -rw-r--r-- 1 root root 91 Jun 12 21:53 killall.sh

                          drwxr-xr-x 2 root root 4096 Jun 12 21:53 log

                          drwxr-xr-x 334 root root 12288 Jun 13 21:35 node_modules

                          -rw-r--r-- 1 root root 254 Jun 13 21:35 package.json

                          -rw-r--r-- 1 root root 655 Jun 12 21:53 reinstall.sh</anonymous></anonymous> `

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

                            Ok, dann hangeln wir uns weiter durch.

                            Existiert das "logs" Verzeichnis im ioBroker-Verzeichnis?

                            Ansonsten bitte mal prüfen ob auf Port 9000 oder 9001 irgendetwas läuft ohne das iobroker läuft.

                            Auch bitte mal den Inhalt der iobroker-conf file schicken.

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

                              Und wenn bitte:

                              sudo chmod -R 777 /opt/iobroker

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

                                @apollon77

                                Ja, das logs-Verzeichnis existiert ebenfalls. Leider bin ich gerade bei der Arbeit und kann die Sachen nur per Handy probieren.

                                Habe mal mit 'netstart -tnl | grep ":9001"' geschaut, ob etwas auf dem Port läuft, die Ausgabe lautet wie folgt:

                                tcp 0 0 0.0.0.0:9001 0.0.0.0.* LISTEN

                                Allerdings habe ich endlich einen LOG-File und darin folgende Errors:

                                error: Another instance is running or same application uses port!
error: uncaught exception: listen EADDRINUSE 127.0.0.1:9001
error: host.raspberrypi_design/system missing - call node iobroker.js setup
                                1 Reply Last reply Reply Quote 0
                                • apollon77
                                  apollon77 last edited by

                                  Dann ist das dein Problem!! Port 9000 und 9001 werden gebraucht.

                                  Finde raus was genau da läuft und mach es weg 😉

                                  Ich denke es ist etwas anderes, ioBroker connected dahin und hängt dann weil er nicht seine Antwort bekommt oder so.

                                  Und denke das das der Grund ist

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

                                    Habe jetzt mal die Ports auf 9002 und 9003 geändert und iobroker status ergibt iobroker is running.

                                    Soweit so gut, aber ich komme immer noch nicht auf das WebInterface 😞

                                    Dieser Fehler taucht immer noch im Logfile auf:

                                    error: host.raspberrypi_design/system missing - call node iobroker.js setup
                                    1 Reply Last reply Reply Quote 0
                                    • apollon77
                                      apollon77 last edited by

                                      Naja jetzt löscher alles und installiere neu.Der Setup-Prozess ist mittendrin hängen geblieben und du hast abgebrochen. Damit "kaputt".

                                      Mach das was da steht: iobroker setup aufrufen oder löschen und neu

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

                                        Ich habe jetzt herausgefunden, wer den Port 9001 blockiert. Es ist node selbst.

                                        Zumindest zeigt mir netstat -nlp folgendes an:

                                        tcp 0  0.0.0.0:9001 0.0.0.0.* LISTEN 297/Node

                                        Wenn ich jetzt alles neu installiere, müsste doch eigentlich dasselbe Problem wieder auftreten, da Standardmäßig ja Port 9000 und Port 9001 frei sein müssen. Dies habe ich ja gerade in der iobroker.json umgebogen auf 9002 und 9003. Jedoch alles gelöscht, somit auch das umbiegen.

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

                                          Hm dann hättet vllt einspringen gehabt den Server auf Port 9000 zu starten?

                                          Es ist ja ok weil ioBroker die Ports selbst öffnet. Aber er müsste beide machen. Wenn nur 9001 da war dann ist die Frage: warum fehlt 9000?

                                          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

                                          865
                                          Online

                                          31.7k
                                          Users

                                          79.7k
                                          Topics

                                          1.3m
                                          Posts

                                          3
                                          23
                                          2404
                                          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