Hello Thomas,
the provided packages are for Debian Bookworm, not for Ubuntu - might
work but I would not recommend this.
Updating the code packages does NOT touch the configuration. The
packages install a snapshot from the current config tree if none is
found, the recommended way for productive setups ALWAYS was to make a
clone from the openxpki-config repo. We spend a lot of work to make new
code working with old configurations while keeping the major version but
a major update always requires manual intervention - the docs on the
minimal steps from 2.x to 3.x are mentioned in the upgrade documentation
found inside the config repo.
Regarding the sequence stuff: This happens as you have very likely
changed the database driver version in system/database.yaml - the old
"mysql" driver used tables to emulated sequnces while the newer MariaDB
driver use native sequences which is also mentioned in the upgrade
documentation.
So if you did not change much in the old config, follow the way given by
Nick and try to adapt your changes onto a fresh checkout - this will
require an up-to-date database schema! If you want to keep your old
configuration, you should be fine with changing the stuff mentioned in
the upgrade document but you will not get any new features. In addition
you might need to build your own translation files as the old workflow
definitions are no longer included in the translation.
More hints on what might need updating can be found in the quickstart
which lists most important changes per version.
The schema version indicator is in fact not mentioned in the docs but is
currently not in use so this is just a warning message which can be
ignored for now. The proper SQL setting to add this can be found in the
recent schema files.
Oliver
On 28.08.23 22:17, Thomas Schachtner via OpenXPKI-users wrote:
Hi there,
I just wanted to tell about my efforts to upgrade OpenXPKI to its
newest version 3.26.
I was using an old Ubuntu build (v2.5.5) on an old Ubuntu box. I
upgraded the OS and also updated the OpenXPKI apt sources file to its
newest releases on each os upgrade.
After the upgrade, OpenXPKI did not run anymore, which was expected,
as I did not yet follow the upgrade instructions. (I found them on GitHub)
But even after doing so, I did not seem to have the newest files
installed. I ended up cloning the config repository and replacing all
the old files in my realm directories.
Is this the the way an update is meant to be done?
If not, or if the newest files are also being downloaded during
"apt-get upgrade", it would be good to know where they are placed.
(Maybe there's a well-known directory in the filesystem hierarchy
standard and I just don't know that, so please bear with me...)
But even after updating all the files, I kept getting crashes. When
looking into the logs, I saw that there are some changes to the
database schema which were not mentioned in the docs (or which I
didn't see).
Btw, I performed all the schema updates form 1.x to 2.x a long time
ago, but there seem to have been added some new columns since that
time which I did not have in my database. After adding the missing
columns one after another, I saw that there's a schema version
informativ in the database which did also not yet exist in my
installation.
(There was a warning message about that, but I did not know where to
specify the database schema version.)
Would it have been better to just set the schema version to some
specific value and to be able to keep using the previous schema? If
so, which value would that be?
I also found that now there are SEQUENCEs in the database where there
have been standard tables before. I updated that as well.
So now my question:
Did I do the update correctly?
Or is there rather a better way to do it?
I have another instance which is used actively by some users as
production system and I would prefer to update that system exactly as
the update is meant to be done.
By the way, thank you very much for this great piece of software you
created and provide to us!
Best regards
Tom
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users
--
Protect your environment - close windows and adopt a penguin!
_______________________________________________
OpenXPKI-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openxpki-users
