Bekomme Noble nicht richtig installiert.

apollon77

Dann such mal in node_modules den noble ordner und versuch es dort

Belei

auch keine Reaktion,

dafür ging heute morgen die Lichter nicht an und die Rolläden nicht hoch.

Der Log wird mit Fehlern vollgespüllt und diverse Adapter wie Zigbee, RFLink, Dashbutton, Cloud usw gehen nicht mehr:

host.ioBroker-Pi3	2018-10-26 07:49:05.706	error	instance system.adapter.amazon-dash.0 terminated with code 0 (OK)
host.ioBroker-Pi3	2018-10-26 07:49:05.706	error	Caught by controller[0]: at Module.load (module.js:566:32)
host.ioBroker-Pi3	2018-10-26 07:49:05.706	error	Caught by controller[0]: at Object.Module._extensions..js (module.js:664:10)
host.ioBroker-Pi3	2018-10-26 07:49:05.706	error	Caught by controller[0]: at Module._compile (module.js:653:30)
host.ioBroker-Pi3	2018-10-26 07:49:05.706	error	Caught by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap/pcap.js:3:21)
host.ioBroker-Pi3	2018-10-26 07:49:05.706	error	Caught by controller[0]: at require (internal/module.js:11:18)
host.ioBroker-Pi3	2018-10-26 07:49:05.705	error	Caught by controller[0]: at Module.require (module.js:597:17)
host.ioBroker-Pi3	2018-10-26 07:49:05.705	error	Caught by controller[0]: at Function.Module._load (module.js:498:3)
host.ioBroker-Pi3	2018-10-26 07:49:05.705	error	Caught by controller[0]: at tryModuleLoad (module.js:506:12)
host.ioBroker-Pi3	2018-10-26 07:49:05.705	error	Caught by controller[0]: at Module.load (module.js:566:32)
host.ioBroker-Pi3	2018-10-26 07:49:05.705	error	Caught by controller[0]: at Object.Module._extensions..node (module.js:682:18)
host.ioBroker-Pi3	2018-10-26 07:49:05.705	error	Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
host.ioBroker-Pi3	2018-10-26 07:49:05.705	error	Caught by controller[0]: NODE_MODULE_VERSION 57\. Please try re-compiling or re-installing
host.ioBroker-Pi3	2018-10-26 07:49:05.705	error	Caught by controller[0]: NODE_MODULE_VERSION 48\. This version of Node.js requires
host.ioBroker-Pi3	2018-10-26 07:49:05.704	error	Caught by controller[0]: was compiled against a different Node.js version using
host.ioBroker-Pi3	2018-10-26 07:49:05.704	error	Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap/build/Release/p</anonymous>

Das ging heute Nacht um 3 Uhr los, nach dem neustart vom ioBroker durch den Backitup Adapter.

Ich habe gestern beim versuch noble zum laufen zu bringen, auf Nodejs 8 upgedatet.

pi@ioBroker-Pi3:~ $ nodejs -v
v8.12.0

pi@ioBroker-Pi3:~ $ npm -v
6.4.1

Könnte das damit zusammenhängen?

apollon77

Was dsagt

node -v

?

Die Fehlermeldung sagt alles: Das amazon dash ist auch für dfie falsche nodejs version compiliert. auch hier "npm rebuild"

Belei

pi@ioBroker-Pi3:~ $  node -v
v8.12.0

Ausgabe aus amazon dash:

pi@ioBroker-Pi3:/opt/iobroker/node_modules/iobroker.amazon-dash $ npm rebuild

> pcap@2.0.0 install /opt/iobroker/node_modules/iobroker.amazon-dash/node_module                                                                                        s/pcap
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/                                                                                        pcap/build“ wird betreten
  CXX(target) Release/obj.target/pcap_binding/pcap_binding.o
  CXX(target) Release/obj.target/pcap_binding/pcap_session.o
../pcap_session.cc: In static member function ‘static void PcapSession::New(const Nan::FunctionCallbackInfo<v8::value>&)’:
../pcap_session.cc:46:49: warning: ‘v8::Local <v8::object>v8::Function::NewInstance() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
     info.GetReturnValue().Set(cons->NewInstance());
                                                 ^
