Erreur sur eibd : BusMonitor() : connect failes

bonjour,

Alors que tout marchait bien depuis longtemps (en EIBD déprécié, puis en KnxD depuis derniere maj) Jeedom ne communique plus avec ma passerelle KNX, toute commande se traduit par un message d’erreur « Erreur sur eibd::BusMonitor() : connect failed »
J’ai relancé les dépendances et le demon sans succés, et testé connexion bus et réseau. Le demon passe en erreur après 'echec d’une commande
Jeedom en V4220
Debian 10.4
sur Jeedom Smart
Pouvez vous m’aider ? Merci

Voici le log Eibd

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_eibd
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../plugins/eibd/plugin_info/pre-install.sh
+ sudo /var/www/html/core/class/../../plugins/eibd/plugin_info/pre-install.sh
*****************************************************************************************************
*                                         Remove eibd                                               *
*****************************************************************************************************
rm: cannot remove '/usr/local/lib/libpthsem*.so*': No such file or directory
rm: cannot remove '/var/log/knxd.log': No such file or directory
*****************************************************************************************************
*                                         Remove knxd                                               *
*****************************************************************************************************
sudo: sytemctl: command not found
sudo: sytemctl: command not found
sudo: sytemctl: command not found
sudo: sytemctl: command not found
Reading package lists...
Building dependency tree...
Reading state information...
Package 'knxd' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 195 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
Package 'knxd' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 195 not upgraded.
rm: cannot remove '/etc/knxd.conf': No such file or directory
rm: cannot remove '/etc/knxd.ini': No such file or directory
rm: cannot remove '/usr/lib/knxd': No such file or directory
rm: cannot remove '/usr/local/src/knxd': No such file or directory
+ echo 3
+ sudo apt update
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Get:1 http://www.deb-multimedia.org buster InRelease [17.8 kB]
Hit:2 http://security.debian.org/debian-security buster/updates InRelease
Hit:3 http://ftp.uk.debian.org/debian buster InRelease
Hit:4 https://deb.nodesource.com/node_16.x buster InRelease
Hit:5 http://ftp.uk.debian.org/debian buster-updates InRelease
Get:6 http://www.deb-multimedia.org buster/non-free Sources [3,244 B]
Hit:7 https://oph.mdrjr.net/meveric all InRelease
Get:8 http://www.deb-multimedia.org buster/main Sources [101 kB]
Hit:9 https://oph.mdrjr.net/meveric buster InRelease
Get:10 http://www.deb-multimedia.org buster/main arm64 Packages [112 kB]
Get:11 http://www.deb-multimedia.org buster/main Translation-en [82.7 kB]
Get:12 http://www.deb-multimedia.org buster/non-free arm64 Packages [1,508 B]
Get:13 http://www.deb-multimedia.org buster/non-free Translation-en [3,058 B]
Fetched 321 kB in 3s (107 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
194 packages can be upgraded. Run 'apt list --upgradable' to see them.
+ echo 4
+ sudo apt install -o Dpkg::Options::=--force-confdef -y knxd
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:
libev4
The following NEW packages will be installed:
knxd libev4
0 upgraded, 2 newly installed, 0 to remove and 195 not upgraded.
Need to get 322 kB of archives.
After this operation, 1,431 kB of additional disk space will be used.
Get:1 http://ftp.uk.debian.org/debian buster/main arm64 libev4 arm64 1:4.25-1 [37.4 kB]
Get:2 http://ftp.uk.debian.org/debian buster/main arm64 knxd arm64 0.14.30-1 [285 kB]
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:
Fetched 322 kB in 0s (1,203 kB/s)
Selecting previously unselected package libev4:arm64.
(Reading e ... 
(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%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 79256 files and directories currently installed.)
Preparing to unpack .../libev4_1%3a4.25-1_arm64.deb ...
Unpacking libev4:arm64 (1:4.25-1) ...
Selecting previously unselected package knxd.
Preparing to unpack .../knxd_0.14.30-1_arm64.deb ...
Unpacking knxd (0.14.30-1) ...
Setting up libev4:arm64 (1:4.25-1) ...
Setting up knxd (0.14.30-1) ...
Adding group `knxd' (GID 114) ...
Done.
Adding system user `knxd' (UID 107) ...
Adding new user `knxd' (UID 107) with group `knxd' ...
Creating home directory `/var/lib/knxd' ...
Created symlink /etc/systemd/system/multi-user.target.wants/knxd.service → /lib/systemd/system/knxd.service.
Created symlink /etc/systemd/system/network-online.target.wants/knxd.service → /lib/systemd/system/knxd.service.
Created symlink /etc/systemd/system/sockets.target.wants/knxd.socket → /lib/systemd/system/knxd.socket.
A dependency job for knxd.service failed. See 'journalctl -xe' for details.
Job for knxd.socket failed.
See "systemctl status knxd.socket" and "journalctl -xe" for details.
A dependency job for knxd.service failed. See 'journalctl -xe' for details.
invoke-rc.d: initscript knxd, action "start" failed.
● knxd.service - KNX Daemon
Loaded: loaded (e]8;;file://Jeedom/lib/systemd/system/knxd.servicea/lib/systemd/system/knxd.servicee]8;;a; enabled; vendor preset: enabled)
Active: inactive (dead)
Jul 02 08:51:41 Jeedom systemd[1]: e[0;1;39me[0;1;31me[0;1;39mDependency failed for KNX Daemon.e[0m
Jul 02 08:51:41 Jeedom systemd[1]: e[0;1;39me[0;1;31me[0;1;39mknxd.service: Job knxd.service/start failed with result 'dependency'.e[0m
Jul 02 08:51:44 Jeedom systemd[1]: e[0;1;39me[0;1;31me[0;1;39mDependency failed for KNX Daemon.e[0m
Jul 02 08:51:44 Jeedom systemd[1]: e[0;1;39me[0;1;31me[0;1;39mknxd.service: Job knxd.service/start failed with result 'dependency'.e[0m
dpkg: error processing package knxd (--configure):
installed knxd package post-installation script subprocess returned error exit status 1
Processing triggers for systemd (241-7~deb10u4) ...
Processing triggers for libc-bin (2.28-10) ...
Errors were encountered while processing:
knxd
E: Sub-process /usr/bin/dpkg returned an error code (1)
+ echo 5
+ sudo apt install -o Dpkg::Options::=--force-confdef -y knxd-tools
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 NEW packages will be installed:
knxd-tools
0 upgraded, 1 newly installed, 0 to remove and 195 not upgraded.
1 not fully installed or removed.
Need to get 47.4 kB of archives.
After this operation, 238 kB of additional disk space will be used.
Get:1 http://ftp.uk.debian.org/debian buster/main arm64 knxd-tools arm64 0.14.30-1 [47.4 kB]
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:
Fetched 47.4 kB in 0s (338 kB/s)
Selecting previously unselected package knxd-tools.
(Reading database ... 
(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%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 79278 files and directories currently installed.)
Preparing to unpack .../knxd-tools_0.14.30-1_arm64.deb ...
Unpacking knxd-tools (0.14.30-1) ...
Setting up knxd (0.14.30-1) ...
addgroup: The group `knxd' already exists as a system group. Exiting.
Warning: The home dir /var/lib/knxd you specified already exists.
The system user `knxd' already exists. Exiting.
A dependency job for knxd.service failed. See 'journalctl -xe' for details.
Job for knxd.socket failed.
See "systemctl status knxd.socket" and "journalctl -xe" for details.
A dependency job for knxd.service failed. See 'journalctl -xe' for details.
invoke-rc.d: initscript knxd, action "start" failed.
● knxd.service - KNX Daemon
Loaded: loaded (e]8;;file://Jeedom/lib/systemd/system/knxd.servicea/lib/systemd/system/knxd.servicee]8;;a; enabled; vendor preset: enabled)
Active: inactive (dead)
Jul 02 08:51:41 Jeedom systemd[1]: e[0;1;39me[0;1;31me[0;1;39mDependency failed for KNX Daemon.e[0m
Jul 02 08:51:41 Jeedom systemd[1]: e[0;1;39me[0;1;31me[0;1;39mknxd.service: Job knxd.service/start failed with result 'dependency'.e[0m
Jul 02 08:51:44 Jeedom systemd[1]: e[0;1;39me[0;1;31me[0;1;39mDependency failed for KNX Daemon.e[0m
Jul 02 08:51:44 Jeedom systemd[1]: e[0;1;39me[0;1;31me[0;1;39mknxd.service: Job knxd.service/start failed with result 'dependency'.e[0m
Jul 02 08:51:52 Jeedom systemd[1]: e[0;1;39me[0;1;31me[0;1;39mDependency failed for KNX Daemon.e[0m
Jul 02 08:51:52 Jeedom systemd[1]: e[0;1;39me[0;1;31me[0;1;39mknxd.service: Job knxd.service/start failed with result 'dependency'.e[0m
Jul 02 08:51:54 Jeedom systemd[1]: e[0;1;39me[0;1;31me[0;1;39mDependency failed for KNX Daemon.e[0m
Jul 02 08:51:54 Jeedom systemd[1]: e[0;1;39me[0;1;31me[0;1;39mknxd.service: Job knxd.service/start failed with result 'dependency'.e[0m
dpkg: error processing package knxd (--configure):
installed knxd package post-installation script subprocess returned error exit status 1
Setting up knxd-tools (0.14.30-1) ...
Processing triggers for libc-bin (2.28-10) ...
Errors were encountered while processing:
knxd
E: Sub-process /usr/bin/dpkg returned an error code (1)
+ echo 6
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end eibd
+ rm /tmp/jeedom_install_in_progress_eibd
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Lo,

Pourriez-vous mettre vos logs entre les balises </> pour une meilleure lecture,

Merci, au plaisir,

Je vois déjà que le service est inactif
Active le en ssh

sudo systemctl enable knxd.service
sudo systemctl enable knxd.socket
sudo systemctl start knxd.service

Puis relance le démon

Bonjour, et merci Mika pour ta réponse
Je ne sais pas comment passer ces commandes, je suis désolé
peux tu m’aiguiller stp
merci

Lo,

Ouvre un terminal de type putty,
Tu dois renseigner l’ IP de ton Jeedom port 22,
Une fois connecté (une fenêtre noir apparaît), tu dois rentrer ton mot de passe
Lorsque tu seras connecté avec ton login, tu pourras copier/coller les commandes de Mika,

Au plaisir, bonne journée,

Merci Toms

voici ce que j’ai quand j’ouvre putty
en fait je ne sais pas quel login password utiliser, dans la doc j’ai vu « Jeedom » et « Mjeedom96 » mais cela ne focntionne pas. Ayant une smart je n’ai jamais créé de login password SSH. Lorsque j’utilise ceux d’ouverture de Jeedom celà ne marche pas,

login as: jeedom
jeedom@192.168.1.250’s password:
Access denied
jeedom@192.168.1.250’s password:
Access denied
jeedom@192.168.1.250’s password:

C’est pourtant ça il me semble.

Sinon depuis Jeedom dans la configuration tu as un outil d’administration système qui permet d’exécuter des commande.

Si tu préfères tu peux me faire parvenir une connexion sur ton jeedom pour que je regarde

merci je veux bien te donner un acces à mon jeedom, comment je dois faire pour un minimum de sécurité, pour te les envoyer ?

1 « J'aime »

Je t’ai transmis par email en réponse a ton message les identifiants administrateur d’un compte que j’ai ouvert pour toi. As tu besoin d’autre chose ?
Merci