Skip to content
  • Aktuell
  • Tags
  • 0 Ungelesen 0
  • Kategorien
  • Unreplied
  • Beliebt
  • GitHub
  • Docu
  • Hilfe
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Standard: (Kein Skin)
  • Kein Skin
Einklappen
ioBroker Logo
  1. ioBroker Community Home
  2. Deutsch
  3. ioBroker Allgemein
  4. js-controller 2.0 ab sofort im Latest Repo

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.2k
  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    1.9k
  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    15
    1
    2.1k

js-controller 2.0 ab sofort im Latest Repo

Geplant Angeheftet Gesperrt Verschoben ioBroker Allgemein
js-controller
1.1k Beiträge 89 Kommentatoren 352.7k Aufrufe 64 Watching
  • Älteste zuerst
  • Neuste zuerst
  • Meiste Stimmen
Antworten
  • In einem neuen Thema antworten
Anmelden zum Antworten
Dieses Thema wurde gelöscht. Nur Nutzer mit entsprechenden Rechten können es sehen.
  • M msauer

    Hi...Ich wollte mal den compact mode ausprobieren. Habe mir dazu heute meine beiden Alexa2 instanzen ausgesucht und dachte, lass die mal zusammen unter einem Daemon laufen...Denkste.. Bekomme die nicht zusammen ans rennen:

    2019-10-23 12:33:51.565 - info: host.MSNUC-IOB stopInstance system.adapter.alexa2.0