In file included from /home/pi/.node-gyp/8.12.0/include/node/v8.h:26:0,
                 from /home/pi/.node-gyp/8.12.0/include/node/node.h:63,
                 from ../../nan/nan.h:51,
                 from ../pcap_session.h:4,
                 from ../pcap_session.cc:7:
/home/pi/.node-gyp/8.12.0/include/node/v8.h:3901:52: note: declared here
   V8_DEPRECATED("Use maybe version", Local <object>NewInstance() const);
                                                    ^
/home/pi/.node-gyp/8.12.0/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
../pcap_session.cc: In static member function ‘static void PcapSession::PacketReady(u_char*, const pcap_pkthdr*, const u_char*)’:
../pcap_session.cc:85:102: warning: ‘v8::Local <v8::value>Nan::MakeCallback(v8::Local<v8::object>, v8::Local<v8::function>, int, v8::Local<v8::value>*)’ is deprecated  -Wdeprecated-declarations]
 n::GetCurrentContext()->Global(), Nan::New(session->packet_ready_cb), 0, NULL);
                                                                              ^
In file included from ../pcap_session.h:4:0,
                 from ../pcap_session.cc:7:
../../nan/nan.h:929:46: note: declared here
   NAN_DEPRECATED inline v8::Local <v8::value>MakeCallback(
                                              ^~~~~~~~~~~~
  SOLINK_MODULE(target) Release/obj.target/pcap_binding.node
  COPY Release/pcap_binding.node
make: Verzeichnis „/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap/build“ wird verlassen

> socketwatcher@0.3.0 install /opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/socketwatcher
> node-gyp rebuild

make: Verzeichnis „/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/socketwatcher/build“ wird betreten
  CXX(target) Release/obj.target/socketwatcher/socket_watcher.o
../socket_watcher.cpp: In static member function ‘static void SocketWatcher::Callback(uv_poll_t*, int, int)’:
../socket_watcher.cpp:77:60: 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(watcher->handle(), callback, argc, argv);
                                                            ^
In file included from ../socket_watcher.hpp:8:0,
                 from ../socket_watcher.cpp:5:
../../nan/nan.h:929:46: note: declared here
   NAN_DEPRECATED inline v8::Local <v8::value>MakeCallback(
                                              ^~~~~~~~~~~~
../socket_watcher.cpp: In static member function ‘static void SocketWatcher::New(const Nan::FunctionCallbackInfo<v8::value>&)’:
../socket_watcher.cpp:104:49: warning: ‘v8::Local <v8::object>v8::Function::NewInstance() const’ is deprecated: Use maybe version [-Wdeprecated-declarations]
     info.GetReturnValue().Set(cons->NewInstance());
                                                 ^
In file included from /home/pi/.node-gyp/8.12.0/include/node/v8.h:26:0,
                 from /home/pi/.node-gyp/8.12.0/include/node/node.h:63,
                 from ../../nan/nan.h:51,
                 from ../socket_watcher.hpp:8,
                 from ../socket_watcher.cpp:5:
/home/pi/.node-gyp/8.12.0/include/node/v8.h:3901:52: note: declared here
   V8_DEPRECATED("Use maybe version", Local <object>NewInstance() const);
                                                    ^
/home/pi/.node-gyp/8.12.0/include/node/v8config.h:318:3: note: in definition of macro ‘V8_DEPRECATED’
   declarator __attribute__((deprecated(message)))
   ^~~~~~~~~~
  SOLINK_MODULE(target) Release/obj.target/socketwatcher.node
  COPY Release/socketwatcher.node
make: Verzeichnis „/opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/socketwatcher/build“ wird verlassen
pcap@2.0.0 /opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/pcap
nan@2.10.0 /opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/nan
socketwatcher@0.3.0 /opt/iobroker/node_modules/iobroker.amazon-dash/node_modules/socketwatcher
pi@ioBroker-Pi3:/opt/iobroker/node_modules/iobroker.amazon-dash $</object></v8::object></v8::value></v8::value></v8::value></v8::function></v8::object></v8::value></v8::value></v8::value></v8::function></v8::object></v8::value></object></v8::object></v8::value>

apollon77

geht denn dash jetzt?

Belei

ja dash läuft wieder, hab system mal neugestartet.

Jetzt meckert der RFLINK Adapter: Bzw wird die USB Hardware nicht mehr gefunden, im RFLINK und Zigbee Adapter.

host.ioBroker-Pi3	2018-10-26 11:52:09.822	error	instance system.adapter.zigbee.0 terminated with code 1 ()
host.ioBroker-Pi3	2018-10-26 11:52:09.822	error	Caught by controller[0]: at Object.Module._extensions..js (module.js:664:10)
host.ioBroker-Pi3	2018-10-26 11:52:09.821	error	Caught by controller[0]: at Module._compile (module.js:653:30)
host.ioBroker-Pi3	2018-10-26 11:52:09.821	error	Caught by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/serialport/lib/bindings/linux.js:2:36)
host.ioBroker-Pi3	2018-10-26 11:52:09.821	error	Caught by controller[0]: at bindings (/opt/iobroker/node_modules/serialport/node_modules/bindings/bindings.js:81:44)
host.ioBroker-Pi3	2018-10-26 11:52:09.821	error	Caught by controller[0]: at require (internal/module.js:11:18)
host.ioBroker-Pi3	2018-10-26 11:52:09.821	error	Caught by controller[0]: at Module.require (module.js:597:17)
host.ioBroker-Pi3	2018-10-26 11:52:09.821	error	Caught by controller[0]: at Function.Module._load (module.js:498:3)
host.ioBroker-Pi3	2018-10-26 11:52:09.821	error	Caught by controller[0]: at tryModuleLoad (module.js:506:12)
host.ioBroker-Pi3	2018-10-26 11:52:09.820	error	Caught by controller[0]: at Module.load (module.js:566:32)
host.ioBroker-Pi3	2018-10-26 11:52:09.820	error	Caught by controller[0]: at Object.Module._extensions..node (module.js:682:18)
host.ioBroker-Pi3	2018-10-26 11:52:09.820	error	Caught by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
host.ioBroker-Pi3	2018-10-26 11:52:09.820	error	Caught by controller[0]: NODE_MODULE_VERSION 57\. Please try re-compiling or re-installing
host.ioBroker-Pi3	2018-10-26 11:52:09.818	error	Caught by controller[0]: NODE_MODULE_VERSION 48\. This version of Node.js requires
host.ioBroker-Pi3	2018-10-26 11:52:09.816	error	Caught by controller[0]: was compiled against a different Node.js version using
host.ioBroker-Pi3	2018-10-26 11:52:09.813	error	Caught by controller[0]: Error: The module '/opt/iobroker/node_modules/serialport/build/Release/serialport.node'
host.ioBroker-Pi3	2018-10-26 11:52:09.812	error	Caught by controller[0]: ^
host.ioBroker-Pi3	2018-10-26 11:52:09.810	error	Caught by controller[0]: throw e
host.ioBroker-Pi3	2018-10-26 11:52:09.810	error	Caught by controller[0]: /opt/iobroker/node_modules/serialport/node_modules/bindings/bindings.js:88</anonymous>

Da warscheinleich auch rebuild? aber in welchem Ordner genau?

apollon77

Wenn Du ein node upgrade machst muss alles was nativ kompilierte Pakete sind neu kompiliert werden und ja, damit npm rebuild

Belei

Da kommt nur das?

pi@ioBroker-Pi3:/opt/iobroker/node_modules/serialport/build/Release $ npm rebuild
bindings@1.3.0 /opt/iobroker/node_modules/serialport/node_modules/bindings
debug@3.2.5 /opt/iobroker/node_modules/serialport/node_modules/debug
ms@2.1.1 /opt/iobroker/node_modules/serialport/node_modules/ms
nan@2.11.0 /opt/iobroker/node_modules/serialport/node_modules/nan
prebuild-install@4.0.0 /opt/iobroker/node_modules/serialport/node_modules/prebuild-install
minimist@1.2.0 /opt/iobroker/node_modules/serialport/node_modules/minimist
prompt-list@3.2.0 /opt/iobroker/node_modules/serialport/node_modules/prompt-list
safe-buffer@5.1.2 /opt/iobroker/node_modules/serialport/node_modules/safe-buffer
pi@ioBroker-Pi3:/opt/iobroker/node_modules/serialport/build/Release $

Und im io Log steht:

rflink.0	2018-10-26 13:34:30.101	warn	Module serialport is not available

Somit keine ansteuerung des RFLINK Hardware Adapters.

apollon77

Und tuts?

Belei

Ich habs jetzt mal im RFLINK Ordner gemacht, jetzt läuft der auch wieder

Belei

Aktuelle Fehlermeldung beim starten des Zigbee Adapters:

host.ioBroker-Pi3	2018-10-26 14:02:38.958	info	Restart adapter system.adapter.zigbee.0 because enabled
host.ioBroker-Pi3	2018-10-26 14:02:38.958	error	instance system.adapter.zigbee.0 terminated with code 1 ()
Caught	2018-10-26 14:02:38.958	error	by controller[0]: at Object.Module._extensions..js (module.js:664:10)
Caught	2018-10-26 14:02:38.958	error	by controller[0]: at Module._compile (module.js:653:30)
Caught	2018-10-26 14:02:38.958	error	by controller[0]: at Object. <anonymous>(/opt/iobroker/node_modules/serialport/lib/bindings/linux.js:2:36)
Caught	2018-10-26 14:02:38.958	error	by controller[0]: at bindings (/opt/iobroker/node_modules/serialport/node_modules/bindings/bindings.js:81:44)
Caught	2018-10-26 14:02:38.957	error	by controller[0]: at require (internal/module.js:11:18)
Caught	2018-10-26 14:02:38.957	error	by controller[0]: at Module.require (module.js:597:17)
Caught	2018-10-26 14:02:38.957	error	by controller[0]: at Function.Module._load (module.js:498:3)
Caught	2018-10-26 14:02:38.957	error	by controller[0]: at tryModuleLoad (module.js:506:12)
Caught	2018-10-26 14:02:38.957	error	by controller[0]: at Module.load (module.js:566:32)
Caught	2018-10-26 14:02:38.957	error	by controller[0]: at Object.Module._extensions..node (module.js:682:18)
Caught	2018-10-26 14:02:38.956	error	by controller[0]: the module (for instance, using `npm rebuild` or `npm install`).
Caught	2018-10-26 14:02:38.956	error	by controller[0]: NODE_MODULE_VERSION 57\. Please try re-compiling or re-installing
Caught	2018-10-26 14:02:38.956	error	by controller[0]: NODE_MODULE_VERSION 48\. This version of Node.js requires
Caught	2018-10-26 14:02:38.956	error	by controller[0]: was compiled against a different Node.js version using
Caught	2018-10-26 14:02:38.956	error	by controller[0]: Error: The module '/opt/iobroker/node_modules/serialport/build/Release/serialport.node'
Caught	2018-10-26 14:02:38.956	error	by controller[0]: ^
Caught	2018-10-26 14:02:38.955	error	by controller[0]: throw e
Caught	2018-10-26 14:02:38.955	error	by controller[0]: /opt/iobroker/node_modules/serialport/node_modules/bindings/bindings.js:88
host.ioBroker-Pi3	2018-10-26 14:02:37.949	info	instance system.adapter.zigbee.0 started with pid 929</anonymous>

npm im Zigbee Ordner Ergebniss:

pi@ioBroker-Pi3:/opt/iobroker/node_modules/iobroker.zigbee $ npm rebuild
debug@3.2.6 /opt/iobroker/node_modules/iobroker.zigbee/node_modules/debug
ms@2.1.1 /opt/iobroker/node_modules/iobroker.zigbee/node_modules/ms

npm im /opt/iobroker/node_modules/serialport/node_modules/bindings

keine Reaktion

npm rebuild im /opt/iobroker/node_modules/serialport/build/Release

pi@ioBroker-Pi3:/opt/iobroker/node_modules/serialport/build/Release $ npm rebuild
bindings@1.3.0 /opt/iobroker/node_modules/serialport/node_modules/bindings
debug@3.2.5 /opt/iobroker/node_modules/serialport/node_modules/debug
ms@2.1.1 /opt/iobroker/node_modules/serialport/node_modules/ms
nan@2.11.0 /opt/iobroker/node_modules/serialport/node_modules/nan
prebuild-install@4.0.0 /opt/iobroker/node_modules/serialport/node_modules/prebuild-install
minimist@1.2.0 /opt/iobroker/node_modules/serialport/node_modules/minimist
prompt-list@3.2.0 /opt/iobroker/node_modules/serialport/node_modules/prompt-list
safe-buffer@5.1.2 /opt/iobroker/node_modules/serialport/node_modules/safe-buffer

Im Zigbee Adapter ist nicht der USB anschluss zur auswahl vorhanden somit bleibt der Bursche rot

apollon77

Fürhre das rebuild mal eher in

/opt/iobroker/node_modules/serialport/

aus

Belei

Dann kommt

pi@ioBroker-Pi3:/opt/iobroker/node_modules/serialport $ npm rebuild
bindings@1.3.0 /opt/iobroker/node_modules/serialport/node_modules/bindings
debug@3.2.5 /opt/iobroker/node_modules/serialport/node_modules/debug
ms@2.1.1 /opt/iobroker/node_modules/serialport/node_modules/ms
nan@2.11.0 /opt/iobroker/node_modules/serialport/node_modules/nan
prebuild-install@4.0.0 /opt/iobroker/node_modules/serialport/node_modules/prebuild-install
minimist@1.2.0 /opt/iobroker/node_modules/serialport/node_modules/minimist
prompt-list@3.2.0 /opt/iobroker/node_modules/serialport/node_modules/prompt-list
safe-buffer@5.1.2 /opt/iobroker/node_modules/serialport/node_modules/safe-buffer

Aber der Fehler im Log ist immer noch da und adapter bleibt rot!

apollon77

dann such mal ob in node_modules des Adapters selbst ggf nochmal ein serialport drin ist

Belei

Nichts zu finden. Nur debug und ms

Auch eine neuinstallation von zigbee hat nix gebracht.

apollon77

ich meine in /opt/iobroker/node_modules

Belei

Da gibts nur ein serialport

apollon77

Dann kann ich nur sagen: lösch den serialport malund installiere adapter nochmal. Dann wäre ich am Ende der Ideen

Belei

öhmm also den Ordner Serialport löschen und dann zigbee adapter neuinstallieren?

installiert der dan den serialport wieder mit?

.–------------------------------------

Gleich fliegt das Ding aus dem Fenster... Jetzt geht wieder gar nix... nach folgender Aktion:

sudo apt-get update
sudo apt-get install build-essential git

cd /opt/iobroker
npm install iobroker.Zigbee

http://www.iobroker.net/docu/?page_id=5510&lang=de

Jetzt startet io nicht mehr….

pi@ioBroker-Pi3:~ $ iobroker start
module.js:550
    throw err;
    ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Function.Module.runMain (module.js:694:10)
    at startup (bootstrap_node.js:204:16)
    at bootstrap_node.js:625:3

Belei

Ich habe ein Backup eingespielt, und die ganzen rebuilds nochmal gemacht, diesmal immer den betreffenden adapter vorher ausgeschaltet.

Jetzt läuft es wieder und siehe da:

RADAR erkennt endlich auch meine beiden BT Anhänger und auch diverse Unknown Devices

Noble wird auch als aktiv angezeigt und ich bin auf

Node.js: v8.12.0

NPM: 6.4.1

Sind die Versionen OK?

PUH was ein Krampf wird Zeit für eine Virtuelle Umgebung um mal eben was zu testen :lol:

Danke an apollon77

NEWS

Bekomme Noble nicht richtig installiert.

Support us

916
Online

31.9k
Users

80.2k
Topics

1.3m
Posts

NEWS

Bekomme Noble nicht richtig installiert.

Support us

916Online

31.9kUsers

80.2kTopics

1.3mPosts

916
Online

31.9k
Users

80.2k
Topics

1.3m
Posts