MAJ qui ne fonctionne pas, reste bloque a 60% pour 4.4.3

Bonjour, j’ai mis a jour mon linux avec update et upgrade.
rebooté puis lancé la MAJ jeedom mais ca reste bloque a 60% je ne sais pas ce qu’il coince.
voila ce que j’ai

[START UPDATE]
****Update from 4.3.23 (2024-04-14 20:26:47)****
Parameters : {"preUpdate":"0","backup::before":"1","plugins":"1","core":"1","force":"0","update::reapply":""}
Send begin of update event | OK
Check update | OK
Check rights | OK
[START BACKUP]
***************Start of Jeedom backup at 2024-04-14 20:26:50***************
Send begin backup event | OK
Checking files rights | OK
Checking  database | OK
Backing up database | OK
Cache persistence: | OK
Creating archive | OK
Cleaning old backup | OK
Limiting backup size to 2000 Mb
Delete: /var/www/html/core/php///backup/backup-kris1208-4.3.23-2024-04-09-01h31.tar.gz | OK
Backup name: /var/www/html/core/php///backup/backup-kris1208-4.3.23-2024-04-14-20h26.tar.gz
Checking files rights | OK
Send end backup event | OK
Backup operation duration: 81s
***************Jeedom backup end***************
[END BACKUP SUCCESS]
Download url : https://github.com/jeedom/core/archive/V4-stable.zip
Download in progress--2024-04-14 20:28:11--  https://github.com/jeedom/core/archive/V4-stable.zip
Resolving github.com (github.com) 140.82.121.3
Connecting to github.com (github.com)|140.82.121.3|:443 connected.
HTTP request sent, awaiting response 302 Found
Location: https://codeload.github.com/jeedom/core/zip/refs/heads/V4-stable [following]
--2024-04-14 20:28:11--  https://codeload.github.com/jeedom/core/zip/refs/heads/V4-stable
Resolving codeload.github.com (codeload.github.com) 140.82.121.9
Connecting to codeload.github.com (codeload.github.com)|140.82.121.9|:443 connected.
HTTP request sent, awaiting response 200 | OK
Length: 87540322 (83M) [application/zip]
Saving to: '/tmp/jeedom/install/jeedom_update.zip'
0K
3% 19.4M 4s
3072K        7% 12.8M 5s
6144K       10% 36.7M 4s
9216K       14% 48.3M 3s
12288K       17% 37.7M 3s
15360K       21% 27.1M 3s
18432K       25% 20.8M 3s
21504K       28% 31.6M 2s
24576K       32% 20.5M 2s
27648K
35% 29.2M 2s
30720K       39% 21.4M 2s
33792K       43% 29.0M 2s
36864K       46% 28.0M 2s
39936K       50% 22.7M 2s
43008K       53% 29.8M 2s
46080K       57% 31.9M 1s
49152K       61% 21.6M 1s
52224K       64% 31.5M 1s
55296K
68% 25.6M 1s
58368K       71% 26.2M 1s
61440K       75% 29.8M 1s
64512K       79% 31.8M 1s
67584K       82% 30.6M 1s
70656K       86% 22.7M 0s
73728K       89% 27.5M 0s
76800K       93% 31.9M 0s
79872K       97% 31.1M 0s
82944K               100% 30.2M=3.2s
2024-04-14 20:28:15 (26.4 MB/s) - '/tmp/jeedom/install/jeedom_update.zip' saved [87540322/87540322] | OK
Cleaning folders | OK
Create temporary folder | OK
Unzip in progress | OK
Clean temporary files (tmp) | OK
Disable all task
 | OK
Disable all scenario | OK
Moving files
Ignore file /tmp/jeedom_unzip/core-4-stable///docs/de_DE/noteVersion.md because size is 0
Ignore file /tmp/jeedom_unzip/core-4-stable///docs/en_US/noteVersion.md because size is 0
Ignore file /tmp/jeedom_unzip/core-4-stable///docs/es_ES/noteVersion.md because size is 0
Ignore file /tmp/jeedom_unzip/core-4-stable///docs/fr_FR/noteVersion.md because size is 0
Ignore file /tmp/jeedom_unzip/core-4-stable///docs/pt_PT/noteVersion.md because size is 0 | OK
Remove temporary files | OK
Remove useless files
Cleaning 3rdparty
Cleaning desktop
Cleaning mobile
Cleaning core
Cleaning docs
Cleaning install
Cleaning script | OK
Update jeedom information date | OK
Update system into : 4.4.1 | OK
Update system into : 4.4.2 | OK
Check jeedom consistency
[START CONSISTENCY]
[START CHECK AND FIX DB]
Fix : ALTER TABLE `cmd` DROP INDEX `unique`;
Fix : ALTER TABLE `cmd` DROP INDEX `isHistorized`;
Fix : ALTER TABLE `cmd` DROP INDEX `type`;
Fix : ALTER TABLE `cmd` DROP INDEX `name`;
Fix : ALTER TABLE `cmd` DROP INDEX `subtype`;
Fix : ALTER TABLE `cmd` DROP INDEX `eqLogic_id`;
Fix : ALTER TABLE `cmd` DROP INDEX `value`;
Fix : ALTER TABLE `cmd` DROP INDEX `order`;
Fix : ALTER TABLE `cmd` DROP INDEX `logicalID`;
Fix : ALTER TABLE `cmd` MODIFY COLUMN `logicalId`  varchar(1023) NULL
Fix :
CREATE UNIQUE INDEX `unique` ON `cmd` (`eqLogic_id` ASC,`name` ASC)
Fix :
CREATE INDEX `isHistorized` ON `cmd` (`isHistorized` ASC)
Fix :
CREATE INDEX `type` ON `cmd` (`type` ASC)
Fix :
CREATE INDEX `name` ON `cmd` (`name` ASC)
Fix :
CREATE INDEX `subtype` ON `cmd` (`subType` ASC)
Fix :
CREATE INDEX `eqLogic_id` ON `cmd` (`eqLogic_id` ASC)
Fix :
CREATE INDEX `value` ON `cmd` (`value` ASC)
Fix :
CREATE INDEX `order` ON `cmd` (`order` ASC)
Fix :
CREATE INDEX `logicalID` ON `cmd` (`logicalId` ASC)[END CHECK AND FIX DB]
Check jeedom package | OK
Check jeedom database | OK
Check crons
Check filesystem right | OK
Flush cache widget

Merci de votre aide.

Je pense que c’est un plugin mais je ne sais pas qui ! comment trouver ? Merci.

Bonjour,

Il y a pas mal de sujets sur ce type de problème.

Le principe est de passer en mode rescue ..../index.php?rescue=1, désactiver les plugins relancer l’installation, réactiver les plugins.

1 « J'aime »