2019-10-23 12:33:51.570 - info: host.MSNUC-IOB stopInstance system.adapter.alexa2.0 send kill signal
2019-10-23 12:33:51.573 - info: alexa2.0 (2204) Got terminate signal TERMINATE_YOURSELF
2019-10-23 12:33:51.577 - info: alexa2.0 (2204) terminating
2019-10-23 12:33:51.578 - info: alexa2.0 (2204) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2019-10-23 12:33:52.264 - info: host.MSNUC-IOB instance system.adapter.alexa2.0 terminated with code 156 (156)
2019-10-23 12:33:52.570 - info: cloud.1 (2174) Trying to connect as system.user.admin
2019-10-23 12:33:52.655 - info: cloud.1 (2174) Connection changed: connect
2019-10-23 12:33:54.074 - info: host.MSNUC-IOB start controller for compactgroup 1
2019-10-23 12:33:54.082 - info: host.MSNUC-IOB instance system.adapter.alexa2.0 is handled by compact group controller pid 3600
2019-10-23 12:33:54.887 - info: host.MSNUC-IOB.compactgroup1 iobroker.js-controller version 2.0.35 js-controller starting
2019-10-23 12:33:55.002 - info: host.MSNUC-IOB.compactgroup1 connected to Objects and States
2019-10-23 12:33:55.618 - info: host.MSNUC-IOB.compactgroup1 starting 1 instance
2019-10-23 12:33:55.855 - info: host.MSNUC-IOB.compactgroup1 instance system.adapter.alexa2.0 started in COMPACT mode
2019-10-23 12:33:56.116 - info: alexa2.0 (COMPACT) starting. Version 2.6.4 in /opt/iobroker/node_modules/iobroker.alexa2, node: v10.16.3
2019-10-23 12:34:00.318 - info: host.MSNUC-IOB stopInstance system.adapter.alexa2.1
2019-10-23 12:34:00.322 - info: host.MSNUC-IOB stopInstance system.adapter.alexa2.1 send kill signal
2019-10-23 12:34:00.325 - info: alexa2.1 (902) Got terminate signal TERMINATE_YOURSELF
2019-10-23 12:34:00.329 - info: alexa2.1 (902) terminating
2019-10-23 12:34:00.330 - info: alexa2.1 (902) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason
2019-10-23 12:34:00.745 - info: alexa2.0 (COMPACT) Alexa-Push-Connection established. Disable Polling
2019-10-23 12:34:01.415 - info: host.MSNUC-IOB instance system.adapter.alexa2.1 terminated with code 156 (156)
2019-10-23 12:34:02.826 - info: host.MSNUC-IOB instance system.adapter.alexa2.1 is handled by compact group controller pid 3600
2019-10-23 12:34:02.840 - info: host.MSNUC-IOB.compactgroup1 instance system.adapter.alexa2.1 started in COMPACT mode
2019-10-23 12:34:02.848 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.0
2019-10-23 12:34:02.859 - error: alexa2.0 (COMPACT) uncaught exception: Cannot read property 'extendObject' of undefined
2019-10-23 12:34:02.861 - error: alexa2.1 (COMPACT) uncaught exception: Cannot read property 'extendObject' of undefined
2019-10-23 12:34:02.849 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.1
2019-10-23 12:34:02.859 - error: alexa2.0 (COMPACT) TypeError: Cannot read property 'extendObject' of undefined
at Adapter.extendObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1794:30)
at adapter.getObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:299:25)
at client.(anonymous function) (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:62808)
at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
at process._tickCallback (internal/process/next_tick.js:68:7)
2019-10-23 12:34:02.862 - error: alexa2.1 (COMPACT) TypeError: Cannot read property 'extendObject' of undefined
at Adapter.extendObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1794:30)
at adapter.getObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:299:25)
at client.(anonymous function) (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:62808)
at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
at process._tickCallback (internal/process/next_tick.js:68:7)
2019-10-23 12:34:02.867 - info: alexa2.0 (COMPACT) terminating
2019-10-23 12:34:02.871 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.0 send kill signal
2019-10-23 12:34:02.868 - info: alexa2.0 (COMPACT) Terminated (NO_ERROR): Without reason
2019-10-23 12:34:02.872 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.1 send kill signal
2019-10-23 12:34:02.875 - info: alexa2.0 (COMPACT) Got terminate signal TERMINATE_YOURSELF
2019-10-23 12:34:03.008 - info: alexa2.1 (COMPACT) starting. Version 2.6.4 in /opt/iobroker/node_modules/iobroker.alexa2, node: v10.16.3
2019-10-23 12:34:03.123 - info: alexa2.1 (COMPACT) Proxy IP not set, use first network interface (192.168.0.13) instead
2019-10-23 12:34:03.364 - info: alexa2.0 (COMPACT) terminating
2019-10-23 12:34:03.499 - info: host.MSNUC-IOB.compactgroup1 instance system.adapter.alexa2.0 terminated with code 0 (NO_ERROR)
2019-10-23 12:34:03.863 - warn: alexa2.1 (COMPACT) Terminated (UNCAUGHT_EXCEPTION): Without reason
2019-10-23 12:34:03.873 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.1 killing pid undefined
2019-10-23 12:34:04.363 - info: alexa2.0 (COMPACT) terminating with timeout
2019-10-23 12:34:04.401 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.0
2019-10-23 12:34:04.403 - warn: alexa2.1 (COMPACT) Exception: TypeError: Cannot read property 'commandSupport' of undefined
2019-10-23 12:34:04.405 - error: alexa2.0 (COMPACT) uncaught exception: Cannot read property 'commandSupport' of undefined
2019-10-23 12:34:04.402 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.1
2019-10-23 12:34:04.407 - error: alexa2.1 (COMPACT) uncaught exception: Cannot read property 'commandSupport' of undefined
2019-10-23 12:34:04.408 - error: alexa2.1 (COMPACT) TypeError: Cannot read property 'commandSupport' of undefined
at createBluetoothStates (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1756:88)
at Object.keys.forEach (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1779:13)
at Array.forEach ()
at alexa.initBluetoothState (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1775:42)
at getBluetooth (/opt/iobroker/node_modules/iobroker.alexa2/node_modules/alexa-remote2/alexa-remote.js:317:29)
at IncomingMessage.res.on (/opt/iobroker/node_modules/iobroker.alexa2/node_modules/alexa-remote2/alexa-remote.js:752:58)
at IncomingMessage.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
2019-10-23 12:34:04.406 - error: alexa2.0 (COMPACT) TypeError: Cannot read property 'commandSupport' of undefined
at createBluetoothStates (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1756:88)
at Object.keys.forEach (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1779:13)
at Array.forEach ()
at alexa.initBluetoothState (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1775:42)
at getBluetooth (/opt/iobroker/node_modules/iobroker.alexa2/node_modules/alexa-remote2/alexa-remote.js:317:29)
at IncomingMessage.res.on (/opt/iobroker/node_modules/iobroker.alexa2/node_modules/alexa-remote2/alexa-remote.js:752:58)
at IncomingMessage.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
2019-10-23 12:34:04.491 - info: host.MSNUC-IOB.compactgroup1 instance system.adapter.alexa2.1 terminated with code 6 (UNCAUGHT_EXCEPTION)
2019-10-23 12:34:04.492 - info: host.MSNUC-IOB.compactgroup1 All instances are stopped.
2019-10-23 12:34:04.495 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.1 send kill signal
2019-10-23 12:34:04.506 - info: host.MSNUC-IOB.compactgroup1 terminated
2019-10-23 12:34:04.602 - info: host.MSNUC-IOB.compactgroup1 terminated
2019-10-23 12:34:05.531 - error: host.MSNUC-IOB Caught by controller[0]: TypeError: Cannot read property 'extendObject' of undefined
2019-10-23 12:34:05.531 - error: host.MSNUC-IOB Caught by controller[0]: at Adapter.extendObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1794:30)
2019-10-23 12:34:05.532 - error: host.MSNUC-IOB Caught by controller[0]: at adapter.getObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:299:25)
2019-10-23 12:34:05.533 - error: host.MSNUC-IOB Caught by controller[0]: at client.(anonymous function) (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:62808)
2019-10-23 12:34:05.533 - error: host.MSNUC-IOB Caught by controller[0]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
2019-10-23 12:34:05.534 - error: host.MSNUC-IOB Caught by controller[0]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
2019-10-23 12:34:05.535 - error: host.MSNUC-IOB Caught by controller[0]: at process._tickCallback (internal/process/next_tick.js:68:7)
2019-10-23 12:34:05.536 - error: host.MSNUC-IOB Caught by controller[1]: TypeError: Cannot read property 'extendObject' of undefined
2019-10-23 12:34:05.536 - error: host.MSNUC-IOB Caught by controller[1]: at Adapter.extendObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1794:30)
2019-10-23 12:34:05.537 - error: host.MSNUC-IOB Caught by controller[1]: at adapter.getObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:299:25)
2019-10-23 12:34:05.537 - error: host.MSNUC-IOB Caught by controller[1]: at client.(anonymous function) (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:62808)
2019-10-23 12:34:05.538 - error: host.MSNUC-IOB Caught by controller[1]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
2019-10-23 12:34:05.538 - error: host.MSNUC-IOB Caught by controller[1]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
2019-10-23 12:34:05.539 - error: host.MSNUC-IOB Caught by controller[1]: at process._tickCallback (internal/process/next_tick.js:68:7)
2019-10-23 12:34:05.540 - error: host.MSNUC-IOB Caught by controller[2]: TypeError: Cannot read property 'commandSupport' of undefined
2019-10-23 12:34:05.540 - error: host.MSNUC-IOB Caught by controller[2]: at createBluetoothStates (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1756:88)
2019-10-23 12:34:05.541 - error: host.MSNUC-IOB Caught by controller[2]: at Object.keys.forEach (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1779:13)
2019-10-23 12:34:05.541 - error: host.MSNUC-IOB Caught by controller[2]: at Array.forEach ()
2019-10-23 12:34:05.542 - error: host.MSNUC-IOB Caught by controller[2]: at alexa.initBluetoothState (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1775:42)
2019-10-23 12:34:05.543 - error: host.MSNUC-IOB Caught by controller[2]: at getBluetooth (/opt/iobroker/node_modules/iobroker.alexa2/node_modules/alexa-remote2/alexa-remote.js:317:29)
2019-10-23 12:34:05.543 - error: host.MSNUC-IOB Caught by controller[2]: at IncomingMessage.res.on (/opt/iobroker/node_modules/iobroker.alexa2/node_modules/alexa-remote2/alexa-remote.js:752:58)
2019-10-23 12:34:05.544 - error: host.MSNUC-IOB Caught by controller[2]: at IncomingMessage.emit (events.js:203:15)
2019-10-23 12:34:05.545 - error: host.MSNUC-IOB Caught by controller[2]: at endReadableNT (_stream_readable.js:1145:12)
2019-10-23 12:34:05.546 - error: host.MSNUC-IOB Caught by controller[2]: at process._tickCallback (internal/process/next_tick.js:63:19)
2019-10-23 12:34:05.548 - error: host.MSNUC-IOB Caught by controller[3]: TypeError: Cannot read property 'commandSupport' of undefined
2019-10-23 12:34:05.549 - error: host.MSNUC-IOB Caught by controller[3]: at createBluetoothStates (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1756:88)
2019-10-23 12:34:05.549 - error: host.MSNUC-IOB Caught by controller[3]: at Object.keys.forEach (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1779:13)
2019-10-23 12:34:05.549 - error: host.MSNUC-IOB Caught by controller[3]: at Array.forEach ()
2019-10-23 12:34:05.550 - error: host.MSNUC-IOB Caught by controller[3]: at alexa.initBluetoothState (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1775:42)
2019-10-23 12:34:05.550 - error: host.MSNUC-IOB Caught by controller[3]: at getBluetooth (/opt/iobroker/node_modules/iobroker.alexa2/node_modules/alexa-remote2/alexa-remote.js:317:29)
2019-10-23 12:34:05.550 - error: host.MSNUC-IOB Caught by controller[3]: at IncomingMessage.res.on (/opt/iobroker/node_modules/iobroker.alexa2/node_modules/alexa-remote2/alexa-remote.js:752:58)
2019-10-23 12:34:05.550 - error: host.MSNUC-IOB Caught by controller[3]: at IncomingMessage.emit (events.js:203:15)
2019-10-23 12:34:05.551 - error: host.MSNUC-IOB Caught by controller[3]: at endReadableNT (_stream_readable.js:1145:12)
2019-10-23 12:34:05.551 - error: host.MSNUC-IOB Caught by controller[3]: at process._tickCallback (internal/process/next_tick.js:63:19)
2019-10-23 12:34:05.551 - info: host.MSNUC-IOB Restart compact group controller 1
2019-10-23 12:34:35.554 - info: host.MSNUC-IOB start controller for compactgroup 1
2019-10-23 12:34:35.572 - info: host.MSNUC-IOB instance system.adapter.alexa2.0 is handled by compact group controller pid 4450
2019-10-23 12:34:35.574 - info: host.MSNUC-IOB instance system.adapter.alexa2.1 is handled by compact group controller pid 4450
2019-10-23 12:34:36.508 - info: host.MSNUC-IOB.compactgroup1 iobroker.js-controller version 2.0.35 js-controller starting
2019-10-23 12:34:36.643 - info: host.MSNUC-IOB.compactgroup1 connected to Objects and States
2019-10-23 12:34:37.249 - info: host.MSNUC-IOB.compactgroup1 starting 2 instances
2019-10-23 12:34:37.483 - info: host.MSNUC-IOB.compactgroup1 instance system.adapter.alexa2.1 started in COMPACT mode
2019-10-23 12:34:37.703 - info: alexa2.1 (COMPACT) starting. Version 2.6.4 in /opt/iobroker/node_modules/iobroker.alexa2, node: v10.16.3
2019-10-23 12:34:37.842 - info: alexa2.1 (COMPACT) Proxy IP not set, use first network interface (192.168.0.13) instead
2019-10-23 12:34:41.072 - info: alexa2.1 (COMPACT) Alexa-Push-Connection established. Disable Polling
2019-10-23 12:34:41.273 - info: host.MSNUC-IOB.compactgroup1 instance system.adapter.alexa2.0 started in COMPACT mode
2019-10-23 12:34:41.283 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.1
2019-10-23 12:34:41.294 - error: alexa2.1 (COMPACT) uncaught exception: Cannot read property 'getObject' of undefined
2019-10-23 12:34:41.297 - error: alexa2.0 (COMPACT) uncaught exception: Cannot read property 'getObject' of undefined
2019-10-23 12:34:41.284 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.0
2019-10-23 12:34:41.295 - error: alexa2.1 (COMPACT) TypeError: Cannot read property 'getObject' of undefined
at Adapter.getObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1957:26)
at handleObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:297:17)
at processObjectQueue (/opt/iobroker/node_modules/iobroker.alexa2/main.js:327:5)
at handleObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:328:16)
at handleValue (/opt/iobroker/node_modules/iobroker.alexa2/main.js:301:44)
at handleValue (/opt/iobroker/node_modules/iobroker.alexa2/main.js:318:32)
at adapter.extendObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:300:21)
at (anonymous function).(anonymous function)._0x5e9959 (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:93449)
at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
2019-10-23 12:34:41.298 - error: alexa2.0 (COMPACT) TypeError: Cannot read property 'getObject' of undefined
at Adapter.getObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1957:26)
at handleObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:297:17)
at processObjectQueue (/opt/iobroker/node_modules/iobroker.alexa2/main.js:327:5)
at handleObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:328:16)
at handleValue (/opt/iobroker/node_modules/iobroker.alexa2/main.js:301:44)
at handleValue (/opt/iobroker/node_modules/iobroker.alexa2/main.js:318:32)
at adapter.extendObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:300:21)
at (anonymous function).(anonymous function)._0x5e9959 (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:93449)
at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
2019-10-23 12:34:41.306 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.1 send kill signal
2019-10-23 12:34:41.307 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.0 send kill signal
2019-10-23 12:34:41.316 - info: alexa2.1 (COMPACT) terminating
2019-10-23 12:34:41.317 - info: alexa2.1 (COMPACT) Terminated (NO_ERROR): Without reason
2019-10-23 12:34:41.320 - info: alexa2.1 (COMPACT) Got terminate signal TERMINATE_YOURSELF
2019-10-23 12:34:41.461 - info: alexa2.0 (COMPACT) starting. Version 2.6.4 in /opt/iobroker/node_modules/iobroker.alexa2, node: v10.16.3
2019-10-23 12:34:41.801 - info: alexa2.1 (COMPACT) terminating
2019-10-23 12:34:41.948 - info: host.MSNUC-IOB.compactgroup1 instance system.adapter.alexa2.1 terminated with code 0 (NO_ERROR)
2019-10-23 12:34:42.298 - warn: alexa2.0 (COMPACT) Terminated (UNCAUGHT_EXCEPTION): Without reason
2019-10-23 12:34:42.316 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.0 killing pid undefined
2019-10-23 12:34:42.798 - info: alexa2.1 (COMPACT) terminating with timeout
2019-10-23 12:34:42.913 - info: host.MSNUC-IOB.compactgroup1 instance system.adapter.alexa2.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
2019-10-23 12:34:42.914 - info: host.MSNUC-IOB.compactgroup1 All instances are stopped.
2019-10-23 12:34:42.959 - info: host.MSNUC-IOB.compactgroup1 terminated
2019-10-23 12:34:43.973 - error: host.MSNUC-IOB Caught by controller[0]: TypeError: Cannot read property 'getObject' of undefined
2019-10-23 12:34:43.974 - error: host.MSNUC-IOB Caught by controller[0]: at Adapter.getObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1957:26)
2019-10-23 12:34:43.974 - error: host.MSNUC-IOB Caught by controller[0]: at handleObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:297:17)
2019-10-23 12:34:43.974 - error: host.MSNUC-IOB Caught by controller[0]: at processObjectQueue (/opt/iobroker/node_modules/iobroker.alexa2/main.js:327:5)
2019-10-23 12:34:43.975 - error: host.MSNUC-IOB Caught by controller[0]: at handleObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:328:16)
2019-10-23 12:34:43.975 - error: host.MSNUC-IOB Caught by controller[0]: at handleValue (/opt/iobroker/node_modules/iobroker.alexa2/main.js:301:44)
2019-10-23 12:34:43.975 - error: host.MSNUC-IOB Caught by controller[0]: at handleValue (/opt/iobroker/node_modules/iobroker.alexa2/main.js:318:32)
2019-10-23 12:34:43.976 - error: host.MSNUC-IOB Caught by controller[0]: at adapter.extendObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:300:21)
2019-10-23 12:34:43.976 - error: host.MSNUC-IOB Caught by controller[0]: at (anonymous function).(anonymous function)._0x5e9959 (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:93449)
2019-10-23 12:34:43.976 - error: host.MSNUC-IOB Caught by controller[0]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
2019-10-23 12:34:43.977 - error: host.MSNUC-IOB Caught by controller[0]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
2019-10-23 12:34:43.977 - error: host.MSNUC-IOB Caught by controller[1]: TypeError: Cannot read property 'getObject' of undefined
2019-10-23 12:34:43.977 - error: host.MSNUC-IOB Caught by controller[1]: at Adapter.getObject (/opt/iobroker/node_modules/iobroker.js-controller/lib/adapter.js:1957:26)
2019-10-23 12:34:43.978 - error: host.MSNUC-IOB Caught by controller[1]: at handleObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:297:17)
2019-10-23 12:34:43.978 - error: host.MSNUC-IOB Caught by controller[1]: at processObjectQueue (/opt/iobroker/node_modules/iobroker.alexa2/main.js:327:5)
2019-10-23 12:34:43.979 - error: host.MSNUC-IOB Caught by controller[1]: at handleObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:328:16)
2019-10-23 12:34:43.979 - error: host.MSNUC-IOB Caught by controller[1]: at handleValue (/opt/iobroker/node_modules/iobroker.alexa2/main.js:301:44)
2019-10-23 12:34:43.980 - error: host.MSNUC-IOB Caught by controller[1]: at handleValue (/opt/iobroker/node_modules/iobroker.alexa2/main.js:318:32)
2019-10-23 12:34:43.980 - error: host.MSNUC-IOB Caught by controller[1]: at adapter.extendObject (/opt/iobroker/node_modules/iobroker.alexa2/main.js:300:21)
2019-10-23 12:34:43.981 - error: host.MSNUC-IOB Caught by controller[1]: at (anonymous function).(anonymous function)._0x5e9959 (/opt/iobroker/node_modules/iobroker.objects-redis/index.js:17:93449)
2019-10-23 12:34:43.981 - error: host.MSNUC-IOB Caught by controller[1]: at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:11:23)
2019-10-23 12:34:43.982 - error: host.MSNUC-IOB Caught by controller[1]: at promise.then (/opt/iobroker/node_modules/standard-as-callback/built/index.js:19:49)
2019-10-23 12:34:43.982 - info: host.MSNUC-IOB Restart compact group controller 1
2019-10-23 12:34:56.222 - info: host.MSNUC-IOB "system.adapter.alexa2.0" disabled
2019-10-23 12:34:56.883 - info: host.MSNUC-IOB "system.adapter.alexa2.1" disabled
2019-10-23 12:35:00.018 - info: host.MSNUC-IOB instance system.adapter.luftdaten.0 started with pid 4958
2019-10-23 12:35:05.926 - info: host.MSNUC-IOB "system.adapter.alexa2.0" enabled
2019-10-23 12:35:05.930 - info: host.MSNUC-IOB start controller for compactgroup 1
2019-10-23 12:35:05.936 - info: host.MSNUC-IOB instance system.adapter.alexa2.0 is handled by compact group controller pid 5130
2019-10-23 12:35:06.756 - info: host.MSNUC-IOB.compactgroup1 iobroker.js-controller version 2.0.35 js-controller starting
2019-10-23 12:35:06.875 - info: host.MSNUC-IOB.compactgroup1 connected to Objects and States
2019-10-23 12:35:07.464 - info: host.MSNUC-IOB.compactgroup1 starting 1 instance
2019-10-23 12:35:07.687 - info: host.MSNUC-IOB.compactgroup1 instance system.adapter.alexa2.0 started in COMPACT mode
2019-10-23 12:35:07.926 - info: alexa2.0 (COMPACT) starting. Version 2.6.4 in /opt/iobroker/node_modules/iobroker.alexa2, node: v10.16.3
2019-10-23 12:35:12.087 - info: host.MSNUC-IOB instance system.adapter.luftdaten.0 terminated with code 0 (NO_ERROR)
2019-10-23 12:35:13.245 - info: alexa2.0 (COMPACT) Alexa-Push-Connection established. Disable Polling
2019-10-23 12:35:21.007 - info: host.MSNUC-IOB.compactgroup1 "system.adapter.alexa2.1" enabled
2019-10-23 12:35:21.010 - info: host.MSNUC-IOB "system.adapter.alexa2.1" enabled
2019-10-23 12:35:21.014 - info: host.MSNUC-IOB stopInstance system.adapter.alexa2.1
2019-10-23 12:35:21.037 - info: host.MSNUC-IOB.compactgroup1 instance system.adapter.alexa2.1 started in COMPACT mode
2019-10-23 12:35:21.055 - error: alexa2.0 (COMPACT) uncaught exception: adapter.setState is not a function
2019-10-23 12:35:21.059 - error: alexa2.1 (COMPACT) uncaught exception: adapter.setState is not a function
2019-10-23 12:35:21.045 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.1
2019-10-23 12:35:21.046 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.0
2019-10-23 12:35:21.060 - error: alexa2.1 (COMPACT) TypeError: adapter.setState is not a function
at alexa.getMedia (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1941:25)
at IncomingMessage.res.on (/opt/iobroker/node_modules/iobroker.alexa2/node_modules/alexa-remote2/alexa-remote.js:752:58)
at IncomingMessage.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
2019-10-23 12:35:21.056 - error: alexa2.0 (COMPACT) TypeError: adapter.setState is not a function
at alexa.getMedia (/opt/iobroker/node_modules/iobroker.alexa2/main.js:1941:25)
at IncomingMessage.res.on (/opt/iobroker/node_modules/iobroker.alexa2/node_modules/alexa-remote2/alexa-remote.js:752:58)
at IncomingMessage.emit (events.js:203:15)
at endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
2019-10-23 12:35:21.082 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.1 send kill signal
2019-10-23 12:35:21.083 - info: host.MSNUC-IOB.compactgroup1 stopInstance system.adapter.alexa2.0 send kill signal
2019-10-23 12:35:21.089 - info: alexa2.0 (COMPACT) terminating
2019-10-23 12:35:21.090 - info: alexa2.0 (COMPACT) Terminated (NO_ERROR): Without reason
2019-10-23 12:35:21.092 - info: alexa2.0 (COMPACT) Got terminate signal TERMINATE_YOURSELF
2019-10-23 12:35:21.233 - info: alexa2.1 (COMPACT) starting. Version 2.6.4 in /opt/iobroker/node_modules/iobroker.alexa2, node: v10.16.3
2019-10-23 12:35:21.358 - info: alexa2.1 (COMPACT) Proxy IP not set, use first network interface (192.168.0.13) instead
2019-10-23 12:35:21.567 - info: alexa2.0 (COMPACT) terminating

    Gibt es Einschränkungen, wenn in einer Gruppe mehrere Instanzen des gleichen Typs laufen?

    PS: Hatte das gestern schon mal mit meinen beiden hm-rpc instanzen versucht...Da hab ich allerdings keine Logfiles, weil ich den Snapshot zurückgespielt hatte.

    apollon77A Online
    apollon77A Online
    apollon77
    schrieb am zuletzt editiert von
    #526

    @msauer An der Stelle kann das gut sein. Compact Mode wurde mal von einem Dev beigesteuert, ich habe es aber noch nicht tief getestet. Bitte issue anlegen, compact mode deaktivieren. 🙂 Muss ich prüfen und fixen.

    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
    sigi234S 1 Antwort Letzte Antwort
    0
    • apollon77A apollon77

      @msauer An der Stelle kann das gut sein. Compact Mode wurde mal von einem Dev beigesteuert, ich habe es aber noch nicht tief getestet. Bitte issue anlegen, compact mode deaktivieren. 🙂 Muss ich prüfen und fixen.

      sigi234S Online
      sigi234S Online
      sigi234
      Forum Testing Most Active
      schrieb am zuletzt editiert von
      #527

      @apollon77 sagte in js-controller 2.0 ab sofort im Latest Repo: compact mode deaktivieren.

      Wie aktiviere ich den eigentlich?

      Bitte benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
      Immer Daten sichern!

      BBTownB 1 Antwort Letzte Antwort
      0
      • sigi234S sigi234

        @apollon77 sagte in js-controller 2.0 ab sofort im Latest Repo: compact mode deaktivieren.

        Wie aktiviere ich den eigentlich?

        BBTownB Offline
        BBTownB Offline
        BBTown
        schrieb am zuletzt editiert von BBTown
        #528

        @sigi234 iobroker compact enable

        Details hatte @apollon77 hier im 3. Beitrag geschrieben

        ioBroker auf NUC (VM debian v13 (Trixie ), node v22.21.0 npm v10.9.4, js-controller v7.0.7 jsonl/jsonl / HomeMatic CCU-2 (Wired und Funk) / Philips HUE / echo.DOT / Broadlink RM pro / SONOS

        1 Antwort Letzte Antwort
        0
        • apollon77A apollon77

          @Andreas-Hochstöger Also in der Benahmung sind zwei Fehler drin: Einmal der "." Am Anfang und semantisch muss danach ein ".0" kommen, also Meine_Objekte.0.xxx wäre ok.

          Theoretisch könntest Du auf controller 1.5 zurück, deine Objekte exportieren, umbenennen, wieder importieren und dann neu updaten. Alternativ:

          ioBroker stoppen, dann in iobroker-data/objects.json und states.json überall ".MeineDaten." durch "Meine_Objekte.0." erstzen und neu starten. Dann Deine Skripte und Visu anpassen

          Andreas HochstögerA Offline
          Andreas HochstögerA Offline
          Andreas Hochstöger
          schrieb am zuletzt editiert von
          #529

          @apollon77
          Ich habe alles super hinbekommen war ziemlich viel Arbeit.
          Dann habe ich die Update gemacht, funktioniert alles außer der Node-Red adapter geht jetzt nicht mehr, ist das normal?
          Oder hab ich da noch einen Fehler gemacht.

          BBTownB 1 Antwort Letzte Antwort
          0
          • Andreas HochstögerA Andreas Hochstöger

            @apollon77
            Ich habe alles super hinbekommen war ziemlich viel Arbeit.
            Dann habe ich die Update gemacht, funktioniert alles außer der Node-Red adapter geht jetzt nicht mehr, ist das normal?
            Oder hab ich da noch einen Fehler gemacht.

            BBTownB Offline
            BBTownB Offline
            BBTown
            schrieb am zuletzt editiert von
            #530

            @Andreas-Hochstöger node-red sollte v1.10.1 oder höher sein
            passt das bei dir?

            ioBroker auf NUC (VM debian v13 (Trixie ), node v22.21.0 npm v10.9.4, js-controller v7.0.7 jsonl/jsonl / HomeMatic CCU-2 (Wired und Funk) / Philips HUE / echo.DOT / Broadlink RM pro / SONOS

            Andreas HochstögerA apollon77A 3 Antworten Letzte Antwort
            0
            • BBTownB BBTown

              @Andreas-Hochstöger node-red sollte v1.10.1 oder höher sein
              passt das bei dir?

              Andreas HochstögerA Offline
              Andreas HochstögerA Offline
              Andreas Hochstöger
              schrieb am zuletzt editiert von
              #531

              @BBTown
              Ja ich habe 1.13.0

              1 Antwort Letzte Antwort
              0
              • BBTownB BBTown

                @Andreas-Hochstöger node-red sollte v1.10.1 oder höher sein
                passt das bei dir?

                Andreas HochstögerA Offline
                Andreas HochstögerA Offline
                Andreas Hochstöger
                schrieb am zuletzt editiert von
                #532

                @BBTown Screenshot (7).png

                1 Antwort Letzte Antwort
                0
                • BBTownB BBTown

                  @Andreas-Hochstöger node-red sollte v1.10.1 oder höher sein
                  passt das bei dir?

                  apollon77A Online
                  apollon77A Online
                  apollon77
                  schrieb am zuletzt editiert von
                  #533

                  @BBTown Logs?

                  Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                  • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                  • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                  Andreas HochstögerA 1 Antwort Letzte Antwort
                  0
                  • apollon77A apollon77

                    @BBTown Logs?

                    Andreas HochstögerA Offline
                    Andreas HochstögerA Offline
                    Andreas Hochstöger
                    schrieb am zuletzt editiert von
                    #534

                    @apollon77 Screenshot (8).png

                    apollon77A 1 Antwort Letzte Antwort
                    0
                    • Andreas HochstögerA Andreas Hochstöger

                      @apollon77 Screenshot (8).png

                      apollon77A Online
                      apollon77A Online
                      apollon77
                      schrieb am zuletzt editiert von
                      #535

                      @Andreas-Hochstöger Da ist Port 80 eingestellt und per efault geht das nicht. vllt beim letzten nodejs update oderso rausgenommen worden. Der Installation fixer fixt die rechte wieder das ioBroker Port 80 Server öffnen darf

                      Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                      • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                      • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                      Andreas HochstögerA AlCalzoneA 2 Antworten Letzte Antwort
                      0
                      • apollon77A apollon77

                        @Andreas-Hochstöger Da ist Port 80 eingestellt und per efault geht das nicht. vllt beim letzten nodejs update oderso rausgenommen worden. Der Installation fixer fixt die rechte wieder das ioBroker Port 80 Server öffnen darf

                        Andreas HochstögerA Offline
                        Andreas HochstögerA Offline
                        Andreas Hochstöger
                        schrieb am zuletzt editiert von
                        #536

                        @apollon77
                        Es ist schön mit Profis zu arbeiten, alles funktioniert.
                        Danke!!!!👍

                        1 Antwort Letzte Antwort
                        0
                        • apollon77A apollon77

                          @Andreas-Hochstöger Da ist Port 80 eingestellt und per efault geht das nicht. vllt beim letzten nodejs update oderso rausgenommen worden. Der Installation fixer fixt die rechte wieder das ioBroker Port 80 Server öffnen darf

                          AlCalzoneA Offline
                          AlCalzoneA Offline
                          AlCalzone
                          Developer
                          schrieb am zuletzt editiert von
                          #537

                          @apollon77 sagte in js-controller 2.0 ab sofort im Latest Repo:

                          @Andreas-Hochstöger Da ist Port 80 eingestellt und per efault geht das nicht. vllt beim letzten nodejs update oderso rausgenommen worden. Der Installation fixer fixt die rechte wieder das ioBroker Port 80 Server öffnen darf

                          Die Berechtigungen, die hierfür auf der Node.js executable gesetzt werden, gehen bei jedem Node.js-Update verloren und müssen wieder hergestellt werden.

                          Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

                          1 Antwort Letzte Antwort
                          0
                          • MathiasJM Offline
                            MathiasJM Offline
                            MathiasJ
                            schrieb am zuletzt editiert von
                            #538

                            Jetzt bin ich mal gespannt.
                            Ich habe den PC und den Slave an einen gemeinsamen Switch angeschlossen.
                            Der Slave ist jetzt 10 Grad wärmer und bis jetzt keine Ausfälle.

                            IObroker auf dem NUC als VM.
                            Da ich noch keine Aktoren habe, wird momentan via Radar nur der AB der Fritzbox ein- und ausgeschaltet.
                            Welches Smarthome-System es letztendlich wird, weiß ich noch nicht. Vielleicht kommen auch nur Zigbee-Geräte ins Haus.

                            K 1 Antwort Letzte Antwort
                            0
                            • MathiasJM MathiasJ

                              Jetzt bin ich mal gespannt.
                              Ich habe den PC und den Slave an einen gemeinsamen Switch angeschlossen.
                              Der Slave ist jetzt 10 Grad wärmer und bis jetzt keine Ausfälle.

                              K Offline
                              K Offline
                              knopers1
                              schrieb am zuletzt editiert von knopers1
                              #539

                              Hallo, jemand von Euch schwierigkeiten mit dem OPI-Adapter ?

                              opi.0	2019-10-24 20:21:11.177	error	(8174) No Value found for soc_temp
opi.0	2019-10-24 20:21:11.152	error	(8174) No Value found for memory_available
opi.0	2019-10-24 20:21:11.143	error	(8174) No Value found for scaling_governor
opi.0	2019-10-24 20:21:11.133	error	(8174) No Value found for cpu_frequency

                              Den RFlink-Adapter bekomme ich auch nicht installiert.

                              $ ./iobroker add rflink  --host orangepiplus2e
NPM version: 6.11.3
npm install iobroker.rflink@2.0.0 --loglevel error --production --save --prefix "/opt/iobroker" (System call)
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.ast
gyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! System Linux 4.19.59-sunxigyp 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 v10.17.0gyp ERR! node-gyp -v v5.0.3gyp ERR! not ok 
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>
    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.ast
gyp
 ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! System Linux 4.19.59-sunxigyp 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/diskusagegyp ERR! node -v v10.17.0gyp 
ERR! node-gyp -v v5.0.3gyp ERR! not ok 
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.astgyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! System Linux 4.19.59-sunxigyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/bcrypt/lib/binding/bcrypt_lib.node" "--module_name=bcrypt_lib" "--module_path=/opt/iobroker/node_modules/bcrypt/lib/binding" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v64"gyp ERR! cwd /opt/iobroker/node_modules/bcryptgyp ERR! node -v v10.17.0gyp ERR! node-gyp -v v5.0.3gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/bcrypt/lib/binding/bcrypt_lib.node --module_name=bcrypt_lib --module_path=/opt/iobroker/node_modules/bcrypt/lib/binding --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/node-pre-gyp/lib/util/compile.js:83:29)node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)node-pre-gyp ERR! System Linux 4.19.59-sunxinode-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"node-pre-gyp ERR! cwd /opt/iobroker/node_modules/bcryptnode-pre-gyp ERR! node -v v10.17.0node-pre-gyp ERR! node-pre-gyp -v v0.12.0node-pre-gyp ERR! not ok 
node-pre-gyp ERR! Tried to download(404): https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz 
node-pre-gyp ERR! Pre-built binaries not found for serialport@4.0.7 and node@10.17.0 (node-v64 ABI) (falling back to source compile with node-gyp) 
node-pre-gyp
 ERR!
 Tried to download(undefined): https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz 
