Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. YAHKA und SQL funktioniert nicht mehr

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    YAHKA und SQL funktioniert nicht mehr

    This topic has been deleted. Only users with topic management privileges can see it.
    • Georg Bachmann
      Georg Bachmann last edited by Georg Bachmann

      Hallo,
      ich hab heute ein Backup von meinem iobroker am raspberry gemacht und das ganze dann auf meine Synology im Docker übersiedelt. Dazu dann noch den Raspberry also slave eingebunden (weil der eben BTLE kann sowie dort mein DeConz Stick läuft)
      Soweit so gut. Läuft auch fast schon alles wieder wie es soll...
      Nur der YAHKA (Homekit) Adapter will nicht so recht. Der startet einfach nicht am neuen System. Egal ob ich den alten raspberry oder die Synology als Host nehme... es will nicht...

      In den Logs hab ich folgendes gefunden...
      Ich schätz dass die Logs alle zu dem instance system.adapter.yahka.0 terminated with code 6 (uncaught exception) gehören weil der Timestamp ja quasi gleich ist?!?

      host.ioBroker-Pi	2019-06-28 23:34:08.847	info	Restart adapter system.adapter.yahka.0 because enabled
      host.ioBroker-Pi	2019-06-28 23:34:08.847	error	instance system.adapter.yahka.0 terminated with code 6 (uncaught exception)
      host.ioBroker-Pi	2019-06-28 23:34:08.847	error	Caught by controller[0]: at Decoder.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15)
      host.ioBroker-Pi	2019-06-28 23:34:08.847	error	Caught by controller[0]: at Manager.ondecoded (/opt/iobroker/node_modules/socket.io-client/lib/manager.js:332:8)
      host.ioBroker-Pi	2019-06-28 23:34:08.847	error	Caught by controller[0]: at Manager.Emitter.emit (/opt/iobroker/node_modules/socket.io-client/node_modules/component-emitter/index.js:133:20)
      host.ioBroker-Pi	2019-06-28 23:34:08.847	error	Caught by controller[0]: at Manager.<anonymous> (/opt/iobroker/node_modules/component-bind/index.js:21:15)
      host.ioBroker-Pi	2019-06-28 23:34:08.846	error	Caught by controller[0]: at Socket.onpacket (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:236:12)
      host.ioBroker-Pi	2019-06-28 23:34:08.846	error	Caught by controller[0]: at Socket.onack (/opt/iobroker/node_modules/socket.io-client/lib/socket.js:312:9)
      host.ioBroker-Pi	2019-06-28 23:34:08.846	error	Caught by controller[0]: at Socket.<anonymous> (/opt/iobroker/node_modules/iobroker.yahka/main.js:3562:21)
      host.ioBroker-Pi	2019-06-28 23:34:08.846	error	Caught by controller[0]: at changeInterceptor (/opt/iobroker/node_modules/iobroker.yahka/main.js:3549:85)
      host.ioBroker-Pi	2019-06-28 23:34:08.846	error	Caught by controller[0]: at TIoBrokerInOutFunction_Homematic_Dimmer_On../yahka.functions/functions.base.ts.TYahkaFunctionBase.subscriptionEvent (/opt/iobroker/node_modules/iobroker.yahka/main.js:2
      host.ioBroker-Pi	2019-06-28 23:34:08.846	error	Caught by controller[0]: at TIoBrokerInOutFunction_Homematic_Dimmer_On../yahka.functions/iofunc.homematic.dimmer.ts.TIoBrokerInOutFunction_Homematic_Dimmer_Base.cacheChanged (/opt/iobroker/node_mo
      host.ioBroker-Pi	2019-06-28 23:34:08.845	error	Caught by controller[0]: TypeError: Cannot read property 'val' of null
      

      Und vermutlich aus einem ähnlichen Grund geht jetzt auch des SQL Adapter nicht mehr. Hier der Log dazu:

      host.iobroker	2019-06-28 23:51:37.687	error	instance system.adapter.sql.0 terminated with code 1 ()
      host.iobroker	2019-06-28 23:51:37.687	error	Caught by controller[0]: at Module.load (module.js:566:32)
      host.iobroker	2019-06-28 23:51:37.687	error	Caught by controller[0]: at Object.Module._extensions..js (module.js:664:10)
      host.iobroker	2019-06-28 23:51:37.687	error	Caught by controller[0]: at Module._compile (module.js:653:30)
      host.iobroker	2019-06-28 23:51:37.687	error	Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/mmmagic/lib/index.js:1:75)
      host.iobroker	2019-06-28 23:51:37.687	error	Caught by controller[0]: at require (internal/module.js:11:18)
      host.iobroker	2019-06-28 23:51:37.686	error	Caught by controller[0]: at Module.require (module.js:597:17)
      host.iobroker	2019-06-28 23:51:37.686	error	Caught by controller[0]: at Function.Module._load (module.js:498:3)
      host.iobroker	2019-06-28 23:51:37.686	error	Caught by controller[0]: at tryModuleLoad (module.js:506:12)
      host.iobroker	2019-06-28 23:51:37.686	error	Caught by controller[0]: at Module.load (module.js:566:32)
      host.iobroker	2019-06-28 23:51:37.686	error	Caught by controller[0]: at Object.Module._extensions..node (module.js:682:18)
      host.iobroker	2019-06-28 23:51:37.686	error	Caught by controller[0]: Error: /opt/iobroker/node_modules/mmmagic/build/Release/magic.node: wrong ELF class: ELFCLASS32
      host.iobroker	2019-06-28 23:51:37.686	error	Caught by controller[0]: ^
      host.iobroker	2019-06-28 23:51:37.686	error	Caught by controller[0]: return process.dlopen(module, path._makeLong(filename));
      host.iobroker	2019-06-28 23:51:37.686	error	Caught by controller[0]: module.js:682```
      
      Bin über alle Tips wie ich das Problem finde sehr dankbar :)
      1 Reply Last reply Reply Quote 0
      • First post
        Last post

      Support us

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

      846
      Online

      31.9k
      Users

      80.1k
      Topics

      1.3m
      Posts

      multihost raspberry synology yahka
      1
      1
      145
      Loading More Posts
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      Community
      Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
      The ioBroker Community 2014-2023
      logo