Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Täglich Fehler im Log - connect ECONNREFUSED 127.0.0.1:9001

    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

    Täglich Fehler im Log - connect ECONNREFUSED 127.0.0.1:9001

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

      @thomas-braun
      Okay, danke für die Hilfe.

      Wie muss ich jetzt vorgehen, gibt es da eine Reihenfolge die ich beachten muss, nicht dass ich mir das System zerschiesse!?

      Das mit dem ordentlichen herunterfahren bekomme ich hin.
      Den Fix mit dem Fehler 25 auch.
      Muss ich etwas beachten um auf nodejs 18 zu updaten?
      Das mit dem falschen Repo verstehe ich nicht, was muss ich da genau tun?

      Grüße

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

        @derroadrunner sagte in Täglich Fehler im Log - connect ECONNREFUSED 127.0.0.1:9001:

        nicht dass ich mir das System zerschiesse!?

        Da musst du nix mehr machen, das ist schon (mindestens) schwer angeschossen.

        Ich würde das vermutlich flugs neuaufsetzen.

        Wenn du das nicht willst, fang mit den Repos an.

        sudo apt update

        sagt?

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

          @thomas-braun
          roadrunner@piroadrunner:~ $ sudo apt update
          Hit:1 http://deb.debian.org/debian bullseye InRelease
          Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
          Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
          Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
          Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
          Hit:6 https://packages.grafana.com/oss/deb stable InRelease
          Get:7 https://repos.influxdata.com/debian stretch InRelease [7,030 B]
          Err:7 https://repos.influxdata.com/debian stretch InRelease
          The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
          Reading package lists... Done
          W: GPG error: https://repos.influxdata.com/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E
          E: The repository 'https://repos.influxdata.com/debian stretch InRelease' is not signed.
          N: Updating from such a repository can't be done securely, and is therefore disabled by default.
          N: See apt-secure(8) manpage for repository creation and user configuration details.

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

            @derroadrunner

            sudo apt-key del 05CE 1508 5FC0 9D18 E99E  FB22 684A 14CF 2582 E0C5
rm /etc/apt/sources.list.d/infl*
wget -q -O - https://repos.influxdata.com/influxdb.key | sudo gpg --dearmor -o /usr/share/keyrings/influxdb.gpg
export DISTRIB_ID=$(lsb_release -si); export DISTRIB_CODENAME=$(lsb_release -sc)
echo "deb [signed-by=/usr/share/keyrings/influxdb.gpg] https://repos.influxdata.com/${DISTRIB_ID,,} ${DISTRIB_CODENAME} stable" | sudo tee /etc/apt/sources.list.d/influxdb.list > /dev/null

            Dann nochmal

            sudo apt update

            Bitte für Text aus der Konsole die CodeTags verwenden. Danke.

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

              @thomas-braun

              roadrunner@piroadrunner:~ $ sudo apt-key del 05CE 1508 5FC0 9D18 E99E  FB22 684A 14CF 2582 E0C5
rm /etc/apt/sources.list.d/infl*
wget -q -O - https://repos.influxdata.com/influxdb.key | sudo gpg --dearmor -o /usr/share/keyrings/influxdb.gpg
export DISTRIB_ID=$(lsb_release -si); export DISTRIB_CODENAME=$(lsb_release -sc)
echo "deb [signed-by=/usr/share/keyrings/influxdb.gpg] https://repos.influxdata.com/${DISTRIB_ID,,} ${DISTRIB_CODENAME} stable" | sudo tee /etc/apt/sources.list.d/influxdb.list > /dev/null
Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
gpg: key "E0C5" not found: Not found
gpg: E0C5: delete key failed: Not found
rm: remove write-protected regular file '/etc/apt/sources.list.d/influxdb.list'? y
rm: cannot remove '/etc/apt/sources.list.d/influxdb.list': Permission denied
File '/usr/share/keyrings/influxdb.gpg' exists. Overwrite? (y/N) y
roadrunner@piroadrunner:~ $ sudo apt update
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 http://archive.raspberrypi.org/debian bullseye InRelease
Get:5 https://repos.influxdata.com/debian bullseye InRelease [7,031 B]
Hit:6 https://packages.grafana.com/oss/deb stable InRelease
Hit:7 https://deb.nodesource.com/node_16.x bullseye 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
Reading package lists... Done
W: 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
E: The repository 'https://repos.influxdata.com/debian bullseye InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
roadrunner@piroadrunner:~ $
              Thomas Braun 1 Reply Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @derroadrunner last edited by

                @derroadrunner

                ls -lAh /etc/apt/sources.list.d/
                D 1 Reply Last reply Reply Quote 0
                • D
                  derroadrunner @Thomas Braun last edited by

                  @thomas-braun

                  roadrunner@piroadrunner:~ $ ls -lAh /etc/apt/sources.list.d/
