Comment 5 for bug 1026680

Revision history for this message
Thomas Schweikle (tps) wrote :

I did a few additional tests now. Some results:

1. I've installed bacula on a newly set up system (Ubuntu 12.04 LTS), with an empty database: works as expected.
2. I've installed bacula on a newly set up system (Ubuntu 10.04 LTS), with an empty database: works as expected.
3. I've installed bacula on a newly set up system (Ubuntu 12.04 LTS), then imported an old bacula database:
  exausts message about wrong database. After migrating the database works as expected.
4. I've installed bacula on a newly set up system (Ubuntu 10.04 LTS), then imported an old bacula database:
  works as expected. Then migrated to Ubuntu 10.10, 11.04, 11.10: works as expected. Then migrated to
  Ubuntu 12.04: crashes after accessing the database to start a backup.
5. I've installed bacula on a newly set up system (Ubuntu 10.04 LTS), then imported an old bacula database:
  works as expected. Then migrated to Ubuntu 10.10, 11.04, 11.10: works as expected. Then migrated to
  Ubuntu 12.04. Wiped the database, then imported an old one, then migrated the database as described
  on the bacula pages: works as expected.
6. I've installed bacula on a newly set up Ubuntu 10.04, then imported an old database: works as expected.
  Next thing done was migrating to 10.10, 11.04, 11.10. Testing after every migration. Each time it worked
  as expected. After migrating to 12.04 bacula crashed (what I awaited). Now I tried to migrate the database
  as described on the bacula web site. This time without success: various error messages, then one stating
  the database allready where migrated and nothing changed.

For me it looks a lot like migrating to Ubuntu 12.04, changing bacula from 5.0.x to 5.2.x breaks the
database, forcing bacula to crash. I did not look at what exactly causes bacula to crash only trying to
replicate the path I had taken leading to this crash.