Bonjour,
Je viens de mettre à jour. J’ai eu un phénomène curieux. La barre de progression s’est arrêtée à 53%, et plus rien n’a bougé. J’ai attendu plus de 1/2 h.
J’ai jeté un coup d’oeil dans les logs (update):
2025-11-26 16:43:00 (9.19 MB/s) - '/tmp/jeedom/install/jeedom_update.zip' saved [83995516/83995516]
[PROGRESS][25]
OK
Cleaning folders...OK
[PROGRESS][30]
Create temporary folder...OK
[PROGRESS][35]
Unzip in progress...
OK
[PROGRESS][40]
Clean temporary files (tmp)...
OK
Disable all task
.
OK
Disable all scenario.........
............. OK
[PROGRESS][45]
Update modification date of unzip file...
OK
[PROGRESS][47]
Moving files...
Ignore file /tmp/jeedom_unzip/core-master///docs/de_DE/noteVersion.md because size is 0
Ignore file /tmp/jeedom_unzip/core-master///docs/en_US/noteVersion.md because size is 0
Ignore file /tmp/jeedom_unzip/core-master///docs/es_ES/noteVersion.md because size is 0
Ignore file /tmp/jeedom_unzip/core-master///docs/fr_FR/noteVersion.md because size is 0
Ignore file /tmp/jeedom_unzip/core-master///docs/pt_PT/noteVersion.md because size is 0
OK
[PROGRESS][50]
Remove temporary files...OK
[PROGRESS][52]
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
OK
[PROGRESS][53]
Update composer file...
OK
[PROGRESS][58]
Update jeedom information date...
OK
[PROGRESS][59]
[PROGRESS][60]
Update system into : 4.5.0...Save state cache found, load it....OKOK
Check jeedom consistency...
[START CONSISTENCY]
[START CHECK AND FIX DB]
Fix : ALTER TABLE `cache` ADD `timestamp` int(11) NULL
Fix : ALTER TABLE `cache` DROP `datetime`
Fix : CREATE TABLE IF NOT EXISTS `queue` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`queueId` varchar(255) NULL,
`class` varchar(255) NULL,
`function` varchar(255) NOT NULL,
`arguments` text NULL,
`createTime` datetime NOT NULL,
`options` text NULL,
`timeout` int(11) NULL,
primary key(`id`))
ENGINE InnoDB;
[END CHECK AND FIX DB]
Check jeedom package...OK
Check jeedom database...OK
Check crons...
Create queue::cron
Create network::cron10
Check filesystem right...OK
Check jeedom object...OK
Check jeedom cmd...OK
Set cache hour...OK
Check composer...OK
Check nodejs...npm warn using --force Recommended protections disabled.
Hit:1 http://deb.debian.org/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease
Get:3 http://archive.raspberrypi.com/debian bookworm InRelease [54.9 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 arm64 Packages [560 kB]
Get:7 http://archive.raspberrypi.com/debian bookworm/main armhf Packages [560 kB]
Fetched 1230 kB in 4s (329 kB/s)
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.5-0+deb12u2).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v20.19.6 : [ OK ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [ OK ]
Clean npm cache
OK
Check apache security file...
Apache is configure in security mode and need update I will update file....warning: commands will be executed using /bin/sh
job 136 at Wed Nov 26 16:46:00 2025
Module headers already enabled
OK
[END CONSISTENCY]
OK
Check update...OK
***************Jeedom is up to date in 4.5***************
[PROGRESS][75]
***************Update plugins***************
***************Update plugin successfully***************
[PROGRESS][90]
Check update
OK
[PROGRESS][95]
Enable scenario : OK
Enable task : OK
Check Network Conf : OK
[PROGRESS][100]
Launch cron dependancy plugins...OK
Send end of update event...OK
Update duration : 380s
[END UPDATE SUCCESS]
Et comme tout semblait correct, j’ai simplement fait un refresh, et là tout semble ok:
Je suppose que c’est juste un problème cosmétique quelque part?