Tâche #34475
Scénario #34369: Traitement express MEN (26-29)
Le service eole-sso devrait être arrêté/désinstallé proprement à la désinstallation du paquet eole-sso-server
Status:
Fermé
Priority:
Normal
Assigned To:
Target version:
Start date:
07/21/2022
Due date:
% Done:
100%
Remaining (hours):
0.0
Description
Si on installe eole-lemonldap-ng-auto, cela désinstalle bien eole-sso-server mais le service reste visible :
root@scribe:~# systemctl status eole-sso.service
× eole-sso.service
Loaded: not-found (Reason: Unit eole-sso.service not found.)
Active: failed (Result: exit-code) since Thu 2022-07-21 15:32:06 CEST; 21s ago
root@scribe:~# diagnose *** Test du module scribe version 2.9.0 (scribe 0000000A) *** Attention, serveur opérationnel mais des services ne sont pas démarrés : ● eole-sso.service not-found
Enfin, ça finit par s'arranger après un redémarrage du serveur ;)
Related issues
Associated revisions
Réinitialisation des services en erreur dans instance/reconfigure
Ref: #34475
History
#1 Updated by Daniel Dehennin 11 months ago
le postrm aurait dû suffire :
root@scribe:~# cat /var/lib/dpkg/info/eole-sso-server.postrm
#!/bin/sh
set -e
# Automatically added by dh_installsystemd/13.6ubuntu1
if [ "$1" = remove ] && [ -d /run/systemd/system ] ; then
systemctl --system daemon-reload >/dev/null || true
fi
# End automatically added section
# Automatically added by dh_installsystemd/13.6ubuntu1
if [ "$1" = "remove" ]; then
if [ -x "/usr/bin/deb-systemd-helper" ]; then
deb-systemd-helper mask 'eole-sso.service' >/dev/null || true
fi
fi
if [ "$1" = "purge" ]; then
if [ -x "/usr/bin/deb-systemd-helper" ]; then
deb-systemd-helper purge 'eole-sso.service' >/dev/null || true
deb-systemd-helper unmask 'eole-sso.service' >/dev/null || true
fi
fi
# End automatically added section
#2 Updated by Daniel Dehennin 11 months ago
Cela ne viendrait-il pas d’une erreur à l’arrêt du service ?
root@scribe:~# systemctl status eole-sso.service
× eole-sso.service
Loaded: not-found (Reason: Unit eole-sso.service not found.)
Active: failed (Result: exit-code) since Thu 2022-07-21 16:09:43 CEST; 54s ago
Main PID: 1783 (code=killed, signal=TERM)
CPU: 20.176s
juil. 21 10:42:09 scribe podman[1783]: 2022-07-21T08:42:09+0000 [-] index 1 assigned to attribute set multi_rne
juil. 21 16:09:32 scribe systemd[1]: Stopping Eole Single Sign On server...
juil. 21 16:09:43 scribe podman[40482]: 2022-07-21 16:09:43.238550077 +0200 CEST m=+0.240735827 container remove 9272a3179d57c9a7db646b5ca3f622ab57f360dff2ac5da11027944a30890c1d (image>
juil. 21 16:09:43 scribe podman[40424]: eolesso
juil. 21 16:09:43 scribe podman[1783]: time="2022-07-21T16:09:43+02:00" level=error msg="Error forwarding signal 15 to container 9272a3179d57c9a7db646b5ca3f622ab57f360dff2ac5da11027944>
juil. 21 16:09:43 scribe podman[40591]: Error: no container with name or ID "eolesso" found: no such container
juil. 21 16:09:43 scribe systemd[1]: eole-sso.service: Control process exited, code=exited, status=1/FAILURE
juil. 21 16:09:43 scribe systemd[1]: eole-sso.service: Failed with result 'exit-code'.
juil. 21 16:09:43 scribe systemd[1]: Stopped Eole Single Sign On server.
juil. 21 16:09:43 scribe systemd[1]: eole-sso.service: Consumed 20.176s CPU time.
Car cela est resolu avec un systemctl reset-failed
root@scribe:~# systemctl status eole-sso.service
× eole-sso.service
Loaded: not-found (Reason: Unit eole-sso.service not found.)
Active: failed (Result: exit-code) since Thu 2022-07-21 16:09:43 CEST; 54s ago
Main PID: 1783 (code=killed, signal=TERM)
CPU: 20.176s
juil. 21 10:42:09 scribe podman[1783]: 2022-07-21T08:42:09+0000 [-] index 1 assigned to attribute set multi_rne
juil. 21 16:09:32 scribe systemd[1]: Stopping Eole Single Sign On server...
juil. 21 16:09:43 scribe podman[40482]: 2022-07-21 16:09:43.238550077 +0200 CEST m=+0.240735827 container remove 9272a3179d57c9a7db646b5ca3f622ab57f360dff2ac5da11027944a30890c1d (image>
juil. 21 16:09:43 scribe podman[40424]: eolesso
juil. 21 16:09:43 scribe podman[1783]: time="2022-07-21T16:09:43+02:00" level=error msg="Error forwarding signal 15 to container 9272a3179d57c9a7db646b5ca3f622ab57f360dff2ac5da11027944>
juil. 21 16:09:43 scribe podman[40591]: Error: no container with name or ID "eolesso" found: no such container
juil. 21 16:09:43 scribe systemd[1]: eole-sso.service: Control process exited, code=exited, status=1/FAILURE
juil. 21 16:09:43 scribe systemd[1]: eole-sso.service: Failed with result 'exit-code'.
juil. 21 16:09:43 scribe systemd[1]: Stopped Eole Single Sign On server.
juil. 21 16:09:43 scribe systemd[1]: eole-sso.service: Consumed 20.176s CPU time.
root@scribe:~# systemctl reset-failed
root@scribe:~# systemctl status eole-sso.service
#3 Updated by Joël Cuissinat 11 months ago
- Parent task set to #34369
#4 Updated by Joël Cuissinat 10 months ago
Proposition : placer un systemctl reset-failed général avant le démarrage des services par reconfigure
#5 Updated by Joël Cuissinat 10 months ago
- Related to Tâche #31411: Après instance logrotate ne doit pas être en erreur added
#6 Updated by Joël Cuissinat 10 months ago
- Status changed from Nouveau to En cours
- Assigned To set to Joël Cuissinat
#7 Updated by Joël Cuissinat 10 months ago
- Status changed from En cours to Résolu
- % Done changed from 0 to 100
#8 Updated by Fabrice Barconnière 9 months ago
OK
git/eole-common (2.8.1/master=)$ git tag --contains b5439cc7 pkg/eole/eole-2.8/2.8.1-74 pkg/eole/eole-2.9/2.9.0-29
#9 Updated by Fabrice Barconnière 9 months ago
- Status changed from Résolu to Fermé
- Remaining (hours) set to 0.0