Anomalie #1984
Erreur dans bacula-dir.conf [2.3-dév]
Status:
Fermé
Priority:
Normal
Assigned To:
Category:
-
Target version:
Distribution:
EOLE 2.3
Description
Visiblement seul RunAfterFailedJob est autorisé mais dans ce cas, les commandes sont appelées avec l'utilisateur bacula et il faut donc adapter les droits sur les scripts et les fichiers de log !
24-Aug 09:50 bacula-dir: ERROR TERMINATION at parse_conf.c:971
Config error: Keyword "ClientRunAfterFailedJob" not permitted in this resource.
Perhaps you left the trailing brace off of the previous resource.
: line 55, col 26 of file /etc/bacula/bacula-dir.conf
ClientRunAfterFailedJob = "/usr/share/eole/bacula/baculaconfig.py --unlock --backup_err"
Related issues
Associated revisions
bacula-dir.conf : ClientRunAfterFailedJob => RunAfterFailedJob + corrections (fixes #1984)
History
#1 Updated by Joël Cuissinat about 12 years ago
- Status changed from Nouveau to Résolu
- % Done changed from 0 to 100
Appliqué par commit b8a0451e1c4ae60e718b80308f0362f7656d83be.
#2 Updated by Joël Cuissinat about 12 years ago
- Assigned To set to Joël Cuissinat
#3 Updated by Joël Cuissinat almost 12 years ago
- Status changed from Résolu to Fermé
- Distribution set to EOLE 2.3
Plus d'erreur visible et :
root@horus23:~# grep ClientRunAfterFailedJob /etc/bacula/bacula-dir.conf root@horus23:~#