Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. Geöst Alexa2 Fehler nach Pi-Hole DHCP Server geändert

    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

    Geöst Alexa2 Fehler nach Pi-Hole DHCP Server geändert

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

      @marcel-drzal

      Du hast kein Problem mit dem apexa2-Adapter, da ist grundsätzlich der Wurm in deinem Netzwerk-Setup.

      Dein influx-Repo läuft auf Buster, der Rest auf Bullseye
      Pass das an.

      ? 1 Reply Last reply Reply Quote 0
      • ?
        A Former User @Thomas Braun last edited by

        @thomas-braun was kann ich machen?

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

          @marcel-drzal

          Den Netzwerk richtig einstellen.
          Bin aber kein Netzwerk -Guru.

          Codierknecht ? 2 Replies Last reply Reply Quote 0
          • Codierknecht
            Codierknecht Developer Most Active @Thomas Braun last edited by

            @thomas-braun sagte in Alexa2 Fehler nach Pi-Hole DHCP Server geändert:

            Den Netzwerk richtig einstellen.
            Bin aber kein Netzwerk -Guru.

            Ich auch nicht 😞

            Aber sowas wie

            failure resolving 'xxx'

            Klingt nach Problemen mit der Namensauflösung und DNS.

            ? 1 Reply Last reply Reply Quote 0
            • ?
              A Former User @Thomas Braun last edited by

              @thomas-braun ich habe den DNS Server neu installiert und ne neue DNS eingestellt
              Soll ich mal Fix

              Thomas Braun 1 Reply Last reply Reply Quote 0
              • ?
                A Former User @Codierknecht last edited by

                @codierknecht ja habe den DNS Server eine IP gegeben im Router

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

                  @marcel-drzal

                  Ich weiß nicht was du da genau wie und wo eingestellt hast.
                  War aber offenbar falsch und die Namensauflösung funktioniert nicht mehr.

                  ? 2 Replies Last reply Reply Quote 0
                  • ?
                    A Former User @Thomas Braun last edited by

                    @thomas-braun

                    was kann ich da machen? Habe schon Fix versucht. geht auch nicht

                    
marcel@iobroker:/opt/iobroker$ iob upgrade self
Server Configured backup period 120 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.
Server Configured backup period 120 is larger than the supported maximum of 35791 minutes. Defaulting to 120 minutes.
Host    "iobroker"       is up to date.
marcel@iobroker:/opt/iobroker$ iob start
marcel@iobroker:/opt/iobroker$
marcel@iobroker:/opt/iobroker$
marcel@iobroker:/opt/iobroker$
marcel@iobroker:/opt/iobroker$ sudo apt update
[sudo] password for marcel:
Err:1 http://security.debian.org/debian-security bullseye-security InRelease
  Temporary failure resolving 'security.debian.org'
Err:2 https://repos.influxdata.com/debian buster InRelease
  Temporary failure resolving 'repos.influxdata.com'
Err:3 https://deb.nodesource.com/node_16.x bullseye InRelease
  Temporary failure resolving 'deb.nodesource.com'
Err:4 https://dl.yarnpkg.com/debian stable InRelease
  Temporary failure resolving 'dl.yarnpkg.com'
Err:5 http://deb.debian.org/debian bullseye InRelease
  Temporary failure resolving 'deb.debian.org'
Err:6 http://deb.debian.org/debian bullseye-updates InRelease
  Temporary failure resolving 'deb.debian.org'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease  Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye-updates/InRelease  Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://security.debian.org/debian-security/dists/bullseye-security/InRelease  Temporary failure resolving 'security.debian.org'
