Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [Gelöst]Installation auf Windows Server 2012

    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

    [Gelöst]Installation auf Windows Server 2012

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

      Hallo,

      mein Name ist Olaf, bin Softwareentwickler im .Net und C# Umfeld und würde mich gerne ein wenig mit iobroker beschäftigen.

      Ich versuche schon seit Tagen iobroker auf einem Windows Server 2012 (6.2.9200) zu installieren. Sowohl die automatische als auch die manuelle Installation schlugen fehl.

      Es läuft aktuell Node 6.11.0 auf dem System. Die windows-build-tools wurden auch installiert.

      Vielleicht kann mich jemand in die richtige Richtung 'bringen'. Danke

      Anbei die Ausgabe der manuellen Installation:

      ! C:\ioBroker>
      ! npm install iobroker
      ! > iobroker@1.0.0 install C:\ioBroker\node_modules\iobroker
      ! > node lib/setup.js
      ! npm install iobroker.discovery –production --prefix "C:/ioBroker"
      ! npm WARN invalid config loglevel="notice"
      ! node-pre-gyp info it worked if it ends with ok
      ! node-pre-gyp verb cli [ 'C:\Program Files\nodejs\node.exe',
      ! node-pre-gyp verb cli 'C:\ioBroker\node_modules\iobroker.discovery\node_mo
      ! dules\serialport\node_modules\node-pre-gyp\bin\node-pre-gyp',
      ! node-pre-gyp verb cli 'install',
      ! node-pre-gyp verb cli '--fallback-to-build' ]
      ! node-pre-gyp info using node-pre-gyp@0.6.32
      ! node-pre-gyp info using node@6.11.0 | win32 | x64
      ! node-pre-gyp verb command install []
      ! node-pre-gyp info check checked for "C:\ioBroker\node_modules\iobroker.discovery
      ! \node_modules\serialport\build\Release\serialport.node" (not found)
      ! node-pre-gyp http GET https://github.com/EmergingTechnologyAd ... de-serialp
      ! ort/releases/download/4.0.7/serialport-v4.0.7-node-v48-win32-x64.tar.gz
      ! node-pre-gyp http 200 https://github.com/EmergingTechnologyAd ... de-serialp
      ! ort/releases/download/4.0.7/serialport-v4.0.7-node-v48-win32-x64.tar.gz
      ! node-pre-gyp info install unpacking obj/
      ! node-pre-gyp info install unpacking obj/serialport/
      ! node-pre-gyp info install unpacking obj/serialport/serialport.obj
      ! node-pre-gyp info install unpacking obj/serialport/serialport.tlog/
      ! node-pre-gyp info install unpacking obj/serialport/serialport.tlog/CL.read.1.tlo
      ! g
      ! node-pre-gyp info install unpacking obj/serialport/serialport.tlog/cl.command.1.
      ! tlog
      ! node-pre-gyp info install unpacking obj/serialport/serialport.tlog/cl.write.1.tl
      ! og
      ! node-pre-gyp info install unpacking obj/serialport/serialport.tlog/link.command.
      ! 1.tlog
      ! node-pre-gyp info install unpacking obj/serialport/serialport.tlog/link.read.1.t
      ! log
      ! node-pre-gyp info install unpacking obj/serialport/serialport.tlog/link.write.1.
      ! tlog
      ! node-pre-gyp info install unpacking obj/serialport/serialport.tlog/serialport.la
      ! stbuildstate
      ! node-pre-gyp info install unpacking obj/serialport/serialport.tlog/serialport.wr
      ! ite.1u.tlog
      ! node-pre-gyp info install unpacking obj/serialport/serialport_win.obj
      ! node-pre-gyp info install unpacking obj/serialport/vc120.pdb
      ! node-pre-gyp info install unpacking obj/serialport/win_delay_load_hook.obj
      ! node-pre-gyp info install unpacking serialport.exp
      ! node-pre-gyp info install unpacking serialport.lib
      ! node-pre-gyp info install unpacking serialport.map
      ! node-pre-gyp info install unpacking serialport.node
      ! node-pre-gyp info install unpacking serialport.pdb
      ! node-pre-gyp info tarball done parsing tarball
      ! node-pre-gyp info validate Running test command: 'C:\Program Files\nodejs\node.e
      ! xe --eval 'require('C:/ioBroker/node_modules/iobroker.discovery/node_modules/se
      ! rialport/build/Release/serialport.node')''
      ! node-pre-gyp info ok
      ! gyp ERR! build error
      ! gyp ERR! stack Error: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe fail
      ! ed with exit code: 1
      ! gyp ERR! stack at ChildProcess.onExit (C:\Users\Administrator\AppData\Roamin
      ! g\npm\node_modules\npm\node_modules\node-gyp\lib\build.js:258: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_proces
      ! s.js:215:12)
      ! gyp ERR! System Windows_NT 6.2.9200
      ! gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\Administrator
      ! \AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gy
      ! p.js" "rebuild"
      ! gyp ERR! cwd C:\ioBroker\node_modules\iobroker.discovery\node_modules\mdns
      ! gyp ERR! node -v v6.11.0
      ! gyp ERR! node-gyp -v v3.6.2
      ! gyp ERR! not ok
      ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.3.3 (node_modules\iobroke
      ! r.discovery\node_modules\mdns):
      ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: mdns@2.3.3 install: node-gyp re ! build
      ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
      ! npm install iobroker.admin --production --prefix "C:/ioBroker"
      ! npm WARN invalid config loglevel="notice"
      ! npm install iobroker.js-controller --production --prefix "C:/ioBroker"
      ! npm WARN invalid config loglevel="notice"
      ! gyp ERR! build error
      ! gyp ERR! stack Error: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe fail
      ! ed with exit code: 1
      ! gyp ERR! stack at ChildProcess.onExit (C:\Users\Administrator\AppData\Roamin
      ! g\npm\node_modules\npm\node_modules\node-gyp\lib\build.js:258: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_proces
      ! s.js:215:12)
      ! gyp ERR! System Windows_NT 6.2.9200
      ! gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\Administrator
      ! \AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gy
      ! p.js" "rebuild"
      ! gyp ERR! cwd C:\ioBroker\node_modules\iobroker.js-controller\node_modules\ursa
      ! gyp ERR! node -v v6.11.0
      ! gyp ERR! node-gyp -v v3.6.2
      ! gyp ERR! not ok
      ! gyp ERR! build error
      ! gyp ERR! stack Error: C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe fail
      ! ed with exit code: 1
      ! gyp ERR! stack at ChildProcess.onExit (C:\Users\Administrator\AppData\Roamin
      ! g\npm\node_modules\npm\node_modules\node-gyp\lib\build.js:258: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_proces
      ! s.js:215:12)
      ! gyp ERR! System Windows_NT 6.2.9200
      ! gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\Administrator
      ! \AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gy
      ! p.js" "rebuild"
      ! gyp ERR! cwd C:\ioBroker\node_modules\iobroker.js-controller\node_modules\unix-d
      ! gram
      ! gyp ERR! node -v v6.11.0
      ! gyp ERR! node-gyp -v v3.6.2
      ! gyp ERR! not ok
      ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ursa@0.9.4 (node_modules\iobroke
      ! r.js-controller\node_modules\ursa):
      ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: ursa@0.9.4 install: node-gyp re ! build
      ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
      ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 (node_modules\i
      ! obroker.js-controller\node_modules\unix-dgram):
      ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@0.2.3 install: node- ! gyp rebuild
      ! npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
      ! Write "iobroker start" to start the ioBroker
      ! npm install https://github.com/arthurblake/node-win ... e93e246966
      ! 3b99a9cf3a64086ecedfe1e4 --production --prefix "C:\ioBroker\node_modules\iobroke
      ! r\lib/../../../"
      ! npm WARN invalid config loglevel="notice"
      ! ioBroker service installed. Write "serviceIoBroker start" to start the service a
      ! nd go to http://localhost:8081 to open the admin UI.
      ! To see the outputs do not start the service, but write "node node_modules/iobrok
      ! er.js-controller/controller"
      ! npm notice created a lockfile as package-lock.json. You should commit this file.
      ! npm WARN enoent ENOENT: no such file or directory, open 'C:\ioBroker\package.jso
      ! n'
      ! npm WARN ioBroker No description
      ! npm WARN ioBroker No repository field.
      ! npm WARN ioBroker No README data
      ! npm WARN ioBroker No license field.
      ! + iobroker@1.0.0
      ! added 46 packages in 318.576s
      ! C:\ioBroker>

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

        Hallo Olaf und Willkommen im Forum!

        Ich kenne mich mit Windows Installationen nicht aus, aber so auf Anhieb sehe ich keine gravierenden Fehler, nur optionale Abhängigkeiten.

        Zum Schluss scheint die Installation auch ioBroker zu starten.

        Was bedeutet das
        @Reisender:

        Sowohl die automatische als auch die manuelle Installation schlugen fehl. `

        Kannst du IP:8081 nicht aufrufen?

        Mach mal

        iobroker restart

        Hast du die Installation als Administrator ausgeführt?

        Gruß

        Rainer

        1 Reply Last reply Reply Quote 0
        • R
          Reisender last edited by

          Hallo Rainer,

          danke für die schnelle Antwort. Ich sehe ein paar ms-Build errors. 🙂

          Ja, ich habe als Admin installiert und ich bekomme die Weboberfläche mit mit IP:8081.

          Restart hatte ich auch schon probiert. Dabei gehen zwei node.exe Fenster auf und nie wieder zu.

          Grüße

          Olaf

          1 Reply Last reply Reply Quote 0
          • R
            Reisender last edited by

            Wenn ich

            iobroker status

            eingebe, kommt folgende Fehlermeldung:

            C:\ioBroker>node node_modules/iobroker.js-controller/iobroker.js status
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE :::9000
    at Object.exports._errnoException (util.js:1018:11)
    at exports._exceptionWithHostPort (util.js:1041:20)
    at Server._listen2 (net.js:1258:14)
    at listen (net.js:1294:10)
    at Server.listen (net.js:1390:5)
    at _initWebServer (C:\ioBroker\node_modules\iobroker.js-controller\lib\states\statesInMemServer.js:1080:20)
    at C:\ioBroker\node_modules\iobroker.js-controller\lib\states\statesInMemServer.js:200:9
    at new StatesInMemory (C:\ioBroker\node_modules\iobroker.js-controller\lib\states\statesInMemServer.js:207:7)
    at Timeout._onTimeout (C:\ioBroker\node_modules\iobroker.js-controller\lib\setup.js:2819:26)
    at ontimeout (timers.js:386:14)

            Und das Log dazu:

            2017-06-14 05:31:54.156  - [31merror[39m: host.xxxxxxx instance system.adapter.discovery.0 terminated with code 3221225786 ()
2017-06-14 05:31:54.156  - [32minfo[39m: host.xxxxxxx Restart adapter system.adapter.discovery.0 because enabled
2017-06-14 05:31:54.733  - [31merror[39m: host.xxxxxxx instance system.adapter.admin.0 terminated with code 3221225786 ()
2017-06-14 05:31:54.733  - [32minfo[39m: host.xxxxxxx Restart adapter system.adapter.admin.0 because enabled
2017-06-14 06:01:27.877  - [32minfo[39m: host.xxxxxxx iobroker.js-controller version 1.0.3 js-controller starting
2017-06-14 06:01:27.908  - [32minfo[39m: host.xxxxxxx Copyright (c) 2014-2017 bluefox, hobbyquaker
2017-06-14 06:01:27.908  - [32minfo[39m: host.xxxxxxx hostname: dhkaufering, node: v6.11.0
2017-06-14 06:01:27.923  - [32minfo[39m: host.xxxxxxx ip addresses: fe80::88f6:3149:aa1c:93fa 192.168.1.1 2001:0:9d38:78cf:100e:3a78:b034:baed fe80::100e:3a78:b034:baed
2017-06-14 06:01:28.064  - [32minfo[39m: host.xxxxxxx  inMem-states listening on port 9000
2017-06-14 06:01:28.111  - [32minfo[39m: host.xxxxxxx  inMem-objects listening on port 9001
2017-06-14 06:01:28.126  - [32minfo[39m: host.xxxxxxx InMemoryDB connected
2017-06-14 06:01:28.142  - [32minfo[39m: host.xxxxxxx 2 instances found
2017-06-14 06:01:28.157  - [32minfo[39m: host.xxxxxxx starting 2 instances
2017-06-14 06:01:28.251  - [32minfo[39m: host.xxxxxxx instance system.adapter.admin.0 started with pid 3960
2017-06-14 06:01:32.245  - [32minfo[39m: host.xxxxxxx instance system.adapter.discovery.0 started with pid 3304
2017-06-14 06:01:39.113  - [31merror[39m: discovery.0 no connection to states DB: Connection timeout
2017-06-14 06:01:44.980  - [31merror[39m: admin.0 no connection to states DB: Connection timeout
2017-06-14 06:06:22.797  - [31merror[39m: host.xxxxxxx instance system.adapter.discovery.0 terminated with code 3221225786 ()
2017-06-14 06:06:22.797  - [32minfo[39m: host.xxxxxxx Restart adapter system.adapter.discovery.0 because enabled
2017-06-14 06:06:23.453  - [31merror[39m: host.xxxxxxx instance system.adapter.admin.0 terminated with code 3221225786 ()
2017-06-14 06:06:23.453  - [32minfo[39m: host.xxxxxxx Restart adapter system.adapter.admin.0 because enabled
2017-06-14 06:06:52.814  - [32minfo[39m: host.xxxxxxx instance system.adapter.discovery.0 started with pid 3688
2017-06-14 06:06:53.485  - [32minfo[39m: host.xxxxxxx instance system.adapter.admin.0 started with pid 3716
2017-06-14 06:06:55.529  - [31merror[39m: host.xxxxxxx instance system.adapter.admin.0 terminated with code 3221225786 ()
2017-06-14 06:06:55.529  - [32minfo[39m: host.xxxxxxx Restart adapter system.adapter.admin.0 because enabled
2017-06-14 06:06:56.012  - [31merror[39m: host.xxxxxxx instance system.adapter.discovery.0 terminated with code 3221225786 ()
2017-06-14 06:06:56.012  - [32minfo[39m: host.xxxxxxx Restart adapter system.adapter.discovery.0 because enabled
2017-06-14 06:07:25.547  - [32minfo[39m: host.xxxxxxx instance system.adapter.admin.0 started with pid 4068
2017-06-14 06:07:26.031  - [32minfo[39m: host.xxxxxxx instance system.adapter.discovery.0 started with pid 2100
2017-06-14 06:07:31.975  - [31merror[39m: discovery.0 no connection to states DB: Connection timeout
2017-06-14 06:07:32.661  - [31merror[39m: admin.0 no connection to states DB: Connection timeout
            1 Reply Last reply Reply Quote 0
            • Thisoft
              Thisoft last edited by

              Hallo Reisender,

              was mir auffällt ist:

              Error: listen EADDRINUSE :::9000

              Das sieht aus als ob da bei dir schon ein anderes Programm auf Port 9000 lauscht - prüf das bitte mal.

              Diverse Reboots nach der Installation hast du sicherlich schon gemacht - oder? Den Effekt mit den node.exe - Fenstern hatte ich auch hin und wieder mal nach Updates etc., war aber jeweils nach einem Reboot wieder OK.

              1 Reply Last reply Reply Quote 0
              • arteck
                arteck Developer Most Active last edited by

                dir ist schon klar dass sich ein Windows Server 2012 anders verhält als eine Windows normalo installation…

                was sagt den node -v direkt nach dem aufruf von CMD

                fehlen die Pfade ??

                1 Reply Last reply Reply Quote 0
                • R
                  Reisender last edited by

                  Danke für Eure Antworten!!

                  @Thisoft

                  Das mit dem Port war der Hinweis!!! Danke, da lief das Medicenter mit.

                  Jetzt gehts. Zumindest komme ich auf die iobroker Seite.

                  @arteck

                  es kommt v6.11.0

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

                    Schön dass dein ioBroker jetzt läuft.

                    Und eine Windows Server Installation ist jetzt nichts soo großartig anderes als ein normales Windows wenn man davon absieht dass es einige viele Funktionen mehr bietet und teurer ist 😉

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

                    Support us

                    ioBroker
                    Community Adapters
                    Donate
                    FAQ Cloud / IOT
                    HowTo: Node.js-Update
                    HowTo: Backup/Restore
                    Downloads
                    BLOG

                    892
                    Online

                    31.9k
                    Users

                    80.2k
                    Topics

                    1.3m
                    Posts

                    4
                    8
                    1209
                    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