node-pre-gyp ERR! Pre-built binaries not found for serialport@4.0.7 and node@10.17.0 (node-v64 ABI) (falling back to source compile with node-gyp) 
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>
    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.ast
gyp
 
ERR! 
configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack
     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp
 ERR! System Linux 4.19.59-sunxigyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/build/Release/serialport.node" "--module_name=serialport" "--module_path=/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/build/Release"gyp ERR! cwd /opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialportgyp ERR! node -v v10.17.0gyp ERR! node-gyp -v v5.0.3gyp ERR! not ok 
node-pre-gyp ERR! build error 
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/build/Release/serialport.node --module_name=serialport --module_path=/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/build/Release' (1)node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/node_modules/node-pre-gyp/lib/util/compile.js:83:29)node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
node-pre-gyp ERR! System Linux 4.19.59-sunxinode-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"node-pre-gyp ERR! cwd /opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialportnode-pre-gyp ERR! node -v v10.17.0node-pre-gyp ERR! node-pre-gyp -v v0.6.32node-pre-gyp ERR! not ok 
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.ast
gyp
 
ERR! 
configure error 
gyp ERR! 
stack Error: `gyp` failed with exit code: 1gyp ERR! stack
     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! 
System Linux 4.19.59-sunxigyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/build/Release/serialport.node" "--module_name=serialport" "--module_path=/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/build/Release"gyp ERR! cwd /opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialportgyp ERR! node -v v10.17.0gyp ERR! node-gyp -v v5.0.3gyp ERR! not ok 
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>
    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.ast
