In response to Kern Sibbald <[EMAIL PROTECTED]>: > On Friday 04 August 2006 12:30, Bill Moran wrote: > > Skylar Thompson <[EMAIL PROTECTED]> wrote: > > > > > Dan Langille wrote: > > > > On 1 Aug 2006 at 8:49, Skylar Thompson wrote: > > > > > > > > > > > >> I just installed Bacula 1.38 in FreeBSD, using a Postgres backend. > > > >> bacula-dir starts up fine, but when I start up bconsole to go to label > a > > > >> tape I get a segfault. > > > >> > > > > > > > > I'm using FreeBSD 4.11-STABLE, and PosgreSQL 8.1.3, and Bacula 1.38.8 > > > > > > > > What versions are you using? > > > > > > > > > > > FreeBSD 6.1-STABLE, Postgres 8.1.4, and Bacula 1.38.11. > > > > I have that setup running in 4 places without problem. > > > > Have a look at the "Kaboom" chapter in the manual and set your system up > > to capture backtraces when it crashes. In my experience, a backtrace is > > about all Kern needs to track these problems down quickly. > > I haven't been following this thread very closely, but I suspect that the > problem is either the user updated PostgreSQL and did not upgrade the > development libraries, or there are two installations of PostgreSQL on the > same machine in different directories, or the user upgraded PostgreSQL and > did not rebuild Bacula from scratch. In those three cases, Bacula would be > linked against PostgreSQL client libraries that do not correspond to the > PostgreSQL servers and thus crashes would not be surprising.
While I haven't tried every possible combination, I've found that having the exact same version of libpq as is the server you're using is not necessary at all. I know that we have at least a few systems here where the client libraries are 8.0 and the server is 8.1 So, personally, I would find crashes resulting from mismatched client/server versions _very_ surprising. It should never result in a crash. Like most client/server systems, there is a network protocol between the client and server that should insulate you from upgrades (unless you're pushing it, like going from 6 to 8) If it does turn out that Bacula is crashing because of mismatched client/server versions, it is a _bug_ and should be reported to the PostgreSQL development team to be fixed. If however, you meant that the OP may have compiled Bakula, then upgraded the client libraries without re-linking Bacula, I could see that potentially being a problem. -- Bill Moran Collaborative Fusion Inc. ------------------------------------------------------------------------- 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
