Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. ioBroker.js-controller 1.5.6

    NEWS

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    ioBroker.js-controller 1.5.6

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

      Zu meinem Erstaunen konnte ich iobroker starten und das UI und auch VIS scheint zu funktionieren.

      1 Reply Last reply Reply Quote 0
      • Bluefox
        Bluefox @Marty56 last edited by

        @Marty56 said in ioBroker.js-controller 1.5.4:

        Hab es mal versucht, sieht nicht so gut aus.

        root@ioBroker-OPi2E:~# iobroker stop
Stopping iobroker controller daemon...
iobroker controller daemon stopped.
Exit code for "killall.sh": 0
root@ioBroker-OPi2E:~# cd ..
root@ioBroker-OPi2E:/# cd opt
root@ioBroker-OPi2E:/opt# cd iobroker
root@ioBroker-OPi2E:/opt/iobroker# npm i iobroker.js-controller@1.5.5
npm WARN lifecycle iobroker.js-controller@1.5.5~preinstall: cannot run in wd %s %s (wd=%s) iobroker.js-controller@1.5.5 node lib/preinstallCheck.js /opt/iobroker/node_modules/.staging/iobroker.js-controller-a76002ca

> authenticate-pam@1.0.2 install /opt/iobroker/node_modules/authenticate-pam
> node-gyp rebuild

make: Entering directory '/opt/iobroker/node_modules/authenticate-pam/build'
  CXX(target) Release/obj.target/authenticate_pam/authenticate_pam.o
../authenticate_pam.cc:30:31: fatal error: security/pam_appl.h: No such file or directory
compilation terminated.
authenticate_pam.target.mk:92: recipe for target 'Release/obj.target/authenticate_pam/authenticate_pam.o' failed
make: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Error 1
make: Leaving directory '/opt/iobroker/node_modules/authenticate-pam/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)
gyp ERR! System Linux 4.14.70-sunxi
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pam
gyp ERR! node -v v6.14.4
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok 

> ursa-optional@0.9.10 install /opt/iobroker/node_modules/ursa-optional
> node rebuild.js


> diskusage@0.2.6 install /opt/iobroker/node_modules/diskusage
> node-gyp rebuild

make: Entering directory '/opt/iobroker/node_modules/diskusage/build'
  CXX(target) Release/obj.target/diskusage/src/main.o
  CXX(target) Release/obj.target/diskusage/src/diskusage_posix.o
  SOLINK_MODULE(target) Release/obj.target/diskusage.node
  COPY Release/diskusage.node
make: Leaving directory '/opt/iobroker/node_modules/diskusage/build'

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


> rsa-compat@1.9.2 postinstall /opt/iobroker/node_modules/acme-v2/node_modules/rsa-compat
> node lib/telemetry.js event:install


> rsa-compat@1.9.2 postinstall /opt/iobroker/node_modules/greenlock/node_modules/rsa-compat
> node lib/telemetry.js event:install