gyp
 
ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1gyp ERR!
 stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! System
 Linux 4.19.59-sunxigyp 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/unix-dgramgyp ERR! node -v v10.17.0gyp ERR! node-gyp -v v5.0.3gyp ERR! not ok 
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>
    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.ast
gyp
 ERR! configure error
 gyp ERR! stack
 Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! System Linux 4.19.59-sunxigyp 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/iobroker.rflink/node_modules/@serialport/bindingsgyp ERR! node -v v10.17.0gyp ERR! node-gyp -v v5.0.3gyp ERR! not ok 
npm ERR!
 code ELIFECYCLEnpm 
ERR! errno
 1npm
 ERR! @serialport/bindings@2.0.8 install: `prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild`
npm ERR!
 Exit status 1npm ERR! npm ERR! Failed at the @serialport/bindings@2.0.8 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-24T18_41_49_379Z-debug.log
ERROR: host.orangepiplus2e Cannot install iobroker.rflink@2.0.0: 1
ERROR: process exited with code 25

                              Es ist ein Armbian Buster

                              root@orangepiplus2e:/opt/iobroker# node -v
v10.17.0
root@orangepiplus2e:/opt/iobroker# nodejs -v
v10.17.0
root@orangepiplus2e:/opt/iobroker# npm -v
6.11.3

                              Welcome to Debian Buster with Armbian Linux 4.19.59-sunxi
                              System load: 1.59 2.70 2.49 Up time: 1:01 hour
                              Memory usage: 38 % of 2013MB IP: 192.168.1.100
                              Usage of /: 13% of 15G

                              [ General system configuration (beta): armbian-config ]

                              root@orangepiplus2e:~#

                              HP Microserver Gen8, RPI-4, IoBroker,

                              apollon77A 1 Antwort Letzte Antwort
                              0
                              • K knopers1

                                Hallo, jemand von Euch schwierigkeiten mit dem OPI-Adapter ?

                                opi.0	2019-10-24 20:21:11.177	error	(8174) No Value found for soc_temp
