Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [HowTo] ioBroker unter Docker auf Synology DiskStation

    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

    [HowTo] ioBroker unter Docker auf Synology DiskStation

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

      Hallo @andre

      ich habe das Problem, dass ich kein Telegram-Adapter im Docker (buanet-Image im macvlan-Modus) zum laufen bekomme. Adapter lässt sich ohne Probleme installieren, jedoch bekomme ich den Adapter nicht gestartet -> mit folgender Fehlermeldung:

      host.iobroker-docker	2020-10-19 20:33:16.326	error	instance system.adapter.telegram.1 terminated with code 1 (JS_CONTROLLER_STOPPED)
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: }
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: ]
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: '/opt/iobroker/node_modules/iobroker.telegram/main.js'
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: '/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/index.js',
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: requireStack: [
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: code: 'MODULE_NOT_FOUND',
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: at internal/main/run_main_module.js:17:47 {
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: at Function.Module._load (internal/modules/cjs/loader.js:878:14)
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: at Module.load (internal/modules/cjs/loader.js:985:32)
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10)
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: at Module._compile (internal/modules/cjs/loader.js:1137:30)
      host.iobroker-docker	2020-10-19 20:33:16.326	error	Caught by controller[1]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.telegram/main.js:23:15)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at require (internal/modules/cjs/helpers.js:72:18)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at Module.require (internal/modules/cjs/loader.js:1025:19)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at Function.Module._load (internal/modules/cjs/loader.js:878:14)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at Module.load (internal/modules/cjs/loader.js:985:32)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1157:10)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at Module._compile (internal/modules/cjs/loader.js:1137:30)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/index.js:13:41)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at Array.forEach (<anonymous>)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/index.js:14:43
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at require (internal/modules/cjs/helpers.js:72:18)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at Module.require (internal/modules/cjs/loader.js:1025:19)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at Function.Module._load (internal/modules/cjs/loader.js:841:27)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: at Function.Module._resolveFilename (internal/modules/cjs/loader.js:965:15)
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: - /opt/iobroker/node_modules/iobroker.telegram/main.js
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: - /opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/index.js
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: Require stack:
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: Error: Cannot find module '/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/auth/@eaDir'
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: ^
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: throw err;
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[1]: internal/modules/cjs/loader.js:968
      host.iobroker-docker	2020-10-19 20:33:16.325	error	Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at internal/modules/cjs/loader.js:1137:30
      host.iobroker-docker	2020-10-19 20:33:16.324	error	Caught by controller[0]: In the future, you will have to enable it yourself.
      host.iobroker-docker	2020-10-19 20:33:16.324	error	Caught by controller[0]: Mon, 19 Oct 2020 18:33:16 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
      

      Eine Idee dazu?

      Danke im voraus!

      mania25 created this issue in yagop/node-telegram-bot-api

      closed Error: cannot enable cancellation after promises are in use #319

      Glasfaser Thomas Braun 2 Replies Last reply Reply Quote 0
      • Glasfaser
        Glasfaser @mumurik last edited by

        @mumurik sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:

        Eine Idee dazu?

        Hat aber nichts mit ..... Docker ...... zu tun !

        im Docker (buanet-Image im macvlan-Modus)

        Da stimmt etwas mit dem Adapter nicht .
        Deinstalliere ihn und über die Katze (git) neu .

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

          @mumurik Versionsnummern? Das verlinkte Issue
          https://github.com/yagop/node-telegram-bot-api/issues/319
          sollte in aktuellen Versionen ja längstens erledigt sein.

          mania25 created this issue in yagop/node-telegram-bot-api

          closed Error: cannot enable cancellation after promises are in use #319

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

            @Thomas-Braun
            Die Version is aktuell 1.5.9

            1 Reply Last reply Reply Quote 0
            • M
              mumurik @Glasfaser last edited by

              @Glasfaser
              auf dem Raspberry läuft's seit Jahren ohne Probleme...

              Glasfaser 1 Reply Last reply Reply Quote 0
              • Glasfaser
                Glasfaser @mumurik last edited by Glasfaser

                @mumurik sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:

                auf dem Raspberry läuft's seit Jahren ohne Probleme...

                und was möchtest du mir damit sagen ... !???

                Du hast es doch jetzt im Docker , das sind doch zwei verschiedene Systeme !

                M 1 Reply Last reply Reply Quote 0
                • M
                  mumurik @Glasfaser last edited by

                  @Glasfaser
                  nicht falsch verstehen, ich wollte nur damit sagen, dass die gleiche Adapter-Version auf dem Pi bereits erfolgreich läuft und im Docker auch ohne Probleme sich installiert hat. Deswegen ging meine Vermutung in Richtung Docker und nicht in Richtung des Adapters selbst

                  dslraser Thomas Braun 3 Replies Last reply Reply Quote 0
                  • dslraser
                    dslraser Forum Testing Most Active @mumurik last edited by dslraser

                    @mumurik
                    ich habe Telegram im ioBroker Docker (auch mac vlan) gefühlt schon ewig laufen. Daran liegt es nicht. Es muß also eine andere Ursache bei Deinem System sein.
                    Und die Fehlermeldung in Deinem log verweist, wie oben schon erwähnt, auf ein Uraltes Issue..

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

                      @mumurik Irgendwie wird da wohl das Modul socksv5 nicht gefunden. Keine Ahnung ob das von telegram abhängig mit installiert werden müsste.
                      Auf meinem System ist es jedenfalls nicht drauf (Habe aber auch telegram nicht drauf):

                      pi@raspberrypi:~ $ cd /opt/iobroker/
                      pi@raspberrypi:/opt/iobroker $ npm list socksv5
                      iobroker.inst@2.0.3 /opt/iobroker
                      └── (empty)
                      
                      Glasfaser 1 Reply Last reply Reply Quote 0
                      • Glasfaser
                        Glasfaser @Thomas Braun last edited by

                        So sieht es im Docker aus :

                        root@iobroker:/opt/iobroker# npm list socksv5                                                                                                              
                        iobroker.inst@2.0.3 /opt/iobroker                                                                                             
                        └─┬ iobroker.telegram@1.5.9                                                                                                   
                          └── socksv5@0.0.6                                                                                                           
                                                                                                                                                      
                        root@iobroker:/opt/iobroker#                                                                                                  
                                                      
                        
                        1 Reply Last reply Reply Quote 0
                        • Thomas Braun
                          Thomas Braun Most Active @mumurik last edited by

                          @mumurik Ich würde wohl telegram nochmal drüberbügeln. Schau in's log.

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

                            @Thomas-Braun
                            habe eben mal downgegraded auf die Version 1.4.3 und dann wieder hoch auf die 1.5.9. Bekomme bei der Installation des Adapters nun folgende Fehlermeldung:

                            $ ./iobroker upgrade telegram
                            Update telegram from @1.4.3 to @1.5.9
                            NPM version: 6.14.6
                            npm install iobroker.telegram@1.5.9 --loglevel error --prefix "/opt/iobroker" (System call)
                            npm
                             ERR! code EINVALIDPACKAGENAME
                            npm ERR! Invalid package name "@eaDir/.bin@SynoResource": name can only contain URL-friendly characters
                            
                            npm ERR! A complete log of this run can be found in:npm ERR!
                            
                            Glasfaser 1 Reply Last reply Reply Quote 0
                            • Glasfaser
                              Glasfaser @mumurik last edited by Glasfaser

                              @mumurik sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:

                              Invalid package name "@eaDir/.bin@SynoResource":

                              Gehört nicht zu ioBroker ... da ist aber ganz schön was schief.

                              cd /opt/iobroker
                              pkill -u iobroker
                              npm cache clean --force
                              iobroker del telegram
                              iobroker start
                              

                              poste mal die Ausgabe von :

                              which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
                              
                              M 1 Reply Last reply Reply Quote 0
                              • M
                                mumurik @Glasfaser last edited by

                                @Glasfaser sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:

                                which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs

                                #which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs
                                /usr/bin/nodejs
                                v12.18.3
                                /usr/bin/node
                                v12.18.3
                                /usr/bin/npm
                                6.14.6
                                nodejs:
                                  Installiert:           12.18.3-1nodesource1
                                  Installationskandidat: 12.18.3-1nodesource1
                                  Versionstabelle:
                                 *** 12.18.3-1nodesource1 500
                                        500 https://deb.nodesource.com/node_12.x buster/main amd64 Packages
                                        100 /var/lib/dpkg/status
                                     10.21.0~dfsg-1~deb10u1 500
                                        500 http://deb.debian.org/debian buster/main amd64 Packages
                                        500 http://security.debian.org/debian-security buster/updates/main amd64 Packages
                                
                                Thomas Braun Glasfaser 2 Replies Last reply Reply Quote 0
                                • Thomas Braun
                                  Thomas Braun Most Active @mumurik last edited by

                                  @mumurik
                                  Das könntest du schon mal aktualisieren.

                                  sudo apt update
                                  sudo apt upgrade
                                  
                                  M 1 Reply Last reply Reply Quote 0
                                  • M
                                    mumurik @Thomas Braun last edited by

                                    @Thomas-Braun sagte in [HowTo] ioBroker unter Docker auf Synology DiskStation:

                                    sudo apt upgrade

                                    apt upgrade durchgeführt

                                    which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nod
                                    ejs
                                    /usr/bin/nodejs
                                    v12.19.0
                                    /usr/bin/node
                                    v12.19.0
                                    /usr/bin/npm
                                    6.14.8
                                    nodejs:
                                      Installiert:           12.19.0-1nodesource1
                                      Installationskandidat: 12.19.0-1nodesource1
                                      Versionstabelle:
                                     *** 12.19.0-1nodesource1 500
                                            500 https://deb.nodesource.com/node_12.x buster/main amd64 Packages
                                            100 /var/lib/dpkg/status
                                         10.21.0~dfsg-1~deb10u1 500
                                            500 http://deb.debian.org/debian buster/main amd64 Packages
                                            500 http://security.debian.org/debian-security buster/updates/main amd64 Packages
                                    

                                    jedoch weiterhin Fehlermeldungen beim Starten des Adapters:

                                    host.iobroker-docker	2020-10-20 15:07:58.918	error	Caught by controller[1]: }
                                    host.iobroker-docker	2020-10-20 15:07:58.918	error	Caught by controller[1]: ]
                                    host.iobroker-docker	2020-10-20 15:07:58.918	error	Caught by controller[1]: '/opt/iobroker/node_modules/iobroker.telegram/main.js'
                                    host.iobroker-docker	2020-10-20 15:07:58.918	error	Caught by controller[1]: '/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/index.js',
                                    host.iobroker-docker	2020-10-20 15:07:58.918	error	Caught by controller[1]: requireStack: [
                                    host.iobroker-docker	2020-10-20 15:07:58.918	error	Caught by controller[1]: code: 'MODULE_NOT_FOUND',
                                    host.iobroker-docker	2020-10-20 15:07:58.917	error	Caught by controller[1]: at internal/main/run_main_module.js:17:47 {
                                    host.iobroker-docker	2020-10-20 15:07:58.917	error	Caught by controller[1]: at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
                                    host.iobroker-docker	2020-10-20 15:07:58.917	error	Caught by controller[1]: at Function.Module._load (internal/modules/cjs/loader.js:724:14)
                                    host.iobroker-docker	2020-10-20 15:07:58.917	error	Caught by controller[1]: at Module.load (internal/modules/cjs/loader.js:879:32)
                                    host.iobroker-docker	2020-10-20 15:07:58.917	error	Caught by controller[1]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10)
                                    host.iobroker-docker	2020-10-20 15:07:58.917	error	Caught by controller[1]: at Module._compile (internal/modules/cjs/loader.js:1015:30)
                                    host.iobroker-docker	2020-10-20 15:07:58.917	error	Caught by controller[1]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.telegram/main.js:23:15)
                                    host.iobroker-docker	2020-10-20 15:07:58.917	error	Caught by controller[1]: at require (internal/modules/cjs/helpers.js:74:18)
                                    host.iobroker-docker	2020-10-20 15:07:58.917	error	Caught by controller[1]: at Module.require (internal/modules/cjs/loader.js:903:19)
                                    host.iobroker-docker	2020-10-20 15:07:58.917	error	Caught by controller[1]: at Function.Module._load (internal/modules/cjs/loader.js:724:14)
                                    host.iobroker-docker	2020-10-20 15:07:58.916	error	Caught by controller[1]: at Module.load (internal/modules/cjs/loader.js:879:32)
                                    host.iobroker-docker	2020-10-20 15:07:58.916	error	Caught by controller[1]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10)
                                    host.iobroker-docker	2020-10-20 15:07:58.916	error	Caught by controller[1]: at Module._compile (internal/modules/cjs/loader.js:1015:30)
                                    host.iobroker-docker	2020-10-20 15:07:58.916	error	Caught by controller[1]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/index.js:13:41)
                                    host.iobroker-docker	2020-10-20 15:07:58.916	error	Caught by controller[1]: at Array.forEach (<anonymous>)
                                    host.iobroker-docker	2020-10-20 15:07:58.916	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/index.js:14:43
                                    host.iobroker-docker	2020-10-20 15:07:58.916	error	Caught by controller[1]: at require (internal/modules/cjs/helpers.js:74:18)
                                    host.iobroker-docker	2020-10-20 15:07:58.916	error	Caught by controller[1]: at Module.require (internal/modules/cjs/loader.js:903:19)
                                    host.iobroker-docker	2020-10-20 15:07:58.916	error	Caught by controller[1]: at Function.Module._load (internal/modules/cjs/loader.js:687:27)
                                    host.iobroker-docker	2020-10-20 15:07:58.916	error	Caught by controller[1]: at Function.Module._resolveFilename (internal/modules/cjs/loader.js:831:15)
                                    host.iobroker-docker	2020-10-20 15:07:58.916	error	Caught by controller[1]: - /opt/iobroker/node_modules/iobroker.telegram/main.js
                                    host.iobroker-docker	2020-10-20 15:07:58.915	error	Caught by controller[1]: - /opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/index.js
                                    host.iobroker-docker	2020-10-20 15:07:58.915	error	Caught by controller[1]: Require stack:
                                    host.iobroker-docker	2020-10-20 15:07:58.915	error	Caught by controller[1]: Error: Cannot find module '/opt/iobroker/node_modules/iobroker.telegram/node_modules/socksv5/lib/auth/@eaDir'
                                    host.iobroker-docker	2020-10-20 15:07:58.915	error	Caught by controller[1]: ^
                                    host.iobroker-docker	2020-10-20 15:07:58.915	error	Caught by controller[1]: throw err;
                                    host.iobroker-docker	2020-10-20 15:07:58.915	error	Caught by controller[1]: internal/modules/cjs/loader.js:834
                                    host.iobroker-docker	2020-10-20 15:07:58.915	error	Caught by controller[0]: See https://github.com/yagop/node-telegram-bot-api/issues/319. at internal/modules/cjs/loader.js:1015:30
                                    host.iobroker-docker	2020-10-20 15:07:58.915	error	Caught by controller[0]: In the future, you will have to enable it yourself.
                                    host.iobroker-docker	2020-10-20 15:07:58.914	error	Caught by controller[0]: Tue, 20 Oct 2020 13:07:58 GMT node-telegram-bot-api deprecated Automatic enabling of cancellation of promises is deprecated.
                                    
                                    
                                    mania25 created this issue in yagop/node-telegram-bot-api

                                    closed Error: cannot enable cancellation after promises are in use #319

                                    1 Reply Last reply Reply Quote 0
                                    • Glasfaser
                                      Glasfaser @mumurik last edited by

                                      @mumurik

                                      Hast du die Befehle die ich dir oben genannt habe einmal gemacht !!!!

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

                                        @Glasfaser @mumurik
                                        Vielleicht auch mal ein rebuild?

                                        iobroker rebuild telegram
                                        

                                        müsste der Befehl sein.

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

                                          @Thomas-Braun

                                          nee lass erstmal ... der Schrott muß erstmal runter

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

                                            @Glasfaser
                                            Ist da irgendwas aus der Synology reingeschwappt?
                                            @eaDir/.bin@SynoResource" hört sich irgendwie so an.

                                            Glasfaser 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

                                            827
                                            Online

                                            31.8k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            buanet diskstation docker iobroker synology
                                            248
                                            2854
                                            1422449
                                            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