Absturzursache Raspi und iO Broker finden
-
@laser sagte in Absturzursache Raspi und iO Broker finden:
Trag das mal so ein:
deb http://deb.debian.org/debian stable main contrib non-free deb http://security.debian.org/debian-security stable-security main contrib non-free deb http://deb.debian.org/debian stable-updates main contrib non-free -
-
pi@Heizung:~ $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer required: raspinfo Use 'sudo apt autoremove' to remove it. The following packages will be upgraded: curl libcurl3-gnutls libcurl4 libtiff5 4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 1,144 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf curl armhf 7. 74.0-1.3+deb11u7 [258 kB] Get:2 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libcurl4 armh f 7.74.0-1.3+deb11u7 [310 kB] Get:3 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libcurl3-gnut ls armhf 7.74.0-1.3+deb11u7 [306 kB] Get:4 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf libtiff5 armh f 4.2.0-1+deb11u4 [270 kB] Fetched 1,144 kB in 1s (1,171 kB/s) Reading changelogs... Done (Reading database ... 54016 files and directories currently installed.) Preparing to unpack .../curl_7.74.0-1.3+deb11u7_armhf.deb ... Unpacking curl (7.74.0-1.3+deb11u7) over (7.74.0-1.3+deb11u5) ... Preparing to unpack .../libcurl4_7.74.0-1.3+deb11u7_armhf.deb ... Unpacking libcurl4:armhf (7.74.0-1.3+deb11u7) over (7.74.0-1.3+deb11u5) ... Preparing to unpack .../libcurl3-gnutls_7.74.0-1.3+deb11u7_armhf.deb ... Unpacking libcurl3-gnutls:armhf (7.74.0-1.3+deb11u7) over (7.74.0-1.3+deb11u5) . .. Preparing to unpack .../libtiff5_4.2.0-1+deb11u4_armhf.deb ... Unpacking libtiff5:armhf (4.2.0-1+deb11u4) over (4.2.0-1+deb11u3) ... Setting up libcurl3-gnutls:armhf (7.74.0-1.3+deb11u7) ... Setting up libcurl4:armhf (7.74.0-1.3+deb11u7) ... Setting up libtiff5:armhf (4.2.0-1+deb11u4) ... Setting up curl (7.74.0-1.3+deb11u7) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u5) ... pi@Heizung:~ $ nano /etc/apt/sources.list pi@Heizung:~ $ sudo nano/etc/apt/sources.list sudo: nano/etc/apt/sources.list: command not found pi@Heizung:~ $ sudo nano /etc/apt/sources.list pi@Heizung:~ $ pi@Heizung:~ $ sudo apt update Get:1 http://security.debian.org/debian-security stable-security InRelease [48.4 kB] Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Get:3 http://deb.debian.org/debian stable InRelease [116 kB] Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Get:5 http://deb.debian.org/debian stable-updates InRelease [44.1 kB] Hit:6 https://deb.nodesource.com/node_16.x bullseye InRelease 0% [Working]gpgv: Signature made Wed Mar 1 05:32:51 2023 CET gpgv: using RSA key A0DA38D0D76E8B5D638872819165938D90FDDD2E gpgv: Good signature from "Mike Thompson (Raspberry Pi Debian armhf ARMv6+VFP) <mpthompson@gmail.com>" /usr/bin/apt-key: 57: cannot create /dev/null: Permission denied 0% [Working]gpgv: Signature made Sat Dec 17 11:15:20 2022 CET gpgv: using RSA key 0146DC6D4A0B2914BDED34DB648ACFD622F3D138 gpgv: Can't check signature: No public key gpgv: Signature made Sat Dec 17 11:15:21 2022 CET gpgv: using RSA key A7236886F3CCCAAD148A27F80E98404D386FA1D9 gpgv: Can't check signature: No public key gpgv: Signature made Sat Dec 17 11:20:04 2022 CET gpgv: using RSA key A4285295FC7B1A81600062A9605C66F00D6C9793 gpgv: issuer "debian-release@lists.debian.org" gpgv: Can't check signature: No public key /usr/bin/apt-key: 57: cannot create /dev/null: Permission denied Err:3 http://deb.debian.org/debian stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 605C66F00D6C9793 0% [Working]gpgv: Signature made Wed Mar 1 06:32:42 2023 CET gpgv: using RSA key 5237CEEEF212F3D51C74ABE0112695A0E562B32A gpgv: Can't check signature: No public key gpgv: Signature made Wed Mar 1 06:32:43 2023 CET gpgv: using RSA key ED541312A33F1128F10B1C6C54404762BBB6E853 gpgv: Can't check signature: No public key /usr/bin/apt-key: 57: cannot create /dev/null: Permission denied Err:1 http://security.debian.org/debian-security stable-security InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 112695A0E562B32A NO_PUBKEY 54404762BBB6E853 0% [Working]gpgv: Signature made Tue Feb 28 15:00:50 2023 CET gpgv: using RSA key CF8A1AF502A2AA2D763BAE7E82B129927FA3303E gpgv: Good signature from "Raspberry Pi Archive Signing Key" /usr/bin/apt-key: 57: cannot create /dev/null: Permission denied 0% [Working]gpgv: Signature made Wed Mar 1 09:14:56 2023 CET gpgv: using RSA key 0146DC6D4A0B2914BDED34DB648ACFD622F3D138 gpgv: Can't check signature: No public key gpgv: Signature made Wed Mar 1 09:15:35 2023 CET gpgv: using RSA key A7236886F3CCCAAD148A27F80E98404D386FA1D9 gpgv: Can't check signature: No public key /usr/bin/apt-key: 57: cannot create /dev/null: Permission denied Err:5 http://deb.debian.org/debian stable-updates InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 0% [Working]gpgv: Signature made Fri Feb 17 01:55:45 2023 CET gpgv: using RSA key 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 gpgv: Good signature from "NodeSource <gpg@nodesource.com>" /usr/bin/apt-key: 57: cannot create /dev/null: Permission denied Reading package lists... Done W: GPG error: http://deb.debian.org/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 605C66F00D6C9793 E: The repository 'http://deb.debian.org/debian stable 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. W: GPG error: http://security.debian.org/debian-security stable-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 112695A0E562B32A NO_PUBKEY 54404762BBB6E853 E: The repository 'http://security.debian.org/debian-security stable-security 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. W: GPG error: http://deb.debian.org/debian stable-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 E: The repository 'http://deb.debian.org/debian stable-updates 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. pi@Heizung:~ $ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer required: raspinfo Use 'sudo apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -
Ersetz mal 'stable' durch den Releasename das du da fährst. 'bullseye'?
-
@thomas-braun so?
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-freepi@Heizung:/etc/apt$ sudo apt update Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB] Get:2 http://security.debian.org/debian-security bullseye-security InRelease [48 .4 kB] Hit:3 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Get:5 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB] Hit:6 https://deb.nodesource.com/node_16.x bullseye InRelease 0% [Working]gpgv: Signature made Wed Mar 1 05:32:51 2023 CET gpgv: using RSA key A0DA38D0D76E8B5D638872819165938D90FDDD2E gpgv: Good signature from "Mike Thompson (Raspberry Pi Debian armhf ARMv6+VFP) < mpthompson@gmail.com>" /usr/bin/apt-key: 57: cannot create /dev/null: Permission denied 0% [Working]gpgv: Signature made Wed Mar 1 06:32:42 2023 CET gpgv: using RSA key 5237CEEEF212F3D51C74ABE0112695A0E562B32A gpgv: Can't check signature: No public key gpgv: Signature made Wed Mar 1 06:32:43 2023 CET gpgv: using RSA key ED541312A33F1128F10B1C6C54404762BBB6E853 gpgv: Can't check signature: No public key /usr/bin/apt-key: 57: cannot create /dev/null: Permission denied Err:2 http://security.debian.org/debian-security bullseye-security InRelease The following signatures couldn't be verified because the public key is not av ailable: NO_PUBKEY 112695A0E562B32A NO_PUBKEY 54404762BBB6E853 0% [Working]gpgv: Signature made Tue Feb 28 15:00:50 2023 CET gpgv: using RSA key CF8A1AF502A2AA2D763BAE7E82B129927FA3303E gpgv: Good signature from "Raspberry Pi Archive Signing Key" /usr/bin/apt-key: 57: cannot create /dev/null: Permission denied 0% [Working]gpgv: Signature made Sat Dec 17 11:15:20 2022 CET gpgv: using RSA key 0146DC6D4A0B2914BDED34DB648ACFD622F3D138 gpgv: Can't check signature: No public key gpgv: Signature made Sat Dec 17 11:15:21 2022 CET gpgv: using RSA key A7236886F3CCCAAD148A27F80E98404D386FA1D9 gpgv: Can't check signature: No public key gpgv: Signature made Sat Dec 17 11:20:04 2022 CET gpgv: using RSA key A4285295FC7B1A81600062A9605C66F00D6C9793 gpgv: issuer "debian-release@lists.debian.org" gpgv: Can't check signature: No public key /usr/bin/apt-key: 57: cannot create /dev/null: Permission denied Err:1 http://deb.debian.org/debian bullseye InRelease The following signatures couldn't be verified because the public key is not av ailable: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 605C66F 00D6C9793 0% [Working]gpgv: Signature made Wed Mar 1 09:14:56 2023 CET gpgv: using RSA key 0146DC6D4A0B2914BDED34DB648ACFD622F3D138 gpgv: Can't check signature: No public key gpgv: Signature made Wed Mar 1 09:15:35 2023 CET gpgv: using RSA key A7236886F3CCCAAD148A27F80E98404D386FA1D9 gpgv: Can't check signature: No public key /usr/bin/apt-key: 57: cannot create /dev/null: Permission denied Err:5 http://deb.debian.org/debian bullseye-updates InRelease The following signatures couldn't be verified because the public key is not av ailable: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 0% [Working]gpgv: Signature made Fri Feb 17 01:55:45 2023 CET gpgv: using RSA key 9FD3B784BC1C6FC31A8A0A1C1655A0AB68576280 gpgv: Good signature from "NodeSource <gpg@nodesource.com>" /usr/bin/apt-key: 57: cannot create /dev/null: Permission denied Reading package lists... Done W: GPG error: http://security.debian.org/debian-security bullseye-security InRel ease: The following signatures couldn't be verified because the public key is no t available: NO_PUBKEY 112695A0E562B32A NO_PUBKEY 54404762BBB6E853 E: The repository 'http://security.debian.org/debian-security bullseye-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disa bled by default. N: See apt-secure(8) manpage for repository creation and user configuration deta ils. W: GPG error: http://deb.debian.org/debian bullseye InRelease: The following sig natures couldn't be verified because the public key is not available: NO_PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 605C66F00D6C9793 E: The repository 'http://deb.debian.org/debian bullseye InRelease' is not signe d. N: Updating from such a repository can't be done securely, and is therefore disa bled by default. N: See apt-secure(8) manpage for repository creation and user configuration deta ils. W: GPG error: http://deb.debian.org/debian bullseye-updates InRelease: The follo wing signatures couldn't be verified because the public key is not available: NO _PUBKEY 648ACFD622F3D138 NO_PUBKEY 0E98404D386FA1D9 E: The repository 'http://deb.debian.org/debian bullseye-updates InRelease' is n ot signed. N: Updating from such a repository can't be done securely, and is therefore disa bled by default. N: See apt-secure(8) manpage for repository creation and user configuration deta ils. pi@Heizung:/etc/apt$ sudo apt upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following package was automatically installed and is no longer required: raspinfo Use 'sudo apt autoremove' to remove it. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. -
Irgendwas stimmt mit den signaturen noch nicht.
Ich kann aber im Moment nicht nachschauen, weil ich hier ein ganz anderes System fahre. -
@thomas-braun
Kein Problem!
Ich suche mal nach einem anderen Pi zur Testinstallation. Ich muß jetzt auch erst mal weg.
Unabhängig von den falschen Quellen hat meine FritzBox ein Problem. Muß ich auch immer mal neu starten. Evtl. hat der Hersteller ein "Gute Nacht- kauf mal was Neues" - Update installiert? -
@laser sagte in Absturzursache Raspi und iO Broker finden:
Evtl. hat der Hersteller ein "Gute Nacht- kauf mal was Neues" - Update installiert?
Das siehst du ja in entsprechenden Logs.
Wenn du die nicht ausknipsen würdest jedenfalls... -
@thomas-braun
ich werde die logs wieder einschalten. Aber gefunden habe ich darin bisher nichts Brauchbares... -
@laser sagte in Absturzursache Raspi und iO Broker finden:
wie es die Anleitung gezeigt hat.
welche?
-
@homoran
Da müßte ich jetzt suchen. Ist schon eine Weile her. Aber es war die, welche mir hier einige Beiträge vorher hier im Forum empfohlen wurde.
IO-Broker so mit dem Script:
sudo apt install curl
sudo curl -sL https://iobroker.net/install.sh | bash -
Zu Beginn hatte ich noch Debmatic mit drauf. Habe ich jetzt auf einem extra Pi. -
@laser hör bitte auf wie "früher" deine Beiträge nachträglich zu editieren... und:
sudo curl -sL https://iobroker.net/install.sh | bash -macht man nicht --- ohne sudo ist da angesagt auf einem gescheiten System !
-
@djmarc75
Das habe ich jetzt nur aus einer alten Textdatei kopiert. Jetzt sehe ich es auch. Habe zum Schluß aber ohne sudo installiert. Muß die abgelegte Hilfedatei korrigieren. -
@laser und vorher Debian mit dem Rasberry Imager.
Wenn ich nicht eine offline Vis Lizenz hätte, würde ich Alles neu auf einem anderen Pi installieren... -
@laser lassen sie die Rechte nachträglich mit sinnvollem Aufwand anpassen?
-
@laser welche Rechte willst du anpassen?
-
@wendy2702
Falls ich, wie hier vermutet wurde, etwas mit Sudo Rechten installiert hätte. -
@laser
Brauche das System heute noch. Habe gerade ein Backup gemacht. Wie lange wird eine komplette Neuinstallation etwa dauern? -
@laser
Beschreibe gerade eine neue SD Card. Ziehe ein Image und schreibe das auf die SSD. Dann habe ich immer noch meine alte SSD, wenn es nicht so klappt. -
@laser sagte in Absturzursache Raspi und iO Broker finden:
Falls ich, wie hier vermutet wurde, etwas mit Sudo Rechten installiert hätte.
Wenn man mal Deine vielen Probleme aus Deinen Beiträgen so liest, dann hast Du definitiv da mit irgendwelchem Murks gearbeitet... kein Vorwurf sondern eine Feststellung !
Dann:
@laser sagte in Absturzursache Raspi und iO Broker finden:
Ziehe ein Image und schreibe das auf die SSD
wie machs Du das ?
@laser sagte in Absturzursache Raspi und iO Broker finden:
Dann habe ich immer noch meine alte SSD, wenn es nicht so klappt.
Was sollte das nicht klappen wenn man es richtig macht ?
