Project

General

Profile

Tâche #20183

Scénario #20195: Finaliser le portage du projet Eole-AD en 2.5.2 et 2.6.2

Faire fonctionner le script schedule "eolead"

Added by Joël Cuissinat over 2 years ago. Updated over 2 years ago.

Status:
Fermé
Priority:
Normal
Assigned To:
Start date:
03/27/2017
Due date:
% Done:

100%

Estimated time:
3.00 h
Spent time:
Remaining (hours):
0.0

Description

Pour un schedule, il faut un dico...


Related issues

Related to Scribe - Tâche #7878: Forcer la synchro lsc toutes les nuits (eole-ad) Fermé 03/25/2015

Associated revisions

Revision 59510448 (diff)
Added by Joël Cuissinat over 2 years ago

Eole-AD : mise à niveau du "schedule"

Ref: #20183

History

#1 Updated by Joël Cuissinat over 2 years ago

  • Parent task changed from #19503 to #20195

#2 Updated by Joël Cuissinat over 2 years ago

  • Status changed from Nouveau to En cours

#3 Updated by Joël Cuissinat over 2 years ago

  • Assigned To set to Joël Cuissinat

#4 Updated by Joël Cuissinat over 2 years ago

  • Related to Tâche #7878: Forcer la synchro lsc toutes les nuits (eole-ad) added

#5 Updated by Joël Cuissinat over 2 years ago

  • % Done changed from 0 to 100
  • Remaining (hours) changed from 3.0 to 0.5

#6 Updated by Gilles Grandgérard over 2 years ago

  • Status changed from En cours to Résolu

#7 Updated by Gérald Schwartzmann over 2 years ago

  • Status changed from Résolu to Fermé
  • Remaining (hours) changed from 0.5 to 0.0
--------------------------------------------------------------------------------------------------------------------------------------------------------------
                                                                    Planificateur de tâche                                                                    
--------------------------------------------------------------------------------------------------------------------------------------------------------------
Tâches planifiées EOLE :
 * les tâches journalières se feront tous les jours à 04:20 (hors sauvegarde)
  - avant sauvegarde
   + Exportation des quotas et du SID Samba (fichier)
   + Exportation de l'annuaire LDAP (annuaire)
   + Exportation des bases MySQL (mysql)
  - après sauvegarde
   + Vérification de l'intégrité des caches Samba (tdbbackup)
   + Synchronisation LSC (eolead)
 * les tâches hebdomadaires se feront le samedi à 04:20 (hors sauvegarde)
  - après sauvegarde
   + Mise à jour du serveur (majauto)
 * les tâches mensuelles se feront le premier jeudi du mois à 04:20 (hors sauvegarde)
  - après sauvegarde
   + Compactage de la base de donnée de Bareos (bareos)
--------------------------------------------------------------------------------------------------------------------------------------------------------------
                                                               Finalisation de la configuration                                                               

root@scribe:~# /usr/share/eole/schedule/schedule cron
Démarrage de pre schedule daily
/usr/share/eole/schedule/daily/pre/annuaire:
Stop System V service slapd                                             [  OK  ]
Start System V service slapd                                            [  OK  ]
pre schedule daily accompli
Démarrage de post schedule daily
/usr/share/eole/schedule/daily/post/eolead:
lsc: [INFO] Using /etc/default/lsc for configuration
lsc: [OK] LSC is already stopped
mai 09 15:40:23 - ERROR - Error opening the LDAP connection to the destination! (javax.naming.CommunicationException: seth1.ac-test.fr:389 [Root exception is java.net.UnknownHostException: seth1.ac-test.fr])
mai 09 15:40:23 - ERROR - org.lsc.exception.LscConfigurationException: Configuration exception: javax.naming.CommunicationException: seth1.ac-test.fr:389 [Root exception is java.net.UnknownHostException: seth1.ac-test.fr]
lsc: [INFO] Using /etc/default/lsc for configuration
lsc: [INFO] Launching LSC configuration test...
lsc: [OK] LSC configuration test successful
lsc: [INFO] Launching LSC...
lsc: [OK] Using LSC JMX port 1099
lsc: [INFO] Waiting 1s for LSC java process to launch
lsc: [OK] Register LSC PID 15840
lsc: [OK] LSC started
post schedule daily accompli
Démarrage de pre schedule once
pre schedule once accompli
Démarrage de post schedule once
post schedule once accompli
root@scribe:~# 
root@scribe:~# tail -f /var/log/rsyslog/local/eole-schedule/
tail: erreur de lecture «/var/log/rsyslog/local/eole-schedule/»: est un dossier
tail: /var/log/rsyslog/local/eole-schedule/ : impossible de suivre la fin de ce type de fichier, abandon sur ce nom
root@scribe:~# tail -f /var/log/rsyslog/local/eole-schedule/eole-schedule.info.log 
2017-05-09T15:40:28.427328+02:00 scribe.ac-test.fr eole-schedule: lsc: [INFO] Launching LSC...
2017-05-09T15:40:28.427598+02:00 scribe.ac-test.fr eole-schedule: lsc: [OK] Using LSC JMX port 1099
2017-05-09T15:40:28.427872+02:00 scribe.ac-test.fr eole-schedule: lsc: [INFO] Waiting 1s for LSC java process to launch
2017-05-09T15:40:28.428177+02:00 scribe.ac-test.fr eole-schedule: lsc: [OK] Register LSC PID 15840
2017-05-09T15:40:28.428444+02:00 scribe.ac-test.fr eole-schedule: lsc: [OK] LSC started
2017-05-09T15:40:28.428741+02:00 scribe.ac-test.fr eole-schedule: post schedule daily accompli
2017-05-09T15:40:28.739707+02:00 scribe.ac-test.fr eole-schedule: Démarrage de pre schedule once
2017-05-09T15:40:28.745112+02:00 scribe.ac-test.fr eole-schedule: pre schedule once accompli
2017-05-09T15:40:28.745353+02:00 scribe.ac-test.fr eole-schedule: Démarrage de post schedule once
2017-05-09T15:40:28.749556+02:00 scribe.ac-test.fr eole-schedule: post schedule once accompli

Also available in: Atom PDF