- asn1js@1.2.12 node_modules/asn1js
- buffer-v6-polyfill@1.0.5 node_modules/buffer-v6-polyfill
- node.extend@1.1.6 node_modules/certpem/node_modules/node.extend
cliui@4.1.0 node_modules/iobroker.js-controller/node_modules/cliui -> node_modules/cliui
- node.extend@1.1.6 node_modules/greenlock/node_modules/node.extend
- arraybuffer.slice@0.0.7 node_modules/iobroker.js-controller/node_modules/arraybuffer.slice
- camelcase@4.1.0 node_modules/iobroker.js-controller/node_modules/camelcase
- component-emitter@1.2.1 node_modules/iobroker.js-controller/node_modules/component-emitter
- debug@3.1.0 node_modules/iobroker.js-controller/node_modules/debug
- engine.io-parser@2.1.2 node_modules/iobroker.js-controller/node_modules/engine.io-parser
- isarray@2.0.1 node_modules/iobroker.js-controller/node_modules/isarray
- socket.io-adapter@1.1.1 node_modules/iobroker.js-controller/node_modules/socket.io-adapter
- socket.io-parser@3.2.0 node_modules/iobroker.js-controller/node_modules/socket.io-parser
- ultron@1.1.1 node_modules/iobroker.js-controller/node_modules/ultron
- ws@3.3.3 node_modules/iobroker.js-controller/node_modules/ws
- engine.io@3.2.0 node_modules/iobroker.js-controller/node_modules/engine.io
- xmlhttprequest-ssl@1.5.5 node_modules/iobroker.js-controller/node_modules/xmlhttprequest-ssl
- engine.io-client@3.2.1 node_modules/iobroker.js-controller/node_modules/engine.io-client
- socket.io-client@2.1.1 node_modules/iobroker.js-controller/node_modules/socket.io-client
- socket.io@2.1.1 node_modules/iobroker.js-controller/node_modules/socket.io
- yargs-parser@9.0.2 node_modules/iobroker.js-controller/node_modules/yargs/node_modules/yargs-parser
- pkijs@1.3.33 node_modules/pkijs
- certpem@1.0.1 node_modules/certpem
- glob@7.1.2 node_modules/rimraf/node_modules/glob
- bindings@1.1.1 node_modules/unix-dgram/node_modules/bindings
- yargs-parser@4.2.1 node_modules/iobroker.js-controller/node_modules/yargs-parser
yargs@11.1.0 node_modules/iobroker.js-controller/node_modules/yargs -> node_modules/yargs
iobroker@1.0.0 /opt/iobroker
└─┬ iobroker.js-controller@1.5.5 
  ├─┬ diskusage@0.2.6 
  │ └── nan@2.12.1 
  ├─┬ greenlock@2.6.7 
  │ ├── acme@1.2.0 
  │ ├─┬ acme-v2@1.5.2 
  │ │ └─┬ rsa-compat@1.9.2 
  │ │   └── node-forge@0.7.6 
  │ ├── cert-info@1.5.0 
  │ ├── le-store-certbot@2.2.1 
  │ └─┬ rsa-compat@1.9.2 
  │   ├── node-forge@0.7.6 
  │   └─┬ ursa-optional@0.9.10 
  │     ├─┬ bindings@1.4.0 
  │     │ └── file-uri-to-path@1.0.0 
  │     └── nan@2.12.1 
  ├─┬ jsonwebtoken@8.4.0 
  │ └─┬ jws@3.2.1 
  │   └── jwa@1.2.0 
  ├─┬ jszip@3.1.5
  │ └── pako@1.0.8 
  ├── le-acme-core@2.1.4 
  ├── le-sni-auto@2.1.6 
  ├─┬ loadavg-windows@1.0.2 
  │ └── weak-daemon@1.0.3 
  ├─┬ node-schedule@1.3.1 
  │ └─┬ cron-parser@2.7.3 
  │   └── moment-timezone@0.5.23 
  ├─┬ node.extend@2.0.2 
  │ ├── has@1.0.3 
  │ └── is@3.3.0 
  ├─┬ pidusage@2.0.17 
  │ └── safe-buffer@5.1.2 
  ├─┬ prompt@1.0.0
  │ └─┬ utile@0.3.0
  │   └─┬ rimraf@2.6.3 
  │     └── glob@7.1.3 
  ├── pyconf@1.1.6 
  ├─┬ redis@2.8.0
  │ └── redis-commands@1.4.0 
  ├── safe-replace@1.1.0 
  ├─┬ tar@4.4.8 
  │ ├── chownr@1.1.1 
  │ ├── minipass@2.3.5 
  │ ├── minizlib@1.2.1 
  │ └── yallist@3.0.3 
  └── winston@2.4.4 

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.7: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/iobroker.javascript/node_modules/mymodule/package.json'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 (node_modules/authenticate-pam):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: authenticate-pam@1.0.2 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1

        Es sind nur Warnungen.

        1 Reply Last reply Reply Quote 0
        • Bluefox
          Bluefox @e-i-k-e last edited by

          @e-i-k-e said in ioBroker.js-controller 1.5.4:

          Auf einen ioBroker Slave mit 1.5.5 habe ich den Javascript Adapter nicht auf grün bekommen.
          Nach einem downgrade auf 1.4.2 wurde dieser sofort weider grün.

          Ich brauche logs, so kann ich nicht mal vermuten, was nicht ging

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

            Es scheint alles zu laufen.
            Scheinbar habe ich noch irgendwo einen undefinierten State, der vorher aber nicht bemerkt wurde.
            Jetzt bekomme ich eine minütliche Fehlermeldung

            javascript.0	2019-02-13 07:48:00.596	error	Error in callback: TypeError: Cannot read property 'common' of undefined

            Ich habe schon alle Scripts durchgesucht, ob ich irgendwo einen Minuten Timer habe. Aber ich habe leider nach 30 Minuten Suche nichts gefunden.

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

              Ich konnte es jetzt einkreisen.

              javascript.0	2019-02-13 07:56:00.209	error	Error in callback: TypeError: Cannot read property 'common' of undefined
