#3315 Issue closed: ReaR BACKUP=BACULA director not responding but bacula works perfectly on ubuntu 20.04 how to resove

Labels: waiting for info, support / question, won't fix / can't fix / obsolete

bacula4392 opened issue at 2024-09-08 05:36:

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

  • 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"):

  • 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):

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

  • 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):

  • Workaround, if any:

  • 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

gdha commented at 2024-09-10 11:56:

@WRice It would be nice if you filled in the issue template. However, please use the latest https://github.com/rear/rear/releases package for your distribution (use a debian one) and verify if that did not fix your issue. Thanks.

[Export of Github issue for rear/rear.]