NEWS
Webinterface nicht mehr aufrufbar
Einsteigerfragen
16
Beiträge
3
Kommentatoren
866
Aufrufe
2
Watching
-
@haselchen Danke, das wars. Aber wieso hat er das nicht mehr automatisch gestartet (hatte auch Restart ausprobiert)?
-
Hi,
leider ist auf einmal mein Webinterface nicht mehr aufrufbar. Der Vis Editor geht noch. Ich habe dann mal iobroker fix probiert und da kamen ein paar Fehler. Dann angeblich alles erfolgreich gefixt aber auf die Oberfläche komme ich immer noch nicht.pi@raspberry64:~ $ iobroker stop pi@raspberry64:~ $ iobroker fix library: loaded Library version=2022-12-09 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2023-04-02 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian bullseye-updates InRelease Get:3 http://security.debian.org/debian-security bullseye-security InRelease [48.4 kB] Get:4 https://repos.influxdata.com/debian bullseye InRelease [7,040 B] Get:5 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B] Get:6 https://apt.grafana.com stable InRelease [5,983 B] Hit:7 http://archive.raspberrypi.org/debian bullseye InRelease Err:4 https://repos.influxdata.com/debian bullseye InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E Err:6 https://apt.grafana.com stable InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 Fetched 60.0 kB in 2s (37.0 kB/s) Reading package lists... Done 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: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://apt.grafana.com stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 W: Failed to fetch https://apt.grafana.com/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 963FA27710458545 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. Installed gcc-c++ ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! Compressing /opt/iobroker/iobroker-data/states.jsonl Compressing /opt/iobroker/iobroker-data/objects.jsonl Compressed 2 JSONL files. Done ========================================================================== Checking autostart (5/5) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== pi@raspberry64:~ $ iobroker start pi@raspberry64:~ $War im Beta Kanal mit Vis 2 im gange und hatte zuletzt alle Updates durchlaufen lassen. Jemand eine Idee?
pi@raspberry64:~ $ iobroker list instances system.adapter.adb.0 : adb : raspberry64 - disabled system.adapter.admin.0 : admin : raspberry64 - disabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alias-manager.0 : alias-manager : raspberry64 - enabled + system.adapter.backitup.0 : backitup : raspberry64 - enabled + system.adapter.ble.0 : ble : raspberry64 - enabled system.adapter.cameras.0 : cameras : raspberry64 - disabled, port: 8200, bind: 127.0.0.1 + system.adapter.chromecast.0 : chromecast : raspberry64 - enabled + system.adapter.device-reminder.0 : device-reminder : raspberry64 - enabled system.adapter.device-watcher.0 : device-watcher : raspberry64 - disabled + system.adapter.discovery.0 : discovery : raspberry64 - enabled + system.adapter.echarts.0 : echarts : raspberry64 - enabled + system.adapter.email.0 : email : raspberry64 - enabled system.adapter.feiertage.0 : feiertage : raspberry64 - enabled system.adapter.firetv.0 : firetv : raspberry64 - disabled system.adapter.flot.0 : flot : raspberry64 - disabled + system.adapter.hiob.0 : hiob : raspberry64 - enabled + system.adapter.history.0 : history : raspberry64 - enabled + system.adapter.hm-rega.0 : hm-rega : raspberry64 - enabled + system.adapter.hm-rpc.0 : hm-rpc : raspberry64 - enabled, port: 12001 + system.adapter.hm-rpc.1 : hm-rpc : raspberry64 - enabled, port: 12010 + system.adapter.hue-extended.0 : hue-extended : raspberry64 - enabled + system.adapter.hue.0 : hue : raspberry64 - enabled, port: 443 + system.adapter.hue.1 : hue : raspberry64 - enabled, port: 443 system.adapter.ical.0 : ical : raspberry64 - disabled system.adapter.icons-icons8.0 : icons-icons8 : raspberry64 - disabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : raspberry64 - disabled system.adapter.icons-open-icon-library-png.0: icons-open-icon-library-png: raspberry64 - disabled + system.adapter.influxdb.0 : influxdb : raspberry64 - enabled, port: 8086 + system.adapter.javascript.0 : javascript : raspberry64 - enabled + system.adapter.net-tools.0 : net-tools : raspberry64 - enabled system.adapter.openweathermap.0 : openweathermap : raspberry64 - enabled + system.adapter.pi-hole.0 : pi-hole : raspberry64 - enabled + system.adapter.ping.0 : ping : raspberry64 - enabled + system.adapter.radar2.0 : radar2 : raspberry64 - enabled + system.adapter.rpi2.0 : rpi2 : raspberry64 - enabled system.adapter.schoolfree.0 : schoolfree : raspberry64 - enabled + system.adapter.signal-cmb.0 : signal-cmb : raspberry64 - enabled + system.adapter.smartmeter.0 : smartmeter : raspberry64 - enabled + system.adapter.smartthings.0 : smartthings : raspberry64 - enabled + system.adapter.socketio.0 : socketio : raspberry64 - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sourceanalytix.0 : sourceanalytix : raspberry64 - enabled + system.adapter.synology.0 : synology : raspberry64 - enabled, port: 5000 + system.adapter.tankerkoenig.0 : tankerkoenig : raspberry64 - enabled + system.adapter.telegram.0 : telegram : raspberry64 - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.tr-064.0 : tr-064 : raspberry64 - enabled + system.adapter.vis-2-beta.0 : vis-2-beta : raspberry64 - enabled system.adapter.vis-2-widgets-energy.0 : vis-2-widgets-energy : raspberry64 - enabled system.adapter.vis-2-widgets-gauges.0 : vis-2-widgets-gauges : raspberry64 - enabled system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: raspberry64 - enabled system.adapter.vis-canvas-gauges.0 : vis-canvas-gauges : raspberry64 - disabled system.adapter.vis-colorpicker.0 : vis-colorpicker : raspberry64 - disabled system.adapter.vis-fancyswitch.0 : vis-fancyswitch : raspberry64 - disabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : raspberry64 - disabled system.adapter.vis-icontwo.0 : vis-icontwo : raspberry64 - enabled + system.adapter.vis-inventwo.0 : vis-inventwo : raspberry64 - enabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : raspberry64 - enabled system.adapter.vis-map.0 : vis-map : raspberry64 - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : raspberry64 - enabled system.adapter.vis.0 : vis : raspberry64 - enabled system.adapter.weatherunderground.0 : weatherunderground : raspberry64 - enabled + system.adapter.web.0 : web : raspberry64 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.wled.0 : wled : raspberry64 - enabled system.adapter.ws.0 : ws : raspberry64 - disabled, port: 8084, bind: 0.0.0.0, run as: admin + instance is alive pi@raspberry64:~ $iob start adminUnd System auf Stand halten, das sind die Repos für grafana und influxdb nicht gepflegt.
-
@thomas-braun Danke aber ganz blöde Frage, wie mache ich das? Hatte gedacht das es mit
sudo apt update && sudo apt upgradeerledigt ist aber leider nicht. Auch die Hilfe bei Influx hat mir nicht wirklich weiter geholfen...
Aus dem August:
https://forum.iobroker.net/topic/67822/grafana-repo-braucht-neuen-schlüsselAus dem Januar:
https://forum.iobroker.net/topic/62040/linux-debian-grafana-repo-muss-aktualisiert-werdenSolange hängt das also schon schief bei dir...
-
Aus dem August:
https://forum.iobroker.net/topic/67822/grafana-repo-braucht-neuen-schlüsselAus dem Januar:
https://forum.iobroker.net/topic/62040/linux-debian-grafana-repo-muss-aktualisiert-werdenSolange hängt das also schon schief bei dir...
@thomas-braun Mag sein, mir fehlt noch ein wenig der Überblich als Windowsuser... Ich hatte es so wie von Dir beschrieben gemacht und
apt-key list | grep -i grafana | wc -lergab die gewünschte 0:
pi@raspberry64:~ $ apt-key list | grep -i grafana | wc -l Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). 0 pi@raspberry64:~ $ sudo wget -q -O /usr/share/keyrings/grafana.key https://apt.grafana.com/gpg.key pi@raspberry64:~ $ echo "deb [signed-by=/usr/share/keyrings/grafana.key] https://apt.grafana.com stable main" | sudo tee /etc/apt/sources.list.d/grafana.list deb [signed-by=/usr/share/keyrings/grafana.key] https://apt.grafana.com stable main pi@raspberry64:~ $ 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 Get:4 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B] Get:5 https://repos.influxdata.com/debian bullseye InRelease [7,040 B] Get:6 https://apt.grafana.com stable InRelease [5,983 B] Hit:7 http://archive.raspberrypi.org/debian 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 Get:8 https://apt.grafana.com stable/main arm64 Packages [112 kB] Get:9 https://apt.grafana.com stable/main armhf Packages [96.5 kB] Fetched 220 kB in 2s (113 kB/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.da das update dann immer noch Fehler zeigte wollte ich dann den Key löschen und neu anlegen. Leider habe ich dann den falschen gelöscht.
Wie kann ich diesen denn wieder herstellen oder ist der nicht wichtig?: :cold_sweat:
/etc/apt/trusted.gpg.d/raspberrypi-archive-stable.gpg ----------------------------------------------------- pub rsa2048 2012-06-17 [SC] CF8A 1AF5 02A2 AA2D 763B AE7E 82B1 2992 7FA3 303E uid [ unknown] Raspberry Pi Archive Signing Key sub rsa2048 2012-06-17 [E] -
@thomas-braun Mag sein, mir fehlt noch ein wenig der Überblich als Windowsuser... Ich hatte es so wie von Dir beschrieben gemacht und
apt-key list | grep -i grafana | wc -lergab die gewünschte 0:
pi@raspberry64:~ $ apt-key list | grep -i grafana | wc -l Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). 0 pi@raspberry64:~ $ sudo wget -q -O /usr/share/keyrings/grafana.key https://apt.grafana.com/gpg.key pi@raspberry64:~ $ echo "deb [signed-by=/usr/share/keyrings/grafana.key] https://apt.grafana.com stable main" | sudo tee /etc/apt/sources.list.d/grafana.list deb [signed-by=/usr/share/keyrings/grafana.key] https://apt.grafana.com stable main pi@raspberry64:~ $ 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 Get:4 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B] Get:5 https://repos.influxdata.com/debian bullseye InRelease [7,040 B] Get:6 https://apt.grafana.com stable InRelease [5,983 B] Hit:7 http://archive.raspberrypi.org/debian 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 Get:8 https://apt.grafana.com stable/main arm64 Packages [112 kB] Get:9 https://apt.grafana.com stable/main armhf Packages [96.5 kB] Fetched 220 kB in 2s (113 kB/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.da das update dann immer noch Fehler zeigte wollte ich dann den Key löschen und neu anlegen. Leider habe ich dann den falschen gelöscht.
Wie kann ich diesen denn wieder herstellen oder ist der nicht wichtig?: :cold_sweat:
/etc/apt/trusted.gpg.d/raspberrypi-archive-stable.gpg ----------------------------------------------------- pub rsa2048 2012-06-17 [SC] CF8A 1AF5 02A2 AA2D 763B AE7E 82B1 2992 7FA3 303E uid [ unknown] Raspberry Pi Archive Signing Key sub rsa2048 2012-06-17 [E]apt-key list | grep -i grafana | wc -l sudo wget -q -O /usr/share/keyrings/grafana.key https://apt.grafana.com/gpg.keysagt?
€dit: Grafana ist doch okay nun. Da ist aber noch die zweite Baustelle bei influxdb. Dazu steht im Thread aus dem Januar aber was drin.
-
apt-key list | grep -i grafana | wc -l sudo wget -q -O /usr/share/keyrings/grafana.key https://apt.grafana.com/gpg.keysagt?
€dit: Grafana ist doch okay nun. Da ist aber noch die zweite Baustelle bei influxdb. Dazu steht im Thread aus dem Januar aber was drin.
@thomas-braun Der ausversehen gelöscht Raspberrypi-Key scheint doch wichtig zu sein. Nachdem ich den Influx Key erneuert habe kommt:
pi@raspberry64:~ $ 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 Get:4 https://repos.influxdata.com/debian bullseye InRelease [7,040 B] Get:5 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B] Hit:6 http://archive.raspberrypi.org/debian bullseye InRelease Err:4 https://repos.influxdata.com/debian bullseye InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E Err:6 http://archive.raspberrypi.org/debian bullseye InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E Fetched 11.6 kB in 1s (7,993 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. 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: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.raspberrypi.org/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E 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: Failed to fetch http://archive.raspberrypi.org/debian/dists/bullseye/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E W: Some index files failed to download. They have been ignored, or old ones used instead. -
@thomas-braun Der ausversehen gelöscht Raspberrypi-Key scheint doch wichtig zu sein. Nachdem ich den Influx Key erneuert habe kommt:
pi@raspberry64:~ $ 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 Get:4 https://repos.influxdata.com/debian bullseye InRelease [7,040 B] Get:5 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B] Hit:6 http://archive.raspberrypi.org/debian bullseye InRelease Err:4 https://repos.influxdata.com/debian bullseye InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E Err:6 http://archive.raspberrypi.org/debian bullseye InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E Fetched 11.6 kB in 1s (7,993 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. 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: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.raspberrypi.org/debian bullseye InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E 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: Failed to fetch http://archive.raspberrypi.org/debian/dists/bullseye/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E W: Some index files failed to download. They have been ignored, or old ones used instead.@gib64 sagte in Webinterface nicht mehr aufrufbar:
82B129927FA3303E
wget http://archive.raspberrypi.org/debian/raspberrypi.gpg.key sudo apt-key add raspberrypi.gpg.key rm raspberrypi.gpg.key -
@gib64 sagte in Webinterface nicht mehr aufrufbar:
82B129927FA3303E
wget http://archive.raspberrypi.org/debian/raspberrypi.gpg.key sudo apt-key add raspberrypi.gpg.key rm raspberrypi.gpg.key@thomas-braun Danke lief fehlerfrei durch aber ich bekomme immer noch Influx angemeckert obwohl ich den Key erneuert hatte:
pi@raspberry64:~ $ sudo apt update Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://security.debian.org/debian-security bullseye-security InRelease Get:5 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B] Get:6 https://repos.influxdata.com/debian bullseye InRelease [7,040 B] Err:6 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 11.6 kB in 2s (7,264 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. 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@raspberry64:~ $Edit: kann es sein das beim Import was schief gelaufen ist?:
pi@raspberry64:~ $ apt-key list Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). /etc/apt/trusted.gpg -------------------- pub rsa2048 2012-06-17 [SC] CF8A 1AF5 02A2 AA2D 763B AE7E 82B1 2992 7FA3 303E uid [ unknown] Raspberry Pi Archive Signing Key sub rsa2048 2012-06-17 [E] /etc/apt/trusted.gpg.d/debian-archive-bookworm-automatic.gpg ------------------------------------------------------------ pub rsa4096 2023-01-21 [SC] [expires: 2031-01-19] B8B8 0B5B 623E AB6A D877 5C45 B7C5 D7D6 3509 47F8 uid [ unknown] Debian Archive Automatic Signing Key (12/bookworm) <ftpmaster@debian.org> sub rsa4096 2023-01-21 [S] [expires: 2031-01-19] /etc/apt/trusted.gpg.d/debian-archive-bookworm-security-automatic.gpg --------------------------------------------------------------------- pub rsa4096 2023-01-21 [SC] [expires: 2031-01-19] 05AB 9034 0C0C 5E79 7F44 A8C8 254C F3B5 AEC0 A8F0 uid [ unknown] Debian Security Archive Automatic Signing Key (12/bookworm) <ftpmaster@debian.org> sub rsa4096 2023-01-21 [S] [expires: 2031-01-19] /etc/apt/trusted.gpg.d/debian-archive-bookworm-stable.gpg --------------------------------------------------------- pub ed25519 2023-01-23 [SC] [expires: 2031-01-21] 4D64 FEC1 19C2 0290 67D6 E791 F8D2 585B 8783 D481 uid [ unknown] Debian Stable Release Key (12/bookworm) <debian-release@lists.debian.org> /etc/apt/trusted.gpg.d/debian-archive-bullseye-automatic.gpg ------------------------------------------------------------ pub rsa4096 2021-01-17 [SC] [expires: 2029-01-15] 1F89 983E 0081 FDE0 18F3 CC96 73A4 F27B 8DD4 7936 uid [ unknown] Debian Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org> sub rsa4096 2021-01-17 [S] [expires: 2029-01-15] /etc/apt/trusted.gpg.d/debian-archive-bullseye-security-automatic.gpg --------------------------------------------------------------------- pub rsa4096 2021-01-17 [SC] [expires: 2029-01-15] AC53 0D52 0F2F 3269 F5E9 8313 A484 4904 4AAD 5C5D uid [ unknown] Debian Security Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org> sub rsa4096 2021-01-17 [S] [expires: 2029-01-15] /etc/apt/trusted.gpg.d/debian-archive-bullseye-stable.gpg --------------------------------------------------------- pub rsa4096 2021-02-13 [SC] [expires: 2029-02-11] A428 5295 FC7B 1A81 6000 62A9 605C 66F0 0D6C 9793 uid [ unknown] Debian Stable Release Key (11/bullseye) <debian-release@lists.debian.org> /etc/apt/trusted.gpg.d/debian-archive-buster-automatic.gpg ---------------------------------------------------------- pub rsa4096 2019-04-14 [SC] [expires: 2027-04-12] 80D1 5823 B7FD 1561 F9F7 BCDD DC30 D7C2 3CBB ABEE uid [ unknown] Debian Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org> sub rsa4096 2019-04-14 [S] [expires: 2027-04-12] /etc/apt/trusted.gpg.d/debian-archive-buster-security-automatic.gpg ------------------------------------------------------------------- pub rsa4096 2019-04-14 [SC] [expires: 2027-04-12] 5E61 B217 265D A980 7A23 C5FF 4DFA B270 CAA9 6DFA uid [ unknown] Debian Security Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org> sub rsa4096 2019-04-14 [S] [expires: 2027-04-12] /etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg ------------------------------------------------------- pub rsa4096 2019-02-05 [SC] [expires: 2027-02-03] 6D33 866E DD8F FA41 C014 3AED DCC9 EFBF 77E1 1517 uid [ unknown] Debian Stable Release Key (10/buster) <debian-release@lists.debian.org> pi@raspberry64:~ $ -
@thomas-braun Danke lief fehlerfrei durch aber ich bekomme immer noch Influx angemeckert obwohl ich den Key erneuert hatte:
pi@raspberry64:~ $ sudo apt update Hit:1 http://archive.raspberrypi.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://security.debian.org/debian-security bullseye-security InRelease Get:5 https://deb.nodesource.com/node_16.x bullseye InRelease [4,586 B] Get:6 https://repos.influxdata.com/debian bullseye InRelease [7,040 B] Err:6 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 11.6 kB in 2s (7,264 B/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. 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@raspberry64:~ $Edit: kann es sein das beim Import was schief gelaufen ist?:
pi@raspberry64:~ $ apt-key list Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)). /etc/apt/trusted.gpg -------------------- pub rsa2048 2012-06-17 [SC] CF8A 1AF5 02A2 AA2D 763B AE7E 82B1 2992 7FA3 303E uid [ unknown] Raspberry Pi Archive Signing Key sub rsa2048 2012-06-17 [E] /etc/apt/trusted.gpg.d/debian-archive-bookworm-automatic.gpg ------------------------------------------------------------ pub rsa4096 2023-01-21 [SC] [expires: 2031-01-19] B8B8 0B5B 623E AB6A D877 5C45 B7C5 D7D6 3509 47F8 uid [ unknown] Debian Archive Automatic Signing Key (12/bookworm) <ftpmaster@debian.org> sub rsa4096 2023-01-21 [S] [expires: 2031-01-19] /etc/apt/trusted.gpg.d/debian-archive-bookworm-security-automatic.gpg --------------------------------------------------------------------- pub rsa4096 2023-01-21 [SC] [expires: 2031-01-19] 05AB 9034 0C0C 5E79 7F44 A8C8 254C F3B5 AEC0 A8F0 uid [ unknown] Debian Security Archive Automatic Signing Key (12/bookworm) <ftpmaster@debian.org> sub rsa4096 2023-01-21 [S] [expires: 2031-01-19] /etc/apt/trusted.gpg.d/debian-archive-bookworm-stable.gpg --------------------------------------------------------- pub ed25519 2023-01-23 [SC] [expires: 2031-01-21] 4D64 FEC1 19C2 0290 67D6 E791 F8D2 585B 8783 D481 uid [ unknown] Debian Stable Release Key (12/bookworm) <debian-release@lists.debian.org> /etc/apt/trusted.gpg.d/debian-archive-bullseye-automatic.gpg ------------------------------------------------------------ pub rsa4096 2021-01-17 [SC] [expires: 2029-01-15] 1F89 983E 0081 FDE0 18F3 CC96 73A4 F27B 8DD4 7936 uid [ unknown] Debian Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org> sub rsa4096 2021-01-17 [S] [expires: 2029-01-15] /etc/apt/trusted.gpg.d/debian-archive-bullseye-security-automatic.gpg --------------------------------------------------------------------- pub rsa4096 2021-01-17 [SC] [expires: 2029-01-15] AC53 0D52 0F2F 3269 F5E9 8313 A484 4904 4AAD 5C5D uid [ unknown] Debian Security Archive Automatic Signing Key (11/bullseye) <ftpmaster@debian.org> sub rsa4096 2021-01-17 [S] [expires: 2029-01-15] /etc/apt/trusted.gpg.d/debian-archive-bullseye-stable.gpg --------------------------------------------------------- pub rsa4096 2021-02-13 [SC] [expires: 2029-02-11] A428 5295 FC7B 1A81 6000 62A9 605C 66F0 0D6C 9793 uid [ unknown] Debian Stable Release Key (11/bullseye) <debian-release@lists.debian.org> /etc/apt/trusted.gpg.d/debian-archive-buster-automatic.gpg ---------------------------------------------------------- pub rsa4096 2019-04-14 [SC] [expires: 2027-04-12] 80D1 5823 B7FD 1561 F9F7 BCDD DC30 D7C2 3CBB ABEE uid [ unknown] Debian Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org> sub rsa4096 2019-04-14 [S] [expires: 2027-04-12] /etc/apt/trusted.gpg.d/debian-archive-buster-security-automatic.gpg ------------------------------------------------------------------- pub rsa4096 2019-04-14 [SC] [expires: 2027-04-12] 5E61 B217 265D A980 7A23 C5FF 4DFA B270 CAA9 6DFA uid [ unknown] Debian Security Archive Automatic Signing Key (10/buster) <ftpmaster@debian.org> sub rsa4096 2019-04-14 [S] [expires: 2027-04-12] /etc/apt/trusted.gpg.d/debian-archive-buster-stable.gpg ------------------------------------------------------- pub rsa4096 2019-02-05 [SC] [expires: 2027-02-03] 6D33 866E DD8F FA41 C014 3AED DCC9 EFBF 77E1 1517 uid [ unknown] Debian Stable Release Key (10/buster) <debian-release@lists.debian.org> pi@raspberry64:~ $@gib64 sagte in Webinterface nicht mehr aufrufbar:
Edit: kann es sein das beim Import was schief gelaufen ist?:
Nein, die Pakete sind mehrfach signiert.
Zu influx:
ls -lAh /etc/apt/sources.list.d/sagt? Ich vermute da liegen zwei Dateien mit Bezug zu influx drin.
-
@gib64 sagte in Webinterface nicht mehr aufrufbar:
Edit: kann es sein das beim Import was schief gelaufen ist?:
Nein, die Pakete sind mehrfach signiert.
Zu influx:
ls -lAh /etc/apt/sources.list.d/sagt? Ich vermute da liegen zwei Dateien mit Bezug zu influx drin.
@thomas-braun said in Webinterface nicht mehr aufrufbar:
ls -lAh /etc/apt/sources.list.d/
pi@raspberry64:~ $ ls -lAh /etc/apt/sources.list.d/ total 12K -rw-r--r-- 1 root root 0 Oct 5 15:19 grafana.list -rw-r--r-- 1 root root 101 Oct 5 15:27 influxdb.list -rw-r--r-- 1 root root 208 Dec 1 2022 nodesource.list -rw-r--r-- 1 root root 191 Sep 22 2022 raspi.list pi@raspberry64:~ $ -
@thomas-braun said in Webinterface nicht mehr aufrufbar:
ls -lAh /etc/apt/sources.list.d/
pi@raspberry64:~ $ ls -lAh /etc/apt/sources.list.d/ total 12K -rw-r--r-- 1 root root 0 Oct 5 15:19 grafana.list -rw-r--r-- 1 root root 101 Oct 5 15:27 influxdb.list -rw-r--r-- 1 root root 208 Dec 1 2022 nodesource.list -rw-r--r-- 1 root root 191 Sep 22 2022 raspi.list pi@raspberry64:~ $sudo rm /etc/apt/sources.list.d/influxdb.list 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 /usr/share/keyrings/influxdata-archive_compat.gpg > /dev/null echo 'deb [signed-by=/usr/share/keyrings/influxdata-archive_compat.gpg] https://repos.influxdata.com/debian stable main' | sudo tee /etc/apt/sources.list.d/influxdata.list rm influxdata-archive_compat.keyDann nochmal
sudo apt update -
@thomas-braun Vielen Dank! Jetzt ist alles auf Stand ohne Fehler. Aber mal ehrlich, wie hätte ich da als Windows User drauf kommen sollen?
@gib64 sagte in Webinterface nicht mehr aufrufbar:
Aber mal ehrlich, wie hätte ich da als Windows User drauf kommen sollen?
Lesen bildet. Linux und Debian ist sehr gut dokumentiert.
Support us
403
Online32.7k
Benutzer82.4k
Themen1.3m
Beiträge