Update 4.3.21 bloqué à 55%

Bonjour,

La mise à jour est bloqué à 55%. J’ai vu que c’est arrivé chez certains par la passé. Pourriez-vous m’indiqué le best pracrice pour résoudre le problème.

Dans mon cas la fenêtre reste active mais impossible de connecter sur une autre onglet ou sur mon mobile.

Merci d’avance,

Scott

[START UPDATE]
****Update from 4.3.21 (2024-01-15 11:22:20)****
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-01-15 11:22:27***************
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 500 Mb
Delete: /var/www/html/core/php///backup/backup-JeeBerry-4.3.21-2024-01-13-06h50.tar.gz | OK
Backup name: /var/www/html/core/php///backup/backup-JeeBerry-4.3.21-2024-01-15-11h22.tar.gz
Checking files rights | OK
Send end backup event | OK
Backup operation duration: 42s
***************Jeedom backup end***************
[END BACKUP SUCCESS]
Download url : https://github.com/jeedom/core/archive/V4-stable.zip
Download in progress--2024-01-15 11:23:09--  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-01-15 11:23:09--  https://codeload.github.com/jeedom/core/zip/refs/heads/V4-stable
Resolving codeload.github.com (codeload.github.com) 140.82.121.10
Connecting to codeload.github.com (codeload.github.com)|140.82.121.10|:443 connected.
HTTP request sent, awaiting response 200 | OK
Length: 82253386 (78M) [application/zip]
Saving to: '/tmp/jeedom/install/jeedom_update.zip'
0K        3% 21.3M 4s
3072K        7% 33.9M 3s
6144K       11% 29.2M 3s
9216K       15% 23.1M 3s
12288K       19% 24.0M 2s
15360K
22% 24.8M 2s
18432K       26% 25.5M 2s
21504K       30% 25.6M 2s
24576K       34% 26.6M 2s
27648K       38% 27.5M 2s
30720K       42% 27.9M 2s
33792K       45% 27.8M 2s
36864K       49% 28.5M 2s
39936K       53% 29.2M 1s
43008K       57% 29.9M 1s
46080K
61% 30.7M 1s
49152K       65% 26.7M 1s
52224K       68% 22.5M 1s
55296K       72% 21.8M 1s
58368K       76% 16.5M 1s
61440K       80% 17.5M 1s
64512K       84% 18.6M 1s
67584K
87% 19.1M 0s
70656K       91% 20.3M 0s
73728K       95% 20.8M 0s
76800K       99% 22.0M 0s
79872K                                               100% 21.2M=3.3s
2024-01-15 11:23:13 (23.8 MB/s) - '/tmp/jeedom/install/jeedom_update.zip' saved [82253386/82253386] | 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
find: '/var/www/html/install//script/*': No such file or directory
Cleaning vendor
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

Bonjour,
Comme toujours que dit la log… Je me demande quand meme si vous avez vraiment besoin d’aide quand vous faite meme pas l’effort de mettre la log.

re-bonjour,

j’ai mis le log dans mon poste. il semble avoir bloqué sur le check du filesystem.

merci encore,

scottt

Il faut attendre si ca passe pas, redemarrer la box si c’est toujours pas alors ya un soucis de filesystem

Hello,

Ça fait plus de trois heures qu’il est coincé à 55%. Je jette l’éponge ou j’attends encore ?

Scott

Dans ce cas redemarre la box et reteste.