javascript.0	2019-02-13 07:55:38.422	error	Error in callback: TypeError: Cannot read property 'common' of undefined
javascript.0	2019-02-13 07:55:38.248	error	TypeError: Cannot read property 'common' of undefined
javascript.0	2019-02-13 07:55:38.248	error	^
javascript.0	2019-02-13 07:55:38.247	error	if (!language || !dayOfWeeksFull[language]) language = objects['system.config'].common.language;
javascript.0	2019-02-13 07:55:38.247	error	script.js.common.Tagescharacteristik: /opt/iobroker/node_modules/iobroker.javascript/javascript.js:2712

              Es ist das Kommando formatDate(new Date(), "W hh:mm").

              Liegt nicht an meinen Scripts sondern wohl an der neuen js-controller Version

              Was funktioniert ist: formatDate(new Date(), "hh:mm")
              update:

              • WW, НН(cyrillic) - full week day as text
              • W, Н(cyrillic) - short week day as text

              funktionieren alle nicht mehr

              Bluefox 2 Replies Last reply Reply Quote 1
              • Bluefox
                Bluefox @Marty56 last edited by

                @Marty56 was für JS Version hast du?

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

                  @Bluefox javascript 3.6.4
                  Ich habe alles sonst auf default als repro.
                  Also die Versionen, die unter http://download.iobroker.net/sources-dist.json liegen

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

                    @Marty56 Hier wäre (rechtebedingt) noch ein --unsafe-perm anzuhängen, aber das preinstall script ist bei nem update nicht so nötig, also alles ok ie BF schon gesagt hat

                    1 Reply Last reply Reply Quote 0
                    • Bluefox
                      Bluefox @Marty56 last edited by

                      @Marty56 said in ioBroker.js-controller 1.5.4/1.5.5:

                      formatDate(new Date(), "hh:mm")

                      Ich kann diesen Fehler nicht erklären. Reproduzieren kann ich auch nicht, aber ich habe js-controller@1.5.6 und javascript@3.6.5 gemacht.
                      Kannst du ausprobieren? Erst javascript updaten und dann js-controller.

                      cd /optOderHomeVerzeichnis/iobroker
iobroker stop
npm i iobroker.javascript@3.6.5 --production
npm i iobroker.js-controller@1.5.6 --production
iobroker u javascript
iobroker start
                      M sigi234 2 Replies Last reply Reply Quote 0
                      • simatec
                        simatec Developer Most Active last edited by

                        Bei einer Iobroker Installation mit neuen Installer ist auf die korrekte Rechtevergabe zu achten.
                        Der Befehl

                        npm i iobroker.js-controller@1.5.6

                        kann nicht einfach als anderer User ausgeführt werden, da sonst der User iobroker nicht alle Recht hat.

                        R apollon77 2 Replies Last reply Reply Quote 0
                        • Neuschwansteini
                          Neuschwansteini last edited by Neuschwansteini

                          js-controller 1.5.5 läuft hier einwandfrei.
                          iobroker.admin - aktuell aus git
                          iobroker.web - aktuell aus git
                          iobroker.iot - aktuell aus git
                          iobroker.javascript - aktuell aus git

                          Node 8.15, NPM 6.7, Linux mint 18.3. in ner VM unter proxmox.
                          ( Hauptsystem, 170 Netzwerkdevices und 88 MiHome - es wird genug traffic erzeugt.. ;-))
                          Auf den Raspi's mit gleichen Versionen unter ARM auch keine Probleme.
                          js-controller 1.5.5 wirkt im admin schneller. ( er aktualisiert die Seite sehr schnell )

                          Testsystem frisch aufgesetzt und auf latest gestellt, auch Node 8.15, NPM6.7, Linux Mint 19.1, keine Fehler.
                          ( hier sind nur ein paar Skripts am laufen)

                          Ansonsten klasse, weiter so! Das neue Forum ist auch viel besser.

                          Frage: auf 1.5.6 kann ich nicht updaten, npm findet die Version nicht?
                          npm ERR! notarget No matching version found for iobroker.js-controller@1.5.6
                          npm ERR! notarget In most cases you or one of your dependencies are requesting
                          npm ERR! notarget a package version that doesn't exist.

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

                            @Bluefox sagte in ioBroker.js-controller 1.5.6:

                            npm i iobroker.js-controller@1.5.6 --production

                            Hab's versucht aber

                            npm i iobroker.js-controller@1.5.6 --production
