as of v3.2 observing events "hash mismatch for patch" during instalation or upgrade (RHEL7 & Debian 10)

Hello,

as of v3.2, I’m observing events “hash mismatch for patch” during the instalation of v3.2 or upgrade to v3.2.1 process.

RHEL/CentOS7.7 + 7.8 & Debian 10 affected likewise.
Prerequsities are basically the same as discussed in V3.2.1 shell installer failing "unknown protocol: classpath"

Using the shell installer for v3.2 procudes following detailed events:
empty dump loading:

loading war ... done
loading jars .............................................................................................................. done

CMDBuild interactive install wizard - welcome!

this wizard will guide you in the process of installing and configuring a new instance of CMDBuild!


tomcat install location </root/cmdbuild_30> : /root/cmdbuild_30

tomcat http port <8080>:
tomcat shutdown port (offset already applied) <8005>:
tomcat debug port (offset already applied) <8000>:

postrgres db <localhost:5432> :
postrgres admin account <postgres/postgres> :
WARNING: server version 10.0.12 is not supported, you may encounter problems
cmdbuild posrgres database name <cmdbuild_9121> : my_cmdbuild_empty
database dump to load <demo> : empty

we're ready to begin, this is your configuration:

         tomcat: /root/cmdbuild_30
         http port: 8080
         shutdown port: 8005
         debug port: 8000
         postgres database: localhost:5432/cmdbuild
         database dump: empty.dump.xz

if everything is ok, press ENTER to begin installation
<press enter to begin>
BEGIN installation
install tomcat...
OK
create database...
create database cmdbuild empty.dump.xz
apply patches
14:47:16.872 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.2.0-54_dashboard_upgrade "upgrade dashboard format" (patch applied on db is different from patch file)
14:47:16.882 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.2.0-18_script_job_name_change "change script job name, job name constraint" (patch applied on db is different from patch file)
adjust configs
done
OK


cmdbuild successfully installed! you can find startup/shutdown scripts in dir /root/cmdbuild_30/bin

demo dump loading:

loading jars .............................................................................................................. done

CMDBuild interactive install wizard - welcome!

this wizard will guide you in the process of installing and configuring a new instance of CMDBuild!


tomcat install location </root/cmdbuild_30> : /root/cmdbuild_30

tomcat http port <8080>:
tomcat shutdown port (offset already applied) <8005>:
tomcat debug port (offset already applied) <8000>:

postrgres db <localhost:5432> :
postrgres admin account <postgres/postgres> :
WARNING: server version 10.0.12 is not supported, you may encounter problems
cmdbuild posrgres database name <cmdbuild_4f17> : my_cmdbuild_demo
database dump to load <demo> : demo

we're ready to begin, this is your configuration:

         tomcat: /root/cmdbuild_30
         http port: 8080
         shutdown port: 8005
         debug port: 8000
         postgres database: localhost:5432/cmdbuild
         database dump: demo.dump.xz

if everything is ok, press ENTER to begin installation
<press enter to begin>
BEGIN installation
install tomcat...
OK
create database...
create database cmdbuild demo.dump.xz
apply patches
15:08:46.945 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.2.0-54_dashboard_upgrade "upgrade dashboard format" (patch applied on db is different from patch file)
15:08:46.955 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-03a_system_functions "mixed system access function" (patch applied on db is different from patch file)
15:08:46.955 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-03b_entity_metadata_upgrade_1 "entity metadata upgrade 1" (patch applied on db is different from patch file)
15:08:46.956 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-09b_multitenant "multitenant" (patch applied on db is different from patch file)
15:08:46.957 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-19b_gis_2 "postgis fix 2" (patch applied on db is different from patch file)
15:08:46.957 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-14_attribute_groups "attribute groups refactoring" (patch applied on db is different from patch file)
15:08:46.958 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-17_lookups "refactoring of lookup table" (patch applied on db is different from patch file)
15:08:46.958 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-19a_gis_1 "upgrade gis tables 1" (patch applied on db is different from patch file)
15:08:46.959 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-22_workflow "upgrade workflow" (patch applied on db is different from patch file)
15:08:46.959 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-24_workflow_fix "fix invalid workflow data, add check" (patch applied on db is different from patch file)
15:08:46.959 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-25_menu_view_fix "fix view format in menu" (patch applied on db is different from patch file)
15:08:46.960 WARN  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
15:08:46.961 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-46_gis_fix "gis fix" (patch applied on db is different from patch file)
15:08:46.963 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.1.0-09_session_expiration_strategies "add fields to support multiple session expiration strategies" (patch applied on db is different from patchfile)
15:08:46.966 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.2.0-18_script_job_name_change "change script job name, job name constraint" (patch applied on db is different from patch file)
adjust configs
done
OK


