Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Nach Update js-controller auf 1.4 startet socket io nicht

    NEWS

    • ioBroker goes Matter ... Matter Adapter in Stable

    • 15. 05. Wartungsarbeiten am ioBroker Forum

    • Monatsrückblick - April 2025

    Nach Update js-controller auf 1.4 startet socket io nicht

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

      Hallo habe den Js-controller auf 1.4.0 upgadatet seitdem kommt bei socket i.o 1.8.6 folgende Fehlermeldungen

      host.linaro-alip	2018-04-04 16:05:47.576	info	Restart adapter system.adapter.socketio.0 because enabled
      host.linaro-alip	2018-04-04 16:05:47.576	error	instance system.adapter.socketio.0 terminated with code 0 (OK)
      host.linaro-alip	2018-04-04 16:05:47.576	error	Caught by controller[3]: at process._tickCallback (internal/process/next_tick.js:104:9)
      host.linaro-alip	2018-04-04 16:05:47.576	error	Caught by controller[3]: at _combinedTickCallback (internal/process/next_tick.js:77:11)
      host.linaro-alip	2018-04-04 16:05:47.576	error	Caught by controller[3]: at emitCloseNT (net.js:1574:8)
      host.linaro-alip	2018-04-04 16:05:47.576	error	Caught by controller[3]: at Server.emit (events.js:185:7)
      host.linaro-alip	2018-04-04 16:05:47.576	error	Caught by controller[3]: at emitNone (events.js:86:13)
      host.linaro-alip	2018-04-04 16:05:47.576	error	Caught by controller[3]: at Server.g (events.js:292:16)
      host.linaro-alip	2018-04-04 16:05:47.575	error	Caught by controller[3]: at Server. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:254:25)
      host.linaro-alip	2018-04-04 16:05:47.575	error	Caught by controller[3]: at /opt/iobroker/node_modules/iobroker.socketio/main.js:87:32
      host.linaro-alip	2018-04-04 16:05:47.575	error	Caught by controller[3]: at Object.createServer (/opt/iobroker/node_modules/iobroker.js-controller/lib/letsencrypt.js:58:26)
      host.linaro-alip	2018-04-04 16:05:47.575	error	Caught by controller[3]: at Object.LE.create (/opt/iobroker/node_modules/greenlock/index.js:291:35)
      host.linaro-alip	2018-04-04 16:05:47.575	error	Caught by controller[3]: at Object.module.exports.create (/opt/iobroker/node_modules/greenlock/lib/middleware.js:20:3)
      host.linaro-alip	2018-04-04 16:05:47.575	error	Caught by controller[3]: at leLog (/opt/iobroker/node_modules/iobroker.js-controller/lib/letsencrypt.js:9:9)
      host.linaro-alip	2018-04-04 16:05:47.575	error	Caught by controller[3]: 2018-04-04 16:05:47.525 - socketio.0 ReferenceError: log is not defined
      host.linaro-alip	2018-04-04 16:05:47.575	error	Caught by controller[2]: 2018-04-04 16:05:47.524 - socketio.0 uncaught exception: log is not defined
      host.linaro-alip	2018-04-04 16:05:47.574	error	Caught by controller[1]: at process._tickCallback (internal/process/next_tick.js:104:9)
      host.linaro-alip	2018-04-04 16:05:47.574	error	Caught by controller[1]: at _combinedTickCallback (internal/process/next_tick.js:77:11)
      host.linaro-alip	2018-04-04 16:05:47.574	error	Caught by controller[1]: at emitCloseNT (net.js:1574:8)
      host.linaro-alip	2018-04-04 16:05:47.574	error	Caught by controller[1]: at Server.emit (events.js:185:7)
      host.linaro-alip	2018-04-04 16:05:47.574	error	Caught by controller[1]: at emitNone (events.js:86:13)
      host.linaro-alip	2018-04-04 16:05:47.574	error	Caught by controller[1]: at Server.g (events.js:292:16)
      host.linaro-alip	2018-04-04 16:05:47.574	error	Caught by controller[1]: at Server. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:254:25)
      host.linaro-alip	2018-04-04 16:05:47.574	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.socketio/main.js:87:32
      host.linaro-alip	2018-04-04 16:05:47.573	error	Caught by controller[1]: at Object.createServer (/opt/iobroker/node_modules/iobroker.js-controller/lib/letsencrypt.js:58:26)
      host.linaro-alip	2018-04-04 16:05:47.573	error	Caught by controller[1]: at Object.LE.create (/opt/iobroker/node_modules/greenlock/index.js:291:35)
      host.linaro-alip	2018-04-04 16:05:47.573	error	Caught by controller[1]: at Object.module.exports.create (/opt/iobroker/node_modules/greenlock/lib/middleware.js:20:3)
      host.linaro-alip	2018-04-04 16:05:47.573	error	Caught by controller[1]: at leLog (/opt/iobroker/node_modules/iobroker.js-controller/lib/letsencrypt.js:9:9)
      host.linaro-alip	2018-04-04 16:05:47.573	error	Caught by controller[1]: ReferenceError: log is not defined
      host.linaro-alip	2018-04-04 16:05:47.573	error	Caught by controller[0]: le.challenges[tls-sni-01].loopback should be defined as function (opts, domain, token, cb) { ... } and should prove (by external means) that the ACME server challenge 'tls-sni
      socketio.0	2018-04-04 16:05:47.535	info	terminating https server on port 8084
      socketio.0	2018-04-04 16:05:47.534	error	ReferenceError: log is not defined at leLog (/opt/iobroker/node_modules/iobroker.js-controller/lib/letsencrypt.js:9:9) at Object.module.exports.create (/opt/iobroker/node_modules/greenlock/lib
      socketio.0	2018-04-04 16:05:47.533	error	uncaught exception: log is not defined
      socketio.0	2018-04-04 16:05:45.970	info	starting. Version 1.8.6 in /opt/iobroker/node_modules/iobroker.socketio, node: v6.13.1
      host.linaro-alip	2018-04-04 16:05:44.345	info	instance system.adapter.socketio.0 started with pid 20082
      

      gruß Stephan

      1 Reply Last reply Reply Quote 0
      • Homoran
        Homoran Global Moderator Administrators last edited by

        Hast du einen reboot gemacht?

        mich irritiert die hohe PID von 20082.

        Gruß

        Rainer

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

          Bei mir läuft nach dem Update alles ohne Probleme.

          Mach mal, wie Rainer schon schrieb, einen kompletten Reboot des Hosts.

          Gruß,

          Eric

          Von unterwegs getippert

          1 Reply Last reply Reply Quote 0
          • S
            stephan61 last edited by

            Hallo Habe ein Reboot durchgeführt

            Fehler bleibt gleich

            PID ist jetzt 3588

            wenn ich letsencript abschalte starte der Adapter ohne Fehler

            Gruß Stephan

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

              @stephan61:

              wenn ich letsencript abschalte starte der Adapter ohne Fehler `
              ok, den nutze ich nicht.

              Gruß,

              Eric

              Von unterwegs getippert

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

                Schalte debug level aus. In der nächsten Version von js-controller wird gefixt.

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

                  Halo,

                  Ich hab ein ähnliches Problem nach dem Update auf JS Controller 1.4

                  Bei mir startet die Webserver Instanz, die Letsencrypt nutzt, nicht.

                  Die ohne (HTTP) läuft ohne Probleme.

                  Ich habe die Version 2.1.9 des Web Adapters installiert.

                  Der Log Level für die Webserver instance stand auf "Warn"

                  Hab den Log Level jetzt auf "error" gesetzt, aber der Adapter stürzt immer noch ab.

                  Grüße, FW

                  hier der Log

                  host.wg6-wetter	2018-04-04 18:56:27.841	info	object change system.adapter.web.1
                  host.wg6-wetter	2018-04-04 18:56:22.398	info	Restart adapter system.adapter.web.1 because enabled
                  host.wg6-wetter	2018-04-04 18:56:22.397	error	instance system.adapter.web.1 terminated with code 0 (OK)
                  Caught	2018-04-04 18:56:22.396	error	by controller[1]: at Manager.ondata (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:322:16)
                  Caught	2018-04-04 18:56:22.396	error	by controller[1]: at Decoder.add (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-parser/index.js:246:12)
                  Caught	2018-04-04 18:56:22.396	error	by controller[1]: at Decoder.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-emitter/index.js:134:20)
                  Caught	2018-04-04 18:56:22.396	error	by controller[1]: at Decoder. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-bind/index.js:21:15)
                  Caught	2018-04-04 18:56:22.396	error	by controller[1]: at Manager.ondecoded (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/manager.js:332:8)
                  Caught	2018-04-04 18:56:22.395	error	by controller[1]: at Manager.Emitter.emit (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
                  Caught	2018-04-04 18:56:22.395	error	by controller[1]: at Manager. (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/component-bind/index.js:21:15)
                  Caught	2018-04-04 18:56:22.395	error	by controller[1]: at Socket.onpacket (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:236:12)
                  Caught	2018-04-04 18:56:22.395	error	by controller[1]: at Socket.onack (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/lib/socket.js:312:9)
                  Caught	2018-04-04 18:56:22.395	error	by controller[1]: at Socket. (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:705:21)
                  Caught	2018-04-04 18:56:22.394	error	by controller[1]: at /opt/iobroker/node_modules/iobroker.web/main.js:168:29
                  Caught	2018-04-04 18:56:22.394	error	by controller[1]: at initWebServer (/opt/iobroker/node_modules/iobroker.web/main.js:700:28)
                  Caught	2018-04-04 18:56:22.394	error	by controller[1]: at Object.createServer (/opt/iobroker/node_modules/iobroker.js-controller/lib/letsencrypt.js:58:26)
                  Caught	2018-04-04 18:56:22.394	error	by controller[1]: at Object.LE.create (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/greenlock/index.js:291:35)
                  Caught	2018-04-04 18:56:22.394	error	by controller[1]: at Object.module.exports.create (/opt/iobroker/node_modules/iobroker.js-controller/node_modules/greenlock/lib/middleware.js:20:3)
                  Caught	2018-04-04 18:56:22.393	error	by controller[1]: at leLog (/opt/iobroker/node_modules/iobroker.js-controller/lib/letsencrypt.js:9:9)
                  Caught	2018-04-04 18:56:22.392	error	by controller[1]: ReferenceError: log is not defined
                  Caught	2018-04-04 18:56:22.391	error	by controller[0]: le.challenges[tls-sni-01].loopback should be defined as function (opts, domain, token, cb) { ... } and should prove (by external means) that the ACME server challenge 'tls-sni-01' w
                  web.1	2018-04-04 18:56:22.320	error	uncaught exception: log is not defined
                  

                  geändert: code in code-Tags; Homoran(Mod)

                  1 Reply Last reply Reply Quote 0
                  • S
                    Sinalco last edited by

                    gleiches Problem hab ich auch.

                    Lösung ist ein Downgrade auf Version 1.3:

                    cd /opt/iobroker
                    sudo iobroker stop
                    npm cache clean
                    npm install iobroker.js-controller@1.3.0
                    sudo iobroker start
                    sudo reboot
                    
                    1 Reply Last reply Reply Quote 0
                    • A
                      aftershowman last edited by

                      Danke für die Anleitung.

                      Hat bei mir auch funktioniert.

                      HTTPS Webserver läuft wieder.

                      Grüße, FW

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

                        Mit 1.4.2 sollte es gefixt sein.

                        1 Reply Last reply Reply Quote 0
                        • S
                          Sinalco last edited by

                          Jap mit 1.4.2 geht https wieder grad getestet.

                          Super Arbeit 🙂

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

                          Support us

                          ioBroker
                          Community Adapters
                          Donate

                          475
                          Online

                          31.6k
                          Users

                          79.5k
                          Topics

                          1.3m
                          Posts

                          6
                          11
                          1102
                          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