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.
    • Codierknecht
      Codierknecht Developer Most Active @Guest last edited by

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

      Node-Version:
      10.x.x

      Nodejs-Version:
      10.x.x

      NPM-Version:
      6.x.x

      Dein System ist steinalt!

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

        @codierknecht sorry falsch ausgefüllt

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

          @marcel-drzal

          In einem richtigen Terminal ausführen:

          iobroker add alexa2 auto --host iobroker --debug
          

          Und deine nodeJS-Installation prüfen, das ist nicht die aktuelle v.16 da bei dir.

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

            @thomas-braun
            NPM Version v8.15.0 habe ich

            bbc56991-605f-4c1d-b1e6-bf88853b1e82-grafik.png

            454b9cad-9ba7-4d54-a698-4e0d6f3754b3-grafik.png

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

              @marcel-drzal

              Bitte Text auch als Text in CodeTags einbetten.

              sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null
              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
              

              sagt?

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

                @thomas-braun

                komme nicht weiter 
                v16.17.1 ist die falsche ?
                
                Thomas Braun Codierknecht 2 Replies Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @Guest last edited by

                  @marcel-drzal

                  Soll heißen?
                  NodeJS ist jedenfalls nicht die aktuelle Version im 16er-Zweig.

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

                    @marcel-drzal
                    Du hast @Thomas-Braun falsch verstanden.
                    Deinen "normalen" Text braucht Du nicht als Code posten.

                    Nimm das was @Thomas-Braun zeigt und führe es in der Konsole aus.
                    Das Ergebnis kopierst Du und postest es hier in Code-Tags, damit man das auch sinnvoll lesen kann.

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

                      @codierknecht
                      @thomas-braun

                      marcel@iobroker:/opt/iobroker$ sudo ln -s /usr/bin/node /usr/bin/nodejs &> /dev/null
                      
                      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://deb.debian.org/debian bullseye InRelease
                        Temporary failure resolving 'deb.debian.org'
                      Err:2 http://security.debian.org/debian-security bullseye-security InRelease
                        Temporary failure resolving 'security.debian.org'
                      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 https://repos.influxdata.com/debian buster InRelease
                        Temporary failure resolving 'repos.influxdata.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$
                      marcel@iobroker:/opt/iobroker$
                      
                      
                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • 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
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            801
                                            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