> On Nov 7, 2017, at 4:21 PM, Ian Douglas wrote:
>
> Hi all
>
> I updated my version of Postgres. Foolishly did it while Bacula was busy with
> a long backup, but that's another story.
>
> I'm on Gentoo Linux and followed their upgrade guide.
>
> Anyway, normal backups run fine. However the nightly catalogue backup fails
> thusly:
>
> 07-Nov 23:10 trooper-dir JobId 13399: shell command: run BeforeJob "/usr/
> libexec/bacula/make_catalog_backup.pl MyCatalog"
> 07-Nov 23:10 trooper-dir JobId 13399: BeforeJob: pg_dump: server version:
> 9.6.4; pg_dump version: 9.5.8
> 07-Nov 23:10 trooper-dir JobId 13399: BeforeJob: pg_dump: aborting because of
> server version mismatch
>
> I have the following:
>
> trooper bacula # ll /usr/bin/pg_dump*
> lrwxrwxrwx 1 root root 35 Oct 1 14:01 /usr/bin/pg_dump93 -> ../lib64/
> postgresql-9.3/bin/pg_dump
> lrwxrwxrwx 1 root root 35 Oct 1 13:54 /usr/bin/pg_dump94 -> ../lib64/
> postgresql-9.4/bin/pg_dump
> lrwxrwxrwx 1 root root 35 Oct 1 13:58 /usr/bin/pg_dump95 -> ../lib64/
> postgresql-9.5/bin/pg_dump
> lrwxrwxrwx 1 root root 35 Oct 1 13:51 /usr/bin/pg_dump96 -> ../lib64/
> postgresql-9.6/bin/pg_dump
>
> So I'm guess that somewhere there is a config file that tells Bacula which
> version to use. I've tried poking around on this machine, and asking Google,
> all to no avail...
>
> Can someone please tell me where or what I must change to tell the catalogue
> backup to use the 9.6 version?
My guess: alter the script Bacula is using to dump, and change it from pg_dump
to pg_dumpXX.
Or perhaps symlink pg_dump to the version you want to use.
--
Dan Langille - BSDCan / PGCon
d...@langille.org
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users