Daemon ne démarre pas en version 2025-01-19 19:08:00

Bonjour,

Je remet un post car le deamon ne veut toujours pas démarrer lors de l’installation dans la version du 19 janvier sous debian 11.

Quelqu’un peut m’aider ?
Merci.
Benoit

[2025-02-03 14:52:00] INFO  : Début d'activation du plugin
[2025-02-03 14:52:01] INFO  : Info sur le démon : {"log":"MyTado_daemon","state":"nok","launchable":"ok","launchable_message":"Gestion automatique d\u00e9sactiv\u00e9e","auto":"0","last_launch":"Inconnue"}
[2025-02-03 14:52:01] DEBUG  : Lancement de : /var/www/html/core/class/../../core/php/jeePlugin.php  plugin_id=MyTado function=install callInstallFunction=1
[2025-02-03 14:52:02] INFO  : Installation du plugin MyTado
[2025-02-03 14:53:29] INFO  : Lancement du démon
[2025-02-03 14:55:07] INFO  : Lancement du démon
+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_MyTado
+ 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 https://deb.debian.org/debian bullseye InRelease
Hit:2 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:3 https://deb.debian.org/debian bullseye-updates InRelease
Hit:4 https://deb.nodesource.com/node_20.x nodistro InRelease
Hit:5 https://deb.debian.org/debian bullseye-backports InRelease
Reading package lists...
Building dependency tree...
Reading state information...
1 package can be upgraded. Run 'apt list --upgradable' to see it.
+ echo 3
+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
python3 is already the newest version (3.9.2-3).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
+ echo 4
++ cut -f 2-
++ awk '$1 <= 4'
++ find /usr/local/lib/python3.9/dist-packages/ -mindepth 1 -maxdepth 1 -type d -exec du -ks '{}' +
+ RESULTTODELETE=
++ sed 's, ,\ ,g'
++ echo ''
+ RESULTTODELETE2=
+ xargs rm -rf
+ echo ''
+ echo 5
+ sudo pip3 cache purge
Files removed: 43 (1.5 MB)
+ echo 6
+ sudo pip3 install --upgrade pip
Requirement already satisfied: pip in /usr/local/lib/python3.9/dist-packages (25.0)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
+ echo 7
+ sudo python3 -m pip install --force-reinstall --upgrade typing
Collecting typing
Downloading typing-3.7.4.3.tar.gz (78 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Building wheels for collected packages: typing
Building wheel for typing (setup.py): started
Building wheel for typing (setup.py): finished with status 'done'
Created wheel for typing: filename=typing-3.7.4.3-py3-none-any.whl size=26308 sha256=cff00fcff2f98f17c698670057016ebb92373286371ca64ea42f6477616af322
Stored in directory: /root/.cache/pip/wheels/fa/17/1f/332799f975d1b2d7f9b3f33bbccf65031e794717d24432caee
Successfully built typing
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
Installing collected packages: typing
Attempting uninstall: typing
Found existing installation: typing 3.7.4.3
Uninstalling typing-3.7.4.3:
Successfully uninstalled typing-3.7.4.3
Successfully installed typing-3.7.4.3
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
+ echo 8
+ sudo python3 -m pip install --force-reinstall --upgrade requests
Collecting requests
Downloading requests-2.32.3-py3-none-any.whl.metadata (4.6 kB)
Collecting charset-normalizer<4,>=2 (from requests)
Downloading charset_normalizer-3.4.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (35 kB)
Collecting idna<4,>=2.5 (from requests)
Downloading idna-3.10-py3-none-any.whl.metadata (10 kB)
Collecting urllib3<3,>=1.21.1 (from requests)
Downloading urllib3-2.3.0-py3-none-any.whl.metadata (6.5 kB)
Collecting certifi>=2017.4.17 (from requests)
Downloading certifi-2025.1.31-py3-none-any.whl.metadata (2.5 kB)
Downloading requests-2.32.3-py3-none-any.whl (64 kB)
Downloading certifi-2025.1.31-py3-none-any.whl (166 kB)
Downloading charset_normalizer-3.4.1-cp39-cp39-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (141 kB)
Downloading idna-3.10-py3-none-any.whl (70 kB)
Downloading urllib3-2.3.0-py3-none-any.whl (128 kB)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
Installing collected packages: urllib3, idna, charset-normalizer, certifi, requests
Attempting uninstall: urllib3
Found existing installation: urllib3 2.3.0
Uninstalling urllib3-2.3.0:
Successfully uninstalled urllib3-2.3.0
Attempting uninstall: idna
Found existing installation: idna 3.10
Uninstalling idna-3.10:
Successfully uninstalled idna-3.10
Attempting uninstall: charset-normalizer
Found existing installation: charset-normalizer 3.4.1
Uninstalling charset-normalizer-3.4.1:
Successfully uninstalled charset-normalizer-3.4.1
Attempting uninstall: certifi
Found existing installation: certifi 2025.1.31
Uninstalling certifi-2025.1.31:
Successfully uninstalled certifi-2025.1.31
Attempting uninstall: requests
Found existing installation: requests 2.32.3
Uninstalling requests-2.32.3:
Successfully uninstalled requests-2.32.3
Successfully installed certifi-2025.1.31 charset-normalizer-3.4.1 idna-3.10 requests-2.32.3 urllib3-2.3.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
+ echo 9
+ sudo python3 -m pip install --force-reinstall --upgrade psutil
Collecting psutil
Downloading psutil-6.1.1-cp36-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (22 kB)
Downloading psutil-6.1.1-cp36-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (289 kB)
WARNING: Error parsing dependencies of gpg: Invalid version: '1.14.0-unknown'
Installing collected packages: psutil
Attempting uninstall: psutil
Found existing installation: psutil 6.1.1
Uninstalling psutil-6.1.1:
Successfully uninstalled psutil-6.1.1
Successfully installed psutil-6.1.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.
+ echo 10
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end MyTado
+ echo 11
+ rm /tmp/jeedom_install_in_progress_MyTado
+ echo '*******************End of package installation******************'
*******************End of package installation******************
Error: importing module jeedom.jeedom
Error: importing module jeedom.jeedom


Informations Jeedom Luna

Core : 4.4.19 (master)
DNS Jeedom Luna : oui

Plugin : MyTado
Version : 2025-01-19 19:08:00 (stable)
Statut Démon : Stoppé - (2025-02-03 14:53:28)

Evitez d’ouvrir plusieurs posts pour un même problème svp. Je vous ai déjà répondu sur le précédent et vous n’avez pas donné suite…
J’attends votre retour sur votre précédent post donc.