Migration 4.3.23 to 4.4 KO & Restore KO

Bonjour,

J’ai fait une mise à jour de Jeedom 4.3.23 en début avril. Il n’a pas marché (erreurs PHP de mémoire). J’ai fait une restore qui lui aussi avait des erreurs mais les vacances scolaires arrivant et je me suis promis de régler le problème au retour.

J’ai fait une fresh install en profitant aussi de passer de debian buster à bullseye. Installation se passe bien mais le restore du back-up avant la migration se bloque également. Et impossible d’installer les noveaux mises à jours.

J’ai recommencer à partir de fresh install pour essayer de voir clair. J’ai fait le restore depuis le GUI et voici le résultat :

[START RESTORE]
***************Begin Jeedom restore 2024-05-01 23:53:56***************
Send begin restore event...OK
Checking rights...OK
Restore from file : /var/www/html/core/class/../../backup/backup-JeeBerry-4.3.23-2024-04-04-06h50.tar.gz
Backup database access configuration...OK
Disable all task
. OK
Disable all scenario OK
Unpacking backup...
OK
Deleting database...Disabling constraints...OK
Deleting table : cmd ...OK
Deleting table : config ...OK
Deleting table : cron ...OK
Deleting table : dataStore ...OK
Deleting table : eqLogic ...OK
Deleting table : history ...OK
Deleting table : historyArch ...OK
Deleting table : interactDef ...OK
Deleting table : interactQuery ...OK
Deleting table : listener ...OK
Deleting table : message ...OK
Deleting table : note ...OK
Deleting table : object ...OK
Deleting table : plan ...OK
Deleting table : plan3d ...OK
Deleting table : plan3dHeader ...OK
Deleting table : planHeader ...OK
Deleting table : scenario ...OK
Deleting table : scenarioElement ...OK
Deleting table : scenarioExpression ...OK
Deleting table : scenarioSubElement ...OK
Deleting table : timeline ...OK
Deleting table : update ...OK
Deleting table : user ...OK
Deleting table : view ...OK
Deleting table : viewData ...OK
Deleting table : viewZone ...OK
Deleting table : widgets ...OK
Restoring database from backup...OK
Enable back constraints...OK
Restoring cache...OK
Restoring Plugin : calendar...OK
sh: 1: /var/www/html/plugins/gardena/core/class/../../resources/venv/bin/python3: not found
Restoring Plugin : homebridge...PHP Fatal error:  Uncaught Error: Call to a member function setLog() on null in /var/www/html/plugins/homebridge/core/class/homebridge.class.php:402
Stack trace:
#0 /var/www/html/install/restore.php(208): homebridge::restore()
#1 {main}
thrown in /var/www/html/plugins/homebridge/core/class/homebridge.class.php on line 402

Je l’ai laissé tourner toute la nuit mais ça n’avance pas. S.O.S. et merci de votre aide,

Scott Needham

Bonjour,

Depuis un nouvel onglet d’un navigateur, vous n’avez pas la page d’accueil ?

On voit une erreur sur le plugin homebridge

Hello,

Effectivement, il marche si je l’ouvre dans une autre fenêtre. Pour certains modules et j’ai du lancer l’installation des dépendances puis redémarrer le daemon.

Par contre rien ne marche avec le plugin jwavejs. il donne une erreur, par exemple :

Erreur exécution de la commande [Living][Radiator Living 4 (29)][Mode-Chaud] : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=FU8dhi7uSmJApKrhG6TkfXaIPHQX3ZiPl3T8EP7qYm2t9OF4Be7Wg39cU47aSh1C cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused

Je ne sais pas quoi faire, désinstaller homebridre, essayer de le mettre à jour ?

Thanks so much,

Scott

bonjour a tous impossible pour moi d’effectuer une restore avec un jeedom fonctionnelle en 4.3.23 sur un jeedom en version 4.4 sur un deuxième Raspberry la restauration plante je ne veux donc pas effectuer de mise a jour car 1 essai déjà effectuer et jeedom planter mort grâce au ligne si dessous tout récupérer

  1. sudo php /var/www/html/install/restore.php
  2. sudo chown -R www-data:www-data /var/www/html

avait vous la solution car je sèche
(debutant en linux)

merci a vous :smiley:

Bonjour
Sans la log on a plus de chance de gagner au loto que de réussir à t’aider

Merci pour la réponse si possible me guide je te récupère le log à quelle endroit car la :no_mouth:

Ben quand tu lances en lignes de commandes c’est ce qui défile à l’écran tout simplement

Ok ça roule je refais ça et le publie merci