cmdbuild successfully installed! you can find startup/shutdown scripts in dir /root/cmdbuild_30/bin

ready2use_demo dump loading:

loading jars .............................................................................................................. done

CMDBuild interactive install wizard - welcome!

this wizard will guide you in the process of installing and configuring a new instance of CMDBuild!


tomcat install location </root/cmdbuild_30> : 

tomcat http port <8080>: 
tomcat shutdown port (offset already applied) <8005>: 
tomcat debug port (offset already applied) <8000>: 

postrgres db <localhost:5432> : 
postrgres admin account <postgres/postgres> : 
WARNING: server version 10.0.12 is not supported, you may encounter problems
cmdbuild posrgres database name <cmdbuild_9644> : my_cmdbuild_ready2use_demo
database dump to load <demo> : ready2use_demo

we're ready to begin, this is your configuration: 

         tomcat: /root/cmdbuild_30
         http port: 8080
         shutdown port: 8005
         debug port: 8000
         postgres database: localhost:5432/my_cmdbuild_ready2use_demo
         database dump: ready2use_demo

if everything is ok, press ENTER to begin installation
<press enter to begin>
BEGIN installation
install tomcat... 
OK
create database... 
create database my_cmdbuild_ready2use_demo ready2use_demo
apply patches
15:11:44.588 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.2.0-54_dashboard_upgrade "upgrade dashboard format" (patch applied on db is different from patch file)
15:11:44.598 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-03a_system_functions "mixed system access function" (patch applied on db is different from patch file)
15:11:44.599 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-03b_entity_metadata_upgrade_1 "entity metadata upgrade 1" (patch applied on db is different from patch file)
15:11:44.599 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-25_menu_view_fix "fix view format in menu" (patch applied on db is different from patch file)
15:11:44.600 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-07f_index_and_constraint_upgrade "index and constraint upgrade" (patch applied on db is different from patch file)
15:11:44.600 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-09b_multitenant "multitenant" (patch applied on db is different from patch file)
15:11:44.600 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-14_attribute_groups "attribute groups refactoring" (patch applied on db is different from patch file)
15:11:44.601 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-15_grant "refactoring of grant table" (patch applied on db is different from patch file)
15:11:44.601 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-17_lookups "refactoring of lookup table" (patch applied on db is different from patch file)
15:11:44.602 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-19a_gis_1 "upgrade gis tables 1" (patch applied on db is different from patch file)
15:11:44.602 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-19b_gis_2 "postgis fix 2" (patch applied on db is different from patch file)
15:11:44.603 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-22_workflow "upgrade workflow" (patch applied on db is different from patch file)
15:11:44.603 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-24_workflow_fix "fix invalid workflow data, add check" (patch applied on db is different from patch file)
15:11:44.603 WARN  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
15:11:44.604 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-46_gis_fix "gis fix" (patch applied on db is different from patch file)
15:11:44.604 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.1.0-09_session_expiration_strategies "add fields to support multiple session expiration strategies" (patch applied on db is different from patch file)
15:11:44.605 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.2.0-04_menu_validation_trigger "menu validation trigger" (patch applied on db is different from patch file)
15:11:44.606 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.2.0-18_script_job_name_change "change script job name, job name constraint" (patch applied on db is different from patch file)
adjust configs
done
OK


cmdbuild successfully installed! you can find startup/shutdown scripts in dir /root/cmdbuild_30/bin

ready2use_empty dump loading:

CMDBuild interactive install wizard - welcome!

this wizard will guide you in the process of installing and configuring a new instance of CMDBuild!


tomcat install location </root/cmdbuild_30_2> : 

