On Sunday 23 July 2006 16:05, Bill Moran wrote:
> Kern Sibbald <[EMAIL PROTECTED]> wrote:
> > Most likely you upgraded you SQL engine but did not rebuild Bacula
> > against the new client libraries.
>
> I just rebuild bacula from source, so it's now linked against the most
> current PostgreSQL client libraries.
>
> The problem persists. Either the client libraries weren't the problem, or
> the problem has resulted in permanent corruption to the database.
>
> > On Saturday 22 July 2006 16:55, Bill Moran wrote:
> > > Do these errors ring a bell with anyone. I've been having trouble with
> > > this catalog database off and on for a few weeks now, but this is the
> > > first tangible error I've seen. (Until now, the dir has froze up or
> > > exited mysteriously or exhibited other mysterious behavior)
> > >
> > > 22-Jul 00:00 mindwipe-dir: sql_create.c:196 INSERT INTO Pool
> > > (Name,NumVols,MaxVols,UseOnce,UseCatalog,AcceptAnyVolume,AutoPrune,Recy
> > >cle,
> > > VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,MaxVolBytes,PoolType
> > >,Labe lType,LabelFormat) VALUES
> > > ('CFOnDisk',0,0,0,1,1,1,1,604800,82800,0,0,100000000000,'Backup',0,'Dai
> > >ly-' ) 22-Jul 00:00 mindwipe-dir: Fatal Error because: Bacula
> > > interrupted by signal 11: Segmentation violation 22-Jul 00:00
> > > mindwipe-dir:
> > > sql_create.c:196 INSERT INTO Pool
> > > (Name,NumVols,MaxVols,UseOnce,UseCatalog,AcceptAnyVolume,AutoPrune,Recy
> > >cle,
> > > VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,MaxVolBytes,PoolType
> > >,Labe lType,LabelFormat) VALUES
> > > ('CFOnDisk',0,0,0,1,1,1,1,604800,82800,0,0,100000000000,'Backup',0,'Dai
> > >ly-' ) 22-Jul 00:00 mindwipe-dir: Fatal Error because: Bacula
> > > interrupted by signal 11: Segmentation violation 22-Jul 10:42
> > > mindwipe-dir:
> > > *Console*.2006-07-22_10.41.57 Error: sql_get.c:560 More than one Pool!:
> > > 2 22-Jul 10:42 mindwipe-dir: *Console*.2006-07-22_10.41.57 Error:
> > > sql_get.c:560 More than one Pool!: 2 22-Jul 10:42 mindwipe-dir:
> > > *Console*.2006-07-22_10.41.57 Fatal error: Pool CFOnDisk not in
> > > database. sql_create.c:171 pool record CFOnDisk already exists
> > >
> > > The last three repeat over and over.
> > >
> > > I ran dbcheck with the fix option, but the problem persists. Any
> > > suggestions as to what could be wrong?
You will have to get a traceback with debug symbols turned on so that we can
see where Bacula is dying. See the Kaboom chapter of the manual.
If you recently upgraded PostgreSQL and your problems started after that, then
it is very likely related to that upgrade. It looks to me like there is some
sort of SQL error, and then when Bacula tries to print the error message, the
pointer to the error message provided by PostgreSQL is NULL, causing Bacula
to die.
Has PostgreSQL changed the interface to obtaining an English message
corresponding to an error code? We use PQresultErrorMessage().
What version of PostgreSQL were you using, and which one are you using now?
I have verified that Bacula works fine on version 8.1.4.
Regards,
Kern
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
