Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. iobroker add ecovacs-deebot

    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

    iobroker add ecovacs-deebot

    This topic has been deleted. Only users with topic management privileges can see it.
    • U
      udo-2112 @mrbungle64 last edited by udo-2112

      @mrbungle64

      Hi, ich kann einen Terminal öffnen. Da gibt es aber keinen Button für CodeTags. Wie könnte ich meinen 25er Fehler denn beheben?

      Danke und Gruß Martin.

      Err25.png

      Homoran mrbungle64 3 Replies Last reply Reply Quote 0
      • Homoran
        Homoran Global Moderator Administrators @udo-2112 last edited by

        @udo-2112 sagte in iobroker add ecovacs-deebot:

        Da gibt es aber keinen Button für CodeTags.

        Natürlich nicht! der ist hier im Forum

        1 Reply Last reply Reply Quote 0
        • mrbungle64
          mrbungle64 Developer @udo-2112 last edited by

          @udo-2112 sagte in iobroker add ecovacs-deebot:

          @mrbungle64

          Hi, ich kann einen Terminal öffnen. Da gibt es aber keinen Button für CodeTags.

          Das habe ich auch nicht behauptet ...

          Wie @Thomas-Braun es dir eigentlich schon erklärt hatte und @Homoran noch mal wiederholt hat bezieht sich das auf eine Funktion hier im Forum:

          1643511571178-code-tags.gif

          1 Reply Last reply Reply Quote 0
          • mrbungle64
            mrbungle64 Developer @udo-2112 last edited by

            @udo-2112 sagte in iobroker add ecovacs-deebot:

            @mrbungle64

            Wie könnte ich meinen 25er Fehler denn beheben?

            Hast Du Dir denn inzwischen mal die anderen Beiträge dazu angeschaut? Davon gibt es nämlich so einige (wie @Thomas-Braun vor ein paar Wochen schon mal erwähnt hatte)

            https://forum.iobroker.net/search?term="error 25"

            U 1 Reply Last reply Reply Quote 0
            • U
              udo-2112 @mrbungle64 last edited by

              @mrbungle64
              Hi, ja habe ich. Hab aber immer diverse Fehlermeldung:

              This upgrade of "discovery" will introduce the following changes:
              ==========================================================================
              -> 3.0.5:
              Fix potential crash cases reported by Sentry
              
              -> 3.0.4:
              Disable configuration settings for this adapter
              ==========================================================================
              
              Would you like to upgrade discovery from @3.0.3 to @3.0.5 now? [(y)es, (n)o]: y
              Update discovery from @3.0.3 to @3.0.5
              NPM version: 8.11.0
              Installing iobroker.discovery@3.0.5... (System call)
              host.Poxdorf Cannot install iobroker.discovery@3.0.5: 217
              

              Ich weiß nicht was hier bei mir falsch ist:

              PLATTFORM: DOCKER
              RAM: 15.5 GB
              NODE.JS: V16.15.1
              NPM: 8.11.0

              Reading package lists... Done
              Building dependency tree... Done
              Reading state information... Done
              nodejs is already the newest version (16.15.1-deb-1nodesource1).
              0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
              
              iobroker is running on this host.
              
              
              Objects type: jsonl
              States  type: jsonl
              
              
              This upgrade of "telegram" will at least introduce the following changes:
              ==========================================================================
              -> 1.13.0:
              Added Admin 5 UI config
              Added rule block for javascript as plugin
              
              -> 1.12.6:
              Fix crash cases reported by Sentry
              
              -> 1.12.5:
              Fix crash cases reported by Sentry
              
              -> 1.12.4:
              Fix crash cases reported by Sentry
              
              -> 1.12.3:
              Make sure also not set states can be queried - will return "State not set" in this case!
              
              -> 1.12.2:
              Fix crash cases reported by Sentry
              
              -> 1.12.0:
              Add new JSON states communication.responseJson and communication.responseSilentJson to also accept json structures (stringified!) to send messages
              Try to prevent adapter crashes when internet is not available 
              Add Sentry for crash reporting
              ==========================================================================
              
              BE CAREFUL: THIS IS A MAJOR UPGRADE, WHICH WILL MOST LIKELY INTRODUCE BREAKING CHANGES!
              Would you like to upgrade telegram from @0.0.0 to @1.13.0 now? [(y)es, (n)o]: y
              Update telegram from @0.0.0 to @1.13.0
              NPM version: 8.11.0
              Installing iobroker.telegram@1.13.0... (System call)
              npm ERR! code ENOTEMPTY
              npm ERR! syscall rename
              npm ERR! path /opt/iobroker/node_modules/concat-stream
              npm ERR! dest /opt/iobroker/node_modules/.concat-stream-0YCrXysM
              npm ERR! errno -39
              npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/concat-stream' -> '/opt/iobroker/node_modules/.concat-stream-0YCrXysM'
              
              npm ERR! A complete log of this run can be found in:
              npm ERR!     /opt/iobroker/.npm/_logs/2022-07-24T07_48_04_751Z-debug-0.log
              host.Poxdorf Cannot install iobroker.telegram@1.13.0: 217
              

              Danke und Gruß Martin

              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @udo-2112 last edited by

                @udo-2112

                Schau in meiner Signatur bei nodeJS nach. Im zweiten Teil steht ein Lösungsansatz drin.

                U 1 Reply Last reply Reply Quote 0
                • U
                  udo-2112 @Thomas Braun last edited by

                  @thomas-braun

                  Hi, ```
                  Get:1 http://security.debian.org/debian-security bullseye-security InRelease [48,4 kB]
                  Get:2 http://deb.debian.org/debian bullseye InRelease [116 kB]
                  Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44,1 kB]
                  Get:4 https://deb.nodesource.com/node_16.x bullseye InRelease [4.586 B]
                  Get:5 http://security.debian.org/debian-security bullseye-security/main amd64 Packages [175 kB]
                  Get:6 http://deb.debian.org/debian bullseye/main amd64 Packages [8.182 kB]
                  Get:7 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages [774 B]
                  Get:8 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [2.592 B]
                  Fetched 8.573 kB in 6s (1.544 kB/s)
                  Reading package lists... Done
                  Building dependency tree... Done
                  Reading state information... Done
                  All packages are up to date.

                  
                  Ich hab:
                  v16.16.0
                  
                  leider immer noch code 25.
                  
                  Was kann ich denn noch tun?
                  
                  Danke und Gruß
                  
                  Martin
                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @udo-2112 last edited by

                    @udo-2112

                    Bitte CodeTags sauber setzen.

                    Welche Meldungen kommen beim Update mit --debug-Option?

                    U 1 Reply Last reply Reply Quote 0
                    • U
                      udo-2112 @Thomas Braun last edited by

                      @thomas-braun
                      Hi,

                      Get:1 http://security.debian.org/debian-security bullseye-security InRelease [48,4 kB]
                      Get:2 http://deb.debian.org/debian bullseye InRelease [116 kB]                                       
                      Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44,1 kB]                                           
                      Get:4 https://deb.nodesource.com/node_16.x bullseye InRelease [4.586 B]              
                      Get:5 http://deb.debian.org/debian bullseye/main amd64 Packages [8.182 kB]           
                      Get:6 http://security.debian.org/debian-security bullseye-security/main amd64 Packages [175 kB]
                      Get:7 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [2.592 B]
                      Get:8 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages [774 B]
                      Fetched 8.573 kB in 5s (1.698 kB/s)                     
                      Reading package lists... Done
                      Building dependency tree... Done
                      Reading state information... Done
                      All packages are up to date.
                      
                      Reading package lists... Done
                      Building dependency tree... Done
                      Reading state information... Done
                      Calculating upgrade... Done
                      0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
                      
                      Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
                      Hit:2 http://deb.debian.org/debian bullseye InRelease                                               
                      Hit:3 http://deb.debian.org/debian bullseye-updates InRelease                                       
                      Hit:4 https://deb.nodesource.com/node_16.x bullseye InRelease                                       
                      Reading package lists... Done                     
                      Building dependency tree... Done
                      Reading state information... Done
                      All packages are up to date.
                      
                      /usr/bin/nodejs
                      /usr/bin/nodejs
                      /usr/bin/which
                      /usr/bin/node
                      /usr/bin/node
                      /usr/bin/which
                      /usr/bin/npm
                      /usr/bin/npm
                      /usr/bin/apt
                      /usr/bin/nodejs
                      
                      This upgrade of "discovery" will introduce the following changes:
                      ==========================================================================
                      -> 3.0.5:
                      Fix potential crash cases reported by Sentry
                      
                      -> 3.0.4:
                      Disable configuration settings for this adapter
                      ==========================================================================
                      
                      Would you like to upgrade discovery from @3.0.3 to @3.0.5 now? [(y)es, (n)o]: y
                      Update discovery from @3.0.3 to @3.0.5
                      NPM version: 8.11.0
                      Installing iobroker.discovery@3.0.5... (System call)
                      host.Poxdorf Cannot install iobroker.discovery@3.0.5: 217
                      

                      Danke und Gruß Martin

                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @udo-2112 last edited by Thomas Braun

                        @udo-2112 sagte in iobroker add ecovacs-deebot:

                        discovery

                        iobroker upgrade discovery --debug
                        
                        sudo ln -s /usr/bin/node /usr/bin/nodejs
                        uname -m && type -P nodejs node npm && nodejs -v && node -v && npm -v && whoami && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
                        

                        Bitte nix zurecht kopieren, sondern 1:1 alles was in der Konsole ein- wie ausgegeben wurde hier rein.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post

                        Support us

                        ioBroker
                        Community Adapters
                        Donate

                        708
                        Online

                        31.8k
                        Users

                        80.0k
                        Topics

                        1.3m
                        Posts

                        4
                        24
                        598
                        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