CMDBuild Forum

Ready2use upgrade from 2.3-a-3.4.2 to 2.4-4.1.0

Configurations
#1

Dear tecnoteca team, dear community,

I have a ready2use 2.3-a-3.4.2 installation running and I would like to upgrade to the new 2.4-4.1.0 release.
I have upgraded my postgresql database server to 17, I have jdk 17 installed.

I installed a new tomcat 10 and deployed the war file to the tomcat. When I start tomcat the war file gets deployed. I copied all the conf file to tomcat/conf/cmdbuild (<- my instance’s name), i.e. also the database.conf file.

When I then start the tomcat my cmdbuild.log file starts with this:
…
2025-10-01T08:34:53.999+02:00 [sys:boot] INFO o.c.d.config.inner.PatchManagerImpl - patch = core-3.0.0-29_lookup_add_active_flag “lookup add active flag” exist only on db, not found on file2025-10-01T08:34:54.003+02:00 [sys:boot] INFO o.c.d.config.inner.PatchManagerImpl - patch = core-3.3.0-23b_gis_fix “gis fix” exist only on db, not found on file
2025-10-01T08:34:54.007+02:00 [sys:boot] INFO o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.4.0-42_report_params “add report config field with params” (patch applied on db is different from patch file)
2025-10-01T08:34:54.018+02:00 [sys:boot] INFO o.c.d.d.ConfigurableDataSourceImpl - enable sql logger
2025-10-01T08:34:54.056+02:00 [sys:boot] INFO o.cmdbuild.minions.MinionServiceImpl -

    system is CHECKING_DATABASE

2025-10-01T08:34:54.057+02:00 [sys:boot] INFO o.cmdbuild.minions.MinionServiceImpl - check database
2025-10-01T08:34:54.068+02:00 [sys:boot] INFO o.cmdbuild.minions.MinionServiceImpl - check patch
2025-10-01T08:34:54.069+02:00 [sys:boot] INFO o.cmdbuild.minions.MinionServiceImpl -

    system is WAITING_FOR_PATCH_MANAGER

2025-10-01T08:34:54.069+02:00 [sys:boot] INFO o.cmdbuild.minions.MinionServiceImpl - patch manager is not ready, waiting for user input
…

My guess is that my DB schema is not updated to the latest version.

What is the correct way to do this upgrade and get the DB schema upgraded without losing all customisations applied to the schema?

Many thanks in advance

Alex

#2

Hi,
if you access the application through the web interface, it will ask you to apply the patches.

Applying them will not remove your customizations, but the CMDBuild database will be upgraded with the requirements for the new version.

#3

Hi,

thank you very much for you reply. Is that the same patching as I can find in the cmbuild terminal command?

I will give this another try over the next couple of days when I find some time …

Is it safe to upgrade from 2.3-a-3.4.2 directly to 2.4 or do I need to upgrade to the latest 2.3 release and then only to 2.4?

Anyway, I will update this ticket with my results

Thank you very much

Alex

#4

Hi,

I first upgraded my 2.3 installation to the latest core update I found on sourceforge, 2.3-a-3.4.4. When I started this version the patch manager showed up in the browser and I install all patches.
I have already a Java 17 and postgres 17 running.

I downloaded the latest Tomcat 10, deployed the war file into webapps copied the database.conf file to tomcat/conf/cmdbuild/ and started tomcat.

I get to see the new login screen and the message that there is a new version but no patch manager. The log files show the same patch manager message from my original post.

I then run the patch manager manually in the shell:
sudo -u cmdbuild ./cmdbuild.sh dbconfig listpatches
then
sudo -u cmdbuild ./cmdbuild.sh dbconfig patch
then again to check
sudo -u cmdbuild ./cmdbuild.sh dbconfig listpatches

last patch on db is =< core-4.0.0-06_change_patch_constraint >
found 0 available patches:

There are some messages:
2025-10-07T10:05:29.766+02:00 [sys:boot] INFO o.c.d.config.inner.PatchManagerImpl - patch = core-3.0.0-29_lookup_add_active_flag “lookup add active flag” exist only on db, not found on file
2025-10-07T10:05:29.773+02:00 [sys:boot] INFO o.c.d.config.inner.PatchManagerImpl - patch = core-3.3.0-23b_gis_fix “gis fix” exist only on db, not found on file
2025-10-07T10:05:29.781+02:00 [sys:boot] INFO o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.4.0-42_report_params “add report config field with params” (patch applied on db is different from patch file)

When I start tomcat I see this in cmdbuild.log
v2.3-a-4.1.0 READY

    BIM Service                     disabled
    Clustering                      disabled
    DMS Service                 *   ready
    DMS_ Alfresco               E   error
    DMS_ SharePoint Online          disabled
    Email Queue                     disabled
    GIS Service                     disabled
    GIS_ GeoServer client           disabled
    Log Service                 *   ready
    Multitenant                     disabled
    Scheduler Service (core)    *   ready
    Scheduler_ Jobs                 disabled
    Waterway Engine             *   ready
    Waterway_ Events            *   ready
    Waterway_ Jobs                  disabled
    Waterway_ Webhook           *   ready
    Workflow Engine             *   ready

Why is it saying v2.3-a-4.1.0 READY? Shouldn’t it be v2.4-4.1.0?
I can see the login page but the login is not working … not with the standard admin account, not with a regular account.
When I try to login, the login button turns “disabled” and then back to enabled.

No message is being displayed on screen, no entry in the log files …

So is there something I’m still missing? Do I need to upgrade to 2.4-4.0.4 first?

Many thanks in advance

Alex