Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Neue Installationsroutine (für Linux)

    NEWS

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    • Minor js-controller 7.0.7 Update in latest repo

    Neue Installationsroutine (für Linux)

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @xadox last edited by Thomas Braun

      @xadox
      Container... Ich mag die Dinger nicht. Jedenfalls nicht für den Einsatz als Ersatz für eine VM. Dafür sind die eigentlich nicht vorgesehen.

      Davon abgesehen sind die Meldungen während der Installation aber grundsätzlich wohl in Ordnung.

      Am Rande: Bitte Konsolentexte auch als TEXT (in CodeTags) ins Forum kopieren. Screenshots von Text sind komplett sinnfrei.

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

        Ich habe nun einen neuen User erzeugt "service" und habe diesen den sudoern hinzugefügt.
        Angemeldet dann über SSH mit dem neu erzeugten User "service". Dennoch erhalte ich:

        ==========================================================================
            Installing ioBroker (3/4)
        ==========================================================================
        
        In file included from ../../nan/nan.h:56,
                         from ../src/main.cpp:3:
        /home/service/.cache/node-gyp/12.20.0/include/node/node.h:737:7: warning: cast between incompatible function ty                                                                    pes from 'void (*)(v8::Local<v8::Object>)' to 'node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>,                                                                     v8::Local<v8::Value>, void*)'} [-Wcast-function-type]
          737 |       (node::addon_register_func) (regfunc),                          \
              |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        /home/service/.cache/node-gyp/12.20.0/include/node/node.h:771:3: note: in expansion of macro 'NODE_MODULE_X'
          771 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
              |   ^~~~~~~~~~~~~
        ../src/main.cpp:42:1: note: in expansion of macro 'NODE_MODULE'
           42 | NODE_MODULE(diskusage, Init)
              | ^~~~~~~~~~~
        In file included from ../../nan/nan.h:56,
                         from ../src/unix_dgram.cc:5:
        /home/service/.cache/node-gyp/12.20.0/include/node/node.h:737:7: warning: cast between incompatible function ty                                                                    pes from 'void (*)(v8::Local<v8::Object>)' to 'node::addon_register_func' {aka 'void (*)(v8::Local<v8::Object>,                                                                     v8::Local<v8::Value>, void*)'} [-Wcast-function-type]
          737 |       (node::addon_register_func) (regfunc),                          \
              |       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        /home/service/.cache/node-gyp/12.20.0/include/node/node.h:771:3: note: in expansion of macro 'NODE_MODULE_X'
          771 |   NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
              |   ^~~~~~~~~~~~~
        ../src/unix_dgram.cc:404:1: note: in expansion of macro 'NODE_MODULE'
          404 | NODE_MODULE(unix_dgram, Initialize)
              | ^~~~~~~~~~~
        
        ATTENTION: Error reporting via Sentry will be activated on next start of ioBroker
        
        
        Thomas Braun 1 Reply Last reply Reply Quote 0
        • Thomas Braun
          Thomas Braun Most Active @xadox last edited by

          @xadox Alles prima. Was soll da nicht passen?

          xadox 1 Reply Last reply Reply Quote 0
          • xadox
            xadox @Thomas Braun last edited by xadox

            @Thomas-Braun Das war ja meine Frage. ioBroker ist über Webinterface erreichbar.
            Ich konnte nur nicht beurteilen ob die ausgegebenen Warnungen wärend der Installation Folgen haben.

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

              Ich habe das Setup nun auch auf einem PI3 mit Raspbian probiert und hier kommt zu noch mehr Warnungen bzw. Hinweisen:

              Directory /opt/iobroker created
              
              ==========================================================================
                  Installing ioBroker (3/4)
              ==========================================================================
              
              In file included from ../../nan/nan.h:56,
                               from ../src/main.cpp:3:
              /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:737:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                     (node::addon_register_func) (regfunc),                          \
                                                         ^
              /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:771:3: note: in expansion of macro ‘NODE_MODULE_X’
                 NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                 ^~~~~~~~~~~~~
              ../src/main.cpp:42:1: note: in expansion of macro ‘NODE_MODULE’
               NODE_MODULE(diskusage, Init)
               ^~~~~~~~~~~
              In file included from ../../nan/nan.h:56,
                               from ../src/unix_dgram.cc:5:
              /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:737:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                     (node::addon_register_func) (regfunc),                          \
                                                         ^
              /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:771:3: note: in expansion of macro ‘NODE_MODULE_X’
                 NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                 ^~~~~~~~~~~~~
              ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
               NODE_MODULE(unix_dgram, Initialize)
               ^~~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Open(Nan::NAN_METHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:78:69: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                 uv_queue_work(uv_default_loop(), req, EIO_Open, (uv_after_work_cb)EIO_AfterOpen);
                                                                                   ^~~~~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Update(Nan::NAN_METHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:135:71: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                 uv_queue_work(uv_default_loop(), req, EIO_Update, (uv_after_work_cb)EIO_AfterUpdate);
                                                                                     ^~~~~~~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Close(Nan::NAN_METHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:175:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                 uv_queue_work(uv_default_loop(), req, EIO_Close, (uv_after_work_cb)EIO_AfterClose);
                                                                                    ^~~~~~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Flush(Nan::NAN_METHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:215:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                 uv_queue_work(uv_default_loop(), req, EIO_Flush, (uv_after_work_cb)EIO_AfterFlush);
                                                                                    ^~~~~~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Set(Nan::NAN_METHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:270:68: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                 uv_queue_work(uv_default_loop(), req, EIO_Set, (uv_after_work_cb)EIO_AfterSet);
                                                                                  ^~~~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Get(Nan::NAN_METHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:314:68: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                 uv_queue_work(uv_default_loop(), req, EIO_Get, (uv_after_work_cb)EIO_AfterGet);
                                                                                  ^~~~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE GetBaudRate(Nan::NAN_METHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:363:76: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                 uv_queue_work(uv_default_loop(), req, EIO_GetBaudRate, (uv_after_work_cb)EIO_AfterGetBaudRate);
                                                                                          ^~~~~~~~~~~~~~~~~~~~
              ../src/serialport.cpp: In function ‘Nan::NAN_METHOD_RETURN_TYPE Drain(Nan::NAN_METHOD_ARGS_TYPE)’:
              ../src/serialport.cpp:409:70: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type]
                 uv_queue_work(uv_default_loop(), req, EIO_Drain, (uv_after_work_cb)EIO_AfterDrain);
                                                                                    ^~~~~~~~~~~~~~
              ../src/serialport.cpp: At global scope:
              ../src/serialport.cpp:430:28: warning: unnecessary parentheses in declaration of ‘ToParityEnum’ [-Wparentheses]
               SerialPortParity NAN_INLINE(ToParityEnum(const v8::Local<v8::String>& v8str)) {
                                          ^
              ../src/serialport.cpp:449:30: warning: unnecessary parentheses in declaration of ‘ToStopBitEnum’ [-Wparentheses]
               SerialPortStopBits NAN_INLINE(ToStopBitEnum(double stopBits)) {
                                            ^
              In file included from ../../../nan/nan.h:56,
                               from ../src/./serialport.h:6,
                               from ../src/serialport.cpp:1:
              /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:737:43: warning: cast between incompatible function types from ‘void (*)(Nan::ADDON_REGISTER_FUNCTION_ARGS_TYPE)’ {aka ‘void (*)(v8::Local<v8::Object>)’} to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                     (node::addon_register_func) (regfunc),                          \
                                                         ^
              /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:771:3: note: in expansion of macro ‘NODE_MODULE_X’
                 NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                 ^~~~~~~~~~~~~
              ../src/serialport.cpp:483:1: note: in expansion of macro ‘NODE_MODULE’
               NODE_MODULE(serialport, init);
               ^~~~~~~~~~~
              ../src/serialport_unix.cpp: In function ‘int setup(int, OpenBaton*)’:
              ../src/serialport_unix.cpp:176:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1005 [-Wformat-truncation=]
                   snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path);
                                                                          ^~~~~~~~~~~~~~~~~~~~~~~~~
              ../src/serialport_unix.cpp:176:13: note: ‘snprintf’ output 20 or more bytes (assuming 1043) into a destination of size 1024
                   snprintf(data->errorString, sizeof(data->errorString), "Error %s Cannot open %s", strerror(errno), data->path);
                   ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              ../src/serialport_unix.cpp: In function ‘void EIO_Open(uv_work_t*)’:
              ../src/serialport_unix.cpp:86:60: warning: ‘%s’ directive output may be truncated writing up to 1023 bytes into a region of size 1003 [-Wformat-truncation=]
                   snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path);
                                                                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~
              ../src/serialport_unix.cpp:86:13: note: ‘snprintf’ output 22 or more bytes (assuming 1045) into a destination of size 1024
                   snprintf(data->errorString, sizeof(data->errorString), "Error: %s, cannot open %s", strerror(errno), data->path);
                   ~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
              
              ATTENTION: Error reporting via Sentry will be activated on next start of ioBroker
              
              
              
              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @xadox last edited by

                @xadox Alles nix besonderes.

                1 Reply Last reply Reply Quote 0
                • M
                  Mercator last edited by

                  ich habe eine neue VM unter Proxmox mit Debian 10.6 mit dem User pi erstellt, mit welchem ich analog zu Mic´s Anleitung dann nodejs v12.20 installiert habe.

                  Installation verlief auch ohne irgendeine Fehlermeldung, weshalb ich bis hier von einem "sauberen" System ausgehe.

                  pi@ioBroker3:~$ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs && who -r && whoami
                  /usr/bin/nodejs
                  v12.20.0
                  /usr/bin/node
                  v12.20.0
                  /usr/bin/npm
                  6.14.10
                  nodejs:
                    Installiert:           12.20.0-1nodesource1
                    Installationskandidat: 12.20.0-1nodesource1
                    Versionstabelle:
                   *** 12.20.0-1nodesource1 500
                          500 https://deb.nodesource.com/node_12.x buster/main amd64 Packages
                          100 /var/lib/dpkg/status
                       10.21.0~dfsg-1~deb10u1 500
                          500 http://deb.debian.org/debian buster/main amd64 Packages
                          500 http://security.debian.org/debian-security buster/updates/main amd64 Packages
                           Runlevel 5   2020-12-20 13:50
                  pi
                  

                  Trotzdem bekomme ich beim anschließenden Installieren von ioBroker folgenden Fehler:

                  ==========================================================================
                      Installing ioBroker (3/4)
                  ==========================================================================
                  
                  In file included from ../../nan/nan.h:56,
                                   from ../src/main.cpp:3:
                  /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:737:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                         (node::addon_register_func) (regfunc),                          \
                                                             ^
                  /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:771:3: note: in expansion of macro ‘NODE_MODULE_X’
                     NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                     ^~~~~~~~~~~~~
                  ../src/main.cpp:42:1: note: in expansion of macro ‘NODE_MODULE’
                   NODE_MODULE(diskusage, Init)
                   ^~~~~~~~~~~
                  In file included from ../../nan/nan.h:56,
                                   from ../src/unix_dgram.cc:5:
                  /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:737:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon_register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                         (node::addon_register_func) (regfunc),                          \
                                                             ^
                  /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:771:3: note: in expansion of macro ‘NODE_MODULE_X’
                     NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                     ^~~~~~~~~~~~~
                  ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
                   NODE_MODULE(unix_dgram, Initialize)
                   ^~~~~~~~~~~
                  
                  ATTENTION: Error reporting via Sentry will be activated on next start of ioBroker
                  
                  ioBroker wants to make sure to deliver the most stable smart home system.
                  
                  

                  Ja, es heißt dann zwar ioBroker was installed successfully und ich kann die Installation per Browser erreichen, aber beim restore mit Backitup kommen zig node-gyp und authenticate_pam.cc Fehler, wie auf meinem Produktivsystem. (weshalb ich es umziehen möchte).

                  Beispielsweise:

                  Update vis from @1.3.4 to @1.3.6
                  NPM version: 6.14.8
                  npm install iobroker.vis@1.3.6 --loglevel error --prefix "/opt/iobroker" (System call)
                  ../authenticate_pam.cc: In function ‘void after_doing_auth(uv_work_t*, int)’:../authenticate_pam.cc:107:87: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);                                                                                       ^In file included from ../authenticate_pam.cc:23:0:../../nan/nan.h:1026:46: note: declared here   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(                                              ^~~~~~~~~~~~
                  ../authenticate_pam.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE Authenticate(Nan::NAN_METHOD_ARGS_TYPE)’:../authenticate_pam.cc:147:83: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]   Local<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());                                                                                   ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/v8-internal.h:14:0,                 from /home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:27,                 from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:3553:51: note: declared here   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));                                                   ^/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’   declarator __attribute__((deprecated(message)))   ^~~~~~~~~~
                  ../authenticate_pam.cc:150:69: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], long unsigned int)’    serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);                                                                     ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67:0,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note: candidate: int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,       ^~~~~~~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’../authenticate_pam.cc:152:69: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]   res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());                                                                     ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/v8-internal.h:14:0,                 from /home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:27,                 from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:3553:51: note: declared here   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));                                                   ^/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’   declarator __attribute__((deprecated(message)))   ^~~~~~~~~~../authenticate_pam.cc:155:66: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], long unsigned int)’    remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);                                                                  ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67:0,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note: candidate: int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,       ^~~~~~~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                  ../authenticate_pam.cc:160:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], long unsigned int)’  username->WriteUtf8(m->username, sizeof(m->username) - 1);                                                          ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67:0,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note: candidate: int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,       ^~~~~~~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’../authenticate_pam.cc:161:58: error: no matching function for call to ‘v8::String::WriteUtf8(char [128], long unsigned int)’  password->WriteUtf8(m->password, sizeof(m->password) - 1);                                                          ^In file included from /home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:67:0,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note: candidate: int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,       ^~~~~~~~~/home/iobroker/.cache/node-gyp/12.18.3/include/node/v8.h:2878:7: note:   no known conversion for argument 1 from ‘char [128]’ to ‘v8::Isolate*’
                  ../authenticate_pam.cc: At global scope:../authenticate_pam.cc:170:11: error: variable or field ‘init’ declared void void init(Handle<Object> exports) {           ^~~~~~../authenticate_pam.cc:170:11: error: ‘Handle’ was not declared in this scope../authenticate_pam.cc:170:24: error: expected primary-expression before ‘>’ token void init(Handle<Object> exports) {                        ^../authenticate_pam.cc:170:26: error: ‘exports’ was not declared in this scope void init(Handle<Object> exports) {                          ^~~~~~~In file included from ../../nan/nan.h:56:0,                 from ../authenticate_pam.cc:23:../authenticate_pam.cc:175:31: error: ‘init’ was not declared in this scope NODE_MODULE(authenticate_pam, init);                               ^/home/iobroker/.cache/node-gyp/12.18.3/include/node/node.h:608:36: note: in definition of macro ‘NODE_MODULE_X’       (node::addon_register_func) (regfunc),                          \                                    ^~~~~~~../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’ NODE_MODULE(authenticate_pam, init); ^~~~~~~~~~~
                  make: *** [Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
                  gyp
                   ERR! 
                  build error 
                  gyp ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)gyp
                   ERR! stack     at ChildProcess.emit (events.js:315:20)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
                  gyp ERR! System Linux 4.9.0-8-amd64gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                  gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pamgyp ERR! node -v v12.18.3gyp ERR! node-gyp -v v5.1.0
                  gyp ERR! not ok 
                  upload [3] vis.admin /opt/iobroker/node_modules/iobroker.vis/admin/words.js words.js application/javascript
                  Adapter "system.adapter.vis.0" restarted.
                  

                  Wie könnte ich eine Installation ohne Fehlermeldungen hinbekommen?

                  Thomas Braun 2 Replies Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @Mercator last edited by Thomas Braun

                    @Mercator
                    In der Fehlermeldung steht was von node -v v12.18.3 drin. Oben schreibst du 12.20.0

                    Da passt was nicht.

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

                      @Thomas-Braun
                      @Mercator

                      Ich weiß nicht, ob das wirklich "echte" Fehler sind, oder ob da nur vom Installer eine Meldung vergessen wird zu unterdrücken, die keine wirkliche Relevanz hat.

                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @Homoran last edited by

                        @Homoran

                        build error 
                        gyp ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)gyp
                         ERR! stack     at ChildProcess.emit (events.js:315:20)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
                        gyp ERR! System Linux 4.9.0-8-amd64gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
                        gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pamgyp ERR! node -v v12.18.3gyp ERR! node-gyp -v v5.1.0
                        gyp ERR! not ok
                        

                        Sind definitiv Fehler beim build.
                        Die Meldungen beim der Installation sind harmlos, stimmt.

                        1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @Mercator last edited by

                          @Mercator sagte in Neue Installationsroutine (für Linux):

                          beim restore mit Backitup kommen zig node-gyp und authenticate_pam.cc Fehler, wie auf meinem Produktivsystem. (weshalb ich es umziehen möchte).

                          Vermutlich ist da der Wurm schon im Alt-System, den backupst du dann natürlich.

                          M 1 Reply Last reply Reply Quote 0
                          • M
                            Mercator @Thomas Braun last edited by

                            @Thomas-Braun Ja, ich denke auch, dass im Altsystem etwas vermurkst ist, daher plane ich den Umzug auf ein Neues. Das sehe ich im Moment auch erstmal als ein getrenntes Problem an.
                            Aber wie gesagt, die Fehlermeldung vom Install-Script kommt ja auf einem ganz frischen Debian und ist reproduzierbar?!?

                            Ich habe zwischenzeitlich 5 VM´s erstellt (straight forward, mal mit mal ohne GUI oder Web Server, immer plus SSH-Server, auch wieder nicht mit user root, sondern mit sudo pi gearbeitet, 1 x debian-10.7.0-amd64-netinst.iso neu runtergeladen und neu installiert) und bekomme bei "Installing ioBroker (3/4)" immer diese node-gyp Fehler.

                            Würde mich normalerweise vermutlich auch nicht weiter stören, nur hat mein Produktivsystem halt genau ein Problem mit node-gyp, weshalb ich hier schon gerne ein "sauberes" neues System hätte, um den Fehler im Alt-System auszumerzen 😉

                            Lieben Dank aber für eure Mühe und Antwort!

                            Beispiel:
                            Letzte VM mit debian-10.7.0-amd64-netinst erstellt und dann nur apt-get install -y sudo, adduser pi sudo, via Putty apt-gets gemacht und curl installiert. Reboot.
                            Dann kam nach curl -sL https://iobroker.net/install.sh | bash -

                            Last login: Sun Dec 20 17:46:19 2020 from 192.168.178.41
                            pi@iobroker5:~$ curl -sL https://iobroker.net/install.sh | bash -
                            library: loaded
                            Library version=2020-12-07
                            
                            ==========================================================================
                            
                                Welcome to the ioBroker installer!
                                Installer version: 2020-12-07
                            
                                You might need to enter your password a couple of times.
                            
                            ==========================================================================
                            
                            
                            ==========================================================================
                                Installing prerequisites (1/4)
                            ==========================================================================
                            
                            [sudo] Passwort für pi:
                            OK:1 http://deb.debian.org/debian buster InRelease
                            OK:2 http://security.debian.org/debian-security buster/updates InRelease
                            OK:3 http://deb.debian.org/debian buster-updates InRelease
                            Paketlisten werden gelesen... Fertig
                            
                            ==========================================================================
                            
                                Node.js not found. Installing...
                            
                            ==========================================================================
                            
                            
                            ## Installing the NodeSource Node.js 12.x repo...
                            
                            
                            ## Populating apt-get cache...
                            
                            + apt-get update
                            OK:1 http://security.debian.org/debian-security buster/updates InRelease
                            OK:2 http://deb.debian.org/debian buster InRelease
                            OK:3 http://deb.debian.org/debian buster-updates InRelease
                            Paketlisten werden gelesen... Fertig
                            
                            ## Installing packages required for setup: gnupg...
                            
                            + apt-get install -y gnupg > /dev/null 2>&1
                            
                            ## Confirming "buster" is supported...
                            
                            + curl -sLf -o /dev/null 'https://deb.nodesource.com/node_12.x/dists/buster/Rele                                                                                         ase'
                            
                            ## Adding the NodeSource signing key to your keyring...
                            
                            + curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
                            OK
                            
                            ## Creating apt sources list file for the NodeSource Node.js 12.x repo...
                            
                            + echo 'deb https://deb.nodesource.com/node_12.x buster main' > /etc/apt/sources                                                                                         .list.d/nodesource.list
                            + echo 'deb-src https://deb.nodesource.com/node_12.x buster main' >> /etc/apt/so                                                                                         urces.list.d/nodesource.list
                            
                            ## Running `apt-get update` for you...
                            
                            + apt-get update
                            OK:1 http://security.debian.org/debian-security buster/updates InRelease
                            OK:2 http://deb.debian.org/debian buster InRelease
                            OK:3 http://deb.debian.org/debian buster-updates InRelease
                            Holen:4 https://deb.nodesource.com/node_12.x buster InRelease [4.584 B]
                            Holen:5 https://deb.nodesource.com/node_12.x buster/main amd64 Packages [765 B]
                            Es wurden 5.349 B in 1 s geholt (4.498 B/s).
                            Paketlisten werden gelesen... Fertig
                            
                            ## Run `sudo apt-get install -y nodejs` to install Node.js 12.x and npm
                            ## You may also need development tools to build native addons:
                                 sudo apt-get install gcc g++ make
                            ## To install the Yarn package manager, run:
                                 curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | sudo apt-key add -
                                 echo "deb https://dl.yarnpkg.com/debian/ stable main" | sudo tee /etc/apt/s                                                                                         ources.list.d/yarn.list
                                 sudo apt-get update && sudo apt-get install yarn
                            
                            
                            Installed nodejs
                            Node.js Installed successfully!
                            Changing npm registry to https://registry.npmjs.org
                            Installed build-essential
                            Installed gcc-c++
                            Installed libavahi-compat-libdnssd-dev
                            Installed libudev-dev
                            Installed libpam0g-dev
                            Installed git
                            Installed net-tools
                            Installed python-dev
                            
                            ==========================================================================
                                Creating ioBroker user and directory (2/4)
                            ==========================================================================
                            
                            User iobroker created
                            Created /etc/sudoers.d/iobroker
                            Directory /opt/iobroker created
                            
                            ==========================================================================
                                Installing ioBroker (3/4)
                            ==========================================================================
                            
                            In file included from ../../nan/nan.h:56,
                                             from ../src/main.cpp:3:
                            /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:737:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon    _register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                                   (node::addon_register_func) (regfunc),                          \
                                                                       ^
                            /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:771:3: note: in expansion of macro ‘NODE_MODULE_X’
                               NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                               ^~~~~~~~~~~~~
                            ../src/main.cpp:42:1: note: in expansion of macro ‘NODE_MODULE’
                             NODE_MODULE(diskusage, Init)
                             ^~~~~~~~~~~
                            In file included from ../../nan/nan.h:56,
                                             from ../src/unix_dgram.cc:5:
                            /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:737:43: warning: cast between incompatible function types from ‘void (*)(v8::Local<v8::Object>)’ to ‘node::addon    _register_func’ {aka ‘void (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)’} [-Wcast-function-type]
                                   (node::addon_register_func) (regfunc),                          \
                                                                       ^
                            /home/pi/.cache/node-gyp/12.20.0/include/node/node.h:771:3: note: in expansion of macro ‘NODE_MODULE_X’
                               NODE_MODULE_X(modname, regfunc, NULL, 0)  // NOLINT (readability/null_usage)
                               ^~~~~~~~~~~~~
                            ../src/unix_dgram.cc:404:1: note: in expansion of macro ‘NODE_MODULE’
                             NODE_MODULE(unix_dgram, Initialize)
                             ^~~~~~~~~~~
                            
                            ATTENTION: Error reporting via Sentry will be activated on next start of ioBroker
                            
                            ioBroker wants to make sure to deliver the most stable smart home system.
                            To allow this we decided to implement an automatic error and crash reporting solution into the js-controller and also into adapters.
                            
                            THIS REPORTING WILL BE ENABLED WITH THE NEXT START OF YOUR IOBROKER!
                            
                            For any error that leads to the crash of the js-controller or one of the relevant adapters the error details are send to a server. For the js-controller and core ada    pters this server is located and operated in germany. For community adapters please check the Github Readme of the affected adapter for details which Sentry server i    s used.
                            
                            If you want to disable the error reporting you can use the command
                            'iobroker plugin disable sentry'
                            This command will also make sure that no adapter that runs on this host will send crash reporting data to sentry.
                            
                            
                            
                            ==========================================================================
                                Finalizing installation (4/4)
                            ==========================================================================
                            
                            Enabling autostart...
                            Created symlink /etc/systemd/system/multi-user.target.wants/iobroker.service → /lib/systemd/system/iobroker.service.
                            Autostart enabled!
                            Fixing directory permissions...
                            
                            ==========================================================================
                            
                                ioBroker was installed successfully
                                Open http://192.168.178.108:8081 in a browser and start configuring!
                            
                            ==========================================================================
                            
                            
                            You need to re-login before doing anything else on the console!
                            
                            
                            Homoran 1 Reply Last reply Reply Quote 0
                            • Homoran
                              Homoran Global Moderator Administrators @Mercator last edited by

                              @Mercator sagte in Neue Installationsroutine (für Linux):

                              die Fehlermeldung vom Install-Script kommt ja auf einem ganz frischen Debian und ist reproduzierbar?!?

                              ist bekannt! und

                              @Thomas-Braun sagte in Neue Installationsroutine (für Linux):

                              Sind definitiv Fehler beim build.
                              Die Meldungen beim der Installation sind harmlos,

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

                                Es ist wahscheinlicher das unix_dgram inzwischen fpr nodejs 14 optimiert udn und ggf mit nodejs 12 solche fehler ausgibt. Müssen wir checken

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

                                  kann jemand auf so einem system bitte mal schauen welche unix_dgram version installiert wurde?

                                  Thomas Braun 1 Reply Last reply Reply Quote 0
                                  • Thomas Braun
                                    Thomas Braun Most Active @apollon77 last edited by Thomas Braun

                                    @apollon77

                                    pi@raspberrypi:/opt/iobroker $ npm list unix-dgram
                                    iobroker.inst@2.0.3 /opt/iobroker
                                    └─┬ iobroker.js-controller@3.1.6
                                       └─┬ winston-syslog@2.4.4
                                          └── unix-dgram@2.0.3
                                    
                                    pi@raspberrypi:/opt/iobroker $ node -v
                                    v15.4.0
                                    
                                    1 Reply Last reply Reply Quote 0
                                    • apollon77
                                      apollon77 last edited by

                                      Ok ... nodejs 15 gilt net ... da fang ich gar nicht an zu schauen 🙂

                                      Thomas Braun F 2 Replies Last reply Reply Quote 0
                                      • Thomas Braun
                                        Thomas Braun Most Active @apollon77 last edited by

                                        @apollon77 Ja,ich weiß... Läuft allerdings superunauffällig mit den von mir verwendeten Adaptern.

                                        1 Reply Last reply Reply Quote 0
                                        • F
                                          fastfoot @apollon77 last edited by

                                          @apollon77 sagte in Neue Installationsroutine (für Linux):

                                          Ok ... nodejs 15 gilt net ... da fang ich gar nicht an zu schauen 🙂

                                          ist aber gleich mit node 14.15.3 und node 12.20.0

                                          apollon77 1 Reply Last reply Reply Quote 0
                                          • apollon77
                                            apollon77 @fastfoot last edited by

                                            @fastfoot Und da wirds interessant weil auf meine System nicht ... Also mal wieder irgendwas was tiefer drin liegt 😞 Auch die Testings zeigen diese meldungen nicht. Strange

                                            M 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

                                            736
                                            Online

                                            31.6k
                                            Users

                                            79.5k
                                            Topics

                                            1.3m
                                            Posts

                                            installation
                                            64
                                            415
                                            93874
                                            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