W: Failed to fetch https://repos.influxdata.com/debian/dists/buster/InRelease  Temporary failure resolving 'repos.influxdata.com'
W: Failed to fetch https://deb.nodesource.com/node_16.x/dists/bullseye/InRelease  Temporary failure resolving 'deb.nodesource.com'
W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease  Temporary failure resolving 'dl.yarnpkg.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
marcel@iobroker:/opt/iobroker$ uname -m && test -f /opt/scripts/.docker_config/.thisisdocker && echo "Docker-Installation" || echo "Kein Docker" && type -P nodejs node npm && nodejs -v && node -v && npm -v && iob -v && whoami && groups && echo $XDG_SESSION_TYPE && echo $DESKTOP_SESSION && pwd && sudo apt update &> /dev/null && sudo apt update && apt policy nodejs
x86_64
Kein Docker
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v16.17.1
v16.17.1
8.15.0
4.0.23
marcel
marcel sudo iobroker
tty

/opt/iobroker
Err:1 http://security.debian.org/debian-security bullseye-security InRelease
  Temporary failure resolving 'security.debian.org'
Err:2 https://repos.influxdata.com/debian buster InRelease
  Temporary failure resolving 'repos.influxdata.com'
Err:3 https://deb.nodesource.com/node_16.x bullseye InRelease
  Temporary failure resolving 'deb.nodesource.com'
Err:4 http://deb.debian.org/debian bullseye InRelease
  Temporary failure resolving 'deb.debian.org'
Err:5 https://dl.yarnpkg.com/debian stable InRelease
  Temporary failure resolving 'dl.yarnpkg.com'
Err:6 http://deb.debian.org/debian bullseye-updates InRelease
  Temporary failure resolving 'deb.debian.org'
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease  Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye-updates/InRelease  Temporary failure resolving 'deb.debian.org'
W: Failed to fetch http://security.debian.org/debian-security/dists/bullseye-security/InRelease  Temporary failure resolving 'security.debian.org'
W: Failed to fetch https://repos.influxdata.com/debian/dists/buster/InRelease  Temporary failure resolving 'repos.influxdata.com'
W: Failed to fetch https://deb.nodesource.com/node_16.x/dists/bullseye/InRelease  Temporary failure resolving 'deb.nodesource.com'
W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease  Temporary failure resolving 'dl.yarnpkg.com'
W: Some index files failed to download. They have been ignored, or old ones used instead.
nodejs:
  Installed: 16.17.1-deb-1nodesource1
  Candidate: 16.17.1-deb-1nodesource1
  Version table:
 *** 16.17.1-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
     12.22.12~dfsg-1~deb11u1 500
        500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
     12.22.5~dfsg-2~11u1 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
marcel@iobroker:/opt/iobroker$
                    1 Reply Last reply Reply Quote 0
                    • Thomas Braun
                      Thomas Braun Most Active last edited by

                      @marcel-drzal

                      Mit dem iobroker hat das nichts zu tun, das ist ein Knoten im Netzwerk-Setup.

                      1 Reply Last reply Reply Quote 0
                      • Codierknecht
                        Codierknecht Developer Most Active @Guest last edited by

                        @marcel-drzal sagte in Alexa2 Fehler nach Pi-Hole DHCP Server geändert:

                        @codierknecht ja habe den DNS Server eine IP gegeben im Router

                        Ich kann da nicht ganz folgen.
                        Du hast dem DNS Deiner Proxmox gesagt, dass der Router die Namen auflöst?
                        Kann ja nicht - Dein Router löst doch keine öffentlichen Domainnamen in IP's auf.

                        Ich kenne Proxmox nicht.
                        Hat das 'nen eigenen DNS? Kannst Du dem sagen, dass der Primary "1.1.1.1" und der Secondary "8.8.8.8" sein soll?

                        @marcel-drzal sagte in Alexa2 Fehler nach Pi-Hole DHCP Server geändert:

                        Habe schon Fix versucht. geht auch nicht

                        Das Netzwerkproblem kann der ioBroker auch nicht lösen 😉

                        1 Reply Last reply Reply Quote 0
                        • ?
                          A Former User @Thomas Braun last edited by

                          @thomas-braun

                          Danke noch mal

                          DNS Server in Proxmox nicht umgestellt.

                          es kann so einfach sein

                          noch eine Frage, die Version v16.17.1 ist die richtige? da ich auf dem Rasperry die v16.17.0 habe?

                          Codierknecht Thomas Braun 2 Replies Last reply Reply Quote 0
                          • Codierknecht
                            Codierknecht Developer Most Active @Guest last edited by Codierknecht

                            @marcel-drzal sagte in Alexa2 Fehler nach Pi-Hole DHCP Server geändert:

                            noch eine Frage, die Version v16.17.1 ist die richtige? da ich auf dem Rasperry die v16.17.0 habe?

                            Meine sind jedenfalls neuer:
                            3158096a-fefa-4bf8-a37b-5fd7317a270f-image.png

                            Update schadet nicht - gibt sonst wieder Mecker vom Chef 😉

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

                              @marcel-drzal

                              Spiel halt Updates regelmäßig per üblichem Vorgehen ein.

                              sudo apt update
