Hi,Yes, I found the culprit. After the upgrade process I ended up with *two* PostgreSQL server instances (trying to) running over the same dataset: the old and the upgraded one. Removed the old and got it working fine.
Hope this helps. Regards. Em 07/10/2016 12:50, Jeremy Parrish escreveu:
I am in the same boat... apparently never tried doing a restore since upgrading to Ubuntu 16.04. I am guessing there is another config option that is not getting its default value set properly. Did you ever find a solution for this? -Jeremy -- View this message in context: http://bacula.10910.n7.nabble.com/Files-pruned-from-catalog-or-never-inserted-For-one-or-more-of-the-JobIds-selected-no-files-were-fou-tp84088p84656.html Sent from the Bacula - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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
-- *Marcio Merlone* TI - Administrador de redes *A1 Engenharia - Unidade Corporativa* Fone: +55 41 3616-3797 Cel: +55 41 9689-0036 http://www.a1.ind.br/ <http://www.a1.ind.br>
------------------------------------------------------------------------------ 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
