Project

General

Profile

Tâche #31487

Scénario #30986: Implémenter l'Upgrade Auto 2.7.2 → 2.8.0

lsc n'est pas fonctionnel après Upgrade en 2.8.0

Added by Joël Cuissinat 9 months ago. Updated 8 months ago.

Status:
Fermé
Priority:
Normal
Assigned To:
Start date:
01/04/2021
Due date:
% Done:

100%

Remaining (hours):
0.0

Description

https://dev-eole.ac-dijon.fr/jenkins/job/2.8.0/job/test-upgradeauto-scribe-272-2.8.0-amd64/20/console

15:16:41             run-parts: executing /usr/share/eole/postservice/05-eolead-join-and-sync-ldap instance
15:16:41             Intégration au domaine Active Directory
15:16:41             Mot de passe de l'utilisateur Administrator pour le domaine DOMPEDAGO.ETB1.LAN :
15:16:41             MONITOR: scribead_001 action:$PASSWORD_SAMBA4
15:16:41             Eole12345!
15:16:41             Using short domain name -- DOMPEDAGO
15:16:41             Joined 'SCRIBE' to dns domain 'dompedago.etb1.lan'
15:16:41             Mise à jour du mot de passe dans les fichiers de configuration
15:16:41             Synchronisation ldap
15:16:41             janv. 04 15:16:38 - INFO  - Logging configuration successfully loaded from /etc/lsc/logback.xml
15:16:41             janv. 04 15:16:38 - INFO  - LSC configuration successfully loaded from /etc/lsc/
15:16:41             janv. 04 15:16:38 - INFO  - Connecting to LDAP server ldaps://addc.dompedago.etb1.lan:636/DC=dompedago,DC=etb1,DC=lan as CN=Administrator,CN=Users,DC=dompedago,DC=etb1,DC=lan
15:16:41             janv. 04 15:16:39 - ERROR - Error opening the LDAP connection to the destination! (javax.naming.CommunicationException: simple bind failed: addc.dompedago.etb1.lan:636 [Root exception is java.net.SocketException: Connection or outbound has closed])
15:16:41             janv. 04 15:16:39 - ERROR - org.lsc.exception.LscConfigurationException: Configuration exception: javax.naming.CommunicationException: simple bind failed: addc.dompedago.etb1.lan:636 [Root exception is java.net.SocketException: Connection or outbound has closed]

Problème de certificats ?

Idem que #31499 ?


Related issues

Related to Distribution EOLE - Tâche #31499: Le service LSC est en erreur après la restauration avec migration28.sh Fermé 01/06/2021

Associated revisions

Revision 67a8e72e (diff)
Added by Joël Cuissinat 8 months ago

logparser-eole.rules : détection erreur LSC dans diagnose

Ref: #31487
Ref: #31499

Revision 72439e36 (diff)
Added by Benjamin Bohard 8 months ago

Allow certificate replacement after upgrade.

Ref #31487

Revision 1389f3a0 (diff)
Added by Benjamin Bohard 8 months ago

New question during instance after Upgrade_Auto

Ref #31487

History

#1 Updated by Joël Cuissinat 8 months ago

  • Related to Tâche #31499: Le service LSC est en erreur après la restauration avec migration28.sh added

#2 Updated by Joël Cuissinat 8 months ago

  • Description updated (diff)

#3 Updated by Benjamin Bohard 8 months ago

Le certificat autosigné récupéré du serveur 2.7.2 ne contient pas le nom alternatif addc.domscribe.ac-test.fr et ne peut donc pas être utilisé sur le serveur 2.8.0.

#4 Updated by Benjamin Bohard 8 months ago

  • Status changed from Nouveau to En cours

#5 Updated by Emmanuel GARETTE 8 months ago

  • Status changed from En cours to Résolu
  • Assigned To set to Benjamin Bohard
  • % Done changed from 0 to 100

Ok dans le dernier test :

14:37:50             Synchronisation ldap
14:37:50             janv. 23 14:37:42 - INFO  - Logging configuration successfully loaded from /etc/lsc/logback.xml
14:37:50             janv. 23 14:37:42 - INFO  - LSC configuration successfully loaded from /etc/lsc/

#6 Updated by Joël Cuissinat 8 months ago

https://dev-eole.ac-dijon.fr/jenkins/job/2.8.0/job/test-upgradeauto-scribe-272-2.8.0-amd64/

11:05:16             --------------------------------------------------------------------------------
11:05:16                                        Génération des certificats
11:05:16             --------------------------------------------------------------------------------
11:05:16             Voulez-vous remplacer l'ancien certificat auto-signé ? [oui/non]
11:05:16             MONITOR: upgrade_auto_cert action:oui
11:05:16             oui
11:05:16             [non] : * Génération du certificat de la CA
11:05:16             * Certificat /etc/ssl/certs/eole.crt généré
11:05:16             * Certificat /etc/courier/imapd.pem généré
11:05:16             * Certificat /etc/courier/pop3d.pem généré

11:09:56             Test du fichier de configuration :
11:09:56             .                     Syntaxe => Ok
11:09:56             Statut du service winbindd :
11:09:56             .            Service winbindd => Ok
11:09:56             .         uid/gid disponibles => Ok
11:09:56             .               Etat du cache => Ok
11:09:56             .            Connexions samba => 0
11:09:56             .             Ticket kerberos => Ok
11:09:56             .         Synchronisation LSC => Ok

#7 Updated by Joël Cuissinat 8 months ago

  • Status changed from Résolu to Fermé
  • Remaining (hours) set to 0.0

Also available in: Atom PDF