Navigation

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

    NEWS

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    js-controller 2 jetzt für alle im Stable

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

      erst bei sudo iobroker start admin

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

        Fehler im Logfile? /opt/iobroker/log/...

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

          also im moment kann er nicht starten da kein js controler da ist

          das log ist seit 40 min nix neues drin hab aber vor 10 min versucht zu starten

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

            @Motsche1 ich lösch mal die log und installiere js neu mom

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

              alsoinstallation geht nur mit

              npm install iobroker.js-controller

              dann hab ich wieder 1.5.14 drauf und iobroker laüft

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

                und dann hab ich im log fplgenden fehler wenn ich starte

                2019-12-27 17:47:54.478  - error: uncaught exception: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/pids.txt'
                2019-12-27 17:47:54.480  - error: Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/pids.txt'
                    at Object.openSync (fs.js:443:3)
                    at Object.writeFileSync (fs.js:1194:35)
                    at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:2024:16)
                    at ontimeout (timers.js:436:11)
                    at tryOnTimeout (timers.js:300:5)
                    at listOnTimeout (timers.js:263:5)
                    at Timer.processTimers (timers.js:223:10)
                
                apollon77 1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 @Motsche1 last edited by

                  @Motsche1 Installation Fixer ... siehe FAQ!

                  Ansonsten mach mal

                  npm install iobroker.js-controller@2.1.1

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

                    hab ich beides schon durch --- selbes ergebnis

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

                      @Motsche1 Immer dieser Fehler mit dem "Flatten"?

                      Ruf mal nach install der 2.1.1 bitte manuell "iobroker setup first" auf.

                      Und immer noch: Was steht im ioBroker Logfile?

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

                        @apollon77 said in js-controller 2 jetzt für alle im Stable:

                        iobroker setup first

                        Iobroker setup first

                        internal/modules/cjs/loader.js:638
                            throw err;
                            ^
                        
                        Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
                            at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
                            at Function.Module._load (internal/modules/cjs/loader.js:562:25)
                            at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)
                            at startup (internal/bootstrap/node.js:283:19)
                            at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)
                        

                        und log file hatte ich schon gepostet aber gern nochmal

                        2019-12-27 17:55:09.310  - error: uncaught exception: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/pids.txt'
                        2019-12-27 17:55:09.314  - error: Error: EACCES: permission denied, open '/opt/iobroker/node_modules/iobroker.js-controller/pids.txt'
                            at Object.openSync (fs.js:443:3)
                            at Object.writeFileSync (fs.js:1194:35)
                            at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:2024:16)
                            at ontimeout (timers.js:436:11)
                            at tryOnTimeout (timers.js:300:5)
                            at listOnTimeout (timers.js:263:5)
                            at Timer.processTimers (timers.js:223:10)
                        2019-12-27 17:55:09.318  - info: iobroker _restart
                        2019-12-27 17:55:09.745  - info: iobroker Starting node restart.js
                        2019-12-27 17:55:09.768  - info: iobroker exit 0
                        2019-12-27 17:55:09.809  - info: admin.0 starting. Version 3.6.12 in /opt/iobroker/node_modules/iobroker.admin, node: v10.18.0
                        2019-12-27 17:55:09.870  - info: admin.0 requesting all states
                        2019-12-27 17:55:09.870  - info: admin.0 requesting all objects
                        2019-12-27 17:55:11.485  - info: admin.0 received all objects
                        2019-12-27 17:55:11.501  - warn: admin.0 No repository source configured
                        2019-12-27 17:55:11.524  - info: admin.0 http server listening on port 8081
                        2019-12-27 17:55:11.524  - info: admin.0 Use link "http://localhost:8081" to configure.
                        2019-12-27 17:55:19.324  - info: host.rockpro64 force terminating
                        2019-12-27 17:55:19.324  - info: Adapter admin still running
                        2019-12-27 17:55:20.218  - info: host.rockpro64 instance system.adapter.sonoff.0 started with pid 26841
                        2019-12-27 17:55:20.399  - info: admin.0 terminating http server on port 8081
                        2019-12-27 17:55:21.905  - info: admin.0 terminating http server on port 8081
                        
                        1 Reply Last reply Reply Quote 0
                        • apollon77
                          apollon77 last edited by

                          Und jetzt bitte mal log von dem Install direkt per npm mit der 2.1.1

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

                            also 2.1.1 install und dann noch mal in die log schauen

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

                              iobroker log nix drin also neuer eintrag

                              in der npm log steht

                              0 info it worked if it ends with ok
                              1 verbose cli [ '/usr/bin/node',
                              1 verbose cli   '/usr/bin/npm',
                              1 verbose cli   'install',
                              1 verbose cli   'iobroker.js-controller@2.1.1' ]
                              2 info using npm@6.13.4
                              3 info using node@v10.18.0
                              4 verbose npm-session 64667189d8460ead
                              5 silly install loadCurrentTree
                              6 silly install readLocalPackageData
                              7 http fetch GET 304 https://registry.npmjs.org/iobroker.js-controller 325ms (from cache)
                              8 silly pacote version manifest for iobroker.js-controller@2.1.1 fetched in 347ms
                              9 timing stage:loadCurrentTree Completed in 11475ms
                              10 silly install loadIdealTree
                              11 silly install cloneCurrentTreeToIdealTree
                              12 timing stage:loadIdealTree:cloneCurrentTree Completed in 136ms
                              13 silly install loadShrinkwrap
                              14 timing stage:loadIdealTree:loadShrinkwrap Completed in 2548ms
                              15 silly install loadAllDepsIntoIdealTree
                              16 silly resolveWithNewModule iobroker.js-controller@2.1.1 checking installable status
                              17 http fetch GET 304 https://registry.npmjs.org/decache 124ms (from cache)
                              18 silly pacote range manifest for decache@^4.5.1 fetched in 129ms
                              19 silly resolveWithNewModule decache@4.5.1 checking installable status
                              20 http fetch GET 304 https://registry.npmjs.org/semver 145ms (from cache)
                              21 silly pacote range manifest for semver@^6.3.0 fetched in 152ms
                              22 silly resolveWithNewModule semver@6.3.0 checking installable status
                              23 http fetch GET 304 https://registry.npmjs.org/respjs 288ms (from cache)
                              24 http fetch GET 304 https://registry.npmjs.org/readline-sync 294ms (from cache)
                              25 silly pacote range manifest for respjs@^4.2.0 fetched in 300ms
                              26 silly resolveWithNewModule respjs@4.2.0 checking installable status
                              27 silly pacote range manifest for readline-sync@^1.4.10 fetched in 308ms
                              28 silly resolveWithNewModule readline-sync@1.4.10 checking installable status
                              29 http fetch GET 304 https://registry.npmjs.org/mime 319ms (from cache)
                              30 http fetch GET 304 https://registry.npmjs.org/node-forge 322ms (from cache)
                              31 http fetch GET 304 https://registry.npmjs.org/chokidar 345ms (from cache)
                              32 silly pacote range manifest for mime@^2.4.4 fetched in 347ms
                              33 silly resolveWithNewModule mime@2.4.4 checking installable status
                              34 silly pacote range manifest for node-forge@^0.9.1 fetched in 351ms
                              35 silly resolveWithNewModule node-forge@0.9.1 checking installable status
                              36 http fetch GET 304 https://registry.npmjs.org/event-stream 363ms (from cache)
                              37 silly pacote range manifest for chokidar@^3.3.0 fetched in 373ms
                              38 silly resolveWithNewModule chokidar@3.3.1 checking installable status
                              39 http fetch GET 304 https://registry.npmjs.org/ioredis 372ms (from cache)
                              40 http fetch GET 304 https://registry.npmjs.org/iobroker.objects-redis 386ms (from cache)
                              41 http fetch GET 304 https://registry.npmjs.org/socket.io-client 223ms (from cache)
                              42 http fetch GET 304 https://registry.npmjs.org/socket.io 264ms (from cache)
                              43 silly pacote range manifest for event-stream@^4.0.1 fetched in 417ms
                              44 silly resolveWithNewModule event-stream@4.0.1 checking installable status
                              45 silly pacote range manifest for ioredis@^4.14.1 fetched in 427ms
                              46 silly resolveWithNewModule ioredis@4.14.1 checking installable status
                              47 silly pacote range manifest for iobroker.objects-redis@^1.2.8 fetched in 444ms
                              48 silly resolveWithNewModule iobroker.objects-redis@1.2.13 checking installable status
                              49 silly pacote version manifest for socket.io-client@2.3.0 fetched in 280ms
                              50 silly resolveWithNewModule socket.io-client@2.3.0 checking installable status
                              51 silly pacote version manifest for socket.io@2.3.0 fetched in 322ms
                              52 silly resolveWithNewModule socket.io@2.3.0 checking installable status
                              53 http fetch GET 304 https://registry.npmjs.org/winston 217ms (from cache)
                              54 http fetch GET 304 https://registry.npmjs.org/tar 229ms (from cache)
                              
                              M 1 Reply Last reply Reply Quote 0
                              • M
                                Motsche1 @Motsche1 last edited by

                                @Motsche1

                                5377 warn enoent ENOENT: no such file or directory, open '/home/pi/package.json'
                                5378 verbose enoent This is related to npm not being able to find a file.
                                5379 warn pi No description
                                5380 warn pi No repository field.
                                5381 warn pi No README data
                                5382 warn pi No license field.
                                5383 warn optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
                                5384 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                                5385 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS:    darwin
                                5385 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch:  any
                                5385 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS:   linux
                                5385 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: arm64
                                5386 verbose stack Error: iobroker.js-controller@2.1.1 install: `node iobroker.js setup first`
                                5386 verbose stack Exit status 25
                                5386 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
                                5386 verbose stack     at EventEmitter.emit (events.js:198:13)
                                5386 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
                                5386 verbose stack     at ChildProcess.emit (events.js:198:13)
                                5386 verbose stack     at maybeClose (internal/child_process.js:982:16)
                                5386 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
                                5387 verbose pkgid iobroker.js-controller@2.1.1
                                5388 verbose cwd /home/pi
                                5389 verbose Linux 4.4.192-rockchip64
                                5390 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "iobroker.js-controller@2.1.1"
                                5391 verbose node v10.18.0
                                5392 verbose npm  v6.13.4
                                5393 error code ELIFECYCLE
                                5394 error errno 25
                                5395 error iobroker.js-controller@2.1.1 install: `node iobroker.js setup first`
                                5395 error Exit status 25
                                5396 error Failed at the iobroker.js-controller@2.1.1 install script.
                                5396 error This is probably not a problem with npm. There is likely additional logging output above.
                                5397 verbose exit [ 25, true ]
                                
                                apollon77 1 Reply Last reply Reply Quote 0
                                • apollon77
                                  apollon77 @Motsche1 last edited by

                                  @Motsche1 sagte in js-controller 2 jetzt für alle im Stable:

                                  5377 warn enoent ENOENT: no such file or directory, open '/home/pi/package.json'

                                  startest du das npm install im richtigen verzeichnis? Muss /opt/iobroker sein! Nicht /home/pi

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

                                    @apollon77 said in js-controller 2 jetzt für alle im Stable:

                                    /opt/iobroker

                                    ja schon

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

                                      @Motsche1 Das log oben sagt aber was anderes

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

                                        ja sorry hab es eben falsch gemacht

                                        jetzt steht bei istall folgendes

                                        > node iobroker.js setup first
                                        
                                        Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../_service_iobroker.bat'
                                        Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../iobroker.bat'
                                        Cannot delete file. Not critical: Error: EACCES: permission denied, unlink '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../iob.bat'
                                        fs.js:114
                                            throw err;
                                            ^
                                        
                                        Error: EACCES: permission denied, mkdir '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/../../tmp'
                                            at Object.mkdirSync (fs.js:757:3)
                                            at Setup.setup (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup/setupSetup.js:688:58)
                                            at processCommand (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:235:23)
                                            at Object.module.exports.execute (/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js:2408:5)
                                            at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js:1:24)
                                            at Module._compile (internal/modules/cjs/loader.js:778:30)
                                            at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
                                            at Module.load (internal/modules/cjs/loader.js:653:32)
                                            at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
                                            at Function.Module._load (internal/modules/cjs/loader.js:585:3)
                                        npm WARN babel-eslint@5.0.4 requires a peer of eslint@<2.3.0 but none is installed. You must install peer dependencies yourself.
                                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
                                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.4 (node_modules/osx-temperature-sensor):
                                        npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm64"})
                                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-bluetooth@1.2.6 (node_modules/node-bluetooth):
                                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: node-bluetooth@1.2.6 install: `node-gyp configure build`
                                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.2 (node_modules/unix-dgram):
                                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.2 install: `node-gyp rebuild`
                                        npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
                                        
                                        npm ERR! code ELIFECYCLE
                                        npm ERR! errno 1
                                        npm ERR! iobroker.js-controller@2.1.1 install: `node iobroker.js setup first`
                                        npm ERR! Exit status 1
                                        npm ERR!
                                        npm ERR! Failed at the iobroker.js-controller@2.1.1 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/2019-12-27T17_32_40_659Z-debug.log
                                        
                                        1 Reply Last reply Reply Quote 0
                                        • apollon77
                                          apollon77 last edited by

                                          Installation Fixer laufen gelassen wie oben schon gefragt? Permission Errors sind blöd

                                          1 Reply Last reply Reply Quote 0
                                          • C
                                            CruziX last edited by CruziX

                                            Hallo zusammen.
                                            Ich versuche es einfach mal hier.

                                            Bin nun auf ein besseres System umgestiegen.
                                            Nun funktionieren meine selektoren aber leider nicht mehr.
                                            Habe die meisten Ids über ein Skript im Verzeichnis alias angelegt und das ging auch beim vorherigen System.

                                            z.B. habe ich
                                            var selectorBattery = $('[id=alias* Licht *An]');

                                            selectorBattery.each(function(id, i)

                                            {

                                            if(getObject(id).common.role =='switch')

                                            log(id);

                                            });

                                            im Log wird aber nichts ausgegeben.

                                            Wenn ich nun die Bedingung rausnehme und nur noch $('[id=alias*]') als selektor nehme bekomme ich genau 2 state ausgegeben. Obwohl ich deutlich mehr habe.

                                            Weiß jemand woran das liegt?
                                            Neugestartet habe ich schon.

                                            80270084_2651084784961421_6533504873445457920_n.jpg

                                            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

                                            892
                                            Online

                                            31.6k
                                            Users

                                            79.6k
                                            Topics

                                            1.3m
                                            Posts

                                            js-controller js-controller 2
                                            74
                                            556
                                            133326
                                            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