Migration sous Debian 12

magifix · Décembre 18, 2024, 4:10

Bonjour,

J’essaie de migrer sous Debian 12, tout semble fonctionner sauf le deamon rfxcom. Dans la liste des compatibilités, il est mentionné que le test a été fait avec la version beta. Est-ce que la version du 2024-11-23 01:02:32 n’est pas encore compatible et donc ne permet pas au deamon de démarrer?

J’ai ce qui suit dans les logs:

> 
> ---
> 
> Traceback (most recent call last):
> File "/var/www/html/plugins/rfxcom/resources/rfxcomd/rfxcomd.py", line 23, in <module>
> from jeedomdaemon.base_config import BaseConfig
> ModuleNotFoundError: No module named 'jeedomdaemon.base_config'
> 
> ---
> 
> [2024-12-14 13:14:37] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
> [2024-12-14 13:14:38] INFO  : Lancement démon rfxcomd : /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv/bin/python3 /var/www/html/plugins/rfxcom/resources/rfxcomd/rfxcomd.py --device /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A11HEEYU-if00-port0 --loglevel debug --socketport 55000 --serialrate 38400 --protocol 1,5,18,20,23 --callback http://127.0.0.1:80/plugins/rfxcom/core/php/jeeRfxcom.php --apikey OGT9FCGR5ZnpUunlkB8l0b6553RuRUGU --cycle 0.3 --pid /tmp/jeedom/rfxcom/deamon.pid
> [2024-12-14 13:15:10] ERROR  : Impossible de lancer le démon RFXcom, vérifiez le log rfxcmd

Et j’ai le status suivant sous santé du plugin:

Le changelog du plugin précise ceci:

27/07/2024

Ajout compatibilité Debian 12 (version Jeedom 4.4.7 requise pour Debian 12)
Correction sur la gestion de l’arrêt du démon en cas de problème de configuration ou de connexion avec le rfxcom

Donc je ne sais pas si le problème est de mon côté ou s’il faut attendre? Merci par avance pour vos réponses

Mips · Décembre 18, 2024, 4:25

Bonjour,

Le plugin est compatible deb12 dans la version stable, comme vous avez vu dans le changelog

Comme pour chaque demande, veuillez fournir:

page santé jeedom (le haut, ce que vous avez donné ne sert à rien)
page config plugin complète
tous les logs collés dans un Texte préformaté (bouton </>), et pas une « Citation » (ni de fichier)

avez-vous lancé les dépendances? je n’ai pas l’impression.
A faire après chaque installation/restauration de backup jeedom même si elles sont marqués OK

magifix · Décembre 20, 2024, 12:13

Bonjour,

Merci d’avoir pris le temps de me répondre et désolé si les informations étaient insuffisantes, Voici les informations demandées:

Page santé:

config:

Et les logs:
rfxcom:

