 |
You seems to want to build with sqlite3 this is no more supported, you can build only with postgresql (see the libbareoscats-postgresql.so ) The delivered binaries allow people to still run bareos 20 with other database to permit them to migrate to PostgreSQL. It is not intended to build with. |
|
|
btw for the cmake flags you can consult the different parts of how is build Bareos packages on debian, freebsd, rpm like by consulting the source code on github.com/bareos/bareos. |
|
|
only PostgreSQL is supported as database. |
|
|
This is version 20.0.7, sqlite was dropped in version 21.0. Also since this is being built under ubuntu (debian) postgress is enabled by the spec file and if you note here that this is NOT running the software but doing a config file test only (-t flag). The issue as mentioned is NOT the database but the fact that the libraries called by the program are NOT installed in the correct directories. -Dlibdir=/opt/bareos/lib openat(AT_FDCWD, "/opt/bareos/lib/tls/x86_64/x86_64/libbareossql.so.20", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) see the '/tls/x86_64/x86_64/" that is a problem with the config/build or install process. As for the location for the cmake/build flags, I am aware of the source code library at github (that's where I'm pulling the code from). I do not see a documented list of the flags there, I've been having to troll through the cmake, debian, etc directories and parse through each to find flags manually as I also cannot find information in the bareos docs either. Can you point to what file actually contains these flags? |
|
|
Hello again, as stated before your build is missing postgresql (mandatory since 20) so you need to add the -Dpostgresql=yes to your cmake. I add a full log of the cmake, build, install and usage of bareos 20 under Ubuntu 20.04 and this work well using your flags + -Dpostgresql=yes If you want to have a list of cmake flags you can get inspired by https://github.com/bareos/bareos/blob/master/core/platforms/packaging/bareos.spec#L924 or parsing the different debian/*rules Hope this will help you to achieve your goal. |
|
|
With 20 -Dpostgresql=yes is mandatory, as PostgreSQL is mandatory |
|
|
Wanting to add a note to this case for the benefit for any future person running into a similar issue. The statement from bruno-at-bareos is incorrect. You can still use & test with sqlite3 in version 20.x (so documentation is correct that sqlite3 is still in version 20). The issue was a cmake compile time flag that you need: -Ddefault_db_backend="sqlite3" As the default is postgresql and if that database is not there or configured correctly the binaries will not continue from the 'default' to any other backend database. This was found in file core/cmake/BareosSetVariableDefaults.cmake |
|
|
Of course you can still run a last time another database, but what will be the future of your installation? So the advise to move as soon as you can to PostgreSQL backend is important, so any future potentially impacted user will keep in this important fact. In almost a year from now 20 will be declared out of maintenance. Can we close this report, or you want to propose a change in documentation, programs? |
|
|
The point is that in my use case sqlite works much better than postgresql and will give us time to figure out another solution to have the database not installed system-wide but localized with the backup program. Anyway, yes the ticket can be closed. The only documentation change that would be really helpful but can open another ticket on that sometime later would be to somehow get a parsed list of all cmake declaration variables and their options/possible values/defaults. Opposed to digging through each file (like a master list of flags). But that's a completely different item. Thanks. |
|
|
You're right on the point that we lack cmake flags documentation, and beside that re-standardization (I've opened a developer task for that internally), but if you want to contribute, please do so by sending a PR ;-) For your database, you can start postgresql also as another user than system installed like bareos user itself and use the initdb binary to located the database wherever you want. so you can compile and have postgresql and bareos running in whatever location you want. |
|
|
All comments have been explained |
- Anonymous