opi.0	2019-10-24 20:21:11.152	error	(8174) No Value found for memory_available
opi.0	2019-10-24 20:21:11.143	error	(8174) No Value found for scaling_governor
opi.0	2019-10-24 20:21:11.133	error	(8174) No Value found for cpu_frequency

                                Den RFlink-Adapter bekomme ich auch nicht installiert.

                                $ ./iobroker add rflink  --host orangepiplus2e
NPM version: 6.11.3
npm install iobroker.rflink@2.0.0 --loglevel error --production --save --prefix "/opt/iobroker" (System call)
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.ast
gyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! System Linux 4.19.59-sunxigyp 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 v10.17.0gyp ERR! node-gyp -v v5.0.3gyp ERR! not ok 
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>
    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.ast
gyp
 ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! System Linux 4.19.59-sunxigyp 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/diskusagegyp ERR! node -v v10.17.0gyp 
ERR! node-gyp -v v5.0.3gyp ERR! not ok 
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.astgyp ERR! configure error gyp ERR! stack Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! System Linux 4.19.59-sunxigyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/bcrypt/lib/binding/bcrypt_lib.node" "--module_name=bcrypt_lib" "--module_path=/opt/iobroker/node_modules/bcrypt/lib/binding" "--napi_version=5" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v64"gyp ERR! cwd /opt/iobroker/node_modules/bcryptgyp ERR! node -v v10.17.0gyp ERR! node-gyp -v v5.0.3gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/bcrypt/lib/binding/bcrypt_lib.node --module_name=bcrypt_lib --module_path=/opt/iobroker/node_modules/bcrypt/lib/binding --napi_version=5 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64' (1)node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/node-pre-gyp/lib/util/compile.js:83:29)node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)node-pre-gyp ERR! System Linux 4.19.59-sunxinode-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"node-pre-gyp ERR! cwd /opt/iobroker/node_modules/bcryptnode-pre-gyp ERR! node -v v10.17.0node-pre-gyp ERR! node-pre-gyp -v v0.12.0node-pre-gyp ERR! not ok 
node-pre-gyp ERR! Tried to download(404): https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz 
node-pre-gyp ERR! Pre-built binaries not found for serialport@4.0.7 and node@10.17.0 (node-v64 ABI) (falling back to source compile with node-gyp) 
node-pre-gyp
 ERR!
 Tried to download(undefined): https://github.com/EmergingTechnologyAdvisors/node-serialport/releases/download/4.0.7/serialport-v4.0.7-node-v64-linux-arm.tar.gz 
