Scénario #29090
Mis à jour par Joël Cuissinat il y a plus de 6 ans
* Pas de problème sur une instance d’un ScribeAD 2.7.1 fraîchement installé
* Vu dans le test jenkins : https://dev-eole.ac-dijon.fr/jenkins/job/2.7.1/job/test-upgradeauto-scribead-262-2.7.1-amd64/lastFailedBuild/console
<pre>
02:34:42.507 Service bareos-director is not running [ KO ]
[…]
02:34:42.508 run-parts: executing /usr/share/eole/postservice/00-bareos instance
02:34:42.508 run-parts: /usr/share/eole/postservice/00-bareos exited with return code 1
02:34:42.508 Erreur : postservice
</pre>
* Lors d’un *@Upgrade-Auto@* manuel, j’obtiens l’erreur suivant sur le service *@bareos-director@*
<pre>
root@scribe:~# systemctl status bareos-director.service
● bareos-director.service - Bareos Director Daemon service
Loaded: loaded (/lib/systemd/system/bareos-director.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Wed 2019-10-09 10:55:00 CEST; 2min 20s ago
Docs: man:bareos-dir(8)
Process: 27469 ExecStart=/usr/sbin/bareos-dir (code=exited, status=0/SUCCESS)
Process: 27375 ExecStartPre=/usr/sbin/bareos-dir -t -f (code=exited, status=1/FAILURE)
Main PID: 27521 (code=exited, status=1/FAILURE)
oct. 09 10:55:00 scribe bareos-dir[27375]: Please correct the configuration in /etc/bareos/bareos-dir.conf
oct. 09 10:55:00 scribe bareos-dir[27375]: bareos-dir ERROR TERMINATION
oct. 09 10:55:00 scribe bareos-dir[27375]: Please correct the configuration in /etc/bareos/bareos-dir.conf
oct. 09 10:55:00 scribe systemd[1]: bareos-director.service: Can't open PID file /run/bareos/bareos-dir.9101.pid (yet?) after start: No such file or directory
oct. 09 10:55:00 scribe systemd[1]: Started Bareos Director Daemon service.
oct. 09 10:55:00 scribe bareos-dir[27521]: bareos-dir JobId 0: Fatal error: Version error for database "bareos". Wanted 2004, got 2003
oct. 09 10:55:00 scribe bareos-dir[27521]: bareos-dir JobId 0: Fatal error: Could not open Catalog "MyCatalog", database "bareos".
oct. 09 10:55:00 scribe bareos-dir[27521]: bareos-dir JobId 0: Fatal error: Version error for database "bareos". Wanted 2004, got 2003
oct. 09 10:55:00 scribe bareos-dir[27521]: bareos-dir ERROR TERMINATION
oct. 09 10:55:00 scribe bareos-dir[27521]: Please correct the configuration in /etc/bareos/bareos-dir.conf
</pre>
Je ne souhaitais pas tester bareos, j’ai donc désactivé tous les services bareos mais le script *@postservice/00-bareos@* s’exécute quand même !
h3. Solutions à mettre en œuvre
* corriger la mise à niveau de la base de données Bareos en *2.7.1* 2.7.1
h3. Critère d'acceptation
* Le test Jenkins est passant : https://dev-eole.ac-dijon.fr/jenkins/job/2.7.1/job/test-upgradeauto-scribead-262-2.7.1-amd64/ (en tout cas sur ce point)
* Vu dans le test jenkins : https://dev-eole.ac-dijon.fr/jenkins/job/2.7.1/job/test-upgradeauto-scribead-262-2.7.1-amd64/lastFailedBuild/console
<pre>
02:34:42.507 Service bareos-director is not running [ KO ]
[…]
02:34:42.508 run-parts: executing /usr/share/eole/postservice/00-bareos instance
02:34:42.508 run-parts: /usr/share/eole/postservice/00-bareos exited with return code 1
02:34:42.508 Erreur : postservice
</pre>
* Lors d’un *@Upgrade-Auto@* manuel, j’obtiens l’erreur suivant sur le service *@bareos-director@*
<pre>
root@scribe:~# systemctl status bareos-director.service
● bareos-director.service - Bareos Director Daemon service
Loaded: loaded (/lib/systemd/system/bareos-director.service; enabled; vendor preset: enabled)
Active: inactive (dead) since Wed 2019-10-09 10:55:00 CEST; 2min 20s ago
Docs: man:bareos-dir(8)
Process: 27469 ExecStart=/usr/sbin/bareos-dir (code=exited, status=0/SUCCESS)
Process: 27375 ExecStartPre=/usr/sbin/bareos-dir -t -f (code=exited, status=1/FAILURE)
Main PID: 27521 (code=exited, status=1/FAILURE)
oct. 09 10:55:00 scribe bareos-dir[27375]: Please correct the configuration in /etc/bareos/bareos-dir.conf
oct. 09 10:55:00 scribe bareos-dir[27375]: bareos-dir ERROR TERMINATION
oct. 09 10:55:00 scribe bareos-dir[27375]: Please correct the configuration in /etc/bareos/bareos-dir.conf
oct. 09 10:55:00 scribe systemd[1]: bareos-director.service: Can't open PID file /run/bareos/bareos-dir.9101.pid (yet?) after start: No such file or directory
oct. 09 10:55:00 scribe systemd[1]: Started Bareos Director Daemon service.
oct. 09 10:55:00 scribe bareos-dir[27521]: bareos-dir JobId 0: Fatal error: Version error for database "bareos". Wanted 2004, got 2003
oct. 09 10:55:00 scribe bareos-dir[27521]: bareos-dir JobId 0: Fatal error: Could not open Catalog "MyCatalog", database "bareos".
oct. 09 10:55:00 scribe bareos-dir[27521]: bareos-dir JobId 0: Fatal error: Version error for database "bareos". Wanted 2004, got 2003
oct. 09 10:55:00 scribe bareos-dir[27521]: bareos-dir ERROR TERMINATION
oct. 09 10:55:00 scribe bareos-dir[27521]: Please correct the configuration in /etc/bareos/bareos-dir.conf
</pre>
Je ne souhaitais pas tester bareos, j’ai donc désactivé tous les services bareos mais le script *@postservice/00-bareos@* s’exécute quand même !
h3. Solutions à mettre en œuvre
* corriger la mise à niveau de la base de données Bareos en *2.7.1* 2.7.1
h3. Critère d'acceptation
* Le test Jenkins est passant : https://dev-eole.ac-dijon.fr/jenkins/job/2.7.1/job/test-upgradeauto-scribead-262-2.7.1-amd64/ (en tout cas sur ce point)