Dear Larry,
In message <0f11700a6a58d852a04b058fabe46...@lerctr.org> you wrote:
> >
> > In message <6f0199d2227115785c7bcb94e3250...@lerctr.org> you wrote:
> >>
> >> > I thought I had succesfully run all DB upgrades during that time,
> >> > but apparently something is missing:
> > ...
> >
> >> Did you run the bacula database upgrade??
> >
> > I was sure I did, but maybe I missed one. Do you have a hint, which
> > one? And, of this was an older one, how to fix it?
...
> there should be a update_bacula_tables script (and it's associated
> DB-Specific SQL files)
> in the share/ directory from the package.
Yes, I know that. And I _think_ I always ran these scripts (usually
because bacula-dir would complain). But what I see is this:
# /usr/libexec/bacula/update_bacula_tables
Altering postgresql tables
This script will update a Bacula PostgreSQL database
from any from version 12-16 or 1014-1021 to version 1022
which is needed to convert from any Bacula Enterprise
version 4.0.x, 6.x.y, 8.x.y, 10.x.y to version 12.4.x
The existing database is version 1022 !!
This script can only update an existing version 12-16, 1014-1021
database to version 1022.
Error. Cannot update this database.
So the database version _is_ correct, and it seems something went
wrong with the update. And it must be a systematic problem, as I
see this in two independent installations.
As far as I can reproduce from old system logs, the problem _might_
have happened during the upgrade from Bacula 9.6.6-1 (FC32) to
Bacula 11.0.2-3 (FC33).
I have kept the log:
# su - postgres -s /bin/bash
$ sh /usr/libexec/bacula/update_bacula_tables
Altering postgresql tables
This script will update a Bacula PostgreSQL database
from any from version 12-16 or 1014-1021 to version 1022
which is needed to convert from any Bacula Enterprise
version 4.0.x, 6.x.y, 8.x.y, 10.x.y to version 12.4.x
Dumping File table to /data/pgsql/file1017.data.
The process may fail if the current user
doesn't have write permission on the current directory,
or if the system doesn't have enough space to store a
compressed export of the File table
BEGIN
DROP TABLE
DROP TABLE
CREATE TABLE
COMMIT
Loading the File table from /data/pgsql/file.748011.data...
COMMIT
Creation of indexes and PK on the File table...
SET
BEGIN
CREATE SEQUENCE
ALTER SEQUENCE
setval
------------
8269427750
(1 row)
ALTER TABLE
ANALYZE
ALTER TABLE
ALTER TABLE
ALTER TABLE
UPDATE 2
COMMIT
Upgrade of the File table succeeded. Version 1017
BEGIN
CREATE TABLE
CREATE INDEX
UPDATE 2
COMMIT
Update of Bacula PostgreSQL tables 1017 to 1018 succeeded.
UPDATE 2
Update of Bacula PostgreSQL tables 1018 to 1019 succeeded.
BEGIN
ALTER TABLE
ALTER TABLE
ALTER TABLE
UPDATE 2
COMMIT
Update of Bacula PostgreSQL tables 1019 to 1020 succeeded.
BEGIN
UPDATE 2
COMMIT
Update of Bacula PostgreSQL tables 1020 to 1021 succeeded.
BEGIN
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE TABLE
CREATE INDEX
CREATE INDEX
CREATE INDEX
CREATE INDEX
CREATE TABLE
CREATE INDEX
UPDATE 2
COMMIT
Update of Bacula PostgreSQL tables 1021 to 1022 succeeded.
As you can see, there were no error messages.
The big question is: what can I do to fix the problem?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
Speculation is always more interesting than facts.
- Terry Pratchett, _Making_Money_
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