[2024-12-20 12:55:57] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-12-20 12:55:59] INFO  : Lancement démon rfxcomd : /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv/bin/python3 /var/www/html/plugins/rfxcom/resources/rfxcomd/rfxcomd.py --device /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A11HEEYU-if00-port0 --loglevel debug --socketport 55000 --serialrate 38400 --protocol 1,5,18,20,23 --callback http://127.0.0.1:80/plugins/rfxcom/core/php/jeeRfxcom.php --apikey OGT9FCGR5ZnpUunlkB8l0b6553RuRUGU --cycle 0.3 --pid /tmp/jeedom/rfxcom/deamon.pid
[2024-12-20 12:57:45] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-12-20 12:57:48] INFO  : Lancement démon rfxcomd : /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv/bin/python3 /var/www/html/plugins/rfxcom/resources/rfxcomd/rfxcomd.py --device /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A11HEEYU-if00-port0 --loglevel debug --socketport 55000 --serialrate 38400 --protocol 1,5,18,20,23 --callback http://127.0.0.1:80/plugins/rfxcom/core/php/jeeRfxcom.php --apikey OGT9FCGR5ZnpUunlkB8l0b6553RuRUGU --cycle 0.3 --pid /tmp/jeedom/rfxcom/deamon.pid
[2024-12-20 12:58:20] ERROR  : Impossible de lancer le démon RFXcom, vérifiez le log rfxcmd
[2024-12-20 13:00:12] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-12-20 13:00:14] INFO  : Lancement démon rfxcomd : /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv/bin/python3 /var/www/html/plugins/rfxcom/resources/rfxcomd/rfxcomd.py --device /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A11HEEYU-if00-port0 --loglevel debug --socketport 55000 --serialrate 38400 --protocol 1,5,18,20,23 --callback http://127.0.0.1:80/plugins/rfxcom/core/php/jeeRfxcom.php --apikey OGT9FCGR5ZnpUunlkB8l0b6553RuRUGU --cycle 0.3 --pid /tmp/jeedom/rfxcom/deamon.pid
[2024-12-20 13:00:46] ERROR  : Impossible de lancer le démon RFXcom, vérifiez le log rfxcmd
[2024-12-20 13:05:14] ERROR  : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement
[2024-12-20 13:05:16] INFO  : Lancement démon rfxcomd : /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv/bin/python3 /var/www/html/plugins/rfxcom/resources/rfxcomd/rfxcomd.py --device /dev/serial/by-id/usb-RFXCOM_RFXtrx433_A11HEEYU-if00-port0 --loglevel debug --socketport 55000 --serialrate 38400 --protocol 1,5,18,20,23 --callback http://127.0.0.1:80/plugins/rfxcom/core/php/jeeRfxcom.php --apikey OGT9FCGR5ZnpUunlkB8l0b6553RuRUGU --cycle 0.3 --pid /tmp/jeedom/rfxcom/deamon.pid
[2024-12-20 13:05:47] ERROR  : Impossible de lancer le démon RFXcom, vérifiez le log rfxcmd

