Interesting. I remember being confused about which `Maximum Concurrent
Jobs` to use (the `bacula-fd.conf` vs the director's config), but your
explanation makes a lot of sense. I hadn't realized/considered the
implications of having it set too low in the FD's config.
I'll test it and if the p
On 5/20/25 20:59, Eric Bollengier wrote:
Hello Andrea,
Hello.
Maybe you can share the job output where the errors and warnings are
printed, it will help to understand the situation.
Just today I got the log I'm pasting at the end of the message (with
sensitive data redacted).
The original
On 5/20/25 3:20 PM, Lloyd Brown wrote:
Hi all,
I'm running into an issue with some bacula-fd instances and hoping someone can
point me in the right direction.
In short: I have bacula-fd instances that are clearly running jobs (confirmed via strace), but they often time out when I run
status c
Which version of bacula-director-pgsql do you have on the PostgreSQL server?
You need 13.0.4.
This line in your output shows that
/usr/share/bacula-director/update_postgresql_tables is from an older version
(probably 9.x.y):
> This script can only update an existing version 12-15 database to vers
Hi Martin,
I tried to run it from the postgresql database. But I got the following
error:
sudo -u postgres /usr/share/bacula-director/update_postgresql_tables -U
baculadev -d baculadev -h localhost
This script will update a Bacula PostgreSQL database from version 12-15 to
16
Depending on the c
