Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#29239 - [bacula] Seems to need postgresql libs for the director to start

Attached to Project: Community Packages
Opened by Mark (fiddlinmacx) - Monday, 02 April 2012, 19:42 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Tuesday, 03 April 2012, 18:16 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
/usr/sbin/bacula-dir: error while loading shared libraries: libpq.so.5: cannot open shared object file: No such file or directory

comes up when starting director. I don't use postgresql and I only see it in the PKGBUILD as a make dependancy.


Additional info:
* package version(s): 5.2.6-2

I wonder if the same thing would happen without sqlite installed as well. I haven't tested this.

Steps to reproduce:
Upgrade bacula to 5.2.6-2 and then restart the director (without postgresql-libs installed, of course).
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Tuesday, 03 April 2012, 18:16 GMT
Reason for closing:  Fixed
Comment by Mark (fiddlinmacx) - Monday, 02 April 2012, 19:45 GMT
Oh... and I just found out the bacula-dir doesn't stay running anyway, even with postgresql-libs installed.
/var/log/bacula says:

02-Apr 15:41 bacula-dir JobId 0: Fatal error: Could not open Catalog "MyCatalog", database "bacula".
02-Apr 15:41 bacula-dir JobId 0: Fatal error: postgresql.c:248 Unable to connect to PostgreSQL server. Database=bacula User=bacula
Possible causes: SQL server not running; password incorrect; max_connections exceeded.
02-Apr 15:41 bacula-dir ERROR TERMINATION
Please correct configuration file: bacula-dir.conf

It seems to want to connect to postgresql now regardless of the fact that all my configs are set up with mysql.
I'm going to have to downgrade so that I can have a functioning system.
Comment by Sven-Hendrik Haase (Svenstaro) - Tuesday, 03 April 2012, 18:16 GMT
Looks like enabling more databases for bacula didn't work out so well. Reverted in rel 3. Though on my server it did work fine and that uses mysql for bacula.

Loading...