Re: [Bacula-devel] PQisthreadsafe returns 0 for unknown reason

[Eric B. <eri...@ba...>]

Hello,

Le mercredi 29 septembre 2010 12:34:53, Spiros Ioannou a écrit :
>   I tried to upgrade from 3.0.1  to 5.0.3 , and it's been a nightmare for
> 2 days.
> after giving up on bat (it's is a impossible to compile due to a variety
> of errors, reminding me of compiling software in the early 90's),

For bat, you need to follow carefully the README instructions, for example, 
you might not be able to compile it if the QT version doesn't match.
 
> I'm now stuck with bacula-dir not starting, with the following error in
> the log:
> 29-Sep 13:22 bacula-dir: ABORTING due to ERROR in postgresql.c:303
> Pg client library must be thread-safe when using BatchMode.
> but, postgres is 8.3.3 configured with  --enable-thread-safety, and in
> bacula's config.log I could find:
> configure:29051: checking for PQisthreadsafe in -lpq
> configure:29086: gcc -o conftest -g -O2   conftest.c -lpq  -ldl
> -L/usr/local/pgsql/lib -lpq -lcrypt >&5
> configure:29092: $? = 0
> configure:29110: result: yes
> ....
> ac_cv_lib_pq_PQisthreadsafe=yes
> 
> doing an ltrace bacula-dir though, outputs this:
> PQisthreadsafe(0x6c1920, 0, 0x6c1920, 0, 0x134ed28) = 0

It's hard to say, maybe you can try the postgresql mailling list, they should 
be able to say why this function doesn't work as expected on your system, but 
you probably missed something during the compilation or you have old libraries 
that interfer.
 
> please help as I'm now left without backup since I've updated the DB to
> the new version.
> Thanks.
> system is CentOs 5.3
> postgres 8.3.3
> bacula 5.0.3

You should be able to avoid all problems by using RPMs available on 
sourceforge.

Bye

-- 
Need professional help and support for Bacula ?
Visit http://www.baculasystems.com