Fehlerhafte Pakete dpkg returned an error code (1)

[pumuckl]

Hallo zusammen und frohes neues Jahr,


Ich hatte gestern bemerkt, dass die Gpio's am Loxberry nicht funktionierten,

Das Problem wurde schnell erkannt:

ModuleNotFoundError: No module named 'RPi'

apt-get install python3-dev python3-rpi.gpio

die Gpio's funktionieren wieder, aber ich hatte folgende Fehler:

dpkg: error processing package libnss-systemd:armhf (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
systemd
libpam-systemd:armhf
libnss-systemd:armhf
E: Sub-process /usr/bin/dpkg returned an error code (1)

Deswegen versuchte ich die Pakte zu aktualisieren und bin auf weiter Fehler gestossen:

root@loxberry:/opt/loxberry/webfrontend/legacy# apt update
Hit:1 http://ftp.de.debian.org/debian testing InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 https://dl.yarnpkg.com/debian stable InRelease
Hit:4 https://deb.nodesource.com/node_12.x buster InRelease
Get:5 https://download.docker.com/linux/raspbian buster InRelease [33.6 kB]
Err:6 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian buster InRelease
Could not connect to ftp.agdsn.de:80 (141.30.235.39), connection timed out
Fetched 33.6 kB in 30s (1,111 B/s)
Update rpimonitor Packages Status
Reading package lists... Done
Building dependency tree
Reading state information... Done
773 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian/dists/buster/InRelease Could not connect to ftp.agdsn.de:80 (141.30.235.39), connection timed out
W: Some index files failed to download. They have been ignored, or old ones used instead.

apt upgrade -y

762 upgraded, 71 newly installed, 0 to remove and 11 not upgraded.
3 not fully installed or removed.
Need to get 0 B/414 MB of archives.
After this operation, 22.9 MB disk space will be freed.
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up systemd (249.7-1) ...
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned error exit status 73
Errors were encountered while processing:
systemd
E: Sub-process /usr/bin/dpkg returned an error code (1)

Ich konnte das an meinen zweiten Loxberry auch feststellen.

Beide sind auf Version 2.2.1.2, die Installationen sind unterschiedlich alt.

Ist das ein allgemeines Problem?


Grüsse

[Prof.Mobilux]

Sieht so aus als ob Du keinen Internetzugriff hast?

Could not connect to ftp.agdsn.de:80 (141.30.235.39), connection timed out

[pumuckl]

Wie es aussieht, kann ich nur den ftp Server nicht erreichen, die Webseite ist erreichbar.

Meine Internetverbindung funktioniert eigentlich, dass der ftp Server von meiner Firewall geblockt wird kann ich nicht feststellen.

Habe nur ich das Problem?

# /sbin/ping -c '3' 'ftp.agdsn.de' PING ftp.agdsn.de (141.30.235.39): 56 data bytes --- ftp.agdsn.de ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss

# /sbin/ping -c '3' 'agdsn.de' PING agdsn.de (141.76.119.130): 56 data bytes 64 bytes from 141.76.119.130: icmp_seq=0 ttl=52 time=34.171 ms 64 bytes from 141.76.119.130: icmp_seq=1 ttl=52 time=33.701 ms 64 bytes from 141.76.119.130: icmp_seq=2 ttl=52 time=33.252 ms --- agdsn.de ping statistics --- 3 packets transmitted, 3 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 33.252/33.708/34.171/0.375 ms

[pumuckl]

Der Ftp Server ist jetzt erreichbar, könnte doch intern blockiert worden sein. muss ich noch genauer prüfen.


Ich habe dennoch fehlerhafte Pakete:
Weder

apt-get install -f

noch

dpkg --configure -a

können daran etwas ändern.


Loxberry1:

root@loxberry:/opt/loxberry/webfrontend/legacy# apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 773 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up systemd (249.7-1) ...
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned error exit status 73
dpkg: dependency problems prevent configuration of libpam-systemd:armhf:
libpam-systemd:armhf depends on systemd (= 249.7-1); however:
Package systemd is not configured yet.

dpkg: error processing package libpam-systemd:armhf (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libnss-systemd:armhf:
libnss-systemd:armhf depends on systemd (= 249.7-1); however:
Package systemd is not configured yet.

dpkg: error processing package libnss-systemd:armhf (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
systemd
libpam-systemd:armhf
libnss-systemd:armhf
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@loxberry:/opt/loxberry/webfrontend/legacy#
root@loxberry:/opt/loxberry/webfrontend/legacy#
root@loxberry:/opt/loxberry/webfrontend/legacy#
root@loxberry:/opt/loxberry/webfrontend/legacy#
root@loxberry:/opt/loxberry/webfrontend/legacy#
root@loxberry:/opt/loxberry/webfrontend/legacy# dpkg --configure -a
Setting up systemd (249.7-1) ...
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned error exit status 73
dpkg: dependency problems prevent configuration of libpam-systemd:armhf:
libpam-systemd:armhf depends on systemd (= 249.7-1); however:
Package systemd is not configured yet.

dpkg: error processing package libpam-systemd:armhf (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libnss-systemd:armhf:
libnss-systemd:armhf depends on systemd (= 249.7-1); however:
Package systemd is not configured yet.

dpkg: error processing package libnss-systemd:armhf (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
systemd
libpam-systemd:armhf
libnss-systemd:armhf
root@loxberry:/opt/loxberry/webfrontend/legacy#

Loxberry2:

root@loxberry:/opt/loxberry/webfrontend/legacy# apt-get install -f
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 773 not upgraded.
3 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up systemd (249.7-1) ...
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned error exit status 73
dpkg: dependency problems prevent configuration of libpam-systemd:armhf:
libpam-systemd:armhf depends on systemd (= 249.7-1); however:
Package systemd is not configured yet.

dpkg: error processing package libpam-systemd:armhf (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libnss-systemd:armhf:
libnss-systemd:armhf depends on systemd (= 249.7-1); however:
Package systemd is not configured yet.

dpkg: error processing package libnss-systemd:armhf (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
systemd
libpam-systemd:armhf
libnss-systemd:armhf
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@loxberry:/opt/loxberry/webfrontend/legacy#
root@loxberry:/opt/loxberry/webfrontend/legacy#
root@loxberry:/opt/loxberry/webfrontend/legacy#
root@loxberry:/opt/loxberry/webfrontend/legacy#
root@loxberry:/opt/loxberry/webfrontend/legacy# dpkg --configure -a
Setting up systemd (249.7-1) ...
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
Detected unsafe path transition /var/log (owned by daemon) → /var/log/journal (owned by root) during canonicalization of /var/log/journal.
dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned error exit status 73
dpkg: dependency problems prevent configuration of libpam-systemd:armhf:
libpam-systemd:armhf depends on systemd (= 249.7-1); however:
Package systemd is not configured yet.

dpkg: error processing package libpam-systemd:armhf (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libnss-systemd:armhf:
libnss-systemd:armhf depends on systemd (= 249.7-1); however:
Package systemd is not configured yet.

dpkg: error processing package libnss-systemd:armhf (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
systemd
libpam-systemd:armhf
libnss-systemd:armhf
root@loxberry:/opt/loxberry/webfrontend/legacy#

Ich habe noch folgendes gefunden:

Check if you are the owner of all directories:

stat / /dev /var
If you aren't the owner, run the following in terminal:

chown root DirectoryYouAreNotOwner
Note: replace DirectoryYouAreNotOwner with the directory that you aren't owner of. So for example if the owner of / was unknown:

chown root /

Das hat aber auch nicht geholfen.


Was kann ich sonst noch versuchen?

[svethi]

Die Probleme kommen wahrscheinlich nicht von Deiner jetzigen Installation. Die Aussage ist, dass ein essentieller Systemdienst nicht konfiguriert wäre und dadurch auch 2 libs nicht installiert werden konnten die zu diesem Dienst gehören. Die sollten sicher auch nicht jetzt installiert werden. Das sieht eigentlich für Deine Installation nicht gut aus. Funktioniert das System überhaupt?

[pumuckl]

Ein System (PI4) läuft schon über ein Jahr, das andere war ein Testsystem (Pi3) und ist seit 2 Wochen produktive.

Beide laufen, wenn die Gpios nicht ausgefallen wären hätte ich das Problem nicht erkannt.

Seltsam das ich auf unterschiedlichen Installationen fast dasselbe Problem haben.

Zwischen den Feiertagen habe ich für einen Freund ein Loxberry aufgesetzt, das ist aber ok.


Ich denke, ich werde meine Systeme neu aufsetzen.

Oder gib es noch Vorschläge wie ich die Systeme reparieren kann.

Gruss

[pumuckl]

Guten Morgen,

Weit bin ich nicht gekommen beim neu aufsetzen.

Das Problem wird vom 1Wire NG Plugin verursacht:

root@loxberry:/opt/loxberry# apt update
Hit:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 https://dl.yarnpkg.com/debian stable InRelease
Hit:4 https://deb.nodesource.com/node_12.x buster InRelease
Update rpimonitor Packages Status
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
root@loxberry:/opt/loxberry# apt upgrade -y
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Installation von MQTT und 1-Wire-NG:

root@loxberry:/opt/loxberry# apt update
Hit:1 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 http://ftp.de.debian.org/debian testing InRelease
Hit:4 https://dl.yarnpkg.com/debian stable InRelease
Hit:5 https://deb.nodesource.com/node_12.x buster InRelease
Update rpimonitor Packages Status
Reading package lists... Done
Building dependency tree
Reading state information... Done
1035 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@loxberry:/opt/loxberry#

apt upgrade -y

root@loxberry:/opt/loxberry# apt update
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian buster InRelease
Hit:3 http://ftp.de.debian.org/debian testing InRelease
Hit:4 https://dl.yarnpkg.com/debian stable InRelease
Hit:5 https://deb.nodesource.com/node_12.x buster InRelease
Update rpimonitor Packages Status
Reading package lists... Done
Building dependency tree
Reading state information... Done
416 packages can be upgraded. Run 'apt list --upgradable' to see them.

root@loxberry:/opt/loxberry# apt upgrade -y

0 upgraded, 0 newly installed, 0 to remove and 416 not upgraded.
root@loxberry:/opt/loxberry# root@loxberry:/opt/loxberry# apt upgrade -y
bash: root@loxberry:/opt/loxberry#: No such file or directory

root@loxberry:/opt/loxberry# 0 upgraded, 0 newly installed, 0 to remove and 415 not upgraded.
bash: 0: command not found
root@loxberry:/opt/loxberry# root@loxberry:/opt/loxberry#
bash: root@loxberry:/opt/loxberry#: No such file or directory

Wie kann das sein, vor der Plugin Installation waren alle Pakete aktuell?


Den dpkg Fehler kann ich gerade nicht reproduzieren, gestern Abend war er auf der neuen Installation nach dem 1 Wire Ng installiert hatte.



Die Installation-Logs sind im Anhang

[Prof.Mobilux]

Mmmhhh, das 1-Wire muss Pakete aus dem Testing-Branch von Buster installieren, weil die Original Buster-Pakete kaputt sind/waren. Aber es setzt den Default-Branch auf "Stable", sodass eigentlich nur Pakete aus Testing installiert werden, wo man das explizit "anweist". Bei Dir sieht es so aus, als ob der Testing jetzt als Standard-Repo hernimmt. Oder er kommt durcheinander, weil das "neue Testing" eventuell jetzt schon auf Bullseye basiert.

https://github.com/mschlenstedt/LoxBerry-Plugin-1-Wire-NG/blob/359cebb66d0705be7a5ac602b3c206214aac9504/postroot.sh#L26

Ich hab das so bei meinen Tests noch nie gesehen. Kannst Du mal schauen, ob bei Dir die Datei /etc/apt/apt.conf.d/99myDefaultRelease existiert und was da drin steht? Und dann mal folgenden Befehl ausführen und hier die Ausgabe posten:

apt-cache policy systemd

[pumuckl]

Bitte schön:

root@loxberry:/etc/apt/apt.conf.d# cat 99myDefaultRelease
APT::default-Release "stable";
root@loxberry:/etc/apt/apt.conf.d#

root@loxberry:/etc/apt/apt.conf.d# apt-cache policy systemd
systemd:
Installed: 241-7~deb10u8+rpi1
Candidate: 249.7-1
Version table:
249.7-1 500
500 http://ftp.de.debian.org/debian testing/main armhf Packages
*** 241-7~deb10u8+rpi1 500
500 http://ftp.agdsn.de/pub/mirrors/raspbian/raspbian buster/main armhf Packages
500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages
100 /var/lib/dpkg/status

Gruss

[Prof.Mobilux]

Danke, ich schau mir das an.