Probleme de dependances network plugin

Bonjour, jetant un oeil a mon installation jeedom aujourd’hui je constate que j’ai un soucis avec les dependances du plugin network, en effet ces dernieres sont NOK et il m’est impossible de forcer leur installation (ou plutot lorsque je force l’installation celle-ci se termine avec une erreur).

voici le log du plugin :


+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_networks
+ echo 1
+ echo 2
+ sudo killall apt apt-get unattended-upgr
apt: no process found
apt-get: no process found
unattended-upgr: no process found
+ sudo rm /var/lib/apt/lists/lock
+ sudo rm /var/cache/apt/archives/lock
+ sudo rm /var/lib/dpkg/lock /var/lib/dpkg/lock-frontend
+ sudo sudo dpkg --configure -a --force-confdef
+ sudo apt update
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 http://phoscon.de/apt/deconz buster InRelease
Hit:4 https://download.docker.com/linux/debian buster InRelease
Reading package lists...
Building dependency tree...
Reading state information...
195 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Problem unlinking the file deb.nodesource.com_node%5f16.x_dists_buster_InRelease - pkgAcquire::Clean (21: Is a directory)
+ echo 3
+ sudo apt install -o Dpkg::Options::=--force-confdef -y wakeonlan
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
wakeonlan is already the newest version (0.41-12).
0 upgraded, 0 newly installed, 0 to remove and 195 not upgraded.
+ echo 4
+ sudo apt install -o Dpkg::Options::=--force-confdef -y etherwake
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
etherwake is already the newest version (1.09-4).
0 upgraded, 0 newly installed, 0 to remove and 195 not upgraded.
+ echo 5
+ sudo apt install -o Dpkg::Options::=--force-confdef -y arping
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
libnet1
The following NEW packages will be installed:
arping libnet1
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin:
0 upgraded, 2 newly installed, 0 to remove and 195 not upgraded.
Need to get 0 B/82.4 kB of archives.
After this operation, 201 kB of additional disk space will be used.
Selecting previously unselected package libnet1:armhf.
(Reading database ... 
dpkg: warning: files list file for package 'net-tools' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'libproxy1v5:armhf' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'libpng-tools' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'libcgi-pm-perl' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'libxext6:armhf' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'xxd' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'libxcb-xinerama0:armhf' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'libass9:armhf' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'libgcc-8-dev:armhf' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'libsmbclient:armhf' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'libpython2-dev:armhf' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'libusb-1.0-0:armhf' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'binutils-arm-linux-gnueabihf' missing; assuming package has no files currently installed
dpkg: warning: files list file for package 'python3-cffi-backend' missing; assuming package has no files currently installed
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
dpkg: unrecoverable fatal error, aborting:
files list file for package 'libbluetooth3:armhf' is missing final newline
E: Sub-process /usr/bin/dpkg returned an error code (2)
+ echo 6
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end networks
+ echo 7
+ rm /tmp/jeedom_install_in_progress_networks
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Core : 4.4.5 (V4-stable)
DNS Jeedom : oui

Plugin : Network
Version : 2024-01-09 01:06:03 (stable)

Bonjour,

Ce n’est pas le plugin le problème là mais plusieurs paquets du système dans un état instable ou corrompu.

Faudrait regarder plus en détails chaque erreur, ou en profiter pour réinstaller proprement sous bullseye

D’ailleurs même log sur un autre plugin :wink:

J’ai fait une reinstallation il y a pas si longtemps en passant d’un raspberry pi 3 a un pi 4, suite a la reinsatllation de bullseye j’ai reinjecté une sauvegarde de mon jeedom dessus, est là mon erreur, ou serait il a nouveau necessaire que je refasse une installation propre (et reconfigure par là même tous mes scénarios)?

Vous n’avez pas un système sous bullseye là mais buster donc si cela a été fait « il n’y a pas longtemps », c’est bien dommage.
Là perso je vais pas perdre du temps à chercher alors qu’en 30min le système est réinstallé…

bah non… aucun besoin de refaire les scénarios après avoir restauré un backup jeedom

Désolé et merci pour votre réponse, pointant mon erreur et de confirmer qu’une restauration de backup (même sous une version anterieur) est bien la marche a suivre.
Effectivement je n’avais pas pris le remps de verifier mon os et lors de la reinstall j’avais du suivre le même tuto qu’a l’epoque du raspberry pi 3.

Navré pour la reponse « a coté » et merci encore à vous.