Hi *,

updated my Bareos v17 Installation to v18. Backup is working fine, but the I 
tried to restore a few files for testing and boom Bareos-dir is crashing. 
Tested in bconsole and webui, now difference. I started Bareos-dir in debug and 
got the following message right after try a restore:

backup1-dir (100): cats/sql_query.cc:124-0 called: bool 
BareosDb::SqlQuery(const char*, int) with query DROP TABLE btempb200061928
backup1-dir (50): cats/postgresql.cc:687-0 Result status fatal: DROP TABLE 
btempb200061928
backup1-dir (10): cats/postgresql.cc:692-0 ERROR TERMINATION: Fatal database 
error
backup1-dir: ERROR TERMINATION at cats/postgresql.cc:692
Fatal database error

My Postgres shows an error, too. That's telling me bareos tries to delete a 
table which doesn't exist:

2019-02-21 12:23:22.479 CET [26313] bareos@bareos ERROR:  table 
"btempb200061928" does not exist
2019-02-21 12:23:22.479 CET [26313] bareos@bareos STATEMENT:  DROP TABLE 
btempb200061928   

But that's not a database issue. Postgres is doing the right things.

I can repeat that again and again. Just tested a clean setup with a fresh/empty 
database, same thing here. Really bad --> backup w/o restore not a good 
combination...

When I look a the whole debug text I can not find any CREATE statement creating 
the not existing (and finally resulting in a crash) table.

OS: Ubuntu 16.04.5 LTS 32-Bit x86 
Database: server 10.7 (Ubuntu 10.7-1.pgdg16.04+1)
Bareos Packages:
ii  bareos                                   18.2.5-139.1                       
        i386         Backup Archiving Recovery Open Sourced - metapackage
ii  bareos-bconsole                          18.2.5-139.1                       
        i386         Backup Archiving Recovery Open Sourced - text console
ii  bareos-client                            18.2.5-139.1                       
        i386         Backup Archiving Recovery Open Sourced - client metapackage
ii  bareos-common                            18.2.5-139.1                       
        i386         Backup Archiving Recovery Open Sourced - common files
ii  bareos-database-common                   18.2.5-139.1                       
        i386         Backup Archiving Recovery Open Sourced - common catalog 
files
ii  bareos-database-postgresql               18.2.5-139.1                       
        i386         Backup Archiving Recovery Open Sourced - PostgreSQL backend
ii  bareos-database-tools                    18.2.5-139.1                       
        i386         Backup Archiving Recovery Open Sourced - database tools
ii  bareos-director                          18.2.5-139.1                       
        i386         Backup Archiving Recovery Open Sourced - director daemon
ii  bareos-filedaemon                        18.2.5-139.1                       
        i386         Backup Archiving Recovery Open Sourced - file daemon
ii  bareos-storage                           18.2.5-139.1                       
        i386         Backup Archiving Recovery Open Sourced - storage daemon
ii  bareos-storage-tape                      18.2.5-139.1                       
        i386         Backup Archiving Recovery Open Sourced - storage daemon 
tape support
ii  bareos-tools                             18.2.5-139.1                       
        i386         Backup Archiving Recovery Open Sourced - common tools
rc  bareos-traymonitor                       14.2.1-31.1                        
        i386         Backup Archiving Recovery Open Sourced - tray monitor
ii  bareos-webui                             18.2.5-126.1                       
        all          Backup Archiving Recovery Open Sourced - webui

Can somebody confirm that problem? Is there a common sollution for that issue?


Regards
Björn

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to