iobroker u javascript
npm ERR! code ETARGET
npm ERR! notarget No matching version found for iobroker.js-controller@1.5.6
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2019-02-13T15_37_04_235Z-debug.log

                            erhalten!
                            p.s.: ich mach solche Sachen unter der neuen iobroker-Installation immer mit vorher:

                            sudo -u iobroker sh
                            1 Reply Last reply Reply Quote 0
                            • M
                              Marty56 @Bluefox last edited by

                              @Bluefox damit geht es wieder.

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

                                Ich habe jetzt 1.5.6 auf npm gepuscht (war noch nicht und ich habe nicht bemerkt)

                                M Neuschwansteini 2 Replies Last reply Reply Quote 1
                                • M
                                  Marty56 @Bluefox last edited by

                                  @Bluefox
                                  mit js-controller 1.5.5 und javscript 3.65 kein Problem

                                  Bluefox 1 Reply Last reply Reply Quote 1
                                  • Bluefox
                                    Bluefox @Marty56 last edited by

                                    @Marty56 Und dein Script zeigt auch Wochentag richtig?

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

                                      @Bluefox
                                      log(formatDate(new Date(), "W hh:mm"));
                                      Mi 17:16

                                      sieht gut aus.

                                      1 Reply Last reply Reply Quote 1
                                      • Neuschwansteini
                                        Neuschwansteini @Bluefox last edited by

                                        @Bluefox Danke, funktioniert !

                                        1 Reply Last reply Reply Quote 1
                                        • Matzebhv
                                          Matzebhv last edited by

                                          Moin,
                                          hier fliegt der iobroker mit der Version alle 30sec. auseinander. Habe die 1.5.5 probiert und auch die 1.5.6.

                                          admin.0	2019-02-13 18:19:16.539	info	terminating http server on port 8081
cloud.0	2019-02-13 18:19:10.594	info	Connection changed: connect
cloud.0	2019-02-13 18:19:10.437	info	Trying to connect as system.user.admin
host.raspberry	2019-02-13 18:19:05.979	info	instance system.adapter.upnp.0 terminated with code 0 (OK)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at Receiver.ontext (/opt/iobroker/node_modules/ws/lib/WebSocket.js:841:10)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at WebSocket.emit (events.js:214:7)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at emitTwo (events.js:126:13)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at WebSocket.onMessage (/opt/iobroker/node_modules/ws/lib/WebSocket.js:442:14)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at WebSocket.ws.onmessage (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:146:10)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at WS.Transport.onData (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:137:8)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at WS.Transport.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:145:8)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at WS.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at WS.<anonymous> (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:268:10)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at Socket.onPacket (/opt/iobroker/node_modules/engine.io-client/lib/socket.js:451:14)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at Socket.Emitter.emit (/opt/iobroker/node_modules/engine.io-client/node_modules/component-emitter/index.js:133:20)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at Manager.ondata (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:322:16)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at Decoder.add (/opt/iobroker/node_modules/socket.io-parser/index.js:237:14)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at decodeString (/opt/iobroker/node_modules/socket.io-parser/index.js:325:9)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: at tryParse (/opt/iobroker/node_modules/socket.io-parser/index.js:336:12)
host.raspberry	2019-02-13 18:19:05.979	error	Caught by controller[0]: RangeError: Maximum call stack size exceeded
host.raspberry	2019-02-13 18:19:05.660	info	iobroker exit 0
host.raspberry	2019-02-13 18:19:05.659	info	iobroker Starting node restart.js
host.raspberry	2019-02-13 18:19:05.539	info	iobroker _restart
host.raspberry	2019-02-13 18:19:05.539	error	RangeError: Maximum call stack size exceeded at Buffer.write (buffer.js:855:34) at fromString (buffer.js:319:20) at Function.Buffer.from (buffer.js:177:12) at new Buffer (buffer.js:158
host.raspberry	2019-02-13 18:19:05.538	error	uncaught exception: Maximum call stack size exceeded
iot.0	2019-02-13 18:19:04.819	info	Connection changed: connect

                                          Matze

                                          Bluefox 1 Reply Last reply Reply Quote 0
                                          • Bluefox
                                            Bluefox @Matzebhv last edited by Bluefox

                                            @Matzebhv Was sagt npm ls socket.io ?

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            482
                                            Online

                                            31.6k
                                            Users

                                            79.4k
                                            Topics

                                            1.3m
                                            Posts

                                            call for action test
                                            31
                                            150
                                            16237
                                            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