sudo apt full-upgrade

                              Schwupps, schon ist sie Kiste auf aktuellem Stand.

                              ? 1 Reply Last reply Reply Quote 0
                              • ?
                                A Former User @Thomas Braun last edited by A Former User

                                @thomas-braun sagte in Geöst Alexa2 Fehler nach Pi-Hole DHCP Server geändert:

                                sudo apt update

                                
pi@pi-Slave1:/ $ sudo apt-get update
Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Get:3 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB]
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Err:2 http://deb.debian.org/debian bullseye InRelease
  Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease into data and signature failed
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Get:6 http://security.debian.org/debian-security bullseye-security/main arm64 Packages [196 kB]
Get:7 http://security.debian.org/debian-security bullseye-security/main armhf Packages [197 kB]
Get:8 http://security.debian.org/debian-security bullseye-security/main Translation-en [130 kB]
Err:5 https://deb.nodesource.com/node_16.x bullseye InRelease
  Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f16.x_dists_bullseye_InRelease into data and signature failed
Fetched 571 kB in 3s (182 kB/s)
Reading package lists... Error!
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian bullseye InRelease: Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease into data and signature failed
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.nodesource.com/node_16.x bullseye InRelease: Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f16.x_dists_bullseye_InRelease into data and signature failed
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease  Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease into data and signature failed
W: Failed to fetch https://deb.nodesource.com/node_16.x/dists/bullseye/InRelease  Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f16.x_dists_bullseye_InRelease into data and signature failed
W: Some index files failed to download. They have been ignored, or old ones used instead.
E: Splitting of clearsigned file /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease failed as it doesn't contain all expected parts
E: The package lists or status file could not be parsed or opened.
pi@pi-Slave1:/ $ 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
Err:2 http://deb.debian.org/debian bullseye InRelease
  Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease into data and signature failed
Hit:5 https://deb.nodesource.com/node_16.x bullseye InRelease
Err:5 https://deb.nodesource.com/node_16.x bullseye InRelease
  Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f16.x_dists_bullseye_InRelease into data and signature failed
Reading package lists... Error!
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian bullseye InRelease: Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease into data and signature failed
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.nodesource.com/node_16.x bullseye InRelease: Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f16.x_dists_bullseye_InRelease into data and signature failed
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease  Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease into data and signature failed
W: Failed to fetch https://deb.nodesource.com/node_16.x/dists/bullseye/InRelease  Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f16.x_dists_bullseye_InRelease into data and signature failed
W: Some index files failed to download. They have been ignored, or old ones used instead.
E: Splitting of clearsigned file /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease failed as it doesn't contain all expected parts
E: The package lists or status file could not be parsed or opened.
pi@pi-Slave1:/ $


sudo apt full-upgrade
Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:2 https://deb.nodesource.com/node_16.x bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye InRelease
Hit:4 http://deb.debian.org/debian bullseye-updates InRelease
Err:2 https://deb.nodesource.com/node_16.x bullseye InRelease
  Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f16.x_dists_bullseye_InRelease into data and signature failed
Err:3 http://deb.debian.org/debian bullseye InRelease
  Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease into data and signature failed
