Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Uninstall - install problem

    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

    Uninstall - install problem

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

      @starfish:

      kann ich bestätigen
      > in den rechten Spalten wechselt es dauern von rot nach grün :(
      wie auch die Logeinträge sehen bei mir gleich aus. `
      Reboot

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

        Auch bei controller 0.6.3 und neuem admin bleibt es dabei, dass bei einem ./iobroker restart einzelne Adapter nicht beendet werden (erst mal nur node-red und hmm) und nach dem restart doppelt laufen.

        Dadurch kommt es andauernd zu terminating code 7

        Nach reboot ist gut!

        Gesendet von meinem LIFETAB_S785X mit Tapatalk

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

          😞

          INSTALL lief durch

          root@pi2:/mnt/ioBroker/iobroker# npm install iobroker.js-controller

> ws@0.5.0 install /mnt/ioBroker/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io/node_m                                           odules/engine.io/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

make: Entering directory '/mnt/ioBroker/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io                                           /node_modules/engine.io/node_modules/ws/build'
  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node: Finished
  COPY Release/bufferutil.node
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/obj.target/validation.node
  SOLINK_MODULE(target) Release/obj.target/validation.node: Finished
  COPY Release/validation.node
make: Leaving directory '/mnt/ioBroker/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io/                                           node_modules/engine.io/node_modules/ws/build'

> ws@0.4.31 install /mnt/ioBroker/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-clien                                           t/node_modules/engine.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

make: Entering directory '/mnt/ioBroker/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io                                           -client/node_modules/engine.io-client/node_modules/ws/build'
  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node: Finished
  COPY Release/bufferutil.node
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/obj.target/validation.node
  SOLINK_MODULE(target) Release/obj.target/validation.node: Finished
  COPY Release/validation.node
make: Leaving directory '/mnt/ioBroker/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-cl           ient/node_modules/ws/build'

> iobroker.js-controller@0.6.3 install /mnt/ioBroker/iobroker/node_modules/iobroker.js-controller
> node lib/setup.js setup first

iobroker.js-controller@0.6.3 node_modules/iobroker.js-controller
├── mime@1.3.4
├── daemonize2@0.4.2
├── node-schedule@0.1.13
├── ncp@2.0.0
├── adm-zip@0.4.7
├── node.extend@1.1.3 (is@2.1.0)
├── yargs@3.7.2 (camelcase@1.0.2, decamelize@1.0.0, window-size@0.1.0, wordwrap@0.0.2)
├── winston@1.0.0 (cycle@1.0.3, stack-trace@0.0.9, eyes@0.1.8, isstream@0.1.2, pkginfo@0.3.0, async@0.9.0, colors@1.0.3)
├── tar.gz@0.1.1 (commander@1.1.1, tar@0.1.20, fstream@0.1.31)
├── request@2.55.0 (caseless@0.9.0, json-stringify-safe@5.0.0, aws-sign2@0.5.0, forever-agent@0.6.1, stringstream@0.0.4, tunnel-agent@0.4.0, oauth-sign@0.6.0, isstream@0.1.2, node-uuid@1.4.3, qs@2.4.1, combined-stream@0.0.7, form-data@0.2.0, mime-types@2.0.10, http-signature@0.10.1, bl@0.9.4, tough-cookie@0.12.1, hawk@2.3.1, har-validator@1.6.1)
├── socket.io@1.3.5 (debug@2.1.0, has-binary-data@0.1.3, socket.io-adapter@0.3.1, socket.io-parser@2.2.4, engine.io@1.5.1)
├── socket.io-client@1.3.5 (to-array@0.1.3, indexof@0.0.1, component-bind@1.0.0, debug@0.7.4, object-component@0.0.3, backo2@1.0.2, component-emitter@1.1.2, has-binary@0.1.6, parseuri@0.0.2, socket.io-parser@2.2.4, engine.io-client@1.5.1)
└── npm@2.7.6
root@pi2:/mnt/ioBroker/iobroker#

          Jedoch ist etwas mit dem symLink

          root@pi2:/mnt/ioBroker/iobroker# iobroker start

module.js:340
    throw err;
          ^
Error: Cannot find module '/mnt/ioBroker/iobroker.Pi2/node_modules/iobroker.js-controller/iobroker.js'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:935:3

          so startet der controler

          root@pi2:/mnt/ioBroker/iobroker# ./iobroker start
Starting ioBroker controller daemon...
ioBroker controller daemon started. PID: 2821
root@pi2:/mnt/ioBroker/iobroker#

          aber Admin wird nicht gestartet

          root@pi2:/mnt/ioBroker/iobroker# ps -A |grep io
   10 ?        00:00:00 migration/0
   11 ?        00:00:00 migration/1
   15 ?        00:00:00 migration/2
   19 ?        00:00:00 migration/3
   30 ?        00:00:00 bioset
   33 ?        00:00:00 rpciod
   37 ?        00:00:00 nfsiod
   49 ?        00:00:00 DWC Notificatio
 2821 ?        00:00:03 io.js-controlle
root@pi2:/mnt/ioBroker/iobroker#
          1 Reply Last reply Reply Quote 0
          • Bluefox
            Bluefox last edited by

            @derAuge:

            😞

            INSTALL lief durch

            root@pi2:/mnt/ioBroker/iobroker# npm install iobroker.js-controller

> ws@0.5.0 install /mnt/ioBroker/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io/node_m                                           odules/engine.io/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

make: Entering directory '/mnt/ioBroker/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io                                           /node_modules/engine.io/node_modules/ws/build'
  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node: Finished
  COPY Release/bufferutil.node
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/obj.target/validation.node
  SOLINK_MODULE(target) Release/obj.target/validation.node: Finished
  COPY Release/validation.node
make: Leaving directory '/mnt/ioBroker/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io/                                           node_modules/engine.io/node_modules/ws/build'

> ws@0.4.31 install /mnt/ioBroker/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-clien                                           t/node_modules/engine.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

make: Entering directory '/mnt/ioBroker/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io                                           -client/node_modules/engine.io-client/node_modules/ws/build'
  CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node
  SOLINK_MODULE(target) Release/obj.target/bufferutil.node: Finished
  COPY Release/bufferutil.node
  CXX(target) Release/obj.target/validation/src/validation.o
  SOLINK_MODULE(target) Release/obj.target/validation.node
  SOLINK_MODULE(target) Release/obj.target/validation.node: Finished
  COPY Release/validation.node
make: Leaving directory '/mnt/ioBroker/iobroker/node_modules/iobroker.js-controller/node_modules/socket.io-client/node_modules/engine.io-cl           ient/node_modules/ws/build'

> iobroker.js-controller@0.6.3 install /mnt/ioBroker/iobroker/node_modules/iobroker.js-controller
> node lib/setup.js setup first

iobroker.js-controller@0.6.3 node_modules/iobroker.js-controller
├── mime@1.3.4
├── daemonize2@0.4.2
├── node-schedule@0.1.13
├── ncp@2.0.0
├── adm-zip@0.4.7
├── node.extend@1.1.3 (is@2.1.0)
├── yargs@3.7.2 (camelcase@1.0.2, decamelize@1.0.0, window-size@0.1.0, wordwrap@0.0.2)
├── winston@1.0.0 (cycle@1.0.3, stack-trace@0.0.9, eyes@0.1.8, isstream@0.1.2, pkginfo@0.3.0, async@0.9.0, colors@1.0.3)
├── tar.gz@0.1.1 (commander@1.1.1, tar@0.1.20, fstream@0.1.31)
├── request@2.55.0 (caseless@0.9.0, json-stringify-safe@5.0.0, aws-sign2@0.5.0, forever-agent@0.6.1, stringstream@0.0.4, tunnel-agent@0.4.0, oauth-sign@0.6.0, isstream@0.1.2, node-uuid@1.4.3, qs@2.4.1, combined-stream@0.0.7, form-data@0.2.0, mime-types@2.0.10, http-signature@0.10.1, bl@0.9.4, tough-cookie@0.12.1, hawk@2.3.1, har-validator@1.6.1)
├── socket.io@1.3.5 (debug@2.1.0, has-binary-data@0.1.3, socket.io-adapter@0.3.1, socket.io-parser@2.2.4, engine.io@1.5.1)
├── socket.io-client@1.3.5 (to-array@0.1.3, indexof@0.0.1, component-bind@1.0.0, debug@0.7.4, object-component@0.0.3, backo2@1.0.2, component-emitter@1.1.2, has-binary@0.1.6, parseuri@0.0.2, socket.io-parser@2.2.4, engine.io-client@1.5.1)
└── npm@2.7.6
root@pi2:/mnt/ioBroker/iobroker#

            Jedoch ist etwas mit dem symLink

            root@pi2:/mnt/ioBroker/iobroker# iobroker start

module.js:340
    throw err;
          ^
Error: Cannot find module '/mnt/ioBroker/iobroker.Pi2/node_modules/iobroker.js-controller/iobroker.js'
    at Function.Module._resolveFilename (module.js:338:15)
    at Function.Module._load (module.js:280:25)
    at Function.Module.runMain (module.js:497:10)
    at startup (node.js:119:16)
    at node.js:935:3

            so startet der controler

            root@pi2:/mnt/ioBroker/iobroker# ./iobroker start
Starting ioBroker controller daemon...
ioBroker controller daemon started. PID: 2821
root@pi2:/mnt/ioBroker/iobroker#

            aber Admin wird nicht gestartet

            root@pi2:/mnt/ioBroker/iobroker# ps -A |grep io
   10 ?        00:00:00 migration/0
   11 ?        00:00:00 migration/1
   15 ?        00:00:00 migration/2
   19 ?        00:00:00 migration/3
   30 ?        00:00:00 bioset
   33 ?        00:00:00 rpciod
   37 ?        00:00:00 nfsiod
   49 ?        00:00:00 DWC Notificatio
 2821 ?        00:00:03 io.js-controlle
root@pi2:/mnt/ioBroker/iobroker#

```` `

            Bei dir ist je etwas schiff:

            installiert nach: /mnt/ioBroker/iobroker

            Gestartet wird aber aus: /mnt/ioBroker/iobroker.Pi2/

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

              ` > Bei dir ist je etwas schiff:

              installiert nach: /mnt/ioBroker/iobroker

              Gestartet wird aber aus: /mnt/ioBroker/iobroker.Pi2/ `

              Jau …. DANK 😉

              mann sollte doch alle Gedanken dabei haben.

              Nun läuft es 🙂

              dann mach ich mich mal ans Update der Adapter

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

                🙂 🙂 🙂 🙂 🙂
                315_iobrokeradmin0.4.1.png

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

                  und auf 0.4.2

                  iobroker	2015-04-17 22:40:10	info	exit 8
iobroker	2015-04-17 22:40:10	error	at Timer.listOnTimeout [as ontimeout] (timers.js:112:15)
iobroker	2015-04-17 22:40:10	error	at null._onTimeout (/mnt/ioBroker/iobroker.Pi2/node_modules/iobroker.js-controller/lib/setup.js:1530:27)
iobroker	2015-04-17 22:40:10	error	at new ObjectsInMemServer (/mnt/ioBroker/iobroker.Pi2/node_modules/iobroker.js-controller/lib/objectsInMemServer.js:146:7)
iobroker	2015-04-17 22:40:10	error	at /mnt/ioBroker/iobroker.Pi2/node_modules/iobroker.js-controller/lib/objectsInMemServer.js:139:9
iobroker	2015-04-17 22:40:10	error	at _initWebServer (/mnt/ioBroker/iobroker.Pi2/node_modules/iobroker.js-controller/lib/objectsInMemServer.js:958:24)
iobroker	2015-04-17 22:40:10	error	at Server.listen (net.js:1139:5)
iobroker	2015-04-17 22:40:10	error	at listen (net.js:1065:10)
iobroker	2015-04-17 22:40:10	error	at Server._listen2 (net.js:1043:14)
iobroker	2015-04-17 22:40:10	error	at errnoException (net.js:905:11)
iobroker	2015-04-17 22:40:10	error	Error: listen EADDRINUSE
iobroker	2015-04-17 22:40:10	error	^
iobroker	2015-04-17 22:40:10	error	throw er; // Unhandled 'error' event
iobroker	2015-04-17 22:40:10	error	events.js:72
iobroker	2015-04-17 22:39:58	info	upgrade admin

                  kann das auch an meiner Installation liegen?

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

                    @Homoran:

                    Nach reboot ist gut! `
                    reboot tut gut - hier auch. Danke.

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

                      push!

                      @Homoran:

                      Auch bei controller 0.6.3 und neuem admin bleibt es dabei, dass bei einem ./iobroker restart einzelne Adapter nicht beendet werden (erst mal nur node-red und hmm) und nach dem restart doppelt laufen.

                      Dadurch kommt es andauernd zu terminating code 7

                      Nach reboot ist gut!

                      Gesendet von meinem LIFETAB_S785X mit Tapatalk `

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

                        Mit 0.6.4 läuft es perfekt. Keine Fehlermeldungen mehr bei der Installation eines Adapters. Vielen Dank.

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

                        Support us

                        ioBroker
                        Community Adapters
                        Donate

                        413
                        Online

                        31.8k
                        Users

                        80.0k
                        Topics

                        1.3m
                        Posts

                        7
                        50
                        15887
                        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