#3082 Issue `closed`: ERROR: Bacula client status unknown on director.¶

Labels: bug, fixed / solved / done, external tool

Githopp192 opened issue at 2023-11-14 17:27:¶

ReaR version ("/usr/sbin/rear -V"):

Relax-and-Recover 2.6 / 2020-06-17

If your ReaR version is not the current version, explain why you can't upgrade:
OS version ("cat /etc/os-release" or "lsb_release -a" or "cat /etc/rear/os.conf"):

Red Hat Enterprise Linux 8.9 (Ootpa)"

ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
Hardware vendor/product (PC or PowerNV BareMetal or ARM) or VM (KVM guest or PowerVM LPAR):

HPE ProLiant DL20 Gen10

System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device):

x86

Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot):
Storage (local disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe):
Storage layout ("lsblk -ipo NAME,KNAME,PKNAME,TRAN,TYPE,FSTYPE,LABEL,SIZE,MOUNTPOINT"):
Description of the issue (ideally so that others can reproduce it):

When REAR will check if bacula is available it will run:

"/usr/share/rear/prep/BACULA/default/500_check_BACULA_bconsole_results.sh"

This script will do a :

grep -i address /etc/bacula/bconsole.conf | awk '{ print $3 }'

In my environment/case i've got an entry in "/etc/bacula/bconsole.conf"

The obove mentioned script's output is:

grep -i address /etc/bacula/bconsole.conf | awk '{ print $3 }':

And that it is - the bacula check will fail - but indeed all is running (bacula) properly.

So the script command line should check in a more specifc way, like :

grep '^[[:space:]]address[[:space:]]=' /etc/bacula/bconsole.conf

Workaround, if any:
remove the comment-"address"-entries in the /etc/bacula/bconsole.conf

... same is valid for command:

grep $(hostname -s) /etc/bacula/bacula-fd.conf | grep "-fd" | awk '{print $3}' | sed -e "s/-fd//g"

It seems REAR will not handle config files properly, when some line are commented with similar content.

Attachments, as applicable ("rear -D mkrescue/mkbackup/recover" debug log files):

You can drag-drop log files into this editor to create an attachment
or paste verbatim text like command output or file content
by including it between a leading and a closing line of
three backticks like this:

verbatim content

jsmeix commented at 2023-11-15 09:03:¶

@gdha
could you please have a look here (as time permits)?

@Githopp192
could you show us your whole
/etc/bacula/bconsole.conf
and
/etc/bacula/bacula-fd.conf
files?

Githopp192 commented at 2023-11-16 17:13:¶

Thanks Johannes .. cannot input the whole backup config - to confidential.

But the context is easy to follow - as long as - in this example "client-fd" is there more than once (one uncommented);
the script will have two results (2x client) the script will return an error an REAR will exit

same is true for your check for "bconsole.conf":

Affected script: /usr/share/rear/prep/BACULA/default/500_check_BACULA_bconsole_results.sh", line 15 & 32

jsmeix commented at 2023-11-17 14:11:¶

@Githopp192
thank you for your information.

I am not a user of Bacula
(or any other third-party backup tool)
so I need sufficient input to understand
how things look with Bacula.

Githopp192 commented at 2023-11-17 14:14:¶

Very welcome, Johannes .. yes can understand & glad to support & thx for this great product.
I used it several timess for Disaster Recovery ... and i got everything back to work :-)

jsmeix commented at 2023-11-17 14:21:¶

@Githopp192
thanks for your explicit feedback that
ReaR works when it comes to the crunch.

We don't get many reports when it works
but mostly when something doesn't work
(which is expected).

gdha commented at 2023-11-17 14:21:¶

@Githopp192 seems you modified the bacula code to work again? Why not provide a pull request so others may benefit from your enhancements?

Githopp192 commented at 2023-11-17 14:38:¶

@gdha (did not change the code ... as workaround only removed the entries with comments ==> #xxxxxxxx)

i'm glad you mentioned that, because today - this got into my mind, too .... may be it sounds stupid enough, i should/i could .. but i'm not experienced with this .. but - yes this is not an excuse :-) - i will give it a try. Thx 4 your input. I do appreciate

... reading ...

https://docs.github.com/de/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests