Hi,
I would like to apologize in advance for re-asking a FAQ: I am well
aware that here have been a ton of similar reports before, and I did
read these and try out suggested solutions, with no avail.
After running bacula for a long, long time with MySQL, I decided to
try it out with PostgreSQL instead.
This is a from-scratch installation based on Fedora 17 and the Bacula
packages that come with this release, i. e.
bacula-client-5.2.12-3.fc17.x86_64
bacula-common-5.2.12-3.fc17.x86_64
bacula-console-5.2.12-3.fc17.x86_64
bacula-console-bat-5.2.12-3.fc17.x86_64
bacula-director-5.2.12-3.fc17.x86_64
bacula-docs-5.2.12-1.fc17.noarch
bacula-libs-5.2.12-3.fc17.x86_64
bacula-libs-sql-5.2.12-3.fc17.x86_64
bacula-storage-5.2.12-3.fc17.x86_64
The problem: I get (like so many others before) these error messages:
...
bacula-dir: dir_plugins.c:160-0 Load dir plugins
bacula-dir: dir_plugins.c:162-0 No dir plugin dir!
bacula-dir: lockmgr.c:583-0 Exit check_deadlock.
bacula-dir: postgresql.c:1126-0 db_init_database first time
bacula-dir: postgresql.c:241-0 pg_real_connect done
bacula-dir: postgresql.c:243-0 db_user=bacula db_name=bacula db_password=XXXXXX
bacula-dir: dird.c:1006 Could not open Catalog "MyCatalog", database "bacula".
bacula-dir: dird.c:1011 postgresql.c:248 Unable to connect to PostgreSQL
server. Databas
Possible causes: SQL server not running; password incorrect; max_connections
exceeded.
27-Dec 15:56 bacula-dir ERROR TERMINATION
Please correct configuration file: /etc/bacula/bacula-dir.conf
...
I used this command to set the db_password :
# su - -s /bin/bash bacula
-bash-4.2$ psql -Ubacula bacula
psql (9.1.7)
Type "help" for help.
bacula=> alter user bacula with password 'XXXXXX';
ALTER ROLE
bacula=> \q
-bash-4.2$
I appears this worked fine. I can also access the batabase manually,
like running the commands described in step "13. Resequence your
tables with the following commands" in the "Installing and
Configuring PostgreSQL" section of the manual:
# su - -s /bin/bash bacula
-bash-4.2$ psql -Ubacula bacula
psql (9.1.7)
Type "help" for help.
bacula=> SELECT SETVAL('client_clientid_seq', (SELECT
bacula(> MAX(clientid) FROM client));
setval
--------
(1 row)
bacula=> \q
-bash-4.2$
So it appears that the PostgreSQL server is up and running, the DB is
there and can be accessed.
Note: none of the commands above did request me to enter any
password. [But then, when changing bacula-dir.conf back to the
default setting (empty db_password), I get the same results]
I tried with misc settings of pg_hba.conf as recommended in some of
the previous postings, with no avail either.
Is there any way to debug which actual operation is failing? Or
otherwise find out which exact setting might be wrong?
Thanks in advance...
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
"You're just jealous." "What, of an overgrown puppy with a single-
figure IQ?" - Terry Pratchett, _Moving Pictures_
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122712
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
