Thread: bacula problem - failures with no error message in postgres?

hiya

I know this is somewhat offtopic, but I am stuck.

I am trying to get bacula to run and am testing the backup catalog
script. I am using postgres for my database and am getting this error

30-Mar 19:33 collab-dir: BackupCatalog.2008-03-30_19.33.00 Fatal error:
sql_create.c:485 sql_create.c:485 query SELECT ClientId,Uname FROM
Client WHERE Name='collab-fd' failed:

30-Mar 19:33 collab-dir: BackupCatalog.2008-03-30_19.33.00 Fatal error:
sql_create.c:520 sql_create.c:520 insert INSERT INTO Client
(Name,Uname,AutoPrune,FileRetention,JobRetention) VALUES
('collab-fd','',1,2592000,15552000) failed:

30-Mar 19:33 collab-dir: BackupCatalog.2008-03-30_19.33.00 Error:
sql_create.c:522 Create DB Client record INSERT INTO Client
(Name,Uname,AutoPrune,FileRetention,JobRetention) VALUES
('collab-fd','',1,2592000,15552000) failed. ERR=
30-Mar 19:33 collab-dir: BackupCatalog.2008-03-30_19.33.00 Fatal error:
Could not create Client record. ERR=sql_create.c:522 Create DB Client
record INSERT INTO Client
(Name,Uname,AutoPrune,FileRetention,JobRetention) VALUES
('collab-fd','',1,2592000,15552000) failed. ERR=

even on the higher debug levels I am not seeing thing in the postgres logs

any ideas?

Thanks a lot

Bernhard


--
Graylion's Fetish & Fashion Store
Goth and Kinky Boots, Clothing and Jewellery
http://www.graylion.net




--
Graylion's Fetish & Fashion Store
Goth and Kinky Boots, Clothing and Jewellery
http://www.graylion.net

> even on the higher debug levels I am not seeing thing in the postgres logs
Are you increasing the debug levels of Bacula or of Postgres? You'll need to
look in the PG logs and increase their verbosity.


THINK BEFORE YOU PRINT - Save paper if you don't really need to print this

*******************Confidentiality and Privilege Notice*******************

The material contained in this message is privileged and confidential to
the addressee.  If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.

Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments
e-mail.