total 16K
-rw-r--r-- 1 root root  53 Feb  5 00:20 grafana.list
-rw-r--r-- 1 root root 101 Apr  1 21:59 influxdb.list
-rw-r--r-- 1 root root 208 Feb  4 22:58 nodesource.list
-rw-r--r-- 1 root root 191 Sep 22  2022 raspi.list
                  Thomas Braun 1 Reply Last reply Reply Quote 0
                  • Thomas Braun
                    Thomas Braun Most Active @derroadrunner last edited by

                    @derroadrunner sagte in Täglich Fehler im Log - connect ECONNREFUSED 127.0.0.1:9001:

                    cat /etc/apt/sources.list.d/influxdb.list
                    D 1 Reply Last reply Reply Quote 0
                    • D
                      derroadrunner @Thomas Braun last edited by

                      @thomas-braun

                      roadrunner@piroadrunner:~ $ cat /etc/apt/sources.list.d/influxdb.list
deb [signed-by=/usr/share/keyrings/influxdb.gpg] https://repos.influxdata.com/debian bullseye stable
                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @derroadrunner last edited by Thomas Braun

                        @derroadrunner

                        Ändere die Zeile ab, die muss so aussehen:

                        
deb [signed-by=/usr/share/keyrings/influxdb.gpg] https://repos.influxdata.com/debian stable main
                        D 1 Reply Last reply Reply Quote 0
                        • D
                          derroadrunner @Thomas Braun last edited by

                          @thomas-braun
                          Jetzt geht es schon los
                          Was muss ich da genau tun?

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

                            @derroadrunner

                            Mit einem Editor wie nano die Datei bearbeiten.
                            Oder damit:

                            sudo rm /etc/apt/sources.list.d/infl*
wget -q https://repos.influxdata.com/influxdata-archive_compat.key
echo '393e8779c89ac8d958f81f942f9ad7fb82a25e133faddaf92e15b16e6ac9ce4c influxdata-archive_compat.key' | sha256sum -c && cat influxdata-archive_compat.key | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/influxdata-archive_compat.gpg > /dev/null
echo 'deb [signed-by=/etc/apt/trusted.gpg.d/influxdata-archive_compat.gpg] https://repos.influxdata.com/debian stable main' | sudo tee /etc/apt/sources.list.d/influxdata.list
sudo apt update
                            D 1 Reply Last reply Reply Quote 0
                            • D
                              derroadrunner @Thomas Braun last edited by

                              @thomas-braun

                              roadrunner@piroadrunner:~ $ sudo rm /etc/apt/sources.list.d/infl*
