Package Details: bacula-dir-postgresql 15.0.2-2

Git Clone URL: https://aur.archlinux.org/bacula.git (read-only, click to copy)
Package Base: bacula
Description: Bacula - A Network Backup Tool (Director - PostgreSQL support)
Upstream URL: https://www.bacula.org
Licenses: AGPL3
Conflicts: bacula-dir-mariadb, bacula-dir-sqlite3
Submitter: None
Maintainer: lifespirit
Last Packager: lifespirit
Votes: 36
Popularity: 0.54
First Submitted: 2014-04-25 13:59 (UTC)
Last Updated: 2024-06-05 06:28 (UTC)

Pinned Comments

lifespirit commented on 2024-06-04 10:13 (UTC)

If you have error "GPG check failed" when you install, run

gpg --recv-keys C0BE2A5FE9DF3643

for user who build package.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »

georgnix commented on 2015-10-02 09:12 (UTC)

I tested disaster recovery with the new 7.2.0 version yesterday. It worked with some fiddling around. Just to document it here, there are some more or less minor glitches with the packaging: * /var/log/bacula is not created by the packages, this causes the start of the director to fail. * /etc/bacula/scripts is not readable for user postgres. Thus database scripts cannot be executed properly. I think it would it be OK to have /etc/bacula and children world readable as long as the config files are only readable by root (clear text passwords). * Generated config files are in the package, i.e. static. They should be generated at package installation to have unique passwords and proper hostname. If anybody wants to fix the PKGBUILD, go ahead. I probably won't find the time to do it myself.

georgnix commented on 2015-10-01 14:29 (UTC)

I created an updated PKGBUILD for bacula 7.2.0 with additional minor fixes. http://www.george-net.de/aur/bacula/PKGBUILD-bacula-7.2.0 Diff against the old PKGBUILD to see the changes.

lka commented on 2015-09-21 15:04 (UTC)

Installation successful, systemctl status bacula-fd successful loaded and running, but server (bacula-dir, 2nd maschine) can't connect to client (arch). Nmap shows tcp port 9102 st up, but servers bconsole (status client arch) says no. By the way all other systems (non-arch) work fine, so i think my configuration is ok. I don't know why there is no respone from bacula-fd.

xisberto commented on 2015-09-02 15:43 (UTC)

Anyone can successfully install bacula-fd? It depends on tcp_wrappers, but its upstream URL can not be reached.

AlD commented on 2015-03-06 01:13 (UTC)

Oh and configure flags haven't changed, tcp_wrappers were always enabled.

AlD commented on 2015-03-06 01:04 (UTC)

Thanks for the patch, georgnix. Tweaked it slightly, let me know if there are problems.

georgnix commented on 2015-03-04 21:29 (UTC)

@lockheed Download the AUR tarball, extract, download the patch, then $ patch -p0 < 2015-03-04-PKGBUILD.patch $ makepkg Install the relevant packages with pacman.

lockheed commented on 2015-03-04 20:15 (UTC)

@georgnix, I see you wrote a patch that might address my problem. After installing bacula on server, when I try to run bacula-dir, I get bacula-dir: error while loading shared libraries: libbaccats-7.0.5.so: cannot open shared object file: No such file or directory If you patch solves it, then how do I apply it? I have no idea how to do it.

georgnix commented on 2015-03-04 17:35 (UTC)

@AlD Did you change the configure flags since 7.0.4? Suddenly bacula daemons respect /etc/hosts.allow which I had to find out the hard way bacula-dir -d 10000 ... also gives every config lexer token ... *YUCK* Does anybody use tcp wrappers? I don't and would be happy if this would be removed from the build. There are firewalls these days...