During a test restore I received the following two error message. Can someone
assist in understand these errors beyond the obvious? One point of note, I
upgraded from 9.0.4 to 9.0.5 between backup job and restore job.
07-Nov 11:53 bacula-fd JobId 4177: Error: attribs.c:558 File size of
Oops, my error. I was looking at a file that was created with the
Enterprise Source.
The correct version for the current community version is actually 16
(not 1019, which is the BEE version).
Anyway, I see that your problem is resolved.
Best regards,
Kern
On 11/08/2017 03:44 PM, Kern
Either it is a Bacula bug, or you are not using version 9.0.x
On 11/08/2017 02:40 PM, bernhard.glomm wrote:
UPDATE Version SET VersionId=1019;
why is that so when bacula-director want version 16 instead of 15 as
said in the logfile
"Fatal error: Version error for database "bacula". Wanted
Sorry for the fuzz,
thnx Martin that was "the right answer" ;-)
that script is okay (one only has to set the dbname in the script)
after executing it the director starts as expected.
thnx everybody for the various hints
best
Bernhard
On 2017-11-08 14:17, Martin Simmons wrote:
You could
UPDATE Version SET VersionId=1019;
why is that so when bacula-director want version 16 instead of 15 as
said in the logfile
"Fatal error: Version error for database "bacula". Wanted 16, got 15"
On 2017-11-08 13:44, Kern Sibbald wrote:
Hello,
In source form the script may not be too useful
You could try:
dpkg -S update_mysql_tables
I think it should be here:
/usr/share/bacula-director/update_mysql_tables
__Martin
> On Wed, 08 Nov 2017 11:58:14 +0100, bernhard glomm said:
>
> hi all
> after a regular apt-get update && apt-get upgrade
> on a "trusty" ubuntu system
> the
I use Git for compil from source.
And to have a v9.x.x not in binary (?) ... i under CentOs 7.4 / Postgres
Prod -> bacula v7.4.7
Test -> bacula v9.0.4 ( -> 9.0.5 at 20171102 )
Le 08/11/2017 à 13:23, bernhard.glomm a écrit :
?? you mean the script might be in the source packages but not in the
Hello,
In source form the script may not be too useful because the paths are
different for each packager. I recommend that you look at your binary
files as they should have included the script. You can also do:
find / -name "update_bacula_tables"
if there are multiple copies, you will
?? you mean the script might be in the source packages but not in the
binary packages ??
bizarre but I will have a look
On 2017-11-08 13:03, Olivier Delestre wrote:
For me with bacula 7.4.7
/usr/local/src/bacula/bacula/src/cats/update_bacula_tables et
grant_bacula_privileges ( with user
> hi all
Hello, Bernhard,
> after a regular apt-get update && apt-get upgrade
> on a "trusty" ubuntu system
> the upgrade of package bacula-director FAILED
> with the following errors in bacula_daemon.log:
>
> 08-Nov 10:27 bacula-dir JobId 0: Fatal error: Version error for database
> "bacula".
For me with bacula 7.4.7
/usr/local/src/bacula/bacula/src/cats/update_bacula_tables et
grant_bacula_privileges ( with user postgres )
bacula=# select * from version;
versionid
---
15
And 16 for version 9 (?)
Le 08/11/2017 à 11:58, bernhard.glomm a écrit :
hi all
after a
hi all
after a regular apt-get update && apt-get upgrade
on a "trusty" ubuntu system
the upgrade of package bacula-director FAILED
with the following errors in bacula_daemon.log:
08-Nov 10:27 bacula-dir JobId 0: Fatal error: Version error for database
"bacula". Wanted 16, got 15
08-Nov 10:27
12 matches
Mail list logo