rfxcom_package:

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_rfxcom
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../plugins/rfxcom/resources/pre-install.sh
+ sudo /var/www/html/core/class/../../plugins/rfxcom/resources/pre-install.sh
Launch pre-install of rfxcom dependancy
error: externally-managed-environment
× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.
If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.
For more information visit http://rptl.io/venv
note: If you believe this is a mistake, please contact your Python installation or OS distribution provider. You can override this, at the risk of breaking your Python installation or OS, by passing --break-system-packages.
hint: See PEP 668 for the detailed specification.
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
Package 'python3-serial' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ echo 3
+ 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://deb.debian.org/debian bookworm InRelease
Get:2 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
Get:3 http://archive.raspberrypi.com/debian bookworm InRelease [39.3 kB]
Get:4 http://deb.debian.org/debian bookworm-updates InRelease [55.4 kB]
Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
Get:6 http://archive.raspberrypi.com/debian bookworm/main armhf Packages [549 kB]
Get:7 http://archive.raspberrypi.com/debian bookworm/main arm64 Packages [520 kB]
Fetched 1211 kB in 4s (319 kB/s)
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
+ echo 4
+ 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.11.2-1+b1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ echo 5
+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-pip
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
python3-pip is already the newest version (23.0.1+dfsg-1+rpt1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ echo 6
+ sudo apt install -o Dpkg::Options::=--force-confdef -y build-essential
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
build-essential is already the newest version (12.9).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ echo 7
+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-pyudev
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
python3-pyudev is already the newest version (0.24.0-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ echo 8
+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-dev
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
python3-dev is already the newest version (3.11.2-1+b1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ echo 9
+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-requests
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
python3-requests is already the newest version (2.28.1+dfsg-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ echo 10
+ sudo apt install -o Dpkg::Options::=--force-confdef -y python3-setuptools
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Reading package lists...
Building dependency tree...
Reading state information...
python3-setuptools is already the newest version (66.1.1-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ echo 11
+ sudo apt update
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
Hit:1 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease
Reading package lists...
Building dependency tree...
Reading state information...
All packages are up to date.
+ sudo apt-get install -y python3 python3-pip python3-dev python3-venv
Reading package lists...
Building dependency tree...
Reading state information...
python3 is already the newest version (3.11.2-1+b1).
python3-pip is already the newest version (23.0.1+dfsg-1+rpt1).
python3-dev is already the newest version (3.11.2-1+b1).
python3-venv is already the newest version (3.11.2-1+b1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
+ echo 12
+ sudo python3 -m venv --upgrade-deps /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: python3 -m pip install --upgrade pip
error: uninstall-no-record-file
× Cannot uninstall setuptools None
╰─> The package's contents are unknown: no RECORD file was found for setuptools.
hint: You might be able to recover from this via: pip install --force-reinstall --no-deps setuptools==72.2.0
Error: Command '['/var/www/html/plugins/rfxcom/resources/python_venv/bin/python3', '-m', 'pip', 'install', '--upgrade', 'pip', 'setuptools']' returned non-zero exit status 1.
+ echo 13
+ sudo /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv/bin/python3 -m pip install --upgrade pip wheel
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: pip in /var/www/html/plugins/rfxcom/resources/python_venv/lib/python3.11/site-packages (24.2)
Collecting pip
Using cached https://www.piwheels.org/simple/pip/pip-24.3.1-py3-none-any.whl (1.8 MB)
Requirement already satisfied: wheel in /var/www/html/plugins/rfxcom/resources/python_venv/lib/python3.11/site-packages (0.44.0)
Collecting wheel
Using cached https://www.piwheels.org/simple/wheel/wheel-0.45.1-py3-none-any.whl (72 kB)
Installing collected packages: wheel, pip
Attempting uninstall: wheel
Found existing installation: wheel None
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: python3 -m pip install --upgrade pip
error: uninstall-no-record-file
× Cannot uninstall wheel None
╰─> The package's contents are unknown: no RECORD file was found for wheel.
hint: You might be able to recover from this via: pip install --force-reinstall --no-deps wheel==0.44.0
+ echo 14
+ sudo /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv/bin/python3 -m pip install --force-reinstall --upgrade six
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting six
Using cached https://www.piwheels.org/simple/six/six-1.17.0-py2.py3-none-any.whl (11 kB)
Installing collected packages: six
Attempting uninstall: six
Found existing installation: six None
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: python3 -m pip install --upgrade pip
error: uninstall-no-record-file
× Cannot uninstall six None
╰─> The package's contents are unknown: no RECORD file was found for six.
hint: You might be able to recover from this via: pip install --force-reinstall --no-deps six==1.16.0
+ echo 15
+ sudo /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv/bin/python3 -m pip install --force-reinstall --upgrade requests
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting requests
Using cached https://www.piwheels.org/simple/requests/requests-2.32.3-py3-none-any.whl (64 kB)
Collecting charset-normalizer<4,>=2 (from requests)
Using cached charset_normalizer-3.4.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (34 kB)
Collecting idna<4,>=2.5 (from requests)
Using cached https://www.piwheels.org/simple/idna/idna-3.10-py3-none-any.whl (70 kB)
Collecting urllib3<3,>=1.21.1 (from requests)
Using cached https://www.piwheels.org/simple/urllib3/urllib3-2.2.3-py3-none-any.whl (126 kB)
Collecting certifi>=2017.4.17 (from requests)
Downloading https://www.piwheels.org/simple/certifi/certifi-2024.12.14-py3-none-any.whl (164 kB)
Using cached charset_normalizer-3.4.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (138 kB)
Installing collected packages: urllib3, idna, charset-normalizer, certifi, requests
Attempting uninstall: urllib3
Found existing installation: urllib3 None
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: python3 -m pip install --upgrade pip
error: uninstall-no-record-file
× Cannot uninstall urllib3 None
╰─> The package's contents are unknown: no RECORD file was found for urllib3.
hint: You might be able to recover from this via: pip install --force-reinstall --no-deps urllib3==2.2.2
+ echo 16
+ sudo /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv/bin/python3 -m pip install --force-reinstall --upgrade setuptools
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting setuptools
Using cached https://www.piwheels.org/simple/setuptools/setuptools-75.6.0-py3-none-any.whl (1.2 MB)
Installing collected packages: setuptools
Attempting uninstall: setuptools
Found existing installation: setuptools None
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: python3 -m pip install --upgrade pip
error: uninstall-no-record-file
× Cannot uninstall setuptools None
╰─> The package's contents are unknown: no RECORD file was found for setuptools.
hint: You might be able to recover from this via: pip install --force-reinstall --no-deps setuptools==72.2.0
+ echo 17
+ sudo /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv/bin/python3 -m pip install --force-reinstall --upgrade pyudev
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting pyudev
Using cached https://www.piwheels.org/simple/pyudev/pyudev-0.24.3-py3-none-any.whl (62 kB)
Installing collected packages: pyudev
Attempting uninstall: pyudev
Found existing installation: pyudev None
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: python3 -m pip install --upgrade pip
error: uninstall-no-record-file
× Cannot uninstall pyudev None
╰─> The package's contents are unknown: no RECORD file was found for pyudev.
hint: You might be able to recover from this via: pip install --force-reinstall --no-deps pyudev==0.24.3
+ echo 18
+ sudo /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv/bin/python3 -m pip install --force-reinstall --upgrade pyserial
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting pyserial
Using cached https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl (90 kB)
Installing collected packages: pyserial
Attempting uninstall: pyserial
Found existing installation: pyserial None
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: python3 -m pip install --upgrade pip
error: uninstall-no-record-file
× Cannot uninstall pyserial None
╰─> The package's contents are unknown: no RECORD file was found for pyserial.
hint: You might be able to recover from this via: pip install --force-reinstall --no-deps pyserial==3.5
+ echo 19
+ sudo /var/www/html/core/class/../../plugins/rfxcom/resources/python_venv/bin/python3 -m pip install --force-reinstall --upgrade jeedomdaemon
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting jeedomdaemon
Using cached https://www.piwheels.org/simple/jeedomdaemon/jeedomdaemon-1.1.0-py3-none-any.whl (13 kB)
Collecting aiohttp (from jeedomdaemon)
Downloading aiohttp-3.11.11-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (7.7 kB)
Collecting aiohappyeyeballs>=2.3.0 (from aiohttp->jeedomdaemon)
Using cached https://www.piwheels.org/simple/aiohappyeyeballs/aiohappyeyeballs-2.4.4-py3-none-any.whl (14 kB)
Collecting aiosignal>=1.1.2 (from aiohttp->jeedomdaemon)
Using cached https://www.piwheels.org/simple/aiosignal/aiosignal-1.3.2-py2.py3-none-any.whl (7.6 kB)
Collecting attrs>=17.3.0 (from aiohttp->jeedomdaemon)
Downloading https://www.piwheels.org/simple/attrs/attrs-24.3.0-py3-none-any.whl (63 kB)
Collecting frozenlist>=1.1.1 (from aiohttp->jeedomdaemon)
Using cached frozenlist-1.5.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (13 kB)
Collecting multidict<7.0,>=4.5 (from aiohttp->jeedomdaemon)
Using cached multidict-6.1.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (5.0 kB)
Collecting propcache>=0.2.0 (from aiohttp->jeedomdaemon)
Using cached propcache-0.2.1-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (9.2 kB)
Collecting yarl<2.0,>=1.17.0 (from aiohttp->jeedomdaemon)
Using cached yarl-1.18.3-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl.metadata (69 kB)
Collecting idna>=2.0 (from yarl<2.0,>=1.17.0->aiohttp->jeedomdaemon)
Using cached https://www.piwheels.org/simple/idna/idna-3.10-py3-none-any.whl (70 kB)
Downloading aiohttp-3.11.11-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (1.7 MB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.7/1.7 MB 6.2 MB/s eta 0:00:00
Using cached frozenlist-1.5.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (276 kB)
Using cached multidict-6.1.0-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (131 kB)
Using cached propcache-0.2.1-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (232 kB)
Using cached yarl-1.18.3-cp311-cp311-manylinux_2_17_aarch64.manylinux2014_aarch64.whl (340 kB)
Installing collected packages: propcache, multidict, idna, frozenlist, attrs, aiohappyeyeballs, yarl, aiosignal, aiohttp, jeedomdaemon
Attempting uninstall: propcache
Found existing installation: propcache 0.2.1
Uninstalling propcache-0.2.1:
Successfully uninstalled propcache-0.2.1
Attempting uninstall: multidict
Found existing installation: multidict None
[notice] A new release of pip is available: 24.2 -> 24.3.1
[notice] To update, run: python3 -m pip install --upgrade pip
error: uninstall-no-record-file
× Cannot uninstall multidict None
╰─> The package's contents are unknown: no RECORD file was found for multidict.
hint: You might be able to recover from this via: pip install --force-reinstall --no-deps multidict==6.0.5
+ echo 20
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end rfxcom
+ echo 21
+ rm /tmp/jeedom_install_in_progress_rfxcom
+ echo '*******************End of package installation******************'
*******************End of package installation******************

rfxcomd:

Traceback (most recent call last):
File "/var/www/html/plugins/rfxcom/resources/rfxcomd/rfxcomd.py", line 23, in <module>
from jeedomdaemon.base_config import BaseConfig
ModuleNotFoundError: No module named 'jeedomdaemon.base_config'
Traceback (most recent call last):
File "/var/www/html/plugins/rfxcom/resources/rfxcomd/rfxcomd.py", line 23, in <module>
from jeedomdaemon.base_config import BaseConfig
ModuleNotFoundError: No module named 'jeedomdaemon.base_config'
Traceback (most recent call last):
File "/var/www/html/plugins/rfxcom/resources/rfxcomd/rfxcomd.py", line 23, in <module>
from jeedomdaemon.base_config import BaseConfig
ModuleNotFoundError: No module named 'jeedomdaemon.base_config'
Traceback (most recent call last):
File "/var/www/html/plugins/rfxcom/resources/rfxcomd/rfxcomd.py", line 23, in <module>
from jeedomdaemon.base_config import BaseConfig
ModuleNotFoundError: No module named 'jeedomdaemon.base_config'

J’avais déjà tenté de relancé l’installation des dépendances, mais sans succès. Le résultat est actuellement que le daemon ne démarre pas:

Vos suggestions sont les bienvenues

dada051 · Décembre 20, 2024, 12:36

Chez moi la page configuration complète ressemble à ça :

la vôtre n’est que partielle.
Quand vous dites migration debian 12, c’est une nouvelle installation de debian 12 avec une restauration de Jeedom ? un debian 11 que vous upgrader ? c’est à partir d’une image Jeedom ou d’une ISO debian ?

Pour info, mon RFXCom tourne sur une Debian 12 pure sur laquelle j’ai installé Jeedom.

Mips · Décembre 20, 2024, 12:47

c’est l’erreur qui empeche l’installation (ne pas executer la commande proposée):

magifix:

error: uninstall-no-record-file
× Cannot uninstall multidict None
╰─> The package's contents are unknown: no RECORD file was found for multidict.
hint: You might be able to recover from this via: pip install --force-reinstall --no-deps multidict==6.0.5

système corrompu donc effectivement la question suivante est intéressante:

si c’est bien une nouvelle installation de debian 12 alors essayez de supprimer le dossier plugins/rfxcom/resources/python_venv et tout ce qu’il contient et ensuite relancez les dépendances et patientez bien jusqu’à la fin de l’installation.

magifix · Décembre 20, 2024, 1:35

Alors c’est une nouvelle installation Debian et une restauration de jeedom. Je vais essayez votre proposition et vous tiens au courant

magifix · Décembre 20, 2024, 2:41

Très bonne nouvelle, après avoir effacé le répertoire plugins/rfxcom/resources/python_venv et relancé les dépendances, tout fonctionne à merveille.

Un tout grand merci pour votre aide efficace!

system · Décembre 21, 2024, 2:42

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.