Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Nach Nodejs Update kein Adapter mehr updatebar

    NEWS

    • ioBroker 10-Jahres Community Treffen - ein kleiner ReCap

    • Tester für Responsive Initiative gesucht

    • 50€: Mach mit bei einer Smarthome Studie mit ioBroker!

    Nach Nodejs Update kein Adapter mehr updatebar

    This topic has been deleted. Only users with topic management privileges can see it.
    • Thomas Braun
      Thomas Braun Most Active @tilly last edited by

      @tilly sagte in Nach Nodejs Update kein Adapter mehr updatebar:

      ah jetzt verstanden

      Nur den root Login noch nicht.

      T 1 Reply Last reply Reply Quote 1
      • T
        tilly @Thomas Braun last edited by

        @thomas-braun

        nein weiß nicht was ich machen muss

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

          @tilly Dich NICHT, niemals, gar nicht, nicht kurz und nicht 'nur dafür mal' als root anmelden.

          Wechsel auf deinen Standarduser und nutze nur für systemnahe Aktionen sudo.

          1 Reply Last reply Reply Quote 1
          • Homoran
            Homoran Global Moderator Administrators @tilly last edited by

            @tilly log dich nicht als root ein!
            nimm den normalen User

            wurde dir auch so bei der Grundinstallation gesagt

            T 1 Reply Last reply Reply Quote 0
            • T
              tilly @Homoran last edited by

              @homoran

              ok mit einem anderen User ändert sich aber nichts

              user@iobroker-ubuntu:/opt/iobroker$ npm ls | grep -E 'github|ERR'
npm ERR! code ELSPROBLEMS
npm ERR! invalid: iobroker.alexa2@3.18.5 /opt/iobroker/node_modules/iobroker.alexa2

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/user/.npm/_logs/2022-07-21T18_14_04_807Z-debug-0.log


              user@iobroker-ubuntu:/opt/iobroker$ iobroker upgrade cloud --debug

This upgrade of "cloud" will introduce the following changes:
==========================================================================
-> 4.2.1:
Used new version of socket library.
==========================================================================

Would you like to upgrade cloud from @4.2.0 to @4.2.1 now? [(y)es, (n)o]: y
Update cloud from @4.2.0 to @4.2.1
NPM version: 8.11.0
Installing iobroker.cloud@4.2.1... (System call)
npm ERR! code ENOTEMPTY
npm ERR! syscall rename
npm ERR! path /opt/iobroker/node_modules/abab
npm ERR! dest /opt/iobroker/node_modules/.abab-bvmibCm3
npm ERR! errno -39
npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/abab' -> '/opt/iobroker/node_modules/.abab-bvmibCm3'

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2022-07-21T18_10_03_414Z-debug-0.log
host.iobroker-ubuntu Cannot install iobroker.cloud@4.2.1: 217
              Glasfaser Thomas Braun 3 Replies Last reply Reply Quote 0
              • Glasfaser
                Glasfaser @tilly last edited by

                @tilly sagte in Nach Nodejs Update kein Adapter mehr updatebar:

                ok mit einem anderen User ändert sich aber nichts

                Sollte auch nicht ...
                nur als Login root kann man viel kaputt machen

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

                  @tilly sagte in Nach Nodejs Update kein Adapter mehr updatebar:

                  npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/abab' -> '/opt/iobroker/node_modules/.abab-bvmibCm3'

                  sudo rm -rf /opt/iobroker/node_modules/.abab-bvmibCm3
                  1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @tilly last edited by

                    @tilly sagte in Nach Nodejs Update kein Adapter mehr updatebar:

                    rm -rf /opt/iobroker/node_modules/.abab-bvmibCm3

                    Weitere Verzeichnisse mit kryptischen Endungen analog dazu auch löschen.

                    1 Reply Last reply Reply Quote 0
                    • Homoran
                      Homoran Global Moderator Administrators @Glasfaser last edited by

                      @glasfaser sagte in Nach Nodejs Update kein Adapter mehr updatebar:

                      @tilly sagte in Nach Nodejs Update kein Adapter mehr updatebar:

                      ok mit einem anderen User ändert sich aber nichts

                      Sollte auch nicht ...
                      nur als Login root kann man viel kaputt machen

                      @tilly
                      Vielleicht solltest du mal

                      iobroker stop
