Bonjour en utilisant le système de Vérification de la base de données, j’ai l’erreur suivante que le bouton corriger n’arrive pas à corriger
Bonjour,
Tu peux ignorer c’est du a ta version de mysql je pense mais ca n’a aucune impact
Bonjour @Loic
J’ai regardé quand est arrivé cette erreur
C’est quand je suis passé de la version Jeedom 4.0.62 à 4.1.22
Quand j’ai restauré une sauvegarde qui était sous 4.0.62 je n’ai plus cette erreur.
Mais si je fais la maj du core en 4.1.22
[START UPDATE]
****Update from 4.0.62 (2021-05-22 16:24:42)****
Parameters : {"preUpdate":"0","backup::before":"1","plugins":"0","core":"1","force":"0","update::reapply":""}
Send begin of update event | OK
Check rights | OK
[START BACKUP]
***************Start of Jeedom backup at 2021-05-22 16:24:43***************
Envoi l'évènement de début de sauvegarde | OK
Vérification des droits sur les fichiers | OK
Vérification de la base de données | OK
Sauvegarde la base de données | OK
Persistance du cache : | OK
Création de l'archive | OK
Nettoyage de l'ancienne sauvegarde | OK
Limitation de la taille des sauvegardes à 700 Mo | OK
Nom de la sauvegarde : /var/www/html/core/php///backup/backup-Jeedom_v4-4.0.62-2021-05-22-16h24.tar.gz
Vérification des droits sur les fichiers | OK
Envoi l'évènement de fin de sauvegarde | OK
Durée de la sauvegarde : 35s
***************Fin de la sauvegarde de Jeedom***************
[END BACKUP SUCCESS]
Download url : https://github.com/jeedom/core/archive/V4-stable.zip
Download in progress--2021-05-22 14:25:19-- 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/V4-stable [following]
--2021-05-22 14:25:19-- https://codeload.github.com/jeedom/core/zip/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: 70809355 (68M) [application/zip]
Saving to: '/tmp/jeedom/install/jeedom_update.zip'
0K 4% 37.6M 2s
3072K 8% 33.7M 2s
6144K 13% 24.1M 2s
9216K 17% 26.1M 2s
12288K 22% 17.3M 2s
15360K 26% 45.8M 2s
18432K 31% 19.3M 2s
21504K
35% 36.1M 2s
24576K 39% 24.1M 2s
27648K 44% 26.3M 1s
30720K 48% 34.0M 1s
33792K 53% 24.2M 1s
36864K 57% 26.4M 1s
39936K 62% 24.4M 1s
43008K 66% 26.3M 1s
46080K 71% 34.1M 1s
49152K 75% 24.4M 1s
52224K
79% 26.4M 1s
55296K 84% 24.3M 0s
58368K 88% 26.8M 0s
61440K 93% 33.9M 0s
64512K 97% 24.6M 0s
67584K 100% 36.6M=2.5s
2021-05-22 14:25:22 (27.0 MB/s) - '/tmp/jeedom/install/jeedom_update.zip' saved [70809355/70809355] | 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
Update system into : 4.1.1 | OK
Update system into : 4.1.2 | OK
Update system into : 4.1.3Running in chroot, ignoring request: daemon-reload | OK
Update system into : 4.1.4 | OK
Update system into : 4.1.5 | OK
Update system into : 4.1.7 | OK
Update system into : 4.1.15 | OK
Check jeedom consistency
[START CONSISTENCY]
[START CHECK AND FIX DB]
Fix : ALTER TABLE `cmd` DROP INDEX `logicalId_eqLogicID`;
Fix : ALTER TABLE `cron` DROP INDEX `deamon`;
Fix : ALTER TABLE `cron` MODIFY COLUMN `option` text NULL
Fix : CREATE INDEX `function` ON `cron` (`function` ASC)
Fix :
CREATE INDEX `deamon` ON `cron` (`deamon` ASC)
Fix : ALTER TABLE `cron` DROP INDEX `type`;
Fix : ALTER TABLE `cron` DROP INDEX `logicalId_Type`;
Fix : ALTER TABLE `eqLogic` DROP `eqReal_id`
Fix : ALTER TABLE `eqLogic` DROP INDEX `logica_id_eqTypeName`;
Fix : ALTER TABLE `eqLogic` DROP INDEX `eqReal_id`;
Fix : ALTER TABLE `eqLogic` DROP INDEX `logicalId`;
Fix : ALTER TABLE `historyArch` DROP INDEX `cmd_id_index`;
Fix : ALTER TABLE `scenario` DROP INDEX `group`;
Fix : ALTER TABLE `viewData` DROP INDEX `fk_data_zone1_idx`;
Fix : ALTER TABLE `widgets` DROP INDEX `unique`;
Fix : ALTER TABLE `widgets` MODIFY COLUMN `name` varchar(191) NOT NULL
Fix :
CREATE UNIQUE INDEX `unique` ON `widgets` (`type` ASC,`subtype` ASC,`name` ASC)
Fix : CREATE TABLE IF NOT EXISTS `timeline` (
`id` int(11) NOT NULL AUTO_INCREMENT,
`folder` varchar(255) NULL,
`type` varchar(27) NULL,
`subtype` varchar(27) NULL,
`link_id` varchar(27) NULL,
`name` varchar(255) NULL,
`datetime` datetime NOT NULL,
`options` text NULL,
primary key(`id`,`datetime`))
ENGINE InnoDB;
CREATE INDEX `datetime` ON `timeline` (`datetime` ASC)[END CHECK AND FIX DB]
Check jeedom database
Fix : ALTER TABLE `eqLogic` DROP `eqReal_id`
Fix : ALTER TABLE `eqLogic` DROP INDEX `eqReal_id`; | OK
Suppression de : scenario::doIn() car il n'y a pas de lancement prévu
Suppression de : scenario::doIn() car il n'y a pas de lancement prévu
Suppression de : scenario::doIn() car il n'y a pas de lancement prévu
Suppression de : scenario::doIn() car il n'y a pas de lancement prévu
Suppression de : scenario::doIn() car il n'y a pas de lancement prévu
Suppression de : thermostat::pull() car il n'y a pas de lancement prévu
Check filesystem right | OK
[END CONSISTENCY] | OK
Check update | OK
***************Jeedom is up to date in 4.1.22***************
Check update | OK
Enable scenario : | OK
Enable task : | OK
Launch cron dependancy plugins | OK
Send end of update event | OK
Update duration : 60s
[END UPDATE SUCCESS]
voici ma version :
mysql Ver 15.1 Distrib 10.3.27-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2