Skip to content
  • Home
  • 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

Community Forum

donate donate
  1. ioBroker Community Home
  2. Deutsch
  3. Off Topic
  4. Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter

NEWS

  • UPDATE 31.10.: Amazon Alexa - ioBroker Skill läuft aus ?
    apollon77A
    apollon77
    48
    3
    8.5k

  • Monatsrückblick – September 2025
    BluefoxB
    Bluefox
    13
    1
    2.1k

  • Neues Video "KI im Smart Home" - ioBroker plus n8n
    BluefoxB
    Bluefox
    16
    1
    2.7k

Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter

Geplant Angeheftet Gesperrt Verschoben Off Topic
33 Beiträge 5 Kommentatoren 3.5k Aufrufe 5 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.
  • Thomas BraunT Thomas Braun

    @smizi

    Bitte VOLLSTÄNDIG.
    Inkl. erstem LogIn Prompt und der Eingabe sowie dem abschließenden LogIn Prompt, damit man sieht wo du da wie unterwegs bist.

    SmiziS Offline
    SmiziS Offline
    Smizi
    schrieb am zuletzt editiert von
    #23

    @thomas-braun ähm ja, aber da ist doch nicht mehr...```
    pi@raspberrypi:~ $ sudo apt install --reinstall nodejs
    Reading package lists... Done
    Building dependency tree... Done
    Reading state information... Done
    0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
    Need to get 28.1 MB of archives.
    After this operation, 0 B of additional disk space will be used.
    Get:1 https://deb.nodesource.com/node_18.x bullseye/main arm64 nodejs arm64 18.17.1-deb-1nodesource1 [28.1 MB]
    Fetched 28.1 MB in 3s (10.1 MB/s)
    (Reading database ... 59608 files and directories currently installed.)
    Preparing to unpack .../nodejs_18.17.1-deb-1nodesource1_arm64.deb ...
    Unpacking nodejs (18.17.1-deb-1nodesource1) over (18.17.1-deb-1nodesource1) ...
    Setting up nodejs (18.17.1-deb-1nodesource1) ...
    Processing triggers for man-db (2.9.4-2) ...

    Thomas BraunT 1 Antwort Letzte Antwort
    0
    • SmiziS Smizi

      @thomas-braun ähm ja, aber da ist doch nicht mehr...```
      pi@raspberrypi:~ $ sudo apt install --reinstall nodejs
      Reading package lists... Done
      Building dependency tree... Done
      Reading state information... Done
      0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
      Need to get 28.1 MB of archives.
      After this operation, 0 B of additional disk space will be used.
      Get:1 https://deb.nodesource.com/node_18.x bullseye/main arm64 nodejs arm64 18.17.1-deb-1nodesource1 [28.1 MB]
      Fetched 28.1 MB in 3s (10.1 MB/s)
      (Reading database ... 59608 files and directories currently installed.)
      Preparing to unpack .../nodejs_18.17.1-deb-1nodesource1_arm64.deb ...
      Unpacking nodejs (18.17.1-deb-1nodesource1) over (18.17.1-deb-1nodesource1) ...
      Setting up nodejs (18.17.1-deb-1nodesource1) ...
      Processing triggers for man-db (2.9.4-2) ...

      Thomas BraunT Online
      Thomas BraunT Online
      Thomas Braun
      Most Active
      schrieb am zuletzt editiert von Thomas Braun
      #24

      @smizi sagte in Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter:

      Setting up nodejs (18.17.1-deb-1nodesource1) ...
      Processing triggers for man-db (2.9.4-2) ...

      Danach geht es doch noch weiter. 100%ig. Und wenn es nur die neue Eingabezeile ist. Die möchte ich aber sehen, damit ich weiß bis wo das mit welchen Meldungen gelaufen ist.

      Linux-Werkzeugkasten:
      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
      NodeJS Fixer Skript:
      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

      SmiziS 1 Antwort Letzte Antwort
      0
      • Thomas BraunT Thomas Braun

        @smizi sagte in Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter:

        Setting up nodejs (18.17.1-deb-1nodesource1) ...
        Processing triggers for man-db (2.9.4-2) ...

        Danach geht es doch noch weiter. 100%ig. Und wenn es nur die neue Eingabezeile ist. Die möchte ich aber sehen, damit ich weiß bis wo das mit welchen Meldungen gelaufen ist.

        SmiziS Offline
        SmiziS Offline
        Smizi
        schrieb am zuletzt editiert von
        #25

        @thomas-braun leider nein, das ist alles...sorry```
        pi@raspberrypi:~ $ sudo apt install --reinstall nodejs
        Reading package lists... Done
        Building dependency tree... Done
        Reading state information... Done
        0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
        Need to get 28.1 MB of archives.
        After this operation, 0 B of additional disk space will be used.
        Get:1 https://deb.nodesource.com/node_18.x bullseye/main arm64 nodejs arm64 18.17.1-deb-1nodesource1 [28.1 MB]
        Fetched 28.1 MB in 3s (10.1 MB/s)
        (Reading database ... 59608 files and directories currently installed.)
        Preparing to unpack .../nodejs_18.17.1-deb-1nodesource1_arm64.deb ...
        Unpacking nodejs (18.17.1-deb-1nodesource1) over (18.17.1-deb-1nodesource1) ...
        Setting up nodejs (18.17.1-deb-1nodesource1) ...
        Processing triggers for man-db (2.9.4-2) ...
        pi@raspberrypi:~ $

        Thomas BraunT 1 Antwort Letzte Antwort
        0
        • SmiziS Smizi

          @thomas-braun leider nein, das ist alles...sorry```
          pi@raspberrypi:~ $ sudo apt install --reinstall nodejs
          Reading package lists... Done
          Building dependency tree... Done
          Reading state information... Done
          0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
          Need to get 28.1 MB of archives.
          After this operation, 0 B of additional disk space will be used.
          Get:1 https://deb.nodesource.com/node_18.x bullseye/main arm64 nodejs arm64 18.17.1-deb-1nodesource1 [28.1 MB]
          Fetched 28.1 MB in 3s (10.1 MB/s)
          (Reading database ... 59608 files and directories currently installed.)
          Preparing to unpack .../nodejs_18.17.1-deb-1nodesource1_arm64.deb ...
          Unpacking nodejs (18.17.1-deb-1nodesource1) over (18.17.1-deb-1nodesource1) ...
          Setting up nodejs (18.17.1-deb-1nodesource1) ...
          Processing triggers for man-db (2.9.4-2) ...
          pi@raspberrypi:~ $

          Thomas BraunT Online
          Thomas BraunT Online
          Thomas Braun
          Most Active
          schrieb am zuletzt editiert von
          #26

          @smizi sagte in Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter:

          1 not upgraded.

          Welches Paket ist das?

          sudo apt update
          sudo apt full-upgrade
          

          Linux-Werkzeugkasten:
          https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
          NodeJS Fixer Skript:
          https://forum.iobroker.net/topic/68035/iob-node-fix-skript
          iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

          SmiziS 1 Antwort Letzte Antwort
          0
          • Thomas BraunT Thomas Braun

            @smizi sagte in Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter:

            1 not upgraded.

            Welches Paket ist das?

            sudo apt update
            sudo apt full-upgrade
            
            SmiziS Offline
            SmiziS Offline
            Smizi
            schrieb am zuletzt editiert von
            #27

            @thomas-braun sagte in Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter:

            sudo apt full-upgrade

            Sorry, ich verstehe nicht ganz:

            pi@raspberrypi:~ $ sudo apt update
            Hit:1 http://deb.debian.org/debian bullseye InRelease
            Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
            Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
            Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
            Get:5 https://repos.influxdata.com/debian bullseye InRelease [7,040 B]
            Hit:6 https://deb.nodesource.com/node_18.x bullseye InRelease
            Hit:7 https://apt.grafana.com stable InRelease
            Err:5 https://repos.influxdata.com/debian bullseye InRelease
            The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
            Fetched 7,040 B in 2s (4,558 B/s)
            Reading package lists... Done
            Building dependency tree... Done
            Reading state information... Done
            1 package can be upgraded. Run 'apt list --upgradable' to see it.
            W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
            W: Failed to fetch https://repos.influxdata.com/debian/dists/bullseye/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
            W: Some index files failed to download. They have been ignored, or old ones used instead.
            pi@raspberrypi:~ $ sudo apt full-upgrade
            Reading package lists... Done
            Building dependency tree... Done
            Reading state information... Done
            Calculating upgrade... Done
            The following packages will be upgraded:
            grafana
            1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
            Need to get 80.4 MB of archives.
            After this operation, 10.1 MB of additional disk space will be used.
            Do you want to continue? [Y/n] Y
            Get:1 https://apt.grafana.com stable/main arm64 grafana arm64 10.0.3 [80.4 MB]
            Fetched 80.4 MB in 10s (7,797 kB/s)
            Reading changelogs... Done
            (Reading database ... 59608 files and directories currently installed.)
            Preparing to unpack .../grafana_10.0.3_arm64.deb ...
            Unpacking grafana (10.0.3) over (9.3.2) ...
            Setting up grafana (10.0.3) ...
            Installing new version of config file /etc/init.d/grafana-server ...
            Installing new version of config file /usr/lib/systemd/system/grafana-server.service ...
            Restarting grafana-server service... OK
            pi@raspberrypi:~ $

            DJMarc75D Thomas BraunT 2 Antworten Letzte Antwort
            0
            • SmiziS Smizi

              @thomas-braun sagte in Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter:

              sudo apt full-upgrade

              Sorry, ich verstehe nicht ganz:

              pi@raspberrypi:~ $ sudo apt update
              Hit:1 http://deb.debian.org/debian bullseye InRelease
              Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
              Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
              Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
              Get:5 https://repos.influxdata.com/debian bullseye InRelease [7,040 B]
              Hit:6 https://deb.nodesource.com/node_18.x bullseye InRelease
              Hit:7 https://apt.grafana.com stable InRelease
              Err:5 https://repos.influxdata.com/debian bullseye InRelease
              The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
              Fetched 7,040 B in 2s (4,558 B/s)
              Reading package lists... Done
              Building dependency tree... Done
              Reading state information... Done
              1 package can be upgraded. Run 'apt list --upgradable' to see it.
              W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
              W: Failed to fetch https://repos.influxdata.com/debian/dists/bullseye/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
              W: Some index files failed to download. They have been ignored, or old ones used instead.
              pi@raspberrypi:~ $ sudo apt full-upgrade
              Reading package lists... Done
              Building dependency tree... Done
              Reading state information... Done
              Calculating upgrade... Done
              The following packages will be upgraded:
              grafana
              1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
              Need to get 80.4 MB of archives.
              After this operation, 10.1 MB of additional disk space will be used.
              Do you want to continue? [Y/n] Y
              Get:1 https://apt.grafana.com stable/main arm64 grafana arm64 10.0.3 [80.4 MB]
              Fetched 80.4 MB in 10s (7,797 kB/s)
              Reading changelogs... Done
              (Reading database ... 59608 files and directories currently installed.)
              Preparing to unpack .../grafana_10.0.3_arm64.deb ...
              Unpacking grafana (10.0.3) over (9.3.2) ...
              Setting up grafana (10.0.3) ...
              Installing new version of config file /etc/init.d/grafana-server ...
              Installing new version of config file /usr/lib/systemd/system/grafana-server.service ...
              Restarting grafana-server service... OK
              pi@raspberrypi:~ $

              DJMarc75D Offline
              DJMarc75D Offline
              DJMarc75
              schrieb am zuletzt editiert von
              #28

              @smizi bitte alles immer in Codetags posten

              Lehrling seit 1975 !!!
              Beitrag geholfen ? dann gerne ein upvote rechts unten im Beitrag klicken ;)
              https://forum.iobroker.net/topic/51555/hinweise-f%C3%BCr-gute-forenbeitr%C3%A4ge

              SmiziS 1 Antwort Letzte Antwort
              0
              • SmiziS Smizi

                @thomas-braun sagte in Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter:

                sudo apt full-upgrade

                Sorry, ich verstehe nicht ganz:

                pi@raspberrypi:~ $ sudo apt update
                Hit:1 http://deb.debian.org/debian bullseye InRelease
                Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
                Hit:3 http://archive.raspberrypi.org/debian bullseye InRelease
                Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
                Get:5 https://repos.influxdata.com/debian bullseye InRelease [7,040 B]
                Hit:6 https://deb.nodesource.com/node_18.x bullseye InRelease
                Hit:7 https://apt.grafana.com stable InRelease
                Err:5 https://repos.influxdata.com/debian bullseye InRelease
                The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
                Fetched 7,040 B in 2s (4,558 B/s)
                Reading package lists... Done
                Building dependency tree... Done
                Reading state information... Done
                1 package can be upgraded. Run 'apt list --upgradable' to see it.
                W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
                W: Failed to fetch https://repos.influxdata.com/debian/dists/bullseye/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
                W: Some index files failed to download. They have been ignored, or old ones used instead.
                pi@raspberrypi:~ $ sudo apt full-upgrade
                Reading package lists... Done
                Building dependency tree... Done
                Reading state information... Done
                Calculating upgrade... Done
                The following packages will be upgraded:
                grafana
                1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
                Need to get 80.4 MB of archives.
                After this operation, 10.1 MB of additional disk space will be used.
                Do you want to continue? [Y/n] Y
                Get:1 https://apt.grafana.com stable/main arm64 grafana arm64 10.0.3 [80.4 MB]
                Fetched 80.4 MB in 10s (7,797 kB/s)
                Reading changelogs... Done
                (Reading database ... 59608 files and directories currently installed.)
                Preparing to unpack .../grafana_10.0.3_arm64.deb ...
                Unpacking grafana (10.0.3) over (9.3.2) ...
                Setting up grafana (10.0.3) ...
                Installing new version of config file /etc/init.d/grafana-server ...
                Installing new version of config file /usr/lib/systemd/system/grafana-server.service ...
                Restarting grafana-server service... OK
                pi@raspberrypi:~ $

                Thomas BraunT Online
                Thomas BraunT Online
                Thomas Braun
                Most Active
                schrieb am zuletzt editiert von
                #29

                @smizi

                Okay, war grafana.

                Dann fällt mir aber auch nix mehr dazu ein.

                Linux-Werkzeugkasten:
                https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                NodeJS Fixer Skript:
                https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                SmiziS 1 Antwort Letzte Antwort
                0
                • DJMarc75D DJMarc75

                  @smizi bitte alles immer in Codetags posten

                  SmiziS Offline
                  SmiziS Offline
                  Smizi
                  schrieb am zuletzt editiert von
                  #30

                  @djmarc75 sagte in Fehler /usr/lib/node_modules/npm/lib/cli.js:35 info-Adapter:

                  @smizi bitte alles immer in Codetags posten

                  Sorry, mein Fehler :confused:

                  1 Antwort Letzte Antwort
                  0
                  • Thomas BraunT Thomas Braun

                    @smizi

                    Okay, war grafana.

                    Dann fällt mir aber auch nix mehr dazu ein.

                    SmiziS Offline
                    SmiziS Offline
                    Smizi
                    schrieb am zuletzt editiert von
                    #31

                    @thomas-braun
                    kann ich noch irgendwas tuen, oder was wäre deine Empfehlung?

                    Gibt es einen bezahlbaren Service via IOB-Projkt, wo ggfs. nochwas geht?

                    Thomas BraunT 1 Antwort Letzte Antwort
                    0
                    • SmiziS Smizi

                      @thomas-braun
                      kann ich noch irgendwas tuen, oder was wäre deine Empfehlung?

                      Gibt es einen bezahlbaren Service via IOB-Projkt, wo ggfs. nochwas geht?

                      Thomas BraunT Online
                      Thomas BraunT Online
                      Thomas Braun
                      Most Active
                      schrieb am zuletzt editiert von
                      #32

                      @smizi

                      Installier es flugs neu und lass diesmal unnötigen Kram von der Kiste.
                      Backup des ioBrokers hast du ja.

                      Linux-Werkzeugkasten:
                      https://forum.iobroker.net/topic/42952/der-kleine-iobroker-linux-werkzeugkasten
                      NodeJS Fixer Skript:
                      https://forum.iobroker.net/topic/68035/iob-node-fix-skript
                      iob_diag: curl -sLf -o diag.sh https://iobroker.net/diag.sh && bash diag.sh

                      SmiziS 1 Antwort Letzte Antwort
                      0
                      • Thomas BraunT Thomas Braun

                        @smizi

                        Installier es flugs neu und lass diesmal unnötigen Kram von der Kiste.
                        Backup des ioBrokers hast du ja.

                        SmiziS Offline
                        SmiziS Offline
                        Smizi
                        schrieb am zuletzt editiert von
                        #33

                        @thomas-braun hm, ok und Danke!

                        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

                        758

                        Online

                        32.4k

                        Benutzer

                        81.5k

                        Themen

                        1.3m

                        Beiträge
                        Community
                        Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen | Einwilligungseinstellungen
                        ioBroker Community 2014-2025
                        logo
                        • Anmelden

                        • Du hast noch kein Konto? Registrieren

                        • Anmelden oder registrieren, um zu suchen
                        • Erster Beitrag
                          Letzter Beitrag
                        0
                        • Home
                        • Aktuell
                        • Tags
                        • Ungelesen 0
                        • Kategorien
                        • Unreplied
                        • Beliebt
                        • GitHub
                        • Docu
                        • Hilfe