Error during 'xtee-misp2-postgresql' upgrade 2.6.3 -> 2.6.4

[uvelokk]

Upgrade of the package xtee-misp2-postgresql from 2.6.3 to 2.6.4 ends with an error:

Setting up xtee-misp2-postgresql (2.6.4) ...
You have package shema version  2.6.4
PostgreSQL service is running.
Using DB connection parameters from configuration file /var/lib/tomcat8/webapps/misp2/WEB-INF/classes/config.cfg.
Allowing 'postgres' user locally trusted access.
true
Creating database 'misp2db'
createdb: database creation failed: ERROR:  database "misp2db" already exists
Cannot create database 'misp2db'
You can try to create "misp2db" by yourself: 
/usr/lib/postgresql/10/bin/createdb  -p 5432 misp2db -U postgres -E UNICODE
dpkg: error processing package xtee-misp2-postgresql (--configure):
 installed xtee-misp2-postgresql package post-installation script subprocess returned error exit status 1

OS: Ubuntu 18.04.6 LTS

[raits]

Thank you for reporting this issue, we are looking into it.

[raits]

@uvelokk Unfortunately, we have been unable to replicate your situation. Could you please check that the database information inside the file /var/lib/tomcat8/webapps/misp2/WEB-INF/classes/config.cfg is correct.

Additionally, could you please provide some additional background that could help us diagnose the issue better:

• Was version 2.6.3 a fresh installation or was that also upgraded from a previous version (if so, what was the original fresh installation version if you can remember)
• Did the previous version work without any issues?
• Did you do any other upgrades in addition to misp2 during the same time?
• Have you modified the database settings manually, do you have any other applications on the same database instance?
• Any other information you feel might be relevant to help us track the issue down

[raits]

Migrated the issue to MISP2-s new main repository. Let's continue the discussion here.

[uvelokk]

Eh,
could not repeat that error anymore as well. I'l close the issue for now.

Thank You.

[uvelokk]

Reopened the issue.

The reason of error lies in the script '/usr/xtee/db/install/install-misp2-postgresql.sh'. If the user 'postgresql' access to local databases is changed from 'peer' to 'trust' and the service 'postgresql' is restarted, then the script must wait as long as the service is fully restarted. Otherwise an error will be triggered.

[raits]

Thank you for providing further details and locating the probable issue. I have created a backlog item in our JIRA to resolve this issue: https://nordic-institute.atlassian.net/browse/MISPDEV-83

Unfortunately, I can not offer a timeline for improving the script at this point.