NEWS

Installation klappt nicht auf RPi2 Raspbian Jessie


  • Starter

    Hallo zusammen!

    Ich versuche ioBroker zu installieren, leider ohne Erfolg. Das Script sagt zwar am Ende, dass es geklappt hätte, allerdings werden folgende Fehler vorher angezeigt:

    ==========================================================================
        Installing ioBroker (3/4)
    ==========================================================================
    
    ../src/diskusage_posix.cpp: In function ‘DiskUsage GetDiskUsage(const char*)’:
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_bsize’ [-Wmiss
         struct statvfs info = {};
                                ^
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_frsize’ [-Wmis
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_blocks’ [-Wmis
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_bfree’ [-Wmiss
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_bavail’ [-Wmis
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_files’ [-Wmiss
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_ffree’ [-Wmiss
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_favail’ [-Wmis
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_fsid’ [-Wmissi
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::__f_unused’ [-Wm
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_flag’ [-Wmissi
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_namemax’ [-Wmi
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::__f_spare’ [-Wmi
    ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:
    ../src/serialport.cpp:41:49: warning: ‘v8::String::Utf8Value::Utf8Value(v8::Local<v8::Value>)’ is de
    p/10.17.0/include/node/v8.h:2891): Use Isolate version [-Wdeprecated-declarations]
       v8::String::Utf8Value path(info[0]->ToString());
                                                     ^
    ../src/serialport.cpp:48:53: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is depreca
    17.0/include/node/v8.h:10046): Use maybe version [-Wdeprecated-declarations]
       v8::Local<v8::Object> options = info[1]->ToObject();
                                                         ^
    ../src/serialport.cpp: In function ‘void EIO_AfterOpen(uv_work_t*)’:
    ../src/serialport.cpp:95:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::V
    ../nan/nan.h:1740) [-Wdeprecated-declarations]
       data->callback.Call(2, argv);
                                  ^
    ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:
    ../src/serialport.cpp:113:53: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprec
    .17.0/include/node/v8.h:10046): Use maybe version [-Wdeprecated-declarations]
       v8::Local<v8::Object> options = info[1]->ToObject();
                                                         ^
    ../src/serialport.cpp: In function ‘void EIO_AfterUpdate(uv_work_t*)’:
    ../src/serialport.cpp:150:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::
    /../nan/nan.h:1740) [-Wdeprecated-declarations]
       data->callback.Call(1, argv);
                                  ^
    ../src/serialport.cpp: In function ‘void EIO_AfterClose(uv_work_t*)’:
    ../src/serialport.cpp:188:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::
    /../nan/nan.h:1740) [-Wdeprecated-declarations]
       data->callback.Call(1, argv);
                                  ^
    ../src/serialport.cpp: In function ‘void EIO_AfterFlush(uv_work_t*)’:
    ../src/serialport.cpp:231:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::
    /../nan/nan.h:1740) [-Wdeprecated-declarations]
       data->callback.Call(1, argv);
                                  ^
    ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:
    ../src/serialport.cpp:250:53: warning: ‘v8::Local<v8::Object> v8::Value::ToObject() const’ is deprec
    .17.0/include/node/v8.h:10046): Use maybe version [-Wdeprecated-declarations]
       v8::Local<v8::Object> options = info[1]->ToObject();
                                                         ^
    ../src/serialport.cpp: In function ‘void EIO_AfterSet(uv_work_t*)’:
    ../src/serialport.cpp:285:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::
    /../nan/nan.h:1740) [-Wdeprecated-declarations]
       data->callback.Call(1, argv);
                                  ^
    ../src/serialport.cpp: In function ‘void EIO_AfterGet(uv_work_t*)’:
    ../src/serialport.cpp:336:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::
    /../nan/nan.h:1740) [-Wdeprecated-declarations]
       data->callback.Call(2, argv);
                                  ^
    ../src/serialport.cpp: In function ‘void EIO_AfterGetBaudRate(uv_work_t*)’:
    ../src/serialport.cpp:383:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::
    /../nan/nan.h:1740) [-Wdeprecated-declarations]
       data->callback.Call(2, argv);
                                  ^
    ../src/serialport.cpp: In function ‘void EIO_AfterDrain(uv_work_t*)’:
    ../src/serialport.cpp:424:30: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::
    /../nan/nan.h:1740) [-Wdeprecated-declarations]
       data->callback.Call(1, argv);
                                  ^
    ../src/poller.cpp: In static member function ‘static void Poller::onData(uv_poll_t*, int, int)’:
    ../src/poller.cpp:69:29: warning: ‘v8::Local<v8::Value> Nan::Callback::Call(int, v8::Local<v8::Value
    an/nan.h:1740) [-Wdeprecated-declarations]
       obj->callback.Call(2, argv);
                                 ^
    events.js:174
          throw er; // Unhandled 'error' event
          ^
    
    Error: listen EADDRINUSE: address already in use 127.0.0.1:9000
        at Server.setupListenHandle [as _listen2] (net.js:1280:14)
        at listenInCluster (net.js:1328:12)
        at doListen (net.js:1461:7)
        at process._tickCallback (internal/process/next_tick.js:63:19)
    Emitted 'error' event at:
        at emitErrorNT (net.js:1307:8)
        at process._tickCallback (internal/process/next_tick.js:63:19)
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! iobroker.js-controller@1.5.14 install: `node iobroker.js setup first`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the iobroker.js-controller@1.5.14 install script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /home/pi/.npm/_logs/2019-10-26T08_53_11_238Z-debug.log
    

    Wenn ich, wie im Fehlersuche Artikel beschrieben, versuche den js-contoller manuell zu starten, passiert folgendes:

    pi@raspberrypi1:/opt/iobroker $ node node_modules/iobroker.js-controller/controller.js --logs
    internal/modules/cjs/loader.js:638
        throw err;
        ^
    
    Error: Cannot find module '/opt/iobroker/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:623:3)
    pi@raspberrypi1:/opt/iobroker $
    

    Führe ich die Installation des js-controller nochmal aus, kommt es zu den obigen Fehlern:

    pi@raspberrypi1:/opt/iobroker $ npm install iobroker.js-controller
    
    > iobroker.js-controller@1.5.14 preinstall /opt/iobroker/node_modules/iobroker.js-controller
    > node lib/preinstallCheck.js
    
    NPM version: 6.12.0
    npm version >= 5: disabling package-lock
    
    > ursa-optional@0.9.10 install /opt/iobroker/node_modules/ursa-optional
    > node rebuild.js
    
    
    > diskusage@1.1.3 install /opt/iobroker/node_modules/diskusage
    > node-gyp rebuild
    
    make: Entering directory '/opt/iobroker/node_modules/diskusage/build'
      CXX(target) Release/obj.target/diskusage/src/main.o
      CXX(target) Release/obj.target/diskusage/src/diskusage_posix.o
    ../src/diskusage_posix.cpp: In function ‘DiskUsage GetDiskUsage(const char*)’:
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_bsize’ [-Wmissing-field-initializers]
         struct statvfs info = {};
                                ^
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_frsize’ [-Wmissing-field-initializers]
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_blocks’ [-Wmissing-field-initializers]
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_bfree’ [-Wmissing-field-initializers]
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_bavail’ [-Wmissing-field-initializers]
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_files’ [-Wmissing-field-initializers]
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_ffree’ [-Wmissing-field-initializers]
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_favail’ [-Wmissing-field-initializers]
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_fsid’ [-Wmissing-field-initializers]
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::__f_unused’ [-Wmissing-field-initializers]
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_flag’ [-Wmissing-field-initializers]
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::f_namemax’ [-Wmissing-field-initializers]
    ../src/diskusage_posix.cpp:10:28: warning: missing initializer for member ‘statvfs::__f_spare’ [-Wmissing-field-initializers]
      SOLINK_MODULE(target) Release/obj.target/diskusage.node
      COPY Release/diskusage.node
    make: Leaving directory '/opt/iobroker/node_modules/diskusage/build'
    
    > iobroker.js-controller@1.5.14 install /opt/iobroker/node_modules/iobroker.js-controller
    > node iobroker.js setup first
    
    events.js:174
          throw er; // Unhandled 'error' event
          ^
    
    Error: listen EADDRINUSE: address already in use 127.0.0.1:9000
        at Server.setupListenHandle [as _listen2] (net.js:1280:14)
        at listenInCluster (net.js:1328:12)
        at doListen (net.js:1461:7)
        at process._tickCallback (internal/process/next_tick.js:63:19)
    Emitted 'error' event at:
        at emitErrorNT (net.js:1307:8)
        at process._tickCallback (internal/process/next_tick.js:63:19)
    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":"linux","arch":"arm"})
    
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! iobroker.js-controller@1.5.14 install: `node iobroker.js setup first`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the iobroker.js-controller@1.5.14 install script.
    npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
    
    npm ERR! A complete log of this run can be found in:
    npm ERR!     /home/iobroker/.npm/_logs/2019-10-26T09_21_04_783Z-debug.log
    pi@raspberrypi1:/opt/iobroker $
    

    Vermutlich ist folgendes dann normal, aber ich hab es einfach mal eingegeben:

    pi@raspberrypi1:/opt/iobroker $ iobroker list instances
    internal/modules/cjs/loader.js:638
        throw err;
        ^
    
    Error: Cannot find module '/opt/iobroker/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:623:3)
    pi@raspberrypi1:/opt/iobroker $
    

    Das /opt/iobroker/log/ Verzeichnis ist übrigens leer.

    Falls jemand einen Tipp hat, würde ich mich freuen 🙂

    Grüße aus Düsseldorf,
    Velo17

    Systemdata Bitte Ausfüllen
    Hardwaresystem: Pi2
    Arbeitsspeicher: 1GB
    Festplattenart: SD-Karte
    Betriebssystem: Raspbian Debian Jessie
    Node-Version: 10.17.0
    Nodejs-Version: 10.17.0
    NPM-Version: 6.12.0
    Installationsart: Skript
    Image genutzt: Nein


  • @Velo17
    Mal ne blöde Frage, warum ein Raspian von 2015 und kein aktuelles Buster?


  • Starter

    @Jan1 So blöd ist die Frage ja nicht 🙂 Ist neben ein paar PiZeros mein einziger schnellerer Pi und darauf laufen einige Dienste. Auch eine andere Heimautomation, die aber für die kommenden Aufgaben nicht mehr geeignet ist. Logitech Mediaserver usw. usf. - ich dachte ich teste ioBroker mal darauf, bevor ich mich entscheide, wie es weitergeht.

    Ob ein Distroupgrade funktioniert, wäre auch eine gute Frage. Könnte ich auch versuchen (ich mache auch Backups, von daher wäre das auch rückgängig zu machen), mit der Frage, was danach alles nicht mehr läuft 😉



  • @Velo17
    Na dann mal ran an Buster 😊


  • Starter

    @Jan1 Ich mach erstmal den Schritt auf Stretch - oder glaubst Du, ein dist upgrade von Jessie auf Buster geht genauso gut / schlecht? Wenn nach Jessie noch alles halbwegs läuft, kann ich ja noch den Versuch zu Buster machen...Ist ja noch früh 😉



  • @Velo17
    Du hast doch bestimmt ein Backup der Karte, dann würde ich eh gleich ne neue nehmen und das das Backup drauf und direkt auf Buster hoch, wenn es funktioniert, dann hast Zeit gespart und wenn nicht, was gelernt😁


Log in to reply
 

Suggested Topics

1.8k
Online

32.1k
Users

38.8k
Topics

525.9k
Posts