node-pre-gyp ERR! Pre-built binaries not found for serialport@4.0.7 and node@10.17.0 (node-v64 ABI) (falling back to source compile with node-gyp) 
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>
    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.ast
gyp
 
ERR! 
configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack
     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp
 ERR! System Linux 4.19.59-sunxigyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/build/Release/serialport.node" "--module_name=serialport" "--module_path=/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/build/Release"gyp ERR! cwd /opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialportgyp ERR! node -v v10.17.0gyp ERR! node-gyp -v v5.0.3gyp ERR! not ok 
node-pre-gyp ERR! build error 
node-pre-gyp ERR! stack Error: Failed to execute '/usr/bin/node /usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/build/Release/serialport.node --module_name=serialport --module_path=/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/build/Release' (1)node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/node_modules/node-pre-gyp/lib/util/compile.js:83:29)node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
node-pre-gyp ERR! System Linux 4.19.59-sunxinode-pre-gyp ERR! command "/usr/bin/node" "/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"node-pre-gyp ERR! cwd /opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialportnode-pre-gyp ERR! node -v v10.17.0node-pre-gyp ERR! node-pre-gyp -v v0.6.32node-pre-gyp ERR! not ok 
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.ast
gyp
 
ERR! 
configure error 
gyp ERR! 
stack Error: `gyp` failed with exit code: 1gyp ERR! stack
     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! 
