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

      @Homoran:

      EDIT:

      nach mehrmaligem reboot ist es jetzt auf einmal (ohne weiteren reboot) wieder ok !???

      Im Vorfeld hatte ich Browsercache mehrfach gelöscht - ohne Änderungen ?!!??? `
      Es liegt an Timeout beim Zugang zu npmjs.org. Vielleicht war der WebServer gestern überlastet. Trotzdem habe ich Timeout erhöht.

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

        Irgend etwas läuft da nicht sauber.

        Habe eben über den admin nach updates suchen wollen. Dabei zeigt das log mir auf einmal an, dass er alle möglichen Adapter killt und auf terminating geht.

        Nach dem wieder hochfahren gibt es wieder den Error 7, dass mindestens zwei Adapter doppelt laufen.

        ! ````
        host-quad-pi 2015-04-16 15:45:23 info Restart adapter system.adapter.hmm.0 because enabled
        host-quad-pi 2015-04-16 15:45:23 error instance system.adapter.hmm.0 terminated with code 7 (Adapter already running)
        host-quad-pi 2015-04-16 15:45:21 info instance system.adapter.hmm.0 started with pid 1554
        host-quad-pi 2015-04-16 15:45:17 info Restart adapter system.adapter.node-red.0 because enabled
        host-quad-pi 2015-04-16 15:45:17 error instance system.adapter.node-red.0 terminated with code 7 (Adapter already running)
        host-quad-pi 2015-04-16 15:45:15 info instance system.adapter.node-red.0 started with pid 1548
        host-quad-pi 2015-04-16 15:44:58 info Update repository "default" under "conf/sources-dist.json"
        host-quad-pi 2015-04-16 15:44:51 info Restart adapter system.adapter.hmm.0 because enabled
        host-quad-pi 2015-04-16 15:44:51 error instance system.adapter.hmm.0 terminated with code 7 (Adapter already running)
        host-quad-pi 2015-04-16 15:44:49 info instance system.adapter.hmm.0 started with pid 1510
        host-quad-pi 2015-04-16 15:44:45 info Restart adapter system.adapter.node-red.0 because enabled
        host-quad-pi 2015-04-16 15:44:45 error instance system.adapter.node-red.0 terminated with code 7 (Adapter already running)
        host-quad-pi 2015-04-16 15:44:41 info instance system.adapter.node-red.0 started with pid 1493
        javascript-0 2015-04-16 15:44:40 info received all states
        javascript-0 2015-04-16 15:44:40 info received all objects
        javascript-0 2015-04-16 15:44:37 info requesting all objects
        javascript-0 2015-04-16 15:44:37 info requesting all states
        javascript-0 2015-04-16 15:44:37 info starting. Version 0.3.0 in /opt/iobroker/node_modules/iobroker.javascript
        host-quad-pi 2015-04-16 15:44:35 info instance system.adapter.yr.0 terminated with code 0 (OK)
        host-quad-pi 2015-04-16 15:44:34 info instance system.adapter.javascript.0 started with pid 1485
        email-0 2015-04-16 15:44:31 info starting. Version 0.1.0 in /opt/iobroker/node_modules/iobroker.email
        yr-0 2015-04-16 15:44:30 info got weather data from yr.no
        host-quad-pi 2015-04-16 15:44:29 info instance system.adapter.email.0 started with pid 1470
        yr-0 2015-04-16 15:44:28 info starting. Version 0.1.5 in /opt/iobroker/node_modules/iobroker.yr
        host-quad-pi 2015-04-16 15:44:26 info instance system.adapter.ical.0 terminated with code 0 (OK)
        host-quad-pi 2015-04-16 15:44:25 info instance system.adapter.yr.0 started with pid 1464
        host-quad-pi 2015-04-16 15:44:25 info instance scheduled system.adapter.yr.0 0 * * * *
        ical-0 2015-04-16 15:44:19 info processing URL: calendar1 http://192.168.2.225:5000/fbsharing/IQExBXbr
        host-quad-pi 2015-04-16 15:44:19 info Restart adapter system.adapter.hmm.0 because enabled
        host-quad-pi 2015-04-16 15:44:19 error instance system.adapter.hmm.0 terminated with code 7 (Adapter already running)
        host-quad-pi 2015-04-16 15:44:17 info instance system.adapter.hmm.0 started with pid 1449
        ical-0 2015-04-16 15:44:17 info starting. Version 0.1.0 in /opt/iobroker/node_modules/iobroker.ical
        host-quad-pi 2015-04-16 15:44:14 info instance system.adapter.ical.0 started with pid 1443
        host-quad-pi 2015-04-16 15:44:13 info instance scheduled system.adapter.ical.0 0,30 * * * *
        host-quad-pi 2015-04-16 15:44:11 info Restart adapter system.adapter.node-red.0 because enabled
        host-quad-pi 2015-04-16 15:44:11 error instance system.adapter.node-red.0 terminated with code 7 (Adapter already running)
        host-quad-pi 2015-04-16 15:44:10 info instance system.adapter.dwd.0 terminated with code 0 (OK)
        host-quad-pi 2015-04-16 15:44:10 info instance system.adapter.node-red.0 started with pid 1428
        ping-0 2015-04-16 15:44:07 info starting. Version 0.1.4 in /opt/iobroker/node_modules/iobroker.ping
        host-quad-pi 2015-04-16 15:44:05 info instance system.adapter.ping.0 started with pid 1418
        dwd-0 2015-04-16 15:44:04 info setting states
        dwd-0 2015-04-16 15:44:04 info starting. Version 0.1.7 in /opt/iobroker/node_modules/iobroker.dwd
        web-0 2015-04-16 15:44:02 info http server listening on port 8082
        web-0 2015-04-16 15:44:02 info socket.io server listening on port 8082
        host-quad-pi 2015-04-16 15:44:01 info instance system.adapter.dwd.0 started with pid 1403
        host-quad-pi 2015-04-16 15:44:01 info instance scheduled system.adapter.dwd.0 5,20,35,50 * * * *
        web-0 2015-04-16 15:44:01 info starting. Version 0.2.6 in /opt/iobroker/node_modules/iobroker.web
        hm-rega-0 2015-04-16 15:43:57 info got state values
        hm-rega-0 2015-04-16 15:43:56 info request state values
        hm-rega-0 2015-04-16 15:43:56 info deleted 0 variables
        hm-rega-0 2015-04-16 15:43:56 info added/updated 64 variables
        hm-rega-0 2015-04-16 15:43:56 info got 64 variables
        hm-rega-0 2015-04-16 15:43:55 info deleted 0 programs
        hm-rega-0 2015-04-16 15:43:55 info added/updated 56 programs
        hm-rega-0 2015-04-16 15:43:54 info got 56 programs
        host-quad-pi 2015-04-16 15:43:53 info instance system.adapter.web.0 started with pid 1396
        hm-rega-0 2015-04-16 15:43:53 info added/updated rooms to enum.rooms
        hm-rega-0 2015-04-16 15:43:53 info added/updated functions to enum.functions
        hm-rega-0 2015-04-16 15:43:53 info added/updated 6 favorites to enum.favorites
        hm-rega-0 2015-04-16 15:43:53 info time difference local-ccu 0s
        hm-rega-0 2015-04-16 15:43:53 info ReGaHSS 192.168.2.186 up
        history-0 2015-04-16 15:43:53 info enabled logging of ping.0.quad-pi.192_168_2_120
        history-0 2015-04-16 15:43:53 info enabled logging of ping.0.quad-pi.192_168_2_7
        history-0 2015-04-16 15:43:53 info enabled logging of ping.0.quad-pi.192_168_2_142
        history-0 2015-04-16 15:43:53 info enabled logging of ping.0.quad-pi.192_168_2_75
        history-0 2015-04-16 15:43:53 info enabled logging of dwd.0.warning.severity
        history-0 2015-04-16 15:43:53 info enabled logging of hm-rpc.0.LEQ0081020.1.TEMPERATURE
        history-0 2015-04-16 15:43:53 info enabled logging of hm-rpc.0.LEQ0081020.1.HUMIDITY
        history-0 2015-04-16 15:43:53 info enabled logging of hm-rpc.0.KEQ0963067.1.TEMPERATURE
        history-0 2015-04-16 15:43:53 info enabled logging of hm-rpc.0.JEQ0459186.1.MOTION
        history-0 2015-04-16 15:43:53 info enabled logging of hm-rpc.0.JEQ0267518.1.TEMPERATURE
        history-0 2015-04-16 15:43:53 info enabled logging of hm-rpc.0.JEQ0267518.1.HUMIDITY
        history-0 2015-04-16 15:43:53 info enabled logging of hm-rpc.0.JEQ0140901.1.TEMPERATURE
        history-0 2015-04-16 15:43:53 info enabled logging of hm-rpc.0.JEQ0140901.1.HUMIDITY
        history-0 2015-04-16 15:43:53 info enabled logging of system.host.quad-pi.load
        history-0 2015-04-16 15:43:53 info enabled logging of system.host.quad-pi.mem
        hm-rega-0 2015-04-16 15:43:51 info subscribe hm-rpc.0.BidCoS-RF:50.PRESS_SHORT
        hm-rega-0 2015-04-16 15:43:51 info starting. Version 0.2.1 in /opt/iobroker/node_modules/iobroker.hm-rega
        history-0 2015-04-16 15:43:53 info starting. Version 0.1.3 in /opt/iobroker/node_modules/iobroker.history
        hm-rpc-0 2015-04-16 15:43:51 info xmlrpc -> 327 devices
        hm-rpc-0 2015-04-16 15:43:51 info xmlrpc <- listDevices ["hm-rpc.0"]
        hm-rpc-0 2015-04-16 15:43:51 info xmlrpc <- system.listMethods ["hm-rpc.0"]
        hm-rpc-0 2015-04-16 15:43:51 info xmlrpc -> 192.168.2.186:2001 init ["http://192.168.2.190:2001","hm-rpc.0"]
        hm-rpc-0 2015-04-16 15:43:51 info xmlrpc server is trying to listen on 192.168.2.190:2001
        hm-rpc-0 2015-04-16 15:43:50 info starting. Version 0.4.0 in /opt/iobroker/node_modules/iobroker.hm-rpc
        host-quad-pi 2015-04-16 15:43:50 info instance system.adapter.history.0 started with pid 1377
        hm-rpc-0 2015-04-16 15:43:48 error no connection to objects DB
        host-quad-pi 2015-04-16 15:43:46 info Update repository "default" under "conf/sources-dist.json"
        host-quad-pi 2015-04-16 15:43:46 info instance system.adapter.hm-rega.0 started with pid 1371
        admin-0 2015-04-16 15:43:45 info received all states
        admin-0 2015-04-16 15:43:45 info received all objects
        admin-0 2015-04-16 15:43:42 info Use link "http://localhost:8081" to configure.
        admin-0 2015-04-16 15:43:42 info http server listening on port 8081
        admin-0 2015-04-16 15:43:42 info requesting all objects
        admin-0 2015-04-16 15:43:42 info requesting all states
        admin-0 2015-04-16 15:43:42 info starting. Version 0.3.27 in /opt/iobroker/node_modules/iobroker.admin
        hmm-0 2015-04-16 15:43:42 warn Reconnection to DB.
        hmm-0 2015-04-16 15:43:41 warn Reconnection to DB.
        host-quad-pi 2015-04-16 15:43:41 info instance system.adapter.hm-rpc.0 started with pid 1356
        host-quad-pi 2015-04-16 15:43:37 info instance system.adapter.admin.0 started with pid 1354
        host-quad-pi 2015-04-16 15:43:37 info starting 15 instances
        host-quad-pi 2015-04-16 15:43:37 info 18 instances found
        host-quad-pi 2015-04-16 15:43:37 info InMemoryDB connected
        node-red-0 2015-04-16 15:43:38 warn Reconnection to DB.
        inMem-objects 2015-04-16 15:43:37 info listening on port 9001
        inMem-states 2015-04-16 15:43:37 info listening on port 9000
        host-quad-pi 2015-04-16 15:43:37 info ip addresses: 192.168.2.190
        node-red-0 2015-04-16 15:43:38 warn Reconnection to DB.
        host-quad-pi 2015-04-16 15:43:37 info hostname: quad-pi
        host-quad-pi 2015-04-16 15:43:37 info Copyright (c) 2014-2015 bluefox, hobbyquaker
        host-quad-pi 2015-04-16 15:43:37 info ioBroker.js-controller version 0.6.1 js-controller starting
        hmm-0 2015-04-16 15:43:36 info hmm exited with 0
        node-red-0 2015-04-16 15:43:35 info node-red exited with 0
        email-0 2015-04-16 15:43:35 info terminating with timeout
        ping-0 2015-04-16 15:43:35 info terminating with timeout
        javascript-0 2015-04-16 15:43:34 info terminating
        admin-0 2015-04-16 15:43:34 info terminating
        web-0 2015-04-16 15:43:34 info terminating
        hm-rega-0 2015-04-16 15:43:34 info terminating
        history-0 2015-04-16 15:43:34 info terminating
        TypeError: 2015-04-16 15:43:33 error at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)
        TypeError: 2015-04-16 15:43:33 error at null._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/lib/statesInMemServer.js:464:25)
        TypeError: 2015-04-16 15:43:33 error at States.change (/opt/iobroker/node_modules/iobroker.js-controller/controller.js:142:48)
        TypeError: 2015-04-16 15:43:33 error Cannot read property 'time' of undefined
        hm-rpc-0 2015-04-16 15:43:34 info terminating
        hmm-0 2015-04-16 15:43:33 info kill hmm task
        node-red-0 2015-04-16 15:43:33 info kill node-red task
        web-0 2015-04-16 15:43:33 info terminated http server on port 8082
        web-0 2015-04-16 15:43:33 info terminating http server on port 8082
        hm-rpc-0 2015-04-16 15:43:33 info xmlrpc -> 192.168.2.186:2001 init ["http://192.168.2.190:2001",""]
        admin-0 2015-04-16 15:43:33 info terminating http server on port 8081
        uncaught 2015-04-16 15:43:33 error exception: Cannot read property 'time' of undefined

        
Daraufhin habe ich über den Reiter hosts einen restart des RPi2 ausgelöst.

jetzt beschwert er sich beim runterfahren, dass diverse Adapetr immer noch laufen.

entsprechend taucht da auch der error code 7 wieder auf

>! ````
quad-pi	2015-04-16 15:45:48	info	host.quad-pi Restart adapter system.adapter.admin.0 because enabled
quad-pi	2015-04-16 15:45:48	error	host.quad-pi instance system.adapter.admin.0 terminated with code 7 (Adapter already running)
quad-pi	2015-04-16 15:45:48	info	host.quad-pi Restart adapter system.adapter.admin.0 because enabled
quad-pi	2015-04-16 15:45:48	error	host.quad-pi instance system.adapter.admin.0 terminated with code 7 (Adapter already running)
history.0	2015-04-16 15:45:43	warn	history.0 Reconnection to DB.
web.0	2015-04-16 15:45:45	warn	web.0 Reconnection to DB.
javascript.0	2015-04-16 15:45:45	warn	javascript.0 Reconnection to DB.
javascript.0	2015-04-16 15:45:45	warn	javascript.0 Reconnection to DB.
history.0	2015-04-16 15:45:42	warn	history.0 Reconnection to DB.
web.0	2015-04-16 15:45:45	warn	web.0 Reconnection to DB.
hm-rpc.0	2015-04-16 15:45:47	warn	hm-rpc.0 Reconnection to DB.
hm-rega.0	2015-04-16 15:45:43	warn	hm-rega.0 Reconnection to DB.
ping.0	2015-04-16 15:45:47	warn	ping.0 Reconnection to DB.
hm-rega.0	2015-04-16 15:45:43	warn	hm-rega.0 Reconnection to DB.
email.0	2015-04-16 15:45:47	warn	email.0 Reconnection to DB.
email.0	2015-04-16 15:45:47	warn	email.0 Reconnection to DB.
hm-rpc.0	2015-04-16 15:45:47	warn	hm-rpc.0 Reconnection to DB.
ping.0	2015-04-16 15:45:47	warn	ping.0 Reconnection to DB.
quad-pi	2015-04-16 15:45:47	info	host.quad-pi instance system.adapter.hm-rpc.0 started with pid 1599
quad-pi	2015-04-16 15:45:47	info	host.quad-pi instance system.adapter.hm-rpc.0 started with pid 1599
admin.0	2015-04-16 15:45:43	warn	admin.0 Reconnection to DB.
admin.0	2015-04-16 15:45:43	warn	admin.0 Reconnection to DB.
admin.0	2015-04-16 15:45:43	warn	admin.0 Reconnection to DB.
admin.0	2015-04-16 15:45:43	warn	admin.0 Reconnection to DB.
quad-pi	2015-04-16 15:45:37	info	Adapter javascript still running
quad-pi	2015-04-16 15:45:37	info	Adapter email still running
quad-pi	2015-04-16 15:45:37	info	Adapter ping still running
quad-pi	2015-04-16 15:45:37	info	Adapter web still running
quad-pi	2015-04-16 15:45:37	info	Adapter history still running
quad-pi	2015-04-16 15:45:37	info	Adapter hm-rega still running
quad-pi	2015-04-16 15:45:37	info	Adapter hm-rpc still running
quad-pi	2015-04-16 15:45:37	info	Adapter admin still running
quad-pi	2015-04-16 15:45:37	info	host.quad-pi force terminated after 10s
quad-pi	2015-04-16 15:45:37	info	host.quad-pi received SIGTERM
quad-pi	2015-04-16 15:45:37	info	host.quad-pi received SIGTERM
quad-pi	2015-04-16 15:45:36	info	host.quad-pi received SIGTERM
quad-pi	2015-04-16 15:45:36	info	host.quad-pi received SIGTERM
quad-pi	2015-04-16 15:45:35	info	host.quad-pi received SIGTERM
quad-pi	2015-04-16 15:45:35	info	host.quad-pi received SIGTERM
quad-pi	2015-04-16 15:45:34	info	host.quad-pi received SIGTERM
quad-pi	2015-04-16 15:45:34	info	host.quad-pi received SIGTERM
quad-pi	2015-04-16 15:45:33	info	host.quad-pi received SIGTERM
quad-pi	2015-04-16 15:45:33	info	host.quad-pi received SIGTERM
host-quad-pi	2015-04-16 15:45:32	info	received SIGTERM
host-quad-pi	2015-04-16 15:45:31	info	received SIGTERM
host-quad-pi	2015-04-16 15:45:30	info	received SIGTERM
host-quad-pi	2015-04-16 15:45:29	info	received SIGTERM
host-quad-pi	2015-04-16 15:45:28	info	received SIGTERM
host-quad-pi	2015-04-16 15:45:27	info	received SIGTERM
iobroker	2015-04-16 15:45:26	info	exit 0
iobroker	2015-04-16 15:45:26	info	Starting node restart.js
iobroker	2015-04-16 15:45:26	info	_restart

        ich wollte eigentlich nicht wieder rebooten. Dann läuft er meistens stabil.

        in den rechten Spalten wechselt es dauern von rot nach grün 😞
        144_iobroker_instances_down.jpg
        jetzt ist doch reboot angesagt 😞

        Gruß

        Rainer

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

          Es hat sich irgendwas verhackt. Da hilft nur reboot.

          Es gibt 0.6.3, wo update wieder funktionieren soll.

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

            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.

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

              @Bluefox:

              Es hat sich irgendwas verhackt. Da hilft nur reboot.

              Es gibt 0.6.3, wo update wieder funktionieren soll. `
              315_update_controller.png

              Was ist nun zu tun?

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

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
root@pi2:/mnt/ioBroker/iobroker#
              1 Reply Last reply Reply Quote 0
              • Bluefox
                Bluefox last edited by 

                cd /mnt/ioBroker/iobroker.Pi2/
npm install iobroker.js-controller
./iobroker start
                1 Reply Last reply Reply Quote 0
                • 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

                                    680
                                    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