Tâche #25025
Scénario #24651: Traitement express MEN (38-40)
Si on redémarre le serveur, les services Bareos sont en erreur
Description
Problème visiblement lié au(x) chemin(s) du PID :
root@scribe:~# service bareos-director status ● bareos-director.service - Bareos Director Daemon service Loaded: loaded (/lib/systemd/system/bareos-director.service; enabled; vendor preset: enabled) Active: activating (start) since Mon 2018-09-17 12:00:18 CEST; 14s ago Docs: man:bareos-dir(8) Process: 1505 ExecStart=/usr/sbin/bareos-dir (code=exited, status=0/SUCCESS) Process: 1482 ExecStartPre=/usr/sbin/bareos-dir -t -f (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 3527) CGroup: /system.slice/bareos-director.service sept. 17 12:00:18 scribe systemd[1]: Starting Bareos Director Daemon service... sept. 17 12:00:18 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 sept. 17 12:00:18 scribe bareos-dir[1508]: bareos-dir: ERROR TERMINATION at bsys.c:635 sept. 17 12:00:18 scribe bareos-dir[1508]: Could not open pid file. /var/run/bareos/bareos-dir.9101.pid ERR=Aucun fichier ou dossier de ce type
Pourtant :
root@scribe:~# grep PID /lib/systemd/system/bareos-director.service PIDFile=/run/bareos/bareos-dir.9101.pid
Associated revisions
/run/bareos must exists with right permissions for PID file
ref #25025
Revert "/run/bareos must exists with right permissions for PID file"
This reverts commit 72e71476af63431a8423511e9d67315ae4354c06.
Ref: #25025
/run/bareos must be created before starting any service
- debian/bareos-director.tmpfile: let systemd create /run/bareos.
- debian/bareos-filedaemon.tmpfile: ditoo.
- debian/bareos-storage.tmpfile: ditoo.
Ref: #25025
Do not enable or start daemons on initial installation
During the first installation the bareos-director daemon want to use
MySQL as default catalog backend but nothing is configured yet.
Ref: #25025
Prepare release 16.2.6-4~eole270.7
Ref: #25025
Do not install SystemV scripts
Ref: #25025
Prepare release 16.2.6-4~eole270.8
Ref: #25025
diagnose: do not fail when there is no job
When there is no job “check_bareos” returns the value “3” and not “0”.
- diagnose/153-bareos (TestBareosMonitorLocal): accept the return code
“3” as not an error.
Ref: #25025
History
#1 Updated by Fabrice Barconnière about 5 years ago
Le pb est après reboot
#2 Updated by Daniel Dehennin about 5 years ago
- Status changed from Nouveau to En cours
#3 Updated by Daniel Dehennin about 5 years ago
- % Done changed from 0 to 100
- Remaining (hours) changed from 2.0 to 0.25
#4 Updated by Scrum Master about 5 years ago
- Status changed from En cours to Résolu
#5 Updated by Scrum Master about 5 years ago
- Status changed from Résolu to Fermé
- Remaining (hours) changed from 0.25 to 0.0