iobroker fix
iobroker start

                      durchführen, um Rechteprobleme, die möglicherweise durch die Nutzung von root entstanden sind zu fixen.

                      Wird an deinem momentanen Problem auch nichts ändern, und auch nicht unbedingt alle Schäden (wenn vorhanden) beheben.

                      1 Reply Last reply Reply Quote 0
                      • T
                        tilly last edited by

                        das sind so viele, kann ich die wirklich alle löschen?

                        70f29d78-b11e-4d86-8b56-22e5f4f90b71-image.png

                        iobroker stop
iobroker fix
iobroker start

                        habe ich gemacht

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

                          @tilly sagte in Nach Nodejs Update kein Adapter mehr updatebar:

                          das sind so viele, kann ich die wirklich alle löschen?

                          Werden alle nach einem upgade Versuch angezeigt , was du da zeigst im Screenshot

                          npm ERR! ENOTEMPTY: directory not empty, rename
                          T 1 Reply Last reply Reply Quote 0
                          • T
                            tilly @Glasfaser last edited by

                            @glasfaser

                            nein ich lösche ein Verzeichnis und versuche erneut einen Adapter upzudaten.
                            Dann kommt wieder ein Ordner etc.

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

                              @tilly

                              In meinem System gibt es bis auf .bin keine Verzeichnisse, die mit Punkt anfangen. Ich vermute, die können dann alle weg.

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

                                @thomas-braun

                                ok dann sicher ich die Dateien mal und lösche dann alles

                                T 1 Reply Last reply Reply Quote 0
                                • T
                                  tilly @tilly last edited by

                                  jetzt tauchen noch mehr komische Verzeichnisse auf

                                  npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/has-binary2/node_modules/isarray' -> '/opt/iobroker/node_modules/has-binary2/node_modules/.isarray-z8HzvEK7'

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

                                    @tilly

                                    Das selbe in Grün...

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

                                      @thomas-braun

                                      hab nun alle Dateien in @verzeichnissen mit kryptischen Endungen gelöscht
                                      jetzt folgendes

                                      user@iobroker-ubuntu:/opt/iobroker$ iobroker upgrade cloud --debug

This upgrade of "cloud" will introduce the following changes:
==========================================================================
-> 4.2.1:
Used new version of socket library.
==========================================================================

Would you like to upgrade cloud from @4.2.0 to @4.2.1 now? [(y)es, (n)o]: y
Update cloud from @4.2.0 to @4.2.1
NPM version: 8.11.0
Installing iobroker.cloud@4.2.1... (System call)
npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies.
npm WARN deprecated crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
npm WARN deprecated node-xmpp-tls-connect@1.0.1: this package is deprecated please use https://github.com/xmppjs/xmpp.js
npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated node-xmpp-core@5.0.9: this package is deprecated please use https://github.com/xmppjs/xmpp.js
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained.
npm WARN deprecated multer@1.4.4: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated uuid@3.3.2: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated appium-logger@2.1.0: Moved into appium-support
npm WARN deprecated node-xmpp-client@3.2.0: this package is deprecated please use https://www.npmjs.com/package/@xmpp/client
npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size
npm WARN deprecated core-js@1.2.7: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code ENOTEMPTY
npm ERR! syscall rename
npm ERR! path /opt/iobroker/node_modules/node-red-node-email/node_modules/encoding-japanese/src
npm ERR! dest /opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src
npm ERR! errno -39
npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/node-red-node-email/node_modules/encoding-japanese/src' -> '/opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src'

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/iobroker/.npm/_logs/2022-07-21T19_54_23_300Z-debug-0.log
host.iobroker-ubuntu Cannot install iobroker.cloud@4.2.1: 217
                                      Thomas Braun 1 Reply Last reply Reply Quote 0
                                      • Thomas Braun
                                        Thomas Braun Most Active @tilly last edited by

                                        @tilly sagte in Nach Nodejs Update kein Adapter mehr updatebar:

                                        rm -rf /opt/iobroker/node_modules/.node-red-node-email-1lk8B7Gi/node_modules/encoding-japanese/src

                                        Das Spiel kennst du ja schon.

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

                                          @thomas-braun

                                          ich wollte gerade Feierabend machen, starte iobroker und wollte morgen weiter machen.
                                          auf einmal sind die ganzen gelöschten Dateien(z.B. /opt/iobroker/node_modules/.abbrev-5eNud0FY) wieder da?

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

                                            @tilly

                                            Lief der iobroker eigentlich die ganze Zeit? Knips den aus, wenn du am npm tree bastelst.

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

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            837
                                            Online

                                            30.4k
                                            Users

                                            76.7k
                                            Topics

                                            1.2m
                                            Posts

                                            nodejs update adaper update
                                            6
                                            67
                                            3146
                                            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