J'ai cassé mon jeedom suite à une MAJ PHP8 (mais rien de grave !)

Bonjour,

J’ai une activité régulière de mise à jour de mon installation jeedom, penser à remettre à jour l’OS et compagnie afin de corriger les éventuelles petites failles et tout. Et l’autre jour j’ai malheureusement manqué de vigilance, un paquet hold (php8) a été sélectionné dans la mise à jour Debian 10 et boum, plus de php fonctionnel.

J’ai tout reconfiguré laborieusement à la main, je suis revenu sur une situation saine en PHP 7.4, donc sous Debian 10, Jeedom 4.1.22.
Tout refonctionne, mais ma section « Vérifications des packages » n’est pas propre, et je pense qu’elle l’était.


php-gd : il est installé mais je ne sais pas pourquoi, jeedom ne le voit pas:

sudo apt install -o Dpkg::Options::="--force-confdef" -y php7.4-gd
[sudo] password for guihome:
Reading package lists... Done
Building dependency tree
Reading state information... Done
php7.4-gd is already the newest version (7.4.20-1+0~20210604.45+debian10~1.gbpfeee62).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

plugins/gsh/resources/gshd: j’ai une erreur npm que pour l’instant je ne sais pas corriger

********************************************************
*             Installation des dépendances             *
********************************************************
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_14.x buster InRelease
Hit:4 https://packages.sury.org/php buster InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
git is already the newest version (1:2.20.1-2+deb10u3).
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[Check Version NodeJS actuelle : v14.17.1 : [  OK  ]
┌──────────────────────────────────────────────────────┐
│               npm update check failed                │
│         Try running with sudo or get access          │
│         to the local update config store via         │
│ sudo chown -R $USER:$(id -gn $USER) /var/www/.config │
└──────────────────────────────────────────────────────┘
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
npm : Depends: nodejs (>= 6.11~) but it is not going to be installed
Depends: node-abbrev (>= 1.1.1~) but it is not going to be installed
Depends: node-ansi-regex (>= 3.0~) but it is not going to be installed
Depends: node-ansistyles (>= 0.1.3~) but it is not going to be installed
Depends: node-aproba (>= 1.2~) but it is not going to be installed
Depends: node-archy (>= 1.0~) but it is not going to be installed
Depends: node-cacache (>= 10.0.4~) but it is not going to be installed
Depends: node-bluebird (>= 3.5.1~) but it is not going to be installed
Depends: node-call-limit (>= 1.1~) but it is not going to be installed
Depends: node-chownr (>= 1.0.1~) but it is not going to be installed
Depends: node-config-chain (>= 1.1.11~) but it is not going to be installed
Depends: node-detect-indent (>= 5.0~) but it is not going to be installed
Depends: node-detect-newline (>= 2.1~) but it is not going to be installed
Depends: node-editor (>= 1.0~) but it is not going to be installed
Depends: node-fs-vacuum (>= 1.2.10~) but it is not going to be installed
Depends: node-fs-write-stream-atomic (>= 1.0.10~) but it is not going to be installed
Depends: node-glob (>= 7.1.2~) but it is not going to be installed
Depends: node-graceful-fs (>= 4.1.11~) but it is not going to be installed
Depends: node-has-unicode (>= 2.0.1~) but it is not going to be installed
Depends: node-hosted-git-info (>= 2.6~) but it is not going to be installed
Depends: node-iferr (>= 0.1.5~) but it is not going to be installed
Depends: node-inflight (>= 1.0.6~) but it is not going to be installed
Depends: node-inherits (>= 2.0.3~) but it is not going to be installed
Depends: node-ini (>= 1.3.5~) but it is not going to be installed
Depends: node-npm-package-arg but it is not going to be installed
Depends: node-promzard but it is not going to be installed
Depends: node-jsonstream (>= 1.3.2~) but it is not going to be installed
Depends: node-json-parse-better-errors (>= 1.0.1~) but it is not going to be installed
Depends: node-lazy-property (>= 1.0~) but it is not going to be installed
Depends: node-libnpx (>= 10.0.1~) but it is not going to be installed
Depends: node-lockfile (>= 1.0.3~) but it is not going to be installed
Depends: node-lru-cache (>= 4.1.1~) but it is not going to be installed
Depends: node-mississippi (>= 3.0~) but it is not going to be installed
Depends: node-mkdirp (>= 0.3.3) but it is not going to be installed
Depends: node-move-concurrently (>= 1.0.1~) but it is not going to be installed
Depends: node-nopt but it is not going to be installed
Depends: node-normalize-package-data (>= 2.4~) but it is not going to be installed
Depends: node-gyp (>= 3.6.2~) but it is not going to be installed
Depends: node-resolve-from (>= 4.0~) but it is not going to be installed
Depends: node-encoding but it is not going to be installed
Depends: node-errno but it is not going to be installed
Depends: node-npmlog (>= 4.1.2~) but it is not going to be installed
Depends: node-once (>= 1.4~) but it is not going to be installed
Depends: node-opener (>= 1.4.3~) but it is not going to be installed
Depends: node-osenv (>= 0.1.5~) but it is not going to be installed
Depends: node-path-is-inside (>= 1.0.2~) but it is not going to be installed
Depends: node-promise-inflight (>= 1.0.1~) but it is not going to be installed
Depends: node-ansi but it is not going to be installed
Depends: node-qw (>= 1.0.1~) but it is not going to be installed
Depends: node-read (>= 1.0.7~) but it is not going to be installed
Depends: node-read-package-json (>= 2.0.13~) but it is not going to be installed
Depends: node-request (>= 2.83~) but it is not going to be installed
Depends: node-retry (>= 0.10.1~) but it is not going to be installed
Depends: node-rimraf (>= 2.6.2~) but it is not going to be installed
Depends: node-safe-buffer (>= 5.1.1~) but it is not going to be installed
Depends: node-semver (>= 5.5~) but it is not going to be installed
Depends: node-sha (>= 2.0.1~) but it is not going to be installed
Depends: node-slide (>= 1.1.6~) but it is not going to be installed
Depends: node-sorted-object (>= 2.0.1~) but it is not going to be installed
Depends: node-from2 but it is not going to be installed
Depends: node-stream-iterate but it is not going to be installed
Depends: node-ssri (>= 5.2.4~) but it is not going to be installed
Depends: node-strip-ansi (>= 4.0~) but it is not going to be installed
Depends: node-tar (>= 4.4~) but it is not going to be installed
Depends: node-text-table (>= 0.2~) but it is not going to be installed
Depends: node-uid-number (>= 0.0.6~) but it is not going to be installed
Depends: node-unique-filename (>= 1.1~) but it is not going to be installed
Depends: node-unpipe (>= 1.0~) but it is not going to be installed
Depends: node-boxen (>= 1.2.1~) but it is not going to be installed
Depends: node-import-lazy but it is not going to be installed
Depends: node-is-npm (>= 1.0~) but it is not going to be installed
Depends: node-latest-version (>= 3.0~) but it is not going to be installed
Depends: node-semver-diff (>= 2.0~) but it is not going to be installed
Depends: node-xdg-basedir (>= 3.0~) but it is not going to be installed
Depends: node-validate-npm-package-name (>= 3.0~) but it is not going to be installed
Depends: node-which (>= 1.3~) but it is not going to be installed
Depends: node-wrappy (>= 1.0.2~) but it is not going to be installed
Depends: node-write-file-atomic (>= 2.3~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
audited 65 packages in 6.636s
found 2 vulnerabilities (1 low, 1 high)
run `npm audit fix` to fix them, or `npm audit` for details
********************************************************
*             Installation terminée                    *
********************************************************

Si je lance npm audit fix à la main dans le répertoire, je n’ai pas le soucis:

/var/www/html/plugins/gsh/resources/gshd $ sudo npm audit fix
[sudo] password for guihome:
updated 2 packages in 7.866s
fixed 2 of 2 vulnerabilities in 65 scanned packages

et restart apache, là, aucune idée, ça fait plusieurs fois que je fais corriger, que je redémarre apache à la main, mais ça reste en erreur. Peut etre lié à php-gd vu que les deux sont liés au plugin caméra

Si ça se trouve j’étais déjà avec des problèmes depuis un moment, je sais juste qu’à mon upgrade en Debian 10 + Jeedom 4.1 tout était au vert, j’avais utilisé ce panneau pour m’assurer que tout allait bien.

Si vous avez des idées de comment diagnostiquer la situation courante pour savoir si j’ai vraiment des soucis, ou si c’est l’outil de Jeedom qui n’arrive pas à analyser la situation, je suis preneur ! Merci !

Salut,
Il ne faut pas tenir compte de cette page encore, pas avant la 4.2 (et à confirmer à la sortie)
Tant que les dépendances des plugins sont OK et que les démons tournent c’est bon.

4 « J'aime »

Ah ok. C’est étrange, je suis persuadé qu’elle marchait il y a encore quelques temps parce que c’est elle qui m’a remonté les gros problèmes que j’ai eu lors de la migration.

Mais si tu penses que c’est bon ainsi, moi de mon côté je ne vois pas (plus !) d’erreur donc c’est bon pour moi ! :grin:

La question a déjà été posée quelques fois et je n’ai plus le post sous la main mais il y a même la confirmation de Loic sur l’en deux qu’il ne faut pas s’en tracasser pour l’instant.

1 « J'aime »

Hello
Pour le restart-Apache, j’avais posé la question il y quelques mois, et effectivement, il m’avait été répondu que c’était en prévision pour une future version.

1 « J'aime »

Je confirme tout ça. C’est une réponse que j’ai eu au supports ça sera géré en 4.2

1 « J'aime »

Merci pour vos confirmations :grin: (qui sont au passage rassurantes, ça m’évite d’avoir à creuser le sujet pour rien !)

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.