System Linux 4.19.59-sunxigyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/build/Release/serialport.node" "--module_name=serialport" "--module_path=/opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialport/build/Release"gyp ERR! cwd /opt/iobroker/node_modules/avrgirl-arduino/node_modules/serialportgyp ERR! node -v v10.17.0gyp ERR! node-gyp -v v5.0.3gyp ERR! not ok 
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>
    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.ast
gyp
 
ERR! configure error 
gyp ERR! stack Error: `gyp` failed with exit code: 1gyp ERR!
 stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! System
 Linux 4.19.59-sunxigyp 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/unix-dgramgyp ERR! node -v v10.17.0gyp ERR! node-gyp -v v5.0.3gyp ERR! not ok 
Traceback (most recent call last):  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py", line 13, in <module>
    import gyp  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/__init__.py", line 10, in <module>    import gyp.input  File "/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/pylib/gyp/input.py", line 7, in <module>    from compiler.ast import ConstImportError: No module named compiler.ast
gyp
 ERR! configure error
 gyp ERR! stack
 Error: `gyp` failed with exit code: 1gyp ERR! stack     at ChildProcess.onCpExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:344:16)gyp ERR! stack     at ChildProcess.emit (events.js:198:13)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)gyp ERR! System Linux 4.19.59-sunxigyp 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/iobroker.rflink/node_modules/@serialport/bindingsgyp ERR! node -v v10.17.0gyp ERR! node-gyp -v v5.0.3gyp ERR! not ok 
npm ERR!
 code ELIFECYCLEnpm 
ERR! errno
 1npm
 ERR! @serialport/bindings@2.0.8 install: `prebuild-install --tag-prefix @serialport/bindings@ || node-gyp rebuild`
npm ERR!
 Exit status 1npm ERR! npm ERR! Failed at the @serialport/bindings@2.0.8 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-24T18_41_49_379Z-debug.log
ERROR: host.orangepiplus2e Cannot install iobroker.rflink@2.0.0: 1
ERROR: process exited with code 25

                                Es ist ein Armbian Buster

                                root@orangepiplus2e:/opt/iobroker# node -v
