Die APT-Datenbank konnte nicht aktualisiert werden

**svethi** · 26.04.2020, 20:39

DNS oder Internetproblem des Loxberry?

**Buffy** · 27.04.2020, 02:15

Wie kann ich das Prüfen, weil die Updates macht er alle, bekomme bloss jedesmal eine Mail mit dieser Meldung

**Christian Fenzl** · 27.04.2020, 05:49

An der Shell anmelden, und:
sudo apt-get update

**Buffy** · 27.04.2020, 15:02

Habe ich gemacht bekomme folgende Rückmeldung:

loxberry@loxberry:~ $ sudo apt-get update

Get:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]

Hit:2 https://deb.nodesource.com/node_12.x buster InRelease

Get:3 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB]

Err:3 https://dl.yarnpkg.com/debian stable InRelease

The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx>

Update rpimonitor Packages Status

Reading package lists... Done

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Origin' value from '' to 'Raspbian'

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Label' value from '' to 'Raspbian'

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from '' to 'stable'

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Codename' value from '' to 'buster'

N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx>

**Christian Fenzl** · 27.04.2020, 15:16

Hi,

wir haben das Yarn Signaturproblem in 2.0.2 (gibt's noch nicht) gefixt - Issue https://github.com/mschlenstedt/Loxberry/issues/1134.

Zur manuellen Lösung, kannst du bitte:

Per Putty als loxberry anmelden
Zu root machen: su
wget -O /tmp/yarnpkg.gpg.pub https://dl.yarnpkg.com/debian/pubkey.gpg
apt-key add /tmp/yarnpkg.gpg.pub

Das sollte das Problem beheben.

lg, Christian

**Buffy** · 27.04.2020, 15:24

super vielen Dank, werde das ganze jetzt beobachten.
Mit freundlichen Grüßen Tobi

**Buffy** · 30.04.2020, 14:15

Hi,
Der Fehler ist leider immer noch da. Hier die Meldung bei sudo apt-get update

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Origin' value from '' to 'Raspbian'

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Label' value from '' to 'Raspbian'

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Suite' value from '' to 'stable'

E: Repository 'http://raspbian.raspberrypi.org/raspbian buster InRelease' changed its 'Codename' value from '' to 'buster'

N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

**TomekWaw** · 22.05.2020, 13:29

Hi guys,
Sorry for writing in English this time but I will be more precise this way.
I have similar problem with APT database so I will not start another thread.

I have 3 LoxBerry systems at home and my oldeset was on on 1.4 until yesterday.
I decided to upgrade it finally and I took the challenge to upgrade it in-place.

The upgrade went almost fine with some minor errors resulting in message:

So I clicked Reset to version 1.99.99 but it didn't help.

So I upgraded to 2.0.1.3 and then upgraded every plugin to newest version.
Everything seems to work fine but that APT database, that gives errors every single plugin update.
It goes something like this:

Code:

[...]
22.05.2020 08:21:43 OK: File ownership set successfully.
22.05.2020 08:21:43 INFO: Refreshing APT database.
22.05.2020 08:21:43 INFO: Command: /usr/bin/dpkg --configure -a
22.05.2020 08:21:43 INFO: Command: APT_LISTCHANGES_FRONTEND=none DEBIAN_FRONTEND=noninteractive /usr/bin/apt-get -y -q --allow-unauthenticated --fix-broken --reinstall --allow-downgrades --allow-remove-essential --allow-change-held-packages --purge autoremove
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
22.05.2020 08:21:47 INFO: Command: APT_LISTCHANGES_FRONTEND=none DEBIAN_FRONTEND=noninteractive /usr/bin/apt-get -q -y --allow-unauthenticated --allow-downgrades --allow-remove-essential --allow-change-held-packages update
Hit:1 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian buster InRelease
Hit:2 https://download.docker.com/linux/raspbian buster InRelease
Hit:3 https://deb.nodesource.com/node_12.x buster InRelease
Hit:4 https://dl.yarnpkg.com/debian stable InRelease
Update rpimonitor Packages Status
No such file or directory
Reading package lists...
E: Problem executing scripts APT::Update::Post-Invoke 'echo 'Update rpimonitor Packages Status' && /usr/share/rpimonitor/scripts/updatePackagesStatus.pl'
E: Sub-process returned an error code
22.05.2020 08:21:58 ERROR: APT database could not be refreshed.

I don't exactly know what is this about. I had rpi-monitor plugin some time ago but I've removed it as it was wearing out my sdcard with it's stats.
I've read somewhere that removing rpimonitor might help so I've apt-get purged rpimonitor, but it didn't help.
I still get those errors.

Question is: can I somehow fix this LoxBerry install?
I really would like to avoid creating it from scratch even if I could reuse most of configurations saved in /opt
Any help appreciated. I'm generally familiar with Linux environment, but mostly with CentOS, Debian/Raspbian is pretty new to me.

**Christian Fenzl** · 22.05.2020, 14:12

As root user in the Shell, Go to
/etc/apt/sources.list.d/

Do ls -l and look for a File that seems to be dependent to rpimonitor.
Delete that file, or move it (only that one) to another directory.

Run sudo apt-get update

Still any error?
If no, retry LoxBerry Update.

Regards, Christian

**TomekWaw** · 22.05.2020, 14:48

Thanks Christian for your answer,
Here is how it looks:

I believe docker is for docker

but no idea what those other two are for (nodesource and yarn).

I've tried to move out yarn first but no any good:

Then I've tried to move other sources as well:

Unfortunately this doesn't seem to help.

**TomekWaw** · 22.05.2020, 15:17

Ok, I've probably handled that issue, this way:

So, I now press "Reset to 2.0.0.0" in update module?

Or shall I handle this state in another way?

**Christian Fenzl** · 22.05.2020, 20:21

You can remove the FAILED_SCRIPT key in general.cfg, as the rpimonitor thing was the only issue.

**TomekWaw** · 22.05.2020, 23:00

Danke schön! Works perfectly now!

**badmage** · 09.09.2020, 17:33

Hallo zusammen,

ich habe nun auch das Problem - wollte MQTT Gateway installieren und erhalte die gleiche Fehlermeldung:

FEHLER MQTT Gateway: APT refresh: Die APT-Datenbank konnte nicht aktualisiert werden.

Den Versuch mit der Aktualisierung vom yarn pub-key habe ich auch gemacht, leider auch ohne Erfolg:

Code:

root@loxberry:~# wget -O /tmp/yarnpkg.gpg.pub https://dl.yarnpkg.com/debian/pubkey.gpg
--2020-09-09 17:27:01-- https://dl.yarnpkg.com/debian/pubkey.gpg
Resolving dl.yarnpkg.com (dl.yarnpkg.com)... 104.18.126.100, 104.16.171.99, 2606:4700::6810:ab63, ...
Connecting to dl.yarnpkg.com (dl.yarnpkg.com)|104.18.126.100|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14115 (14K) [application/octet-stream]
Saving to: ‘/tmp/yarnpkg.gpg.pub’

/tmp/yarnpkg.gpg.pub 100%[================================================== ================================================== ====================================>] 13.78K --.-KB/s in 0.001s

2020-09-09 17:27:01 (9.47 MB/s) - ‘/tmp/yarnpkg.gpg.pub’ saved [14115/14115]

root@loxberry:~# apt-key add /tmp/yarnpkg.gpg.pub
OK
root@loxberry:~# apt-get update
Hit:1 http://ftp.halifax.rwth-aachen.de/raspbian/raspbian buster InRelease
Hit:3 http://debian.fhem.de/nightly InRelease
Hit:4 https://dl.yarnpkg.com/debian stable InRelease
Hit:5 https://deb.nodesource.com/node_12.x buster InRelease
Ign:2 https://apt.pilight.org stable InRelease
Get:6 https://apt.pilight.org stable Release [4,565 B]
Ign:7 https://apt.pilight.org stable Release.gpg
Ign:7 http://apt.pilight.org stable Release.gpg
Reading package lists... Done
E: The repository 'http://apt.pilight.org stable Release' is no longer 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.

Was kann ich tun um das Problem zu beheben?

Vielen Dank & viele Grüße

Die APT-Datenbank konnte nicht aktualisiert werden

Die APT-Datenbank konnte nicht aktualisiert werden

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar

Kommentar