tomcat http port <8080>: 
tomcat shutdown port (offset already applied) <8005>: 
tomcat debug port (offset already applied) <8000>: 

postrgres db <localhost:5432> : 
postrgres admin account <postgres/postgres> : 
WARNING: server version 10.0.12 is not supported, you may encounter problems
cmdbuild posrgres database name <cmdbuild_12e1> : ready2use_empty
database dump to load <demo> : ready2use_empty

we're ready to begin, this is your configuration: 

         tomcat: /root/cmdbuild_30_2
         http port: 8080
         shutdown port: 8005
         debug port: 8000
         postgres database: localhost:5432/ready2use_empty
         database dump: ready2use_empty

if everything is ok, press ENTER to begin installation
<press enter to begin>
BEGIN installation
install tomcat... 
OK
create database... 
create database ready2use_empty ready2use_empty
apply patches
15:14:26.234 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.2.0-54_dashboard_upgrade "upgrade dashboard format" (patch applied on db is different from patch file)
15:14:26.242 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-03a_system_functions "mixed system access function" (patch applied on db is different from patch file)
15:14:26.242 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-03b_entity_metadata_upgrade_1 "entity metadata upgrade 1" (patch applied on db is different from patch file)
15:14:26.243 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-09b_multitenant "multitenant" (patch applied on db is different from patch file)
15:14:26.243 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-19b_gis_2 "postgis fix 2" (patch applied on db is different from patch file)
15:14:26.244 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-22_workflow "upgrade workflow" (patch applied on db is different from patch file)
15:14:26.244 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-14_attribute_groups "attribute groups refactoring" (patch applied on db is different from patch file)
15:14:26.244 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-17_lookups "refactoring of lookup table" (patch applied on db is different from patch file)
15:14:26.245 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-19a_gis_1 "upgrade gis tables 1" (patch applied on db is different from patch file)
15:14:26.245 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-24_workflow_fix "fix invalid workflow data, add check" (patch applied on db is different from patch file)
15:14:26.245 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-25_menu_view_fix "fix view format in menu" (patch applied on db is different from patch file)
15:14:26.245 WARN  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
15:14:26.246 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.0.0-46_gis_fix "gis fix" (patch applied on db is different from patch file)
15:14:26.246 WARN  o.c.d.config.inner.PatchManagerImpl - hash mismatch for patch = core-3.1.0-09_session_expiration_strategies "add fields to support multiple session expiration strategies" (patch applied on db is different from patch file)
adjust configs
done
OK


cmdbuild successfully installed! you can find startup/shutdown scripts in dir /root/cmdbuild_30_2/bin

Btw., when you were checking & fixing the V3.2.1 shell installer failing "unknown protocol: classpath" , haven’t you noticed anything similar “hash mismatch for patch” as I’m reporting in here?
You could easily simulate this again, e.g. on RHEL7.7/7.8:

yum -y install https://download.postgresql.org/pub/repos/yum/reporpms/EL-8-x86_64/pgdg-redhat-repo-latest.noarch.rpm;
yum -y update;
yum -y install postgresql10-server postgresql10-contrib postgresql10-libs postgresql10 unzip;

/usr/pgsql-10/bin/postgresql-10-setup initdb
sed '/^host.*\//s/ident/md5/g' -i /var/lib/pgsql/10/data/pg_hba.conf
systemctl enable postgresql-10.service
systemctl start postgresql-10.service
sudo su - postgres -c "psql template1 -c \"ALTER USER postgres WITH PASSWORD 'postgres';\""
systemctl restart postgresql-10.service

sh cmdbuild-3.2.sh install

The war package to upgrade from v3.2 to v3.2.1, is reporting the same events in the Tomcat log.

I’ve searched for it a little, and have found something at your forum, something mentioning possible issue with driver postgresql-42.2.5.jar.
So I tried:

  • to replace your default package provided file with a newer one from https://download.postgresql.org/pub/repos/
  • i tried downgrading the PostgreSQL to the 10.7, which is the lowest available in the RHEL repository, APT for Debian don’t have that low version, unfortunatelly

However, nothing of it helped to get rid of those events.

Could you please take a statement about it, like if there is any imminent danger once upgraded to v3.2+ or so?
Thank you in advance.