Hit:5 http://security.debian.org/debian-security bullseye-security InRelease
Reading package lists... Error!
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://deb.nodesource.com/node_16.x bullseye InRelease: Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f16.x_dists_bullseye_InRelease into data and signature failed
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian bullseye InRelease: Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease into data and signature failed
W: Failed to fetch http://deb.debian.org/debian/dists/bullseye/InRelease  Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease into data and signature failed
W: Failed to fetch https://deb.nodesource.com/node_16.x/dists/bullseye/InRelease  Splitting up /var/lib/apt/lists/deb.nodesource.com_node%5f16.x_dists_bullseye_InRelease into data and signature failed
W: Some index files failed to download. They have been ignored, or old ones used instead.
E: Splitting of clearsigned file /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease failed as it doesn't contain all expected parts
E: The package lists or status file could not be parsed or opened.
Reading package lists... Error!
E: Splitting of clearsigned file /var/lib/apt/lists/deb.debian.org_debian_dists_bullseye_InRelease failed as it doesn't contain all expected parts
E: The package lists or status file could not be parsed or opened.
pi@pi-Slave1:~ $


                                pi@pi-Slave1:/etc/network $ sudo systemctl status dhcpcd
● dhcpcd.service - DHCP Client Daemon
     Loaded: loaded (/lib/systemd/system/dhcpcd.service; enabled; vendor preset>
     Active: active (running) since Wed 2022-11-16 17:39:53 CET; 18h ago
       Docs: man:dhcpcd(8)
    Process: 411 ExecStart=/usr/sbin/dhcpcd -b -q (code=exited, status=0/SUCCES>
   Main PID: 469 (dhcpcd)
      Tasks: 2 (limit: 779)
        CPU: 14.446s
     CGroup: /system.slice/dhcpcd.service
             ├─469 /usr/sbin/dhcpcd -b -q
             └─548 wpa_supplicant -B -c/etc/wpa_supplicant/wpa_supplicant.conf >

Nov 17 11:34:35 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3e>
Nov 17 11:34:39 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3e>
Nov 17 11:34:43 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3e>
Nov 17 11:36:27 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3e>
Nov 17 11:45:36 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3e>
Nov 17 11:51:27 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3e>
Nov 17 11:52:39 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3e>
Nov 17 11:57:00 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3e>
Nov 17 12:06:24 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3e>
Nov 17 12:06:27 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3e>
lines 1-22/22 (END)
● dhcpcd.service - DHCP Client Daemon
     Loaded: loaded (/lib/systemd/system/dhcpcd.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2022-11-16 17:39:53 CET; 18h ago
       Docs: man:dhcpcd(8)
    Process: 411 ExecStart=/usr/sbin/dhcpcd -b -q (code=exited, status=0/SUCCESS)
   Main PID: 469 (dhcpcd)
      Tasks: 2 (limit: 779)
        CPU: 14.446s
     CGroup: /system.slice/dhcpcd.service
             ├─469 /usr/sbin/dhcpcd -b -q
             └─548 wpa_supplicant -B -c/etc/wpa_supplicant/wpa_supplicant.conf -iwlan0

Nov 17 11:34:35 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3ea6:2fff:fee0:916e
Nov 17 11:34:39 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3ea6:2fff:fee0:916e
Nov 17 11:34:43 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3ea6:2fff:fee0:916e
Nov 17 11:36:27 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3ea6:2fff:fee0:916e
Nov 17 11:45:36 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3ea6:2fff:fee0:916e
Nov 17 11:51:27 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3ea6:2fff:fee0:916e
Nov 17 11:52:39 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3ea6:2fff:fee0:916e
Nov 17 11:57:00 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3ea6:2fff:fee0:916e
Nov 17 12:06:24 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3ea6:2fff:fee0:916e
Nov 17 12:06:27 pi-Slave1 dhcpcd[469]: eth0: Router Advertisement from fe80::3ea6:2fff:fee0:916e
~

                                auf meinen Raspi, Hier stell ich doch keinen DHCP ein oder? wo schau ich das nach?

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

                                  @marcel-drzal

                                  Nee, da sind deine Repos falsch. Kann das aber im Moment nicht gut nachvollziehen, da am Handy unterwegs.

                                  ? 1 Reply Last reply Reply Quote 0
                                  • ?
                                    A Former User @Guest last edited by

                                    sudo rm /var/lib/apt/lists/* dann ging es

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

                                      @marcel-drzal

                                      Dann lass jetzt mal ein

                                      sudo apt update

                                      sehen. Und bitte auch

                                      df -h
                                      ? 2 Replies Last reply Reply Quote 0
                                      • ?
                                        A Former User @Thomas Braun last edited by A Former User

                                        @thomas-braun sagte in Geöst Alexa2 Fehler nach Pi-Hole DHCP Server geändert:

                                        sudo apt update

                                        bei Rasperry Pi-Slave

                                        
pi@pi-Slave1:~ $ sudo apt update
Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease
Hit:2 https://deb.nodesource.com/node_16.x bullseye InRelease
Hit:3 http://security.debian.org/debian-security bullseye-security InRelease
Hit:4 http://deb.debian.org/debian bullseye InRelease
Hit:5 http://deb.debian.org/debian bullseye-updates InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
pi@pi-Slave1:~ $ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        29G  4.0G   24G  15% /
devtmpfs        325M     0  325M   0% /dev
tmpfs           455M     0  455M   0% /dev/shm
tmpfs           182M  1.1M  181M   1% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
/dev/mmcblk0p1  255M   31M  225M  12% /boot
tmpfs            91M   20K   91M   1% /run/user/1000

                                        bei Rasperry pi-Test

                                        pi@pi-Test:~ $ sudo apt update
OK:1 http://archive.raspberrypi.org/debian buster InRelease
OK:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
OK:3 https://deb.nodesource.com/node_16.x bullseye InRelease
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen.... Fertig
Alle Pakete sind aktuell.
pi@pi-Test:~ $ df -h
Dateisystem    Größe Benutzt Verf. Verw% Eingehängt auf
/dev/root        30G    4,5G   24G   17% /
devtmpfs        430M       0  430M    0% /dev
tmpfs           462M       0  462M    0% /dev/shm
tmpfs           462M     12M  450M    3% /run
tmpfs           5,0M    4,0K  5,0M    1% /run/lock
tmpfs           462M       0  462M    0% /sys/fs/cgroup
/dev/mmcblk0p1  253M     49M  204M   20% /boot
tmpfs            93M       0   93M    0% /run/user/1000
pi@pi-Test:~ $

                                        c762efcf-3bdc-48c5-bb47-6a045987e82a-grafik.png

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

                                          @marcel-drzal sagte in Geöst Alexa2 Fehler nach Pi-Hole DHCP Server geändert:
                                          Auf pi-Test stimmt die nodesource-Quelle nicht, wenn da als OS buster läuft. Die release names sollen übereinstimmen.

                                          Und auf dem dritten System schaut es wie aus?

                                          1 Reply Last reply Reply Quote 0
                                          • ?
                                            A Former User @Thomas Braun last edited by A Former User

                                            @thomas-braun

                                            sudo nano /etc/apt/sources.list

                                            vom Pik-Slave

                                            
deb http://deb.debian.org/debian bullseye main contrib non-free
deb http://security.debian.org/debian-security bullseye-security main contrib non-free
deb http://deb.debian.org/debian bullseye-updates main contrib non-free
# Uncomment deb-src lines below then 'apt-get update' to enable 'apt-get source'
#deb-src http://deb.debian.org/debian bullseye main contrib non-free
#deb-src http://security.debian.org/debian-security bullseye-security main contrib non-free
#deb-src http://deb.debian.org/debian bullseye-updates main contrib non-free

                                            vom Pi-Test

                                            
deb http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi
# Uncomment line below then 'apt-get update' to enable 'apt-get source'
#deb-src http://raspbian.raspberrypi.org/raspbian/ buster main contrib non-free rpi
                                            Thomas Braun 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            868
                                            Online

                                            31.8k
                                            Users

                                            80.0k
                                            Topics

                                            1.3m
                                            Posts

                                            3
                                            47
                                            1212
                                            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