Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Windows Dienst lässt sich nicht mehr starten

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

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

    • ioBroker goes Matter ... Matter Adapter in Stable

    Windows Dienst lässt sich nicht mehr starten

    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      aleks-83 @aleks-83 last edited by aleks-83

      Was mir gerade noch aufgefallen ist bei der Neueinrichtung:

      Als er alle Adapter aus der Migration installiert hatte, habe ich per admin Adapter gesagt er soll alle Adapter updaten.
      Dann hat er versucht NPM upzugraden.
      Das ging schief.

      ... Hier wurden Adapter geupdatet ...
      Adapter "xs1" is not installed.
      Adapter "yahka" is not installed.
      Adapter "yamaha" is not installed.
      Adapter "yeelight-2" is not installed.
      Adapter "yr" is not installed.
      Adapter "zigbee" is not installed.
      Adapter "zont" is not installed.
      Adapter "zwave" is not installed.
      Adapter "zwave2" is not installed.
      Update js-controller from @1.5.14 to @2.0.29
      2019-10-14 20:36:35.125 - warn: host.NUC(NUCmaster) instance system.adapter.web.0 terminated due to SIGTERM
      2019-10-14 20:36:35.125 - info: host.NUC(NUCmaster) instance system.adapter.web.0 terminated with code null ()
      2019-10-14 20:36:37.511 - info: host.NUC(NUCmaster) instance system.adapter.web.0 started with pid 6360
      2019-10-14 20:36:38.566 - info: iobroker NPM version: 6.9.0
      2019-10-14 20:36:38.566 - info: iobroker npm install iobroker.js-controller@2.0.29 --unsafe-perm --production --save --prefix "D:/ioBroker/NUCmaster" (System call)
      2019-10-14 20:36:39.571 - info: web.0 starting. Version 2.4.5 in D:/ioBroker/NUCmaster/node_modules/iobroker.web, node: v10.16.3
      2019-10-14 20:36:41.833 - info: web.0 socket.io server listening on port 8083
      2019-10-14 20:36:41.838 - info: web.0 http server listening on port 8083
      2019-10-14 20:37:33.190 - info: iobroker gyp
      2019-10-14 20:37:33.191 - info: iobroker ERR!
      2019-10-14 20:37:33.193 - info: iobroker
      2019-10-14 20:37:33.199 - info: iobroker build error
      2019-10-14 20:37:33.200 - info: iobroker
      2019-10-14 20:37:33.229 - info: iobroker gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1gyp ERR! stack at ChildProcess.onExit (D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
      gyp ERR! stack at ChildProcess.emit (events.js:198:13)
      gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
      gyp ERR! System Windows_NT 10.0.18362
      2019-10-14 20:37:33.235 - info: iobroker gyp ERR! command "D:\\ioBroker\\NUCmaster\\nodejs\\node.exe" "D:\\ioBroker\\NUCmaster\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"gyp
      2019-10-14 20:37:33.237 - info: iobroker ERR!
      2019-10-14 20:37:33.241 - info: iobroker cwd D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller\node_modules\unix-dgramgyp ERR!
      2019-10-14 20:37:33.242 - info: iobroker node -v v10.16.3gyp ERR! node-gyp -v v3.8.0
      gyp ERR! not ok
      2019-10-14 20:38:12.125 - info: iobroker npm
      2019-10-14 20:38:12.126 - info: iobroker
      2019-10-14 20:38:12.130 - info: iobroker WARN
      2019-10-14 20:38:12.133 - info: iobroker
      2019-10-14 20:38:12.140 - info: iobroker optional
      2019-10-14 20:38:12.144 - info: iobroker SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.1 (node_modules\iobroker.js-controller\node_modules\fsevents):
      2019-10-14 20:38:12.165 - info: iobroker npm
      2019-10-14 20:38:12.176 - info: iobroker
      2019-10-14 20:38:12.180 - info: iobroker WARN
      2019-10-14 20:38:12.181 - info: iobroker
      2019-10-14 20:38:12.182 - info: iobroker notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
      2019-10-14 20:38:12.183 - info: iobroker npm
      2019-10-14 20:38:12.187 - info: iobroker WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.2 (node_modules\iobroker.js-controller\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
      2019-10-14 20:38:12.256 - info: iobroker Host "NUC(NUCmaster)" (win32) updated
      2019-10-14 20:38:12.256 - info: iobroker Starting node restart.js
      2019-10-14 20:38:12.343 - info: iobroker exit 0
      2019-10-14 20:39:43.348 - info: host.NUC(NUCmaster) Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
      

      Kann es sein dass er das beim letzten Update auch versucht hat, und mir die Zeile mit dem mkdir zerschossen hat?

      Ich habe den NUC jetzt aber schon neu gestartet.
      Der Dienst startet noch ganz normal.

      Dann werde ich den button "Alle Adapter updaten" erst mal meiden.

      EDIT:
      Der Admin zeigt mir aber an ich hätte die 2.0.29
      6eecac3a-5558-4fc6-9bab-6690b58f759f-image.png

      Stabilostick A 2 Replies Last reply Reply Quote 0
      • Stabilostick
        Stabilostick @aleks-83 last edited by Stabilostick

        @aleks-83 sagte in Windows Dienst lässt sich nicht mehr starten:

        Dann hat er versucht NPM upzugraden.
        Das ging schief.

        Nein, hat er nicht.

        Du hast den neuesten js-controller installiert aus Latest. Dabei ist der Buildvorgang für die optionale Komponente "unix-dgram", die sowieso nur auf Linux funktioniert, fehlgeschlagen. "fsevents" braucht es nur auf Apple-Rechnern. Also alles kein Problem und kein Grund zur Sorge:

        2019-10-14 20:38:12.182 - info: iobroker notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

        2019-10-14 20:38:12.187 - info: iobroker WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.2 (node_modules\iobroker.js-controller\node_modules\unix-dgram)

        2019-10-14 20:38:12.343 - info: iobroker exit 0

        Das ist das Wichtige am Ende. 0 = alles Ok.

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

          @sigi234

          Ich fürchte, da bin ich raus. Firebase, iogo und Meross kenne ich nicht. Gehört das wirklich zum Thema "Windows Dienst lässt sich nicht starten", das hier besprochen wird?

          sigi234 1 Reply Last reply Reply Quote 0
          • sigi234
            sigi234 Forum Testing Most Active @Stabilostick last edited by

            @Stabilostick sagte in Windows Dienst lässt sich nicht mehr starten:

            @sigi234

            Ich fürchte, da bin ich raus. Firebase, iogo und Meross kenne ich nicht. Gehört das wirklich zum Thema "Windows Dienst lässt sich nicht starten", das hier besprochen wird?

            Erledigt.

            1 Reply Last reply Reply Quote 0
            • A
              aleks-83 @Stabilostick last edited by

              @Stabilostick
              Sorry, ich meinte nicht NPM updaten sondern den JS Controller.

              Im Ankündigungsthread stand ja dass man Systeme die per Windows Installer erstellt wurden, nicht per npm updaten soll, deshalb hatte ich Sorge dass da was ungewollt gestartet ist. Gerade auch weil ich gestern erst alles neu aufgesetzt habe (mit Migration).

              Also kann ich davon ausgehen dass der JS 2.0.29 bei mir jetzt läuft?
              Oder wirds nur falsch angezeigt? Also dass noch der 1.5.14 installiert ist?

              1 Reply Last reply Reply Quote 0
              • A
                aleks-83 last edited by aleks-83

                Komplettausfall #2

                Jetzt hat der Dienst des ioBroker plötzlich nach der Deinstallation des "mobile" Adapters gestoppt, und lässt sich nicht mehr starten.

                iobroker log während des Absturzes:

                2019-10-16 07:45:06.764  - info: host.NUC(NUCmaster) iobroker del mobile.0
                2019-10-16 07:45:08.910  - info: host.NUC(NUCmaster) iobroker Delete adapter "mobile.0"
                2019-10-16 07:45:08.941  - info: host.NUC(NUCmaster) iobroker host.NUC(NUCmaster) Counted 1 instances of mobile.0
                2019-10-16 07:45:11.870  - info: host.NUC(NUCmaster) iobroker host.NUC(NUCmaster) Deleting 1 object(s).
                2019-10-16 07:45:11.894  - info: host.NUC(NUCmaster) object deleted system.adapter.mobile.0
                2019-10-16 07:45:11.896  - info: lovelace.0 (9380) object system.adapter.mobile.0 deleted
                2019-10-16 07:45:12.921  - info: host.NUC(NUCmaster) iobroker exit 0
                2019-10-16 07:45:27.747  - info: host.NUC(NUCmaster) iobroker del mobile
                2019-10-16 07:45:29.418  - info: host.NUC(NUCmaster) iobroker Delete adapter "mobile"
                2019-10-16 07:45:29.474  - info: host.NUC(NUCmaster) iobroker host.NUC(NUCmaster) Counted 1 adapter for mobile
                2019-10-16 07:45:29.554  - info: host.NUC(NUCmaster) iobroker host.NUC(NUCmaster) Counted 1 states of system.adapter.mobile
                2019-10-16 07:45:29.871  - info: lovelace.0 (9380) object mobile deleted
                2019-10-16 07:45:29.883  - info: lovelace.0 (9380) object mobile.admin deleted
                2019-10-16 07:45:29.895  - info: lovelace.0 (9380) object system.adapter.mobile.upload deleted
                2019-10-16 07:45:29.904  - info: lovelace.0 (9380) object system.adapter.mobile deleted
                2019-10-16 07:45:29.886  - info: host.NUC(NUCmaster) iobroker host.NUC(NUCmaster) Deleting 2 object(s).
                2019-10-16 07:45:29.909  - info: host.NUC(NUCmaster) iobroker npm uninstall iobroker.mobile --silent --save --prefix "D:/ioBroker/NUCmaster" (System call)
                2019-10-16 07:45:30.860  - error: host.NUC(NUCmaster) Cannot write files: D:\ioBroker\NUCmaster\iobroker-data\files\mobile\_data.json: ENOENT: no such file or directory, open 'D:\ioBroker\NUCmaster\iobroker-data\files\mobile\_data.json'
                2019-10-16 07:45:30.861  - error: host.NUC(NUCmaster) Cannot write files: D:\ioBroker\NUCmaster\iobroker-data\files\mobile.admin\_data.json: ENOENT: no such file or directory, open 'D:\ioBroker\NUCmaster\iobroker-data\files\mobile.admin\_data.json'
                2019-10-16 07:45:53.665  - info: geofency.0 (11084) adapter geofency received webhook from device Steffi with values: name: KiGa, entry: 0
                2019-10-16 07:47:04.872  - error: host.NUC(NUCmaster) Objects 127.0.0.1:59186 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                2019-10-16 07:47:04.874  - error: host.NUC(NUCmaster) States 127.0.0.1:59187 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                2019-10-16 07:47:05.682  - error: host.NUC(NUCmaster) Objects 127.0.0.1:59191 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                2019-10-16 07:47:05.850  - error: host.NUC(NUCmaster) States 127.0.0.1:59192 (Init=false) Redis error:Error: Invalid Chunk: parse failed
                2019-10-16 07:47:08.643  - info: host.NUC(NUCmaster) iobroker events.js:174
                     throw e
                2019-10-16 07:47:08.644  - info: host.NUC(NUCmaster) iobroker r; // Unhandled 'error' event
                     ^
                
                Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
                   at Server.setupListenHandle [as _listen2] (net.js:1279:14)
                   at listenInCluster (net.js:1327:12)
                   at doListen (net.js:1460:7)
                   at process._tickCallback (internal/process/next_tick.js:63:19)
                Emitted 'error' event at:
                   at emitErrorNT (net.js:1306:8)
                   at process._tickCallback (internal/process/next_tick.js:63:19)
                
                2019-10-16 07:48:28.872  - error: host.NUC(NUCmaster) uncaught exception: ENOENT: no such file or directory, open 'D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller\lib/../io-package.json'
                2019-10-16 07:48:28.907  - info: ping.0 (11592) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:28.930  - info: geofency.0 (11084) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:28.926  - info: backitup.0 (8420) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:28.935  - info: enigma2.0 (6524) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:28.945  - info: javascript.0 (8992) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:29.007  - info: enigma2.1 (2716) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:29.019  - info: email.0 (9008) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:29.016  - info: text2command.0 (5956) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:29.023  - info: telegram.0 (5972) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:29.025  - info: iot.0 (8428) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:29.020  - info: pushover.0 (8276) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:29.028  - info: lovelace.0 (9380) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:29.042  - info: hue-extended.0 (8700) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:29.046  - info: web.0 (10252) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:29.100  - info: sonos.0 (8728) Got terminate signal TERMINATE_YOURSELF
                2019-10-16 07:48:28.874  - error: host.NUC(NUCmaster) Error: ENOENT: no such file or directory, open 'D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller\lib/../io-package.json'
                   at Object.openSync (fs.js:443:3)
                   at Object.readFileSync (fs.js:343:35)
                   at Object.getInstalledInfo (D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller\lib\tools.js:533:37)
                   at objects.getObjectView (D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller\main.js:1763:42)
                   at Immediate.callback.function.setImmediate (D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller\lib\objects\objectsInMemFileDB.js:1813:62)
                   at runCallback (timers.js:705:18)
                   at tryOnImmediate (timers.js:676:5)
                   at processImmediate (timers.js:658:5)
                2019-10-16 07:48:28.876  - info: host.NUC(NUCmaster) stopInstance system.adapter.admin.0
                2019-10-16 07:48:28.876  - info: host.NUC(NUCmaster) stopInstance system.adapter.discovery.0
                2019-10-16 07:48:28.876  - info: host.NUC(NUCmaster) stopInstance system.adapter.history.0
                2019-10-16 07:48:28.876  - info: host.NUC(NUCmaster) stopInstance system.adapter.tr-064.0
                2019-10-16 07:48:28.877  - info: host.NUC(NUCmaster) stopInstance system.adapter.vis.0
                2019-10-16 07:48:28.877  - info: host.NUC(NUCmaster) stopInstance system.adapter.ping.0
                2019-10-16 07:48:28.877  - info: host.NUC(NUCmaster) stopInstance system.adapter.ical.0
                2019-10-16 07:48:28.877  - info: host.NUC(NUCmaster) stopInstance canceled schedule system.adapter.ical.0
                2019-10-16 07:48:28.877  - info: host.NUC(NUCmaster) stopInstance system.adapter.ical.1
                2019-10-16 07:48:28.878  - info: host.NUC(NUCmaster) stopInstance canceled schedule system.adapter.ical.1
                2019-10-16 07:48:28.878  - info: host.NUC(NUCmaster) stopInstance system.adapter.hue.0
                2019-10-16 07:48:28.878  - info: host.NUC(NUCmaster) stopInstance system.adapter.denon.0
                2019-10-16 07:48:28.878  - info: host.NUC(NUCmaster) stopInstance system.adapter.vis-fancyswitch.0
                2019-10-16 07:48:28.878  - info: host.NUC(NUCmaster) stopInstance system.adapter.harmony.0
                2019-10-16 07:48:28.879  - info: host.NUC(NUCmaster) stopInstance system.adapter.vis-timeandweather.0
                2019-10-16 07:48:28.879  - info: host.NUC(NUCmaster) stopInstance system.adapter.firetv.0
                2019-10-16 07:48:28.879  - info: host.NUC(NUCmaster) stopInstance system.adapter.vis-hqwidgets.0
                2019-10-16 07:48:28.879  - info: host.NUC(NUCmaster) stopInstance system.adapter.vis-colorpicker.0
                2019-10-16 07:48:28.879  - info: host.NUC(NUCmaster) stopInstance system.adapter.backitup.0
                2019-10-16 07:48:28.879  - info: host.NUC(NUCmaster) stopInstance system.adapter.geofency.0
                2019-10-16 07:48:28.880  - info: host.NUC(NUCmaster) stopInstance system.adapter.enigma2.0
                2019-10-16 07:48:28.880  - info: host.NUC(NUCmaster) stopInstance system.adapter.vis-metro.0
                2019-10-16 07:48:28.880  - info: host.NUC(NUCmaster) stopInstance system.adapter.mihome-vacuum.0
                2019-10-16 07:48:28.880  - info: host.NUC(NUCmaster) stopInstance system.adapter.vis-canvas-gauges.0
                2019-10-16 07:48:28.880  - info: host.NUC(NUCmaster) stopInstance system.adapter.unifi.0
                2019-10-16 07:48:28.880  - info: host.NUC(NUCmaster) stopInstance system.adapter.stiebel-isg.0
                2019-10-16 07:48:28.880  - info: host.NUC(NUCmaster) stopInstance system.adapter.terminal.0
                2019-10-16 07:48:28.880  - info: host.NUC(NUCmaster) stopInstance system.adapter.alexa2.0
                2019-10-16 07:48:28.881  - info: host.NUC(NUCmaster) stopInstance system.adapter.vis-google-fonts.0
                2019-10-16 07:48:28.881  - info: host.NUC(NUCmaster) stopInstance system.adapter.vis-players.0
                2019-10-16 07:48:28.881  - info: host.NUC(NUCmaster) stopInstance system.adapter.scenes.0
                2019-10-16 07:48:28.881  - info: host.NUC(NUCmaster) stopInstance system.adapter.vis-bars.0
                2019-10-16 07:48:28.882  - info: host.NUC(NUCmaster) stopInstance system.adapter.tankerkoenig.0
                2019-10-16 07:48:28.882  - info: host.NUC(NUCmaster) stopInstance system.adapter.javascript.0
                2019-10-16 07:48:28.882  - info: host.NUC(NUCmaster) stopInstance system.adapter.fritzdect.0
                2019-10-16 07:48:28.883  - info: host.NUC(NUCmaster) stopInstance system.adapter.info.0
                2019-10-16 07:48:28.883  - info: host.NUC(NUCmaster) stopInstance system.adapter.vis-rgraph.0
                2019-10-16 07:48:28.883  - info: host.NUC(NUCmaster) stopInstance system.adapter.gruenbeck.0
                2019-10-16 07:48:28.883  - info: host.NUC(NUCmaster) stopInstance system.adapter.fullybrowser.0
                2019-10-16 07:48:28.884  - info: host.NUC(NUCmaster) stopInstance system.adapter.enigma2.1
                2019-10-16 07:48:28.884  - info: host.NUC(NUCmaster) stopInstance system.adapter.text2command.0
                2019-10-16 07:48:28.884  - info: host.NUC(NUCmaster) stopInstance system.adapter.email.0
                2019-10-16 07:48:28.884  - info: host.NUC(NUCmaster) stopInstance system.adapter.pushover.0
                2019-10-16 07:48:28.885  - info: host.NUC(NUCmaster) stopInstance system.adapter.telegram.0
                2019-10-16 07:48:28.885  - info: host.NUC(NUCmaster) stopInstance system.adapter.iot.0
                2019-10-16 07:48:28.885  - info: host.NUC(NUCmaster) stopInstance system.adapter.smartmeter.0
                2019-10-16 07:48:28.885  - info: host.NUC(NUCmaster) stopInstance system.adapter.lovelace.0
                2019-10-16 07:48:28.888  - info: host.NUC(NUCmaster) stopInstance system.adapter.upnp.0
                2019-10-16 07:48:28.888  - info: host.NUC(NUCmaster) stopInstance system.adapter.mihome.0
                2019-10-16 07:48:28.888  - info: host.NUC(NUCmaster) stopInstance system.adapter.weatherunderground.0
                2019-10-16 07:48:28.888  - info: host.NUC(NUCmaster) stopInstance canceled schedule system.adapter.weatherunderground.0
                2019-10-16 07:48:28.889  - info: host.NUC(NUCmaster) stopInstance system.adapter.fakeroku.0
                2019-10-16 07:48:28.889  - info: host.NUC(NUCmaster) stopInstance system.adapter.hue-extended.0
                2019-10-16 07:48:28.889  - info: host.NUC(NUCmaster) stopInstance system.adapter.web.0
                2019-10-16 07:48:28.889  - info: host.NUC(NUCmaster) stopInstance system.adapter.socketio.0
                2019-10-16 07:48:28.889  - info: host.NUC(NUCmaster) stopInstance system.adapter.sonos.0
                2019-10-16 07:48:28.889  - info: host.NUC(NUCmaster) stopInstance system.adapter.dwd.0
                2019-10-16 07:48:28.890  - info: host.NUC(NUCmaster) stopInstance canceled schedule system.adapter.dwd.0
                2019-10-16 07:48:28.890  - info: host.NUC(NUCmaster) iobroker _restart
                2019-10-16 07:48:28.901  - info: host.NUC(NUCmaster) stopInstance system.adapter.admin.0 send kill signal
                2019-10-16 07:48:28.904  - info: host.NUC(NUCmaster) stopInstance system.adapter.tr-064.0 send kill signal
                2019-10-16 07:48:28.907  - info: host.NUC(NUCmaster) stopInstance system.adapter.ping.0 send kill signal
                2019-10-16 07:48:28.915  - info: host.NUC(NUCmaster) stopInstance system.adapter.hue.0 send kill signal
                2019-10-16 07:48:28.918  - info: host.NUC(NUCmaster) stopInstance system.adapter.harmony.0 send kill signal
                2019-10-16 07:48:28.925  - info: host.NUC(NUCmaster) stopInstance system.adapter.backitup.0 send kill signal
                2019-10-16 07:48:28.930  - info: host.NUC(NUCmaster) stopInstance system.adapter.geofency.0 send kill signal
                2019-10-16 07:48:28.934  - info: host.NUC(NUCmaster) stopInstance system.adapter.enigma2.0 send kill signal
                2019-10-16 07:48:28.936  - info: host.NUC(NUCmaster) stopInstance system.adapter.alexa2.0 send kill signal
                2019-10-16 07:48:28.940  - info: host.NUC(NUCmaster) stopInstance system.adapter.tankerkoenig.0 send kill signal
                2019-10-16 07:48:28.944  - info: host.NUC(NUCmaster) stopInstance system.adapter.javascript.0 send kill signal
                2019-10-16 07:48:28.947  - info: host.NUC(NUCmaster) stopInstance system.adapter.fritzdect.0 send kill signal
                2019-10-16 07:48:28.951  - info: host.NUC(NUCmaster) stopInstance system.adapter.info.0 send kill signal
                2019-10-16 07:48:28.952  - info: host.NUC(NUCmaster) stopInstance system.adapter.gruenbeck.0 send kill signal
                2019-10-16 07:48:29.002  - info: host.NUC(NUCmaster) stopInstance system.adapter.fullybrowser.0 send kill signal
                2019-10-16 07:48:29.005  - info: host.NUC(NUCmaster) stopInstance system.adapter.enigma2.1 send kill signal
                2019-10-16 07:48:29.015  - info: host.NUC(NUCmaster) stopInstance system.adapter.text2command.0 send kill signal
                2019-10-16 07:48:29.017  - info: host.NUC(NUCmaster) stopInstance system.adapter.email.0 send kill signal
                2019-10-16 07:48:29.019  - info: host.NUC(NUCmaster) stopInstance system.adapter.pushover.0 send kill signal
                2019-10-16 07:48:29.021  - info: host.NUC(NUCmaster) stopInstance system.adapter.telegram.0 send kill signal
                2019-10-16 07:48:29.023  - info: host.NUC(NUCmaster) stopInstance system.adapter.iot.0 send kill signal
                2019-10-16 07:48:29.026  - info: host.NUC(NUCmaster) stopInstance system.adapter.lovelace.0 send kill signal
                2019-10-16 07:48:29.028  - info: host.NUC(NUCmaster) stopInstance system.adapter.upnp.0 send kill signal
                2019-10-16 07:48:29.030  - info: host.NUC(NUCmaster) stopInstance system.adapter.mihome.0 send kill signal
                2019-10-16 07:48:29.037  - info: host.NUC(NUCmaster) stopInstance system.adapter.fakeroku.0 send kill signal
                2019-10-16 07:48:29.040  - info: host.NUC(NUCmaster) stopInstance system.adapter.hue-extended.0 send kill signal
                2019-10-16 07:48:29.044  - info: host.NUC(NUCmaster) stopInstance system.adapter.web.0 send kill signal
                2019-10-16 07:48:29.046  - info: host.NUC(NUCmaster) stopInstance system.adapter.socketio.0 send kill signal
                2019-10-16 07:48:29.054  - info: host.NUC(NUCmaster) stopInstance system.adapter.sonos.0 send kill signal
                ...
                2019-10-16 07:48:28.946  - ( Hier wurden alle Skripte gestoppt )
                ...
                2019-10-16 07:48:29.141  - info: javascript.0 (8992) terminating
                2019-10-16 07:48:29.142  - info: javascript.0 (8992) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                2019-10-16 07:48:29.320  - info: host.NUC(NUCmaster) instance system.adapter.geofency.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.323  - info: host.NUC(NUCmaster) instance system.adapter.harmony.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.326  - info: host.NUC(NUCmaster) instance system.adapter.tr-064.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.413  - info: ping.0 (11592) terminating
                2019-10-16 07:48:29.414  - info: ping.0 (11592) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                2019-10-16 07:48:29.431  - info: backitup.0 (8420) terminating
                2019-10-16 07:48:29.439  - info: enigma2.0 (6524) terminating
                2019-10-16 07:48:29.511  - info: enigma2.1 (2716) terminating
                2019-10-16 07:48:29.521  - info: email.0 (9008) terminating
                2019-10-16 07:48:29.523  - info: text2command.0 (5956) terminating
                2019-10-16 07:48:29.522  - info: email.0 (9008) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                2019-10-16 07:48:29.527  - info: pushover.0 (8276) terminating
                2019-10-16 07:48:29.532  - info: telegram.0 (5972) terminating
                2019-10-16 07:48:29.533  - info: telegram.0 (5972) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
                2019-10-16 07:48:29.663  - info: host.NUC(NUCmaster) instance system.adapter.fritzdect.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.665  - info: host.NUC(NUCmaster) instance system.adapter.hue.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.666  - info: host.NUC(NUCmaster) instance system.adapter.alexa2.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.668  - info: host.NUC(NUCmaster) instance system.adapter.hue-extended.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.670  - info: host.NUC(NUCmaster) instance system.adapter.socketio.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.671  - info: host.NUC(NUCmaster) instance system.adapter.fakeroku.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.673  - info: host.NUC(NUCmaster) instance system.adapter.lovelace.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.674  - info: host.NUC(NUCmaster) instance system.adapter.upnp.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.676  - info: host.NUC(NUCmaster) instance system.adapter.info.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.677  - info: host.NUC(NUCmaster) instance system.adapter.sonos.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.679  - info: host.NUC(NUCmaster) instance system.adapter.mihome.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.680  - info: host.NUC(NUCmaster) instance system.adapter.iot.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.682  - info: host.NUC(NUCmaster) instance system.adapter.gruenbeck.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.683  - info: host.NUC(NUCmaster) instance system.adapter.web.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.685  - info: host.NUC(NUCmaster) instance system.adapter.fullybrowser.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:29.739  - error: host.NUC(NUCmaster) iobroker internal/modules/cjs/loader.js:638
                   throw err;
                   ^
                
                Error: Cannot find module 'D:\ioBroker\NUCmaster\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:622:3)
                
                2019-10-16 07:48:29.766  - info: host.NUC(NUCmaster) iobroker exit 1
                2019-10-16 07:48:30.073  - info: host.NUC(NUCmaster) instance system.adapter.admin.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:30.075  - info: host.NUC(NUCmaster) instance system.adapter.javascript.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:30.076  - info: host.NUC(NUCmaster) instance system.adapter.ping.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:30.076  - info: host.NUC(NUCmaster) instance system.adapter.enigma2.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:30.077  - info: host.NUC(NUCmaster) instance system.adapter.backitup.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:30.078  - info: host.NUC(NUCmaster) instance system.adapter.tankerkoenig.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:30.078  - info: host.NUC(NUCmaster) instance system.adapter.enigma2.1 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:30.079  - info: host.NUC(NUCmaster) instance system.adapter.email.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:30.079  - info: host.NUC(NUCmaster) instance system.adapter.text2command.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:30.080  - info: host.NUC(NUCmaster) instance system.adapter.pushover.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:30.080  - info: host.NUC(NUCmaster) instance system.adapter.telegram.0 terminated with code 4294967196 (START_IMMEDIATELY_AFTER_STOP_HEX)
                2019-10-16 07:48:31.235  - info: host.NUC(NUCmaster) stopInstance timeout "2000 system.adapter.history.0 killing pid  8360
                2019-10-16 07:48:31.270  - warn: host.NUC(NUCmaster) instance system.adapter.history.0 terminated due to SIGTERM
                2019-10-16 07:48:31.271  - info: host.NUC(NUCmaster) instance system.adapter.history.0 terminated with code null ()
                2019-10-16 07:48:31.271  - info: host.NUC(NUCmaster) All instances are stopped.
                2019-10-16 07:48:31.441  - info: host.NUC(NUCmaster) terminated
                


                Windows Dienste beim Versuch den Dienst zu starten:

                ac290bac-eca1-44b9-8e6f-6e1add0d0e9e-image.png


                ioBroker.wrapper.log beim Versuch den Dienst zu starten:

                2019-10-16 08:12:24,317 INFO  - Starting ServiceWrapper in the service mode
                2019-10-16 08:12:24,368 INFO  - Starting "D:\ioBroker\NUCmaster\nodejs\node.exe" "D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller\controller.js"
                2019-10-16 08:12:24,375 INFO  - Starting "D:\ioBroker\NUCmaster\nodejs\node.exe" "D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller\controller.js"
                2019-10-16 08:12:24,418 INFO  - Started process 5864
                2019-10-16 08:12:24,430 DEBUG - Forwarding logs of the process System.Diagnostics.Process (node) to winsw.RollingSizeTimeLogAppender
                

                iobroker.err.log beim Versuch den Dienst zu starten:

                Error: Cannot find module 'D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller\controller.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:622:3)
                
                apollon77 1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 @aleks-83 last edited by

                  @aleks-83 hm ... da hat npm was kaputt gemacht. Bitte js Controller wieder Manuel installieren.

                  1 Reply Last reply Reply Quote 1
                  • A
                    aleks-83 last edited by Stabilostick

                    OK, wie mache ich das unter Windows?
                    Das Update auf 2.0.29 ist ja eh "versehentlich" passiert durch den button "alle Adapter updaten".
                    Kann ich dann jetzt erst wieder zurück zu 1.5.14?

                    Stabilostick 1 Reply Last reply Reply Quote 0
                    • Stabilostick
                      Stabilostick @aleks-83 last edited by

                      @aleks-83

                      Kann es sein, dass Du in der ioBroker Konfiguration vor der Migration diesen auf „latest“ stehen hattest? Das würde die Installation von 2.0.29 erklären.

                      Ist die Datei „ D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller\controller.js“ vorhanden?

                      A 1 Reply Last reply Reply Quote 0
                      • A
                        aleks-83 @Stabilostick last edited by aleks-83

                        @Stabilostick sagte in Windows Dienst lässt sich nicht mehr starten:

                        @aleks-83

                        Kann es sein, dass Du in der ioBroker Konfiguration vor der Migration diesen auf „latest“ stehen hattest? Das würde die Installation von 2.0.29 erklären.

                        Ja, hatte ich.
                        Soll ich nochmal neu migrieren?
                        Und sobald der Admin startet, direkt als erstes auf "stable" stellen?

                        Ist die Datei „ D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller\controller.js“ vorhanden?

                        Nein, es gibt den Ordner "iobroker.js-controller" nicht.

                        Stabilostick 1 Reply Last reply Reply Quote 0
                        • Stabilostick
                          Stabilostick @aleks-83 last edited by

                          @aleks-83 sagte in Windows Dienst lässt sich nicht mehr starten:

                          Nein, es gibt den Ordner "iobroker.js-controller" nicht.

                          Wau. Na dann mache mal die Kommandozeile der Instanz über das Startmenü auf und führe aus:

                          npm install iobroker.js-controller@latest --production
                          

                          Was passiert da dann?

                          A 1 Reply Last reply Reply Quote 1
                          • A
                            aleks-83 @Stabilostick last edited by aleks-83

                            @Stabilostick sagte in Windows Dienst lässt sich nicht mehr starten:

                            npm install iobroker.js-controller@latest --production

                            Er scheint was installiert zu haben.
                            Sind aber auch viele ERR Meldungen dabei:

                            D:\ioBroker\NUCmaster>npm install iobroker.js-controller@latest --production
                            
                            > iobroker.js-controller@2.0.29 preinstall D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller
                            > node lib/preinstallCheck.js
                            
                            NPM version: 6.9.0
                            
                            > authenticate-pam@1.0.2 install D:\ioBroker\NUCmaster\node_modules\authenticate-pam
                            > node-gyp rebuild
                            
                            
                            D:\ioBroker\NUCmaster\node_modules\authenticate-pam>if not defined npm_config_node_gyp (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
                            Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu ermöglichen, müssen Sie den Schalter "/m" hinzufügen.
                             authenticate_pam.cc
                             win_delay_load_hook.cc
                            d:\iobroker\nucmaster\node_modules\authenticate-pam\authenticate_pam.cc(24): fatal error C1083: Datei (Include) kann nicht geöffnet werden: "uni
                            std.h": No such file or directory [D:\ioBroker\NUCmaster\node_modules\authenticate-pam\build\authenticate_pam.vcxproj]
                            gyp ERR! build error
                            gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
                            gyp ERR! stack     at ChildProcess.onExit (D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
                            gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
                            gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
                            gyp ERR! System Windows_NT 10.0.18362
                            gyp ERR! command "D:\\ioBroker\\NUCmaster\\nodejs\\node.exe" "D:\\ioBroker\\NUCmaster\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
                            gyp ERR! cwd D:\ioBroker\NUCmaster\node_modules\authenticate-pam
                            gyp ERR! node -v v10.16.3
                            gyp ERR! node-gyp -v v3.8.0
                            gyp ERR! not ok
                            
                            > serialport@6.2.2 install D:\ioBroker\NUCmaster\node_modules\iobroker.discovery\node_modules\serialport
                            > prebuild-install || node-gyp rebuild
                            
                            
                            > unix-dgram@2.0.2 install D:\ioBroker\NUCmaster\node_modules\unix-dgram
                            > node-gyp rebuild
                            
                            
                            D:\ioBroker\NUCmaster\node_modules\unix-dgram>if not defined npm_config_node_gyp (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
                            Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu ermöglichen, müssen Sie den Schalter "/m" hinzufügen.
                             unix_dgram.cc
                             win_delay_load_hook.cc
                            d:\iobroker\nucmaster\node_modules\unix-dgram\src\unix_dgram.cc(9): fatal error C1083: Datei (Include) kann nicht geöffnet werden: "unistd.h": N
                            o such file or directory [D:\ioBroker\NUCmaster\node_modules\unix-dgram\build\unix_dgram.vcxproj]
                            gyp ERR! build error
                            gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
                            gyp ERR! stack     at ChildProcess.onExit (D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
                            gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
                            gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
                            gyp ERR! System Windows_NT 10.0.18362
                            gyp ERR! command "D:\\ioBroker\\NUCmaster\\nodejs\\node.exe" "D:\\ioBroker\\NUCmaster\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
                            gyp ERR! cwd D:\ioBroker\NUCmaster\node_modules\unix-dgram
                            gyp ERR! node -v v10.16.3
                            gyp ERR! node-gyp -v v3.8.0
                            gyp ERR! not ok
                            
                            > ursa-optional@0.9.10 install D:\ioBroker\NUCmaster\node_modules\ursa-optional
                            > node rebuild.js
                            
                            
                            > diskusage@1.1.3 install D:\ioBroker\NUCmaster\node_modules\diskusage
                            > node-gyp rebuild
                            
                            
                            D:\ioBroker\NUCmaster\node_modules\diskusage>if not defined npm_config_node_gyp (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
                            Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu ermöglichen, müssen Sie den Schalter "/m" hinzufügen.
                             main.cpp
                             diskusage_win.cpp
                             win_delay_load_hook.cc
                                Bibliothek "D:\ioBroker\NUCmaster\node_modules\diskusage\build\Release\diskusage.lib" und Objekt "D:\ioBroker\NUCmaster\node_modules\diskus
                             age\build\Release\diskusage.exp" werden erstellt.
                             Code wird generiert.
                             All 262 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.
                             Codegenerierung ist abgeschlossen.
                             diskusage.vcxproj -> D:\ioBroker\NUCmaster\node_modules\diskusage\build\Release\\diskusage.node
                            
                            > iobroker.js-controller@2.0.29 install D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller
                            > node iobroker.js setup first
                            
                            
                            > acme-v2@1.8.5 postinstall D:\ioBroker\NUCmaster\node_modules\acme-v2
                            > node scripts/postinstall
                            
                            
                            ================================================================================
                            
                            👇👇👇👇👇👇👇👇👇👇👇👇👇👇👇
                            👉                             👈
                            👉  Do you rely on Greenlock?  👈
                            👉               (or ACME.js)  👈
                            👉                             👈
                            👆👆👆👆👆👆👆👆👆👆👆👆👆👆👆
                            
                            Hey! Let's Encrypt will STOP WORKING with Greenlock and ACME.js at the end of Oct 2019.
                            WITHOUT YOUR HELP we won't get the next release out in time.
                            
                            If Greenlock (or ACME.js) has saved you time and money, and taken stress out of your life,
                            or you just love it, please reach out to return the favor today:
                            
                            SAVE GREENLOCK / ACME.js:
                            https://indiegogo.com/at/greenlock
                            
                            ================================================================================
                            
                            npm WARN xmlhttprequest-ts@1.0.1 requires a peer of @angular/common@>= 5.0.0 but none is installed. You must install peer dependencies yourself.
                            npm WARN xmlhttprequest-ts@1.0.1 requires a peer of @angular/core@>= 5.0.0 but none is installed. You must install peer dependencies yourself.
                            npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.1 (node_modules\fsevents):
                            npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
                            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":"win32","arch":"x64"})
                            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
                            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
                            
                            + iobroker.js-controller@2.0.29
                            added 207 packages from 214 contributors, removed 74 packages, updated 3 packages, moved 10 packages and audited 1566 packages in 117.15s
                            found 12 vulnerabilities (9 low, 3 high)
                             run `npm audit fix` to fix them, or `npm audit` for details
                            
                            D:\ioBroker\NUCmaster>
                            

                            Läuft wieder alles.

                            Stabilostick 1 Reply Last reply Reply Quote 0
                            • Stabilostick
                              Stabilostick @aleks-83 last edited by Stabilostick

                              @aleks-83

                              npm install @angular/common@
                              npm install @angular/core@
                              

                              Sieht aber schon einmal trotz der Meldungen gut aus. Bist freiwilliger Betatester, weil Du Dein System auf „latest“ stehen hast. 👌 🤗

                              1 Reply Last reply Reply Quote 0
                              • A
                                aleks-83 last edited by aleks-83

                                OK, habe ich durchgeführt.

                                D:\ioBroker\NUCmaster>npm install @angular/common@
                                
                                > authenticate-pam@1.0.2 install D:\ioBroker\NUCmaster\node_modules\authenticate-pam
                                > node-gyp rebuild
                                
                                
                                D:\ioBroker\NUCmaster\node_modules\authenticate-pam>if not defined npm_config_node_gyp (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
                                Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu ermöglichen, müssen Sie den Schalter "/m" hinzufügen.
                                  authenticate_pam.cc
                                  win_delay_load_hook.cc
                                d:\iobroker\nucmaster\node_modules\authenticate-pam\authenticate_pam.cc(24): fatal error C1083: Datei (Include) kann nicht geöffnet werden: "uni
                                std.h": No such file or directory [D:\ioBroker\NUCmaster\node_modules\authenticate-pam\build\authenticate_pam.vcxproj]
                                gyp ERR! build error
                                gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
                                gyp ERR! stack     at ChildProcess.onExit (D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
                                gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
                                gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
                                gyp ERR! System Windows_NT 10.0.18362
                                gyp ERR! command "D:\\ioBroker\\NUCmaster\\nodejs\\node.exe" "D:\\ioBroker\\NUCmaster\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
                                gyp ERR! cwd D:\ioBroker\NUCmaster\node_modules\authenticate-pam
                                gyp ERR! node -v v10.16.3
                                gyp ERR! node-gyp -v v3.8.0
                                gyp ERR! not ok
                                
                                > unix-dgram@2.0.2 install D:\ioBroker\NUCmaster\node_modules\unix-dgram
                                > node-gyp rebuild
                                
                                
                                D:\ioBroker\NUCmaster\node_modules\unix-dgram>if not defined npm_config_node_gyp (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
                                Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu ermöglichen, müssen Sie den Schalter "/m" hinzufügen.
                                  unix_dgram.cc
                                  win_delay_load_hook.cc
                                d:\iobroker\nucmaster\node_modules\unix-dgram\src\unix_dgram.cc(9): fatal error C1083: Datei (Include) kann nicht geöffnet werden: "unistd.h": N
                                o such file or directory [D:\ioBroker\NUCmaster\node_modules\unix-dgram\build\unix_dgram.vcxproj]
                                gyp ERR! build error
                                gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
                                gyp ERR! stack     at ChildProcess.onExit (D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
                                gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
                                gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
                                gyp ERR! System Windows_NT 10.0.18362
                                gyp ERR! command "D:\\ioBroker\\NUCmaster\\nodejs\\node.exe" "D:\\ioBroker\\NUCmaster\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
                                gyp ERR! cwd D:\ioBroker\NUCmaster\node_modules\unix-dgram
                                gyp ERR! node -v v10.16.3
                                gyp ERR! node-gyp -v v3.8.0
                                gyp ERR! not ok
                                npm WARN xmlhttprequest-ts@1.0.1 requires a peer of @angular/core@>= 5.0.0 but none is installed. You must install peer dependencies yourself.
                                npm WARN @angular/common@8.2.11 requires a peer of rxjs@^6.4.0 but none is installed. You must install peer dependencies yourself.
                                npm WARN @angular/common@8.2.11 requires a peer of @angular/core@8.2.11 but none is installed. You must install peer dependencies yourself.
                                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.1 (node_modules\fsevents):
                                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
                                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":"win32","arch":"x64"})
                                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
                                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
                                
                                + @angular/common@8.2.11
                                added 2 packages from 2 contributors and audited 1568 packages in 303.548s
                                found 12 vulnerabilities (9 low, 3 high)
                                  run `np
                                [/s]m audit fix` to fix them, or `npm audit` for details
                                
                                D:\ioBroker\NUCmaster>
                                

                                D:\ioBroker\NUCmaster>npm install @angular/core@
                                
                                > authenticate-pam@1.0.2 install D:\ioBroker\NUCmaster\node_modules\authenticate-pam
                                > node-gyp rebuild
                                
                                
                                D:\ioBroker\NUCmaster\node_modules\authenticate-pam>if not defined npm_config_node_gyp (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
                                Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu ermöglichen, müssen Sie den Schalter "/m" hinzufügen.
                                  authenticate_pam.cc
                                  win_delay_load_hook.cc
                                d:\iobroker\nucmaster\node_modules\authenticate-pam\authenticate_pam.cc(24): fatal error C1083: Datei (Include) kann nicht geöffnet werden: "uni
                                std.h": No such file or directory [D:\ioBroker\NUCmaster\node_modules\authenticate-pam\build\authenticate_pam.vcxproj]
                                gyp ERR! build error
                                gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
                                gyp ERR! stack     at ChildProcess.onExit (D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
                                gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
                                gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
                                gyp ERR! System Windows_NT 10.0.18362
                                gyp ERR! command "D:\\ioBroker\\NUCmaster\\nodejs\\node.exe" "D:\\ioBroker\\NUCmaster\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
                                gyp ERR! cwd D:\ioBroker\NUCmaster\node_modules\authenticate-pam
                                gyp ERR! node -v v10.16.3
                                gyp ERR! node-gyp -v v3.8.0
                                gyp ERR! not ok
                                
                                > unix-dgram@2.0.2 install D:\ioBroker\NUCmaster\node_modules\unix-dgram
                                > node-gyp rebuild
                                
                                
                                D:\ioBroker\NUCmaster\node_modules\unix-dgram>if not defined npm_config_node_gyp (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild )  else (node "D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
                                Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu ermöglichen, müssen Sie den Schalter "/m" hinzufügen.
                                  unix_dgram.cc
                                  win_delay_load_hook.cc
                                d:\iobroker\nucmaster\node_modules\unix-dgram\src\unix_dgram.cc(9): fatal error C1083: Datei (Include) kann nicht geöffnet werden: "unistd.h": N
                                o such file or directory [D:\ioBroker\NUCmaster\node_modules\unix-dgram\build\unix_dgram.vcxproj]
                                gyp ERR! build error
                                gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
                                gyp ERR! stack     at ChildProcess.onExit (D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262:23)
                                gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
                                gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
                                gyp ERR! System Windows_NT 10.0.18362
                                gyp ERR! command "D:\\ioBroker\\NUCmaster\\nodejs\\node.exe" "D:\\ioBroker\\NUCmaster\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
                                gyp ERR! cwd D:\ioBroker\NUCmaster\node_modules\unix-dgram
                                gyp ERR! node -v v10.16.3
                                gyp ERR! node-gyp -v v3.8.0
                                gyp ERR! not ok
                                npm WARN @angular/common@8.2.11 requires a peer of rxjs@^6.4.0 but none is installed. You must install peer dependencies yourself.
                                npm WARN @angular/core@8.2.11 requires a peer of rxjs@^6.4.0 but none is installed. You must install peer dependencies yourself.
                                npm WARN @angular/core@8.2.11 requires a peer of zone.js@~0.9.1 but none is installed. You must install peer dependencies yourself.
                                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.1 (node_modules\fsevents):
                                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
                                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":"win32","arch":"x64"})
                                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
                                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
                                
                                + @angular/core@8.2.11
                                added 1 package from 1 contributor and audited 1570 packages in 70.735s
                                found 12 vulnerabilities (9 low, 3 high)
                                  run `npm audit fix` to fix them, or `npm audit` for details
                                
                                D:\ioBroker\NUCmaster>
                                

                                @Stabilostick
                                Bist freiwilliger Betatester, weil Du Dein System auf „latest“ stehen hast. 👍🏻🤗

                                "Freiwillig", ja 😂
                                Eigentlich möchte ich nur dass es wieder (rund) läuft... 🤕

                                1 Reply Last reply Reply Quote 0
                                • A
                                  aleks-83 last edited by aleks-83

                                  Wie kann ich denn bitte wieder zurück zum JS 1.5.14 downgraden?
                                  Mit dem 2.x habe ich immer wieder mal Probleme.
                                  Bin jetzt bei 2.0.38.
                                  Admin 3.6.10
                                  Javascript 4.3.1

                                  Aktuell zeigt mir der Javasript Adapter an dass die Instanz deaktiviert wäre, obwohl sie grün ist.
                                  1c1416dc-2461-4566-a280-0cf91121b7cf-image.png

                                  Als ich gerade mal den Moment beobachtet habe wo die Instanz angeblich in deaktiviert gewechsel hat, erschien im Log die Debug Zeile:

                                  (10140) sendTo "loadTypings" to system.adapter.admin.0 from system.adapter.javascript.0
                                  
                                  Stabilostick apollon77 2 Replies Last reply Reply Quote 0
                                  • Stabilostick
                                    Stabilostick @aleks-83 last edited by

                                    @aleks-83

                                    Downgrade über den 1.5.14‘er Installer und Migration in neue Instanz. Vorher ggf. das Repository im Admin von latest nach stable (=default) umstellen.

                                    1 Reply Last reply Reply Quote 0
                                    • apollon77
                                      apollon77 @aleks-83 last edited by apollon77

                                      @aleks-83 JavaScript macht so einige Dinge ggf hintendran. Die Anzeige "Instanz ist deaktiviert" hat nichts mit dem js.controller zu tun. Da hat Javascript irgendwie noch nicht alle Daten. Das "loadTypings" bedeutet zB das der Editor erst mal Typinformationen lädt ... das kann kurz dauern ... geduld bitte, es gibst(gab dazu ein JavaScrtiot Issue, und nicht gleich controller downgraden.

                                      ... und "immer mal wieder" gern detaillieren ...

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

                                        @aleks-83

                                        Js-Controller 2.0 wird bald stable. Ich stimme @apollon77 zu, lieber die Probleme zu suchen und zu beheben, als downzugraden.

                                        1 Reply Last reply Reply Quote 0
                                        • A
                                          aleks-83 last edited by

                                          Ich möchte ja eigentlich auch beim 2.x bleiben.

                                          In den letzten Wochen häufen sich bei mir aber die Probleme.
                                          Es muss ja nicht am JS 2.x selbst liegen.
                                          Vielleicht sind meine Adapter dann noch nicht alle damit kompatibel!?

                                          Heute morgen hatte ich z.B. Probleme mit meinem Sonos Adapter dass er keine Geräte mehr steuern konnte mit der Meldung "Sonos "" not found".
                                          Und der Fully Adapter zeigt den "fully alive" nur sporadisch an. Meistens false, manchmal null, manchmal true.

                                          apollon77 1 Reply Last reply Reply Quote 0
                                          • apollon77
                                            apollon77 @aleks-83 last edited by

                                            @aleks-83 ggf bitte mal Adapter auf Loglevel Debug oder sogar "silly" stellen und dann log schicken von solchen vorkommnissen, Dann kann man schauen ob es Adapter oder controller ist.

                                            Was ist "fully alive"?

                                            A 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

                                            735
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            node.js windows dienst
                                            4
                                            54
                                            4644
                                            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