Est-ce que le plugin MQTT Manager fonctionne bien de son côté ? Il est sensé marcher de pair.

Essaye à tout hasard une réparation des droits des fichiers et dossiers, dans l’onglet Configuration de Jeedom…

bon voila je démarre avec jeedom vierge


je lance une restaure avec un backup de mon jeedom fonctionnel et donc voila le log de restaure

[START RESTORE]
***************Begin Jeedom restore 2024-05-02 21:08:45***************
Send begin restore event...OK
Checking rights...
OK
Restore from file : /var/www/html/core/class/../../backup/backup-raspberrycoin-4.3.23-2024-05-02-13h29.tar.gz
Backup database access configuration...OK
Disable all taskkill: (43316): No such process
kill: (43316): No such process
kill: (43316): No such process
kill: (43316): No such process
kill: (43316): No such process
kill: (43316): No such process
kill: (43316): No such process
kill: (43316): No such process
kill: (43316): No such process
kill: (43316): No such process
kill: (43316): No such process
kill: (43316): No such process
kill: (43316): No such process
. OK
Disable all scenario OK
Unpacking backup...
OK
Update composer file...
OK
[PROGRESS][58]
Deleting database...Disabling constraints...OK
Deleting table : cmd ...OK
Deleting table : config ...OK
Deleting table : cron ...OK
Deleting table : dataStore ...OK
Deleting table : eqLogic ...OK
Deleting table : history ...OK
Deleting table : historyArch ...OK
Deleting table : interactDef ...OK
Deleting table : interactQuery ...OK
Deleting table : listener ...OK
Deleting table : message ...OK
Deleting table : note ...OK
Deleting table : object ...OK
Deleting table : plan ...OK
Deleting table : plan3d ...OK
Deleting table : plan3dHeader ...OK
Deleting table : planHeader ...OK
Deleting table : scenario ...OK
Deleting table : scenarioElement ...OK
Deleting table : scenarioExpression ...OK
Deleting table : scenarioSubElement ...OK
Deleting table : timeline ...OK
Deleting table : update ...OK
Deleting table : user ...OK
Deleting table : view ...OK
Deleting table : viewData ...OK
Deleting table : viewZone ...OK
Deleting table : widgets ...OK
Restoring database from backup...OK
Enable back constraints...OK
Restoring cache...OK
Restoring Plugin : calendar...OK
sudo: yarn: command not found
Restoring Plugin : homebridge...OK
/var/www/html/plugins/noip/core/class/../../resources/install_check.sh: line 17: /tmp/jeedom/noip/dependancy_noip: No such file or directory
Check jeedom consistency...[START CONSISTENCY]
[START CHECK AND FIX DB]
[END CHECK AND FIX DB]
Check jeedom package...OK
Check jeedom database...OK
Check crons...
Check filesystem right...
OK
Flush cache widget...
Check jeedom object...OK
Check jeedom cmd...
OK
Set cache hour...OK
Check nodejs...
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
Hit:3 http://deb.debian.org/debian bookworm-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
Hit:5 http://archive.raspberrypi.com/debian bookworm InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
lsb-release is already the newest version (12.0-1).
build-essential is already the newest version (12.9).
apt-utils is already the newest version (2.6.1).
git is already the newest version (1:2.39.2-1.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v18.20.2 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
OK
[END CONSISTENCY]
OK
Enable scenario : OK
Enable task : OK
Check Network Conf : OK
Sending end restore event...OK
Restore duration : 170s
***************Jeedom Restore End***************
[END RESTORE SUCCESS]

voila ce qu’il a après la restaure rien Apart le fond écran

Utilise le formatage pour coller ton code pour faciliter la lecture, cf. bouton [</>] dans l’éditeur de texte,

Exemple de résultat:

[START RESTORE]
Begin Jeedom restore 2024-05-02 21:08:45
Send begin restore event…OK
Checking rights…

Edite ton post précédent stp :wink:

ci je souhaite me reconnecter au compte voila ce qu’il me sort

Ok y’a pas de soucis sur la restoration la ca marche mais y’a un soucis ensuite sur ton jeedom. Sûrement un plugin qui gêne. Regarde le log http.error

c ca que tu souhaite voir

Created directory: /var/lib/snmp/cert_indexes
[Thu May 02 20:56:32.593922 2024] [mpm_prefork:notice] [pid 41355] AH00163: Apache/2.4.59 (Debian) configured -- resuming normal operations
[Thu May 02 20:56:32.594084 2024] [core:notice] [pid 41355] AH00094: Command line: '/usr/sbin/apache2'
[Thu May 02 21:00:51.681751 2024] [mpm_prefork:notice] [pid 41355] AH00170: caught SIGWINCH, shutting down gracefully
[Thu May 02 21:01:00.111946 2024] [mpm_prefork:notice] [pid 912] AH00163: Apache/2.4.59 (Debian) configured -- resuming normal operations
[Thu May 02 21:01:00.142072 2024] [core:notice] [pid 912] AH00094: Command line: '/usr/sbin/apache2'
[Thu May 02 21:14:09.187089 2024] [php:error] [pid 2204] [client 192.168.1.102:16644] PHP Fatal error:  Trait "Psr\\Log\\LoggerAwareTrait" not found in /var/www/html/vendor/symfony/cache/Traits/ArrayTrait.php on line 22
[Thu May 02 21:14:09.396131 2024] [php:error] [pid 938] [client 192.168.1.102:16710] PHP Fatal error:  Trait "Psr\\Log\\LoggerAwareTrait" not found in /var/www/html/vendor/symfony/cache/Traits/ArrayTrait.php on line 22
[Thu May 02 21:14:09.647015 2024] [php:error] [pid 939] [client 192.168.1.102:16711] PHP Fatal error:  Trait "Psr\\Log\\LoggerAwareTrait" not found in /var/www/html/vendor/symfony/cache/Traits/ArrayTrait.php on line 22
[Thu May 02 21:14:09.818183 2024] [php:error] [pid 940] [client 192.168.1.102:16712] PHP Fatal error:  Trait "Psr\\Log\\LoggerAwareTrait" not found in /var/www/html/vendor/symfony/cache/Traits/ArrayTrait.php on line 22
[Thu May 02 21:14:17.343058 2024] [php:warn] [pid 936] [client 192.168.1.102:16718] PHP Warning:  Undefined variable $mbState in /var/www/html/desktop/php/index.php on line 499, referer: http://192.168.1.99/index.php?v=d
[Thu May 02 21:14:17.348456 2024] [php:error] [pid 936] [client 192.168.1.102:16718] PHP Fatal error:  Trait "Psr\\Log\\LoggerAwareTrait" not found in /var/www/html/vendor/symfony/cache/Traits/ArrayTrait.php on line 22, referer: http://192.168.1.99/index.php?v=d
[Thu May 02 21:15:56.296355 2024] [php:warn] [pid 940] [client 192.168.1.102:16767] PHP Warning:  Undefined variable $mbState in /var/www/html/desktop/php/index.php on line 499, referer: http://192.168.1.99/index.php?v=d
[Thu May 02 21:15:56.301265 2024] [php:error] [pid 940] [client 192.168.1.102:16767] PHP Fatal error:  Trait "Psr\\Log\\LoggerAwareTrait" not found in /var/www/html/vendor/symfony/cache/Traits/ArrayTrait.php on line 22, referer: http://192.168.1.99/index.php?v=d
[Thu May 02 21:18:22.307341 2024] [mpm_prefork:notice] [pid 912] AH00170: caught SIGWINCH, shutting down gracefully
[Thu May 02 21:18:32.410871 2024] [mpm_prefork:notice] [pid 914] AH00163: Apache/2.4.59 (Debian) configured -- resuming normal operations
[Thu May 02 21:18:32.411947 2024] [core:notice] [pid 914] AH00094: Command line: '/usr/sbin/apache2'
[Thu May 02 21:19:04.442135 2024] [php:warn] [pid 943] [client 192.168.1.102:16830] PHP Warning:  Undefined variable $mbState in /var/www/html/desktop/php/index.php on line 499, referer: http://192.168.1.99/index.php?v=d
[Thu May 02 21:19:04.465798 2024] [php:error] [pid 943] [client 192.168.1.102:16830] PHP Fatal error:  Trait "Psr\\Log\\LoggerAwareTrait" not found in /var/www/html/vendor/symfony/cache/Traits/ArrayTrait.php on line 22, referer: http://192.168.1.99/index.php?v=d
[Thu May 02 21:19:38.453615 2024] [php:warn] [pid 946] [client 192.168.1.102:16854] PHP Warning:  Undefined variable $mbState in /var/www/html/desktop/php/index.php on line 499
[Thu May 02 21:19:38.458717 2024] [php:error] [pid 946] [client 192.168.1.102:16854] PHP Fatal error:  Trait "Psr\\Log\\LoggerAwareTrait" not found in /var/www/html/vendor/symfony/cache/Traits/ArrayTrait.php on line 22
[Thu May 02 21:20:05.779765 2024] [php:error] [pid 943] [client 192.168.1.102:16867] PHP Fatal error:  Uncaught Error: Interface "Psr\\Log\\LoggerInterface" not found in /var/www/html/vendor/monolog/monolog/src/Monolog/Logger.php:28\nStack trace:\n#0 /var/www/html/vendor/composer/ClassLoader.php(576): include()\n#1 /var/www/html/vendor/composer/ClassLoader.php(427): Composer\\Autoload\\{closure}()\n#2 /var/www/html/core/class/log.class.php(55): Composer\\Autoload\\ClassLoader->loadClass()\n#3 /var/www/html/core/class/log.class.php(110): log::getLogger()\n#4 /var/www/html/core/class/user.class.php(149): log::add()\n#5 /var/www/html/core/ajax/user.ajax.php(50): user::connect()\n#6 {main}\n  thrown in /var/www/html/vendor/monolog/monolog/src/Monolog/Logger.php on line 28, referer: http://192.168.1.99/index.php?v=d
[Thu May 02 21:31:01.227388 2024] [php:error] [pid 941] [client 192.168.1.102:17144] PHP Fatal error:  Uncaught Error: Interface "Psr\\Log\\LoggerInterface" not found in /var/www/html/vendor/monolog/monolog/src/Monolog/Logger.php:28\nStack trace:\n#0 /var/www/html/vendor/composer/ClassLoader.php(576): include()\n#1 /var/www/html/vendor/composer/ClassLoader.php(427): Composer\\Autoload\\{closure}()\n#2 /var/www/html/core/class/log.class.php(55): Composer\\Autoload\\ClassLoader->loadClass()\n#3 /var/www/html/core/class/log.class.php(110): log::getLogger()\n#4 /var/www/html/core/class/user.class.php(149): log::add()\n#5 /var/www/html/core/ajax/user.ajax.php(50): user::connect()\n#6 {main}\n  thrown in /var/www/html/vendor/monolog/monolog/src/Monolog/Logger.php on line 28, referer: http://192.168.1.99/index.php?v=d&p=dashboard
[Thu May 02 21:31:18.666684 2024] [php:error] [pid 946] [client 192.168.1.102:17154] PHP Fatal error:  Uncaught Error: Interface "Psr\\Log\\LoggerInterface" not found in /var/www/html/vendor/monolog/monolog/src/Monolog/Logger.php:28\nStack trace:\n#0 /var/www/html/vendor/composer/ClassLoader.php(576): include()\n#1 /var/www/html/vendor/composer/ClassLoader.php(427): Composer\\Autoload\\{closure}()\n#2 /var/www/html/core/class/log.class.php(55): Composer\\Autoload\\ClassLoader->loadClass()\n#3 /var/www/html/core/class/log.class.php(110): log::getLogger()\n#4 /var/www/html/core/class/user.class.php(149): log::add()\n#5 /var/www/html/core/ajax/user.ajax.php(50): user::connect()\n#6 {main}\n  thrown in /var/www/html/vendor/monolog/monolog/src/Monolog/Logger.php on line 28, referer: http://192.168.1.99/index.php?v=d&p=dashboard
[Thu May 02 21:37:41.886328 2024] [php:error] [pid 1365] [client 192.168.1.102:17378] PHP Fatal error:  Uncaught Error: Interface "Psr\\Log\\LoggerInterface" not found in /var/www/html/vendor/monolog/monolog/src/Monolog/Logger.php:28\nStack trace:\n#0 /var/www/html/vendor/composer/ClassLoader.php(576): include()\n#1 /var/www/html/vendor/composer/ClassLoader.php(427): Composer\\Autoload\\{closure}()\n#2 /var/www/html/core/class/log.class.php(55): Composer\\Autoload\\ClassLoader->loadClass()\n#3 /var/www/html/core/class/log.class.php(110): log::getLogger()\n#4 /var/www/html/core/class/user.class.php(149): log::add()\n#5 /var/www/html/core/ajax/user.ajax.php(50): user::connect()\n#6 {main}\n  thrown in /var/www/html/vendor/monolog/monolog/src/Monolog/Logger.php on line 28, referer: http://192.168.1.99/index.php?v=d&p=dashboard

Tu aurais pas installé un nouvel os en debian 12 par hasard ?

1 « J'aime »

je peux controler en ligne de commande avec putty sur raspberry?
quelle ligne ?

tu a raison

Linux raspberrypi 6.6.28+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.28-1+rpt1 (2024-                                                                                        04-22) aarch64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Thu May  2 21:01:33 2024 from 192.168.1.102
pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Ben cherche pas plus loin jeedom 4.3 est pas compatible debian 12 donc pas possible ce que tu veux faire

ok je vais essayer de trouver debian 11 a lors et le réinstaller