bacula failing on puppet runs

RESOLVED FIXED

Status

Infrastructure & Operations
Infrastructure: Backups
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: arr, Assigned: rtucker)

Tracking

Details

(Reporter)

Description

a year ago
I happened to be looking at a puppet run on admin1b.private.releng.scl3.mozilla.com and noticed a bunch of failure messages for bacula. I didn't see any accompanying puppet freshness issues for the host, so I don't know how widespread this is, since it seems to fail silently. It's been complaining on every puppet run on this host as far back as the logs go (Apr 24 03:53:01).

Error: Could not start Service[bacula-fd]: Execution of '/sbin/service bacula-fd start' returned 1: Starting Bacula File services: admin1b.private.releng.scl3.mozilla.com: Fatal Error at filed.c:623 because:
Failed to initialize TLS context for Director "bacula1.private.scl3.mozilla.com" in /opt/bacula/etc/bacula-fd.conf.
25-May 10:36 admin1b.private.releng.scl3.mozilla.com: Fatal Error at filed.c:623 because:
Failed to initialize TLS context for Director "bacula1.private.scl3.mozilla.com" in /opt/bacula/etc/bacula-fd.conf.
admin1b.private.releng.scl3.mozilla.com: ERROR in filed.c:211 Please correct configuration file: /opt/bacula/etc/bacula-fd.conf
25-May 10:36 admin1b.private.releng.scl3.mozilla.com: ERROR in filed.c:211 Please correct configuration file: /opt/bacula/etc/bacula-fd.conf
[FAILED]
Wrapped exception:
Execution of '/sbin/service bacula-fd start' returned 1: Starting Bacula File services: admin1b.private.releng.scl3.mozilla.com: Fatal Error at filed.c:623 because:
Failed to initialize TLS context for Director "bacula1.private.scl3.mozilla.com" in /opt/bacula/etc/bacula-fd.conf.
25-May 10:36 admin1b.private.releng.scl3.mozilla.com: Fatal Error at filed.c:623 because:
Failed to initialize TLS context for Director "bacula1.private.scl3.mozilla.com" in /opt/bacula/etc/bacula-fd.conf.
admin1b.private.releng.scl3.mozilla.com: ERROR in filed.c:211 Please correct configuration file: /opt/bacula/etc/bacula-fd.conf
25-May 10:36 admin1b.private.releng.scl3.mozilla.com: ERROR in filed.c:211 Please correct configuration file: /opt/bacula/etc/bacula-fd.conf
[FAILED]
Error: /Stage[main]/Bacula_client/Service[bacula-fd]/ensure: change from stopped to running failed: Could not start Service[bacula-fd]: Execution of '/sbin/service bacula-fd start' returned 1: Starting Bacula File services: admin1b.private.releng.scl3.mozilla.com: Fatal Error at filed.c:623 because:
Failed to initialize TLS context for Director "bacula1.private.scl3.mozilla.com" in /opt/bacula/etc/bacula-fd.conf.
25-May 10:36 admin1b.private.releng.scl3.mozilla.com: Fatal Error at filed.c:623 because:
Failed to initialize TLS context for Director "bacula1.private.scl3.mozilla.com" in /opt/bacula/etc/bacula-fd.conf.
admin1b.private.releng.scl3.mozilla.com: ERROR in filed.c:211 Please correct configuration file: /opt/bacula/etc/bacula-fd.conf
25-May 10:36 admin1b.private.releng.scl3.mozilla.com: ERROR in filed.c:211 Please correct configuration file: /opt/bacula/etc/bacula-fd.conf
(Assignee)

Comment 1

a year ago
I installed the TLS certs and bacula has started as expected.

We don't have anything earmarked to be backed up on the releng admin hosts, is there anything that needs backed up on it?
Assignee: infra → rtucker
(Assignee)

Comment 2

a year ago
I've added the same backup sets as found on the other admin nodes.
(Assignee)

Comment 3

a year ago
Backups have been functional. Closing this out
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.