wget -q https://repos.influxdata.com/influxdata-archive_compat.key
echo '393e8779c89ac8d958f81f942f9ad7fb82a25e133faddaf92e15b16e6ac9ce4c influxdata-archive_compat.key' | sha256sum -c && cat influxdata-archive_compat.key | gpg --dearmor | sudo tee /etc/apt/trusted.gpg.d/influxdata-archive_compat.gpg > /dev/null
echo 'deb [signed-by=/etc/apt/trusted.gpg.d/influxdata-archive_compat.gpg] https://repos.influxdata.com/debian stable main' | sudo tee /etc/apt/sources.list.d/influxdata.list
sudo apt update
influxdata-archive_compat.key: OK
deb [signed-by=/etc/apt/trusted.gpg.d/influxdata-archive_compat.gpg] https://repos.influxdata.com/debian stable main
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye-updates InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Get:5 https://repos.influxdata.com/debian stable InRelease [6,883 B]
Hit:6 https://deb.nodesource.com/node_16.x bullseye InRelease
Hit:7 https://packages.grafana.com/oss/deb stable InRelease
Get:8 https://repos.influxdata.com/debian stable/main armhf Packages [2,218 B]
Get:9 https://repos.influxdata.com/debian stable/main arm64 Packages [3,834 B]
Fetched 12.9 kB in 4s (3,644 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
33 packages can be upgraded. Run 'apt list --upgradable' to see them.
roadrunner@piroadrunner:~ $ apt list --upgradable
Listing... Done
grafana/stable 9.4.7 arm64 [upgradable from: 9.4.1]
influxdb/unknown 1.8.10-1 arm64 [upgradable from: 1.6.7~rc0-1+b5]
libcamera-apps/stable 0~git20230301+54a781d-1 arm64 [upgradable from: 0~git20230125+9f08463-1]
libcamera-tools/stable 0~git20230302+923f5d70-1 arm64 [upgradable from: 0~git20230124+9b860a66-1]
libcamera0/stable 0~git20230302+923f5d70-1 arm64 [upgradable from: 0~git20230124+9b860a66-1]
libvlc-bin/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
libvlc5/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
libvlccore9/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
linux-libc-dev/stable 1:1.20230317-1 arm64 [upgradable from: 1:1.20230106-1]
python3-libcamera/stable 0~git20230302+923f5d70-1 arm64 [upgradable from: 0~git20230124+9b860a66-1]
python3-picamera2/stable,stable 0.3.9-1 all [upgradable from: 0.3.8-1]
python3-v4l2/stable,stable 0.3.2-1 all [upgradable from: 0.3.1-1]
raspberrypi-bootloader/stable 1:1.20230317-1 arm64 [upgradable from: 1:1.20230106-1]
raspberrypi-kernel/stable 1:1.20230317-1 arm64 [upgradable from: 1:1.20230106-1]
realvnc-vnc-server/stable 7.0.1.49073 arm64 [upgradable from: 6.10.1.47571]
rp-prefapps/stable 0.46 arm64 [upgradable from: 0.45]
tzdata/stable-updates,stable-updates 2021a-1+deb11u9 all [upgradable from: 2021a-1+deb11u8]
vlc-bin/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
vlc-data/stable,stable 3.0.18-0+rpt3+deb11u1 all [upgradable from: 3.0.18-0+rpt2+deb11u1]
vlc-l10n/stable,stable 3.0.18-0+rpt3+deb11u1 all [upgradable from: 3.0.18-0+rpt2+deb11u1]
vlc-plugin-access-extra/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
vlc-plugin-base/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
vlc-plugin-notify/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
vlc-plugin-qt/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
vlc-plugin-samba/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
vlc-plugin-skins2/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
vlc-plugin-video-output/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
vlc-plugin-video-splitter/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
vlc-plugin-visualization/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
vlc/stable 3.0.18-0+rpt3+deb11u1 arm64 [upgradable from: 3.0.18-0+rpt2+deb11u1]
xserver-common/stable,stable 2:1.20.11-1+rpt3+deb11u6 all [upgradable from: 2:1.20.11-1+rpt1+deb11u5]
xserver-xorg-core/stable 2:1.20.11-1+rpt3+deb11u6 arm64 [upgradable from: 2:1.20.11-1+rpt1+deb11u5]
xwayland/stable 2:1.20.11-1+rpt3+deb11u6 arm64 [upgradable from: 2:1.20.11-1+rpt1+deb11u5]
roadrunner@piroadrunner:~ $
                              Thomas Braun 1 Reply Last reply Reply Quote 0
                              • Thomas Braun
                                Thomas Braun Most Active @derroadrunner last edited by Thomas Braun

                                @derroadrunner

                                Dann ran da.

                                sudo apt full-upgrade
sudo reboot

                                Und Server werden OHNE graphische Oberfläche betrieben...
                                Ist vermutlich ein Überrest von einer Installation mit Desktop.

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

                                  @thomas-braun
                                  Die graphische Oberfläche hatte ich eigentlich ausgeschaltet. Das Check ich nochmal

                                  jetzt habe ich statt full upgrade ___ sudo apt upgrade eingegeben, ist das ein Problem?

                                  Er steht auch seit 5 min. hier

                                  Adding 'diversion of /boot/fixup4db.dat to /usr/share/rpikernelhack/fixup4db.dat by rpikernelhack'
Adding 'diversion of /boot/fixup4x.dat to /usr/share/rpikernelhack/fixup4x.dat by rpikernelhack'
Adding 'diversion of /boot/LICENCE.broadcom to /usr/share/rpikernelhack/LICENCE.broadcom by rpikernelhack'
Unpacking raspberrypi-bootloader (1:1.20230317-1) over (1:1.20230106-1) ...
Preparing to unpack .../21-realvnc-vnc-server_7.0.1.49073_arm64.deb ...
Unpacking realvnc-vnc-server (7.0.1.49073) over (6.10.1.47571) ...

Progress: [ 32%] [########################........................
                                  Thomas Braun 1 Reply Last reply Reply Quote 0
                                  • Thomas Braun
                                    Thomas Braun Most Active @derroadrunner last edited by Thomas Braun

                                    @derroadrunner sagte in Täglich Fehler im Log - connect ECONNREFUSED 127.0.0.1:9001:

                                    Die graphische Oberfläche hatte ich eigentlich ausgeschaltet.

                                    Ja, die ist ausgeschaltet, die entsprechenden Pakete schleppst du natürlich dennoch weiter.

                                    ist das ein Problem?

                                    Nein. Ist meistens bei einfachen updates nicht relevant. Kannste aber mit

                                    sudo apt full-upgrade

                                    noch nachholen. Da war ein Kernel-Upgrade dabei, hier unbedingt die Kiste neustarten.

                                    sudo reboot

                                    Er steht auch seit 5 min.

                                    Abwarten... Mit 1GB RAM musst du halt Geduld haben.

                                    D 2 Replies Last reply Reply Quote 0
                                    • D
                                      derroadrunner @Thomas Braun last edited by

                                      @thomas-braun
                                      Okay, dann werde ich den Stromstecker noch nicht abziehen 😁
                                      Wenn das durchgelaufen ist, gebe ich Bescheid, wie der Stand ist.

                                      Vielen Dank schon mal

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

                                        @thomas-braun
                                        Hallo, so sieht es jetzt nach dem update aus

                                        roadrunner@piroadrunner:~ $ sudo apt update
Hit:1 http://deb.debian.org/debian bullseye InRelease
Get:2 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB]
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:5 https://repos.influxdata.com/debian stable InRelease
Get:6 https://packages.grafana.com/oss/deb stable InRelease [5,983 B]
Hit:7 https://deb.nodesource.com/node_16.x bullseye InRelease
Fetched 50.0 kB in 4s (13.1 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
                                        Thomas Braun 1 Reply Last reply Reply Quote 0
                                        • Thomas Braun
                                          Thomas Braun Most Active @derroadrunner last edited by

                                          @derroadrunner

                                          Ja, dann kannst du jetzt nodejs auf die derzeitig empfohlene Version 18 bringen.

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

                                            @thomas-braun
                                            Nehme ich da am Besten deine Anleitung?

                                            Teil 1.1 Node-Upgrade/ Wechsel der nodejs-Version:

                                            Thomas Braun 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

                                            965
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            2
                                            30
                                            487
                                            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