v10.17.0
root@orangepiplus2e:/opt/iobroker# nodejs -v
v10.17.0
root@orangepiplus2e:/opt/iobroker# npm -v
6.11.3

                                Welcome to Debian Buster with Armbian Linux 4.19.59-sunxi
                                System load: 1.59 2.70 2.49 Up time: 1:01 hour
                                Memory usage: 38 % of 2013MB IP: 192.168.1.100
                                Usage of /: 13% of 15G

                                [ General system configuration (beta): armbian-config ]

                                root@orangepiplus2e:~#

                                apollon77A Online
                                apollon77A Online
                                apollon77
                                schrieb am zuletzt editiert von
                                #540

                                @knopers1 opi kann ggf. daran liegen das als User iobroker bestimmte Werte nicht mehr lesbar sind? Da gabs auch was bei rpi.

                                Rflink: irgendwas scheint mit deiner node-Gyp installation zu sein oder mit Python. Google mal nach der Meldung am Anfang.

                                Beides nicht Controller related

                                Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                J 1 Antwort Letzte Antwort
                                0
                                • apollon77A apollon77

                                  @knopers1 opi kann ggf. daran liegen das als User iobroker bestimmte Werte nicht mehr lesbar sind? Da gabs auch was bei rpi.

                                  Rflink: irgendwas scheint mit deiner node-Gyp installation zu sein oder mit Python. Google mal nach der Meldung am Anfang.

                                  Beides nicht Controller related

                                  J Offline
                                  J Offline
                                  Jogi19
                                  schrieb am zuletzt editiert von
                                  #541

                                  Hallo,
                                  ich habe jetzt auch erfolgreich auf iobroker 2.0.35 umgestellt. Die oben beschriebenen Befehle haben allerdings so nicht funktioniert. Ich habe dann "sudo -H -u iobroker npm install iobroker.js-controller@2.0" angegeben und dann ging es. bei mir laufen scheinbar alle Adapter einwandfrei, auch der TR-064 Adapter.
                                  Gestern habe ich dann noch auf Redis umgestellt.
                                  Ein paar Tage zuvor bin ich von einem Raspberry Pi 3 auf ein Intel NUC i3 umgestiegen. Hier läuft Proxmox und den ioBroker und Redis habe ich unter Debian 10 installiert. In einer zweiten VM habe ich MariaDB installiert in der ich die History Werte ablege.

                                  apollon77A AlCalzoneA 2 Antworten Letzte Antwort
                                  0
                                  • J Jogi19

                                    Hallo,
                                    ich habe jetzt auch erfolgreich auf iobroker 2.0.35 umgestellt. Die oben beschriebenen Befehle haben allerdings so nicht funktioniert. Ich habe dann "sudo -H -u iobroker npm install iobroker.js-controller@2.0" angegeben und dann ging es. bei mir laufen scheinbar alle Adapter einwandfrei, auch der TR-064 Adapter.
                                    Gestern habe ich dann noch auf Redis umgestellt.
                                    Ein paar Tage zuvor bin ich von einem Raspberry Pi 3 auf ein Intel NUC i3 umgestiegen. Hier läuft Proxmox und den ioBroker und Redis habe ich unter Debian 10 installiert. In einer zweiten VM habe ich MariaDB installiert in der ich die History Werte ablege.

                                    apollon77A Online
                                    apollon77A Online
                                    apollon77
                                    schrieb am zuletzt editiert von
                                    #542

                                    @Jogi19 sagte in js-controller 2.0 ab sofort im Latest Repo:

                                    Die oben beschriebenen Befehle haben allerdings so nicht funktioniert.

                                    Hast du mehr Details dazu?

                                    Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77

                                    • Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
                                    • Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
                                    1 Antwort Letzte Antwort
                                    -1
                                    • J Jogi19

                                      Hallo,
                                      ich habe jetzt auch erfolgreich auf iobroker 2.0.35 umgestellt. Die oben beschriebenen Befehle haben allerdings so nicht funktioniert. Ich habe dann "sudo -H -u iobroker npm install iobroker.js-controller@2.0" angegeben und dann ging es. bei mir laufen scheinbar alle Adapter einwandfrei, auch der TR-064 Adapter.
                                      Gestern habe ich dann noch auf Redis umgestellt.
                                      Ein paar Tage zuvor bin ich von einem Raspberry Pi 3 auf ein Intel NUC i3 umgestiegen. Hier läuft Proxmox und den ioBroker und Redis habe ich unter Debian 10 installiert. In einer zweiten VM habe ich MariaDB installiert in der ich die History Werte ablege.

                                      AlCalzoneA Offline
                                      AlCalzoneA Offline
                                      AlCalzone
                                      Developer
                                      schrieb am zuletzt editiert von
                                      #543

                                      @Jogi19 sagte in js-controller 2.0 ab sofort im Latest Repo:

                                      Ich habe dann "sudo -H -u iobroker npm install iobroker.js-controller@2.0" angegeben und dann ging es.

                                      Hast du in letzter Zeit mal den Fixer ausgefürht? Mit der neuesten Version sollte das nicht mehr nötig sein.

                                      Warum `sudo` böse ist: https://forum.iobroker.net/post/17109

                                      1 Antwort Letzte Antwort
                                      0
                                      • sissiwupS Offline
                                        sissiwupS Offline
                                        sissiwup
                                        schrieb am zuletzt editiert von
                                        #544 
                                        host.zotac	2019-10-25 19:41:27.571	error	Objects 127.0.0.1:53536 (Init=false) Redis error:Error: Invalid Chunk: parse failed
host.zotac	2019-10-25 19:41:24.516	error	States 127.0.0.1:51570 (Init=false) Redis error:Error: Invalid Chunk: parse failed
host.zotac	2019-10-25 19:41:24.515	error	States 127.0.0.1:51568 (Init=false) Redis error:Error: Invalid Chunk: parse failed
host.zotac	2019-10-25 19:41:24.010	error	States 127.0.0.1:51556 (Init=false) Redis error:Error: Invalid Chunk: parse failed
host.zotac	2019-10-25 19:41:24.009	error	Objects 127.0.0.1:53510 (Init=false) Redis error:Error: Invalid Chunk: parse failed
host.zotac	2019-10-25 19:41:22.567	error	Objects 127.0.0.1:53482 (Init=false) Redis error:Error: Invalid Chunk: parse failed
host.zotac	2019-10-25 19:41:22.565	error	Objects 127.0.0.1:53480 (Init=false) Redis error:Error: Invalid Chunk: parse failed
host.zotac	2019-10-25 19:41:19.510	error	States 127.0.0.1:51510 (Init=false) Redis error:Error: Invalid Chunk: parse failed
host.zotac	2019-10-25 19:41:19.508	error	States 127.0.0.1:51508 (Init=false) Redis error:Error: Invalid Chunk: parse failed
host.zotac	2019-10-25 19:41:19.001	error	States 127.0.0.1:51506 (Init=false) Redis error:Error: Invalid Chunk: parse failed
host.zotac	2019-10-25 19:41:19.000	error	Objects 127.0.0.1:53460 (Init=false) Redis error:Error: Invalid Chunk: parse failed
host.zotac	2019-10-25 19:41:17.562	error	Objects 127.0.0.1:53438 (Init=false) Redis error:Error: Invalid Chunk: parse failed
host.zotac	2019-10-25 19:41:17.560	error	Objects 127.0.0.1:53436 (Init=false) Redis error:Error: Invalid Chunk: parse failed

                                        Hallo,

                                        nach Update. Ich nutze kein Redis (so viel ich weiss, möchte ich auch nicht)
                                        VIS geht.
                                        Simple-API: auf "alle" umgestellt
                                        Admin und WEB: Alle IPs
                                        WEB:
                                        Puffer ja, Socket io:integriert, Laufen unter "simple API"

                                        MfG

                                        Sissi

                                        –-----------------------------------------

                                        1 CCU3 1 CCU2-Gateway 1 LanGateway 1 Pi-Gateway 1 I7 für ioBroker/MySQL

                                        sissiwupS crunchipC J apollon77A 4 Antworten Letzte Antwort
                                        0
                                        • R Offline
                                          R Offline
                                          RandyAndy
                                          schrieb am zuletzt editiert von
                                          #545

                                          Hi,

                                          jetzt habe ich zum js-controller aucch mal eine Frage.
                                          Wenn ich über das Terminal versuche den iobroker anzuhalten über sudo iobroker stop dann bekomme ich die Meldung das der daemeon gar nicht läuft. er läuft aber denn der iobroker ist über admin usw. erreichbar.Remotedesktopverbindung.png

                                          Interessant ist auch dass er offensichtlich den js-controller unter dem pfad: home/pi sucht.
                                          Remotedesktopverbindung.png

                                          Da komme ich nun nicht mehr alleine durch

                                          Andreas

                                          AlCalzoneA 1 Antwort Letzte Antwort
                                          0
                                          Antworten
                                          • In einem neuen Thema antworten
                                          Anmelden zum Antworten
                                          • Älteste zuerst
                                          • Neuste zuerst
                                          • Meiste Stimmen

                                          Support us

                                          ioBroker
                                          Community Adapters
                                          Donate
                                          FAQ Cloud / IOT
                                          HowTo: Node.js-Update
                                          HowTo: Backup/Restore
                                          Downloads
                                          BLOG

                                          755

                                          Online

                                          32.4k

                                          Benutzer

                                          81.4k

                                          Themen

                                          1.3m

                                          Beiträge
                                          Community
                                          Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                          ioBroker Community 2014-2025
                                          logo
                                          • Anmelden
                                          • Du hast noch kein Konto? Registrieren
                                          • Anmelden oder registrieren, um zu suchen
                                          • Erster Beitrag
                                            Letzter Beitrag
                                          0
                                          • Aktuell
                                          • Tags
                                          • Ungelesen 0
                                          • Kategorien
                                          • Unreplied
                                          • Beliebt
                                          • GitHub
                                          • Docu
                                          • Hilfe