itmicus/cmdbuild_docker

CMDBuild 3.4 with READY2USE 2.3 and openMAINT 2.3 in Docker

cmdbuild_docker's Issues

ERROR: manifest for itmicus/cmdbuild:app-3.2 not found

Hi ,
same error for docker run and docker-compose
thank

Is there any security vulnerable in this docker setup? I got attack kdevtmpfsi

Hi, so I'm trying this image, and yesterday I setup an fresh instance just for this app, and not long after that, I found my server cpu so high.

I found out that I got attack by this script called kdevtmpfsi. I searched it that it's a cryptocurrency miner script that’s utilizing your CPU.

And I deleted the first instance and setup another one, and it's happening again now.

So, how this could happen?

Any help would be appreciated 🙏

BIMserver

Could be posible to have a docker-compose.yml with instructions to install openmaint with bimserver¿

How to install CMDBuilt via DockerDesktop

Hi,
I install CMDBuild READY2USE on my Desktop Docker on Windows 10.
First, I try to find the package name on Hub and install "ready2use-2.3-3.4.1-d" and then "openmaint-2.3-3.4.1-d"
But after I run, these containers show the error below:
2023-08-18 16:32:58 Postgres is unavailable - sleeping
2023-08-18 16:30:09 Edit /usr/local/tomcat/conf/cmdbuild/database.conf

Could you please guide me to fix it? I am a newbie to Docker.
Thank you very much!
LocDP

Manifest for itmicus/cmdbuild:r2u-2.0-3.2 not found: manifest unknown: manifest unknown.

Hello,

I get this error

Creating network "ready2use-20-32_default" with the default driver
Creating volume "ready2use-20-32_cmdbuild-db" with default driver
Creating volume "ready2use-20-32_cmdbuild-tomcat" with default driver
Pulling cmdbuild_app (itmicus/cmdbuild:r2u-2.0-3.2)...
manifest for itmicus/cmdbuild:r2u-2.0-3.2 not found: manifest unknown: manifest unknown

When trying to deploy using these commands:

docker run --name cmdbuild_db -p 5432:5432 -d itmicus/cmdbuild:db-3.0 docker run --name cmdbuild_app --restart unless-stopped --link cmdbuild_db -p 8090:8080 -d itmicus/cmdbuild:app-3.2

Or trying to deploy via docker-compose by doing:

~/git/cmdbuild_docker/ready2use-2.0-3.2 (master) $ docker-compose.exe up -d

Can you please help me solve this?
André

Incorrect usage of shorthand flag '-d' in the command "docker compose -d -f openmaint-2.3-3.4.1-d/docker-compose.yml up"

The README.md file and the Github page of the project suggest using the command "docker compose -d -f openmaint-2.3-3.4.1-d/docker-compose.yml up" to start the project. However, when running the command, the output shows an error message "unknown shorthand flag: 'd' in -d".

Expected behavior: The command should start the project without any errors.

Actual behavior: The command fails to start the project due to incorrect usage of the shorthand flag.

Steps to reproduce:

Clone the repository from Github.
Navigate to the project directory.
Run the command "docker compose -d -f openmaint-2.3-3.4.1-d/docker-compose.yml up".
The output shows an error message "unknown shorthand flag: 'd' in -d".

Proposed solution: The correct usage of the shorthand flag is "-d" instead of "-d". The correct command is "docker-compose -f openmaint-2.3-3.4.1-d/docker-compose.yml up -dl".

Impact: The incorrect usage of the shorthand flag in the command can cause confusion for new users trying to start the project. It can also lead to wasted time and effort trying to troubleshoot the issue.

Recommendation: Update the README.md file and the Github page of the project with the correct command to start the project.

Cmdbuild ready2use-2.0-3.3 sql issue

org.cmdbuild.dao.DaoException: error processing patch = Patch{version=1.0.3-01, category=core, applied=false}, caused by: org.cmdbuild.dao.DaoException: error processing patch =< core-1.0.3-01 (Change Role class type from reserved to sysread) >, caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [ SET SESSION cmdbuild.ignore_tenant_policies = 'true'; SET SESSION cmdbuild.user_tenants = '{}'; DO $$ BEGIN RAISE NOTICE 'apply cmdbuild patch %', 'core-1.0.3-01'; END $$ LANGUAGE PLPGSQL; -- Change Role class type from reserved to sysread COMMENT ON TABLE "Role" IS 'MODE: sysread|TYPE: class|DESCR: Roles|SUPERCLASS: false|MANAGER: class|STATUS: active'; DO $$ BEGIN RAISE NOTICE 'applied cmdbuild patch %', 'core-1.0.3-01'; END $$ LANGUAGE PLPGSQL; ]; nested exception is org.postgresql.util.PSQLException: ERROR: relation "Role" does not exist, caused by: org.postgresql.util.PSQLException: ERROR: relation "Role" does not exist

om-2.0-3.3 not found

Pulling openmaint_app (itmicus/cmdbuild:om-2.0-3.3)...
ERROR: manifest for itmicus/cmdbuild:om-2.0-3.3 not found: manifest unknown: manifest unknown

cmdbuid ready2use shutdown a few seconds after started up

Hello team,

We recently were deploying cmdbuild (cmdbuild:r2u-2.3-3.4.1-d) into our kubernetes cluster, all the deployment steps are followed, but the tomcat application just stopped a few seconds after it started up. The port is not occupied, it running inside pod, the postgres database should be fine as we tested both with our PGS and the one from docker-compose.

Here is the detailed log:

19-Apr-2024 07:09:51.481 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded Apache Tomcat Native library [1.2.35] using APR version [1.7.0].
19-Apr-2024 07:09:51.482 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true], UDS [true].
19-Apr-2024 07:09:51.482 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]
19-Apr-2024 07:09:51.484 INFO [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 3.0.2 15 Mar 2022]
19-Apr-2024 07:09:51.972 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
19-Apr-2024 07:09:51.986 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [814] milliseconds
19-Apr-2024 07:09:52.071 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
19-Apr-2024 07:09:52.071 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.71]
19-Apr-2024 07:09:52.085 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/usr/local/tomcat/webapps/cmdbuild.war]
19-Apr-2024 07:10:10.374 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [/usr/local/tomcat/webapps/cmdbuild.war] has finished in [18,287] ms
19-Apr-2024 07:10:10.374 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [/usr/local/tomcat/webapps/manager]
19-Apr-2024 07:10:10.387 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [/usr/local/tomcat/webapps/manager] has finished in [12] ms
19-Apr-2024 07:10:10.388 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
19-Apr-2024 07:10:10.395 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [18409] milliseconds
19-Apr-2024 07:10:14.557 INFO [main] org.apache.catalina.core.StandardServer.await A valid shutdown command was received via the shutdown port. Stopping the Server instance.
19-Apr-2024 07:10:14.557 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-8080"]
19-Apr-2024 07:10:14.560 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service [Catalina]
19-Apr-2024 07:10:14.659 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [cmdbuild] appears to have started a thread named [pool-2-thread-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[email protected]/java.util.concurrent.locks.LockSupport.park(LockSupport.java:341)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(AbstractQueuedSynchronizer.java:506)
[email protected]/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3463)
[email protected]/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3434)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1623)
[email protected]/java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:435)
[email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062)
[email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
[email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[email protected]/java.lang.Thread.run(Thread.java:833)
19-Apr-2024 07:10:14.660 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [cmdbuild] appears to have started a thread named [pool-2-thread-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[email protected]/java.util.concurrent.locks.LockSupport.park(LockSupport.java:341)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(AbstractQueuedSynchronizer.java:506)
[email protected]/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3463)
[email protected]/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3434)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1623)
[email protected]/java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:435)
[email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062)
[email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
[email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[email protected]/java.lang.Thread.run(Thread.java:833)
19-Apr-2024 07:10:14.660 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [cmdbuild] appears to have started a thread named [pool-2-thread-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[email protected]/java.util.concurrent.locks.LockSupport.park(LockSupport.java:341)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(AbstractQueuedSynchronizer.java:506)
[email protected]/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3463)
[email protected]/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3434)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1623)
[email protected]/java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:435)
[email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062)
[email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
[email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[email protected]/java.lang.Thread.run(Thread.java:833)
19-Apr-2024 07:10:14.660 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [cmdbuild] appears to have started a thread named [pool-2-thread-4] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[email protected]/java.util.concurrent.locks.LockSupport.park(LockSupport.java:341)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(AbstractQueuedSynchronizer.java:506)
[email protected]/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3463)
[email protected]/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3434)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1623)
[email protected]/java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:435)
[email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062)
[email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
[email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[email protected]/java.lang.Thread.run(Thread.java:833)
19-Apr-2024 07:10:14.661 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [cmdbuild] appears to have started a thread named [pool-2-thread-5] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[email protected]/java.util.concurrent.locks.LockSupport.park(LockSupport.java:341)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(AbstractQueuedSynchronizer.java:506)
[email protected]/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3463)
[email protected]/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3434)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1623)
[email protected]/java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:435)
[email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062)
[email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
[email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[email protected]/java.lang.Thread.run(Thread.java:833)
19-Apr-2024 07:10:14.661 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [cmdbuild] appears to have started a thread named [pool-2-thread-6] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
[email protected]/jdk.internal.misc.Unsafe.park(Native Method)
[email protected]/java.util.concurrent.locks.LockSupport.park(LockSupport.java:341)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(AbstractQueuedSynchronizer.java:506)
[email protected]/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3463)
[email protected]/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3434)
[email protected]/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1623)
[email protected]/java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:435)
[email protected]/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1062)
[email protected]/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1122)
[email protected]/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[email protected]/java.lang.Thread.run(Thread.java:833)
19-Apr-2024 07:10:14.663 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-8080"]
19-Apr-2024 07:10:14.673 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-8080"]

Could someone help on this issue, thanks.

Ready2Use Email Account Creation: Password error exceed maximum attr len of 100

docker image version: itmicus/cmdbuild:r2u-2.0-3.2.1

I'm trying to create the email account, however the password field shows exceed maximum attr len of 100 despite my password characters not exceeding the 100 length. Can I get help on this?

Error in starting container

Hi,

I've cloned project
git clone https://github.com/itmicus/cmdbuild_docker
and the I've started containers
docker-compose up -d

I've this error

cmdbuild_db | 2019-07-11 13:49:49.019 UTC [146] FATAL: no pg_hba.conf entry for host "172.18.0.3", user "cmdbuild", database "cmdbuild_30", SSL off

It seems related to postgres container.
There's something that must be configured?
thanks

itmicus / cmdbuild_docker behind a Proxy

Is there a way, to get itmicus / cmdbuild_docker work behind a proxy (e.g. traefik, Sophos UTM, ...) ?

There ist no way to log in: The Web-Browser detects "Mixed Contend" and rejects a connection.

shark cmdbuild

Sir, Thanks.
I have successfully installed r2u-2.0-3.2
I'd like to ask you, this image, not included shark-cmdbuild.
If I want to use workflow, I need to install it by myself?
Hope to wait for your reply

TODO: Update cmdbuild:db-3.0 from postgres:10.7 to postgres:10.23-bullseye

Update cmdbuild:db-3.0 from postgres:10.7 to postgres:10.23-bullseye

• Could and should be updated to 10.23-bullseye
• Target Dockerfile is File

When completed I can push the image to the dockerhubafcarvalho1991/cmdbuild:db-3.0 and update all the docker-compose files that are currently using the image itmicus/cmdbuild:db-3.0

error with CMDBUILD_DUMP=openmaint_demo.dump.xz

I modified my docker-compose.yml and change to CMDBUILD_DUMP=openmaint_demo.dump.xz

running docker-compose up -d

and going to http://localhost:8090/cmdbuild

Closing the small window and clicking apply patches I get the following

With the following error message
org.cmdbuild.dao.DaoException: error processing patch = Patch{version=1.0.3-01, category=core, applied=false}, caused by: org.cmdbuild.dao.DaoException: error processing patch = core-1.0.3-01 (Change Role class type from reserved to sysread), caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [ SET SESSION cmdbuild.ignore_tenant_policies = 'true'; SET SESSION cmdbuild.user_tenants = '{}'; DO $$ BEGIN RAISE NOTICE 'apply cmdbuild patch %', 'core-1.0.3-01'; END $$ LANGUAGE PLPGSQL; -- Change Role class type from reserved to sysread COMMENT ON TABLE "Role" IS 'MODE: sysread|TYPE: class|DESCR: Roles|SUPERCLASS: false|MANAGER: class|STATUS: active'; DO $$ BEGIN RAISE NOTICE 'applied cmdbuild patch %', 'core-1.0.3-01'; END $$ LANGUAGE PLPGSQL; ]; nested exception is org.postgresql.util.PSQLException: ERROR: relation "Role" does not exist, caused by: org.postgresql.util.PSQLException: ERROR: relation "Role" does not exist

Dumping the demo data results in error

Hi,
I am trying to use openmaint and successfully executed the docker-compose file located in openmaint-2.0-3.2.1 directory.
The demo data is launched successfully, but when i try to drop the demo data using the command given below and change the CMDBUILD_DUMP=my_db and relaunch the container as guided here (https://github.com/itmicus/cmdbuild_docker#how-drop-cmdbuild-database)

After relaunching the container, i get a screen with lot of patches on it and when i press the patch button, it simply gives a generic error and get stuck on that screen like this

Any help regarding how to link a new db after dumping the demo would be highly appreciated.

ERROR: unauthorized: authentication required

(python3) [root@centos-7 ready2use-2.0-3.2]# docker-compose up -d
Creating network "ready2use-20-32_default" with the default driver
Creating volume "ready2use-20-32_cmdbuild-db" with default driver
Creating volume "ready2use-20-32_cmdbuild-tomcat" with default driver
Pulling cmdbuild_app (itmicus/cmdbuild:r2u-2.0-3.2)...
Trying to pull repository docker.io/itmicus/cmdbuild ...
r2u-2.0-3.2: Pulling from docker.io/itmicus/cmdbuild
dc65f448a2e2: Pull complete
346ffb2b67d7: Pull complete
dea4ecac934f: Pull complete
8ac92ddf84b3: Downloading [=========================================> ] 42.53 MB/51.79 MB
d8ef64070a18: Download complete
2a5539a27f97: Download complete
9732d0b27efa: Downloading [========> ] 33.8 MB/196.1 MB
9203e26c4e49: Downloading
fb8b237ece22: Waiting
b305916d228c: Waiting
dfb315679f9f: Waiting
635c1995a7ef: Waiting
44e5f486e676: Waiting
6bda4d75326d: Waiting
59735935f22e: Waiting
0b996e08a085: Waiting
b7aaf7680305: Waiting
06d30f7d0968: Waiting
ERROR: unauthorized: authentication required

DataBase issue "Could not create any assest or building"

Hi all i installed openmaint with last update version 2.3-3.4.1-d and deployed by docker compose but i cannot create or save anything this some of error:

2023-07-16 11:07:53.790 UTC [114] DETAIL: Failing row contains (401639, "Building", 100, null, null, null, 2023-07-16 11:07:53.790409+00, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, null, 100, null, null, null, null, null, null, null, null, null, null).
openmaint_db | 2023-07-16 11:07:53.790 UTC [114] STATEMENT: INSERT INTO "Building" ("Code", "Description", "Name", "MainUse", "State", "Complex", "Address", "ZIP", "City", "Coordinates", "Condition", "Criticality", "TotalFloors", "TotalUnits", "TotalRooms", "GlazedArea", "CleanableArea", "CoveredArea", "TotalNetArea", "TotalGrossArea", "TotalHeatedVolume", "TotalVolume", "ServiceStatus", "CalendarEntity", "IdTenant") VALUES ('100', NULL, '100', NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL) RETURNING "Id"
openmaint_db | 2023-07-16 11:10:38.745 UTC [112] ERROR: null value in column "CurrentId" violates not-null constraint
openmaint_db | 2023-07-16 11:10:38.745 UTC [112] DETAIL: Failing row contains (401769, "Component", 10, null, null, null, 2023-07-16 11:10:38.745204+00, null, null, null, null, 379526, 280414, null, null, null, null, null, null, null, 382605, 60, 10, null, null, null, null, null, null, null, null, null, null, null, null, 339754, 340991, 342051, null, null, null, 372279, null, null, null, null, null, null, 382210).
openmaint_db | 2023-07-16 11:10:38.745 UTC [112] STATEMENT: INSERT INTO "Component" ("Code", "Name", "Description", "SerialNumber", "CISubset", "Type", "Brand", "Number", "Condition", "Criticality", "LastCheckDate", "Complex", "Building", "Floor", "Unit", "Room", "State", "PurchasePrice", "DisposalDate", "Life", "AmortizationStart", "AmortizationEnd", "AnnualAmortization", "FullyDepreciated", "WarrantyStart", "WarrantyEnd", "InstallationDate", "AcceptanceDate", "Weight", "ModelData", "Supplier", "Invoice", "NoiseLevel", "SystemPlant", "CI", "Dimensions", "ServiceStatus", "CalendarEntity", "IdTenant") VALUES ('10', '10', NULL, NULL, 379526, 339754, 372279, NULL, 280414, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 60, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, 382605, NULL, NULL, NULL, 382210, NULL, 340991, 342051, NULL) RETURNING "Id"

Hope resolve soon

dump file not found for name = openmaint_empty_gis.dump.xz

org.cmdbuild.dao.DaoException: org.cmdbuild.dao.DaoException: dump file not found for name = openmaint_empty_gis.dump.xz

I have this error when trying to set CMDBUILD_DUMP=openmaint_empty_gis.dump.xz

The cmdbuild_3 database is empty after docker-compose up finishes.

Any suggestion?
Thanks.

How to restart docker container after a reboot?

Hello,

The title is self explanatory... :)
How do I restart the docker container after rebooting the computer?

\git\cmdbuild-openmaint-docker\ready2use-2.0-3.1.1> docker container ls
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

\git\cmdbuild-openmaint-docker\ready2use-2.0-3.1.1> docker image ls
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE
itmicus/cmdbuild    r2u-2.0-3.1.1       39274a8d6907        2 weeks ago         1.37GB
itmicus/cmdbuild    db-3.0              b1b6df7ca09e        4 months ago        625MB

Best regards,
André.

problems with POSTGRES_PASSWORD in docker-compose

Hi,

For version 3.4, if you init docker-compose normaly, you can see in the logs of cmdbuild_db the next error:

fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting dynamic shared memory implementation ... posix
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    pg_ctl -D /var/lib/postgresql/data -l logfile start

****************************************************
WARNING: No password has been set for the database.
         This will allow anyone with access to the
         Postgres port to access your database. In
         Docker's default configuration, this is
         effectively any other container on the same
         system.

         Use "-e POSTGRES_PASSWORD=password" to set
         it in "docker run".
****************************************************
waiting for server to start....2023-10-31 12:35:15.684 UTC [44] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-10-31 12:35:15.715 UTC [45] LOG:  database system was shut down at 2023-10-31 12:35:15 UTC
2023-10-31 12:35:15.722 UTC [44] LOG:  database system is ready to accept connections
 done
server started

/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*

2023-10-31 12:35:15.763 UTC [44] LOG:  received fast shutdown request
waiting for server to shut down....2023-10-31 12:35:15.767 UTC [44] LOG:  aborting any active transactions
2023-10-31 12:35:15.770 UTC [44] LOG:  worker process: logical replication launcher (PID 51) exited with exit code 1
2023-10-31 12:35:15.777 UTC [46] LOG:  shutting down
2023-10-31 12:35:15.801 UTC [44] LOG:  database system is shut down
 done
server stopped

PostgreSQL init process complete; ready for start up.

2023-10-31 12:35:15.879 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-10-31 12:35:15.879 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-10-31 12:35:15.886 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-10-31 12:35:15.911 UTC [53] LOG:  database system was shut down at 2023-10-31 12:35:15 UTC
2023-10-31 12:35:15.919 UTC [1] LOG:  database system is ready to accept connections
2023-10-31 12:35:16.956 UTC [60] LOG:  incomplete startup packet
2023-10-31 12:35:19.036 UTC [61] FATAL:  role "cmdbuild" does not exist
2023-10-31 12:36:27.918 UTC [1471] LOG:  incomplete startup packet

To solved it, i need to add the POSTGRES_PASSWORD in docker-compose.yml for the cmdbuild_db

    cmdbuild_db:
        image: itmicus/cmdbuild:db-3.0
        container_name: cmdbuild_db
        volumes:
            - cmdbuild-db:/var/lib/postgresql
        ports:
            - 5432:5432
        environment:
            - POSTGRES_USER=postgres
            - POSTGRES_PASS=postgres
            - POSTGRES_PASSWORD=postgres
        restart: always
        networks:
            cmdbuildnet:

if i do that, all init OK.

root@ip-172-31-19-114:/home/ubuntu# docker logs cmdbuild_db
2023-10-31 12:38:02.129 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-10-31 12:38:02.129 UTC [1] LOG:  listening on IPv6 address "::", port 5432
2023-10-31 12:38:02.136 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2023-10-31 12:38:02.164 UTC [24] LOG:  database system was interrupted; last known up at 2023-10-31 12:35:19 UTC
2023-10-31 12:38:02.231 UTC [24] LOG:  database system was not properly shut down; automatic recovery in progress
2023-10-31 12:38:02.236 UTC [24] LOG:  redo starts at 0/16341E8
2023-10-31 12:38:02.739 UTC [24] LOG:  invalid record length at 0/275F748: wanted 24, got 0
2023-10-31 12:38:02.739 UTC [24] LOG:  redo done at 0/275F720
2023-10-31 12:38:02.739 UTC [24] LOG:  last completed transaction was at log time 2023-10-31 12:37:50.018698+00
2023-10-31 12:38:03.077 UTC [1] LOG:  database system is ready to accept connections

Can you fix or i am doing something wrong?

Thank you very much!! :)

CMDBuild source

Will it be possible to install and run from source? It will be great, because i can deploy cmdbuild 3.X from source

Deploying in Kubernetes

kubectl run openmaint --image=... --env "CMDBUILD_DUMP=*.dump.xz" ...
fails. After a successful creation of the database the running pod gets a Tomcat shut down event which stops it. After a reschedule it's successor does the same and so forth.
I'm wondering who shuts down Tomcat?

Empty CMDBuild environment from docker-compose

If I install cmdbuild 3.3 version on a Virtual Machine, I have the possibility to choose between an empty or a demo environment.
In order to have an empty environment from the execution of the Dockerfile, I tried to modify the flag ENV CMDBUILD_DUMP from demo.empty.xz to empty.dump.xz inside the Dockerfile ofthe openmaint-2.0-3.3 version. It didn't work for me.
Have you any ideas on how can I succeed in having an empty environment from the Dockerfile? There are other flags/configuration s that I need to consider?

Thank you a lot!

access to tomcat admin page

Hello,

I deployed successfully the docker image "openmaint-2.0-3.2"
Yet I'm unable to access the tomcat admin page at:
http://localhost:8080/manager or http://localhost:8090/manager

Does anyone have any idea what am I missing?
I know that on previous versions (+6 months ago), I used to be able to connect to it. What changed?

Best regards,
André.

404 after successfully runnig docker-compose up -d

git clone https://github.com/itmicus/cmdbuild_docker
cd openmaint-2.1-3.3-b
docker build -t itmicus/cmdbuild:om-2.1-3.3-b .
docker-compose up -d

Then access http://10.2.15.42:8082/ (I change 8090 to 8082 in the docker-compose.yml) , it shows 404 as below:

ERROR: manifest for itmicus/cmdbuild:r2u-2.0-3.3 not found: manifest unknown: manifest unknown

I have a ERROR.

docker-compose up -d
↓
Pulling cmdbuild_app (itmicus/cmdbuild:r2u-2.0-3.3)...
ERROR: manifest for itmicus/cmdbuild:r2u-2.0-3.3 not found: manifest unknown: manifest unknown

ERROR: relation "Gis_Building_Position" does not exist

In my OpenMaint installation I always have this error when creating a FLOOR card. I have imported the demo.dump into db.
What would be your suggestion? Thanks.

org.cmdbuild.dao.DaoException: error executing insert for entry = CardImpl{id=null, code=VIA10, type=Floor}, caused by: org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar []; nested exception is org.postgresql.util.PSQLException: ERROR: relation "Gis_Building_Position" does not exist Where: PL/pgSQL function _cm3_trigger_card_enforce_foreign_key_for_target() line 4 during statement block local variable initialization SQL statement "UPDATE "Building" SET "TotFloors" = new_subsites_current, "User" = NEW."User" WHERE "Id" = new_site_id" PL/pgSQL function tt_site_to_parent_data() line 50 at SQL statement, caused by: org.postgresql.util.PSQLException: ERROR: relation "Gis_Building_Position" does not exist Where: PL/pgSQL function _cm3_trigger_card_enforce_foreign_key_for_target() line 4 during statement block local variable initialization SQL statement "UPDATE "Building" SET "TotFloors" = new_subsites_current, "User" = NEW."User" WHERE "Id" = new_site_id" PL/pgSQL function tt_site_to_parent_data() line 50 at SQL statement

Failed to executing the command 'docker-compose up -d' for the cmdbuild 3.3 release

I've downloaded the docker-compose.yml file for the CMDbuild 3.3 release. Each time I try to run 'docker-compose up -d' command, the execution fails, retrieving the following error: "ERROR: manifest for itmicus/cmdbuild:app-3.3 not found: manifest unknown: manifest unknown". Have you any ideas on how to fix it?

Thank you.

Database reinitializes every time you run docker compose down then up

Symptoms:

1. run openMaint using the default setup with docker-compose up -d
2. Add something to the database
3. docker-compose down
4. docker-compose up -d

In the logs you can see that after step 4 the docker-entrypoint.sh runs the dbcreate command again causing the database to be wiped every time it is started anew. It looks like in docker-entrypoint.sh there used to be some kind of check, but the code will never the section after the ||, it always runs the first command below.

echo "Init DB"
{ # try
  
    $CATALINA_HOME/webapps/cmdbuild/cmdbuild.sh dbconfig create $CMDBUILD_DUMP -configfile $CATALINA_HOME/conf/cmdbuild/database.conf
   
} || { 
    echo "DB was initiliazed. Use dbconfig recreate or dbconfig drop"
}

How do I connect Docker to an existing database?

Hi!,

How do I connect Docker to an existing external database? If I leave the CMDBUILD_DUMP variable empty, it throws an error upon initialization. The database already contains data from a non-Docker installation.

Thank you and good job!

OpenMAINT throws a generic error when creating a new class.

Hi there,

I'm trying to use OpenMAINT-2.3-3.4.1, and as previously mentioned, whenever I try to create a new class, add a new entry, do corrective maintenance or do quite literally anything, a generic error is thrown.

org.cmdbuild.dao.DaoException: error while creating new class from definition = ClassDefinitionImpl{oid=null, name=Vehicle}, caused by: org.springframework.dao.DataIntegrityViolationException: PreparedStatementCallback; SQL [SELECT x::oid FROM _cm3_class_create(?, ?::regclass, ?::jsonb) x]; ERROR: null value in column "CurrentId" violates not-null constraint
Detail: Failing row contains (391192, "_ClassMetadata", Vehicle, null, null, null, 2023-06-28 10:02:47.46313+00, null, null, null, null, {"cm_note_inline": "false", "cm_ui_routing_custom": "null", "cm_...).
Where: SQL statement "INSERT INTO "_ClassMetadata" ("Code","Metadata") VALUES (_cm3_utils_regclass_to_name(_class), _metadata)"
PL/pgSQL function _cm3_class_metadata_set(regclass,jsonb) line 11 at SQL statement
SQL statement "SELECT _cm3_class_metadata_set(_classe, (SELECT coalesce(jsonb_object_agg(key, value), '{}'::jsonb) FROM jsonb_each_text(_features) WHERE key NOT IN (SELECT _cm3_class_comment_keys())))"
PL/pgSQL function _cm3_class_features_set(regclass,jsonb) line 3 at PERFORM
SQL statement "SELECT _cm3_class_features_set(_class, _features)"
PL/pgSQL function _cm3_class_create(character varying,regclass,jsonb) line 25 at PERFORM; nested exception is org.postgresql.util.PSQLException: ERROR: null value in column "CurrentId" violates not-null constraint
Detail: Failing row contains (391192, "_ClassMetadata", Vehicle, null, null, null, 2023-06-28 10:02:47.46313+00, null, null, null, null, {"cm_note_inline": "false", "cm_ui_routing_custom": "null", "cm_...).
Where: SQL statement "INSERT INTO "_ClassMetadata" ("Code","Metadata") VALUES (_cm3_utils_regclass_to_name(_class), _metadata)"
PL/pgSQL function _cm3_class_metadata_set(regclass,jsonb) line 11 at SQL statement
SQL statement "SELECT _cm3_class_metadata_set(_classe, (SELECT coalesce(jsonb_object_agg(key, value), '{}'::jsonb) FROM jsonb_each_text(_features) WHERE key NOT IN (SELECT _cm3_class_comment_keys())))"
PL/pgSQL function _cm3_class_features_set(regclass,jsonb) line 3 at PERFORM
SQL statement "SELECT _cm3_class_features_set(_class, _features)"
PL/pgSQL function _cm3_class_create(character varying,regclass,jsonb) line 25 at PERFORM, caused by: org.postgresql.util.PSQLException: ERROR: null value in column "CurrentId" violates not-null constraint
Detail: Failing row contains (391192, "_ClassMetadata", Vehicle, null, null, null, 2023-06-28 10:02:47.46313+00, null, null, null, null, {"cm_note_inline": "false", "cm_ui_routing_custom": "null", "cm_...).
Where: SQL statement "INSERT INTO "_ClassMetadata" ("Code","Metadata") VALUES (_cm3_utils_regclass_to_name(_class), _metadata)"
PL/pgSQL function _cm3_class_metadata_set(regclass,jsonb) line 11 at SQL statement
SQL statement "SELECT _cm3_class_metadata_set(_classe, (SELECT coalesce(jsonb_object_agg(key, value), '{}'::jsonb) FROM jsonb_each_text(_features) WHERE key NOT IN (SELECT _cm3_class_comment_keys())))"
PL/pgSQL function _cm3_class_features_set(regclass,jsonb) line 3 at PERFORM
SQL statement "SELECT _cm3_class_features_set(_class, _features)"
PL/pgSQL function _cm3_class_create(character varying,regclass,jsonb) line 25 at PERFORM

I installed the correct version and used docker-compose up -d to set it up. Any help would be very much appreciated.

Cmbuild_db not found

I used the following command copied from the guide
docker run --name cmdbuild_db -p 5432:5432 -d itmicus/cmdbuild:db-3.0
docker run --name cmdbuild_app --restart unless-stopped -e CMDBUILD_DUMP="demo.dump.xz" --link cmdbuild_db -p 8090:8080 -d itmicus/cmdbuild:r2u-2.0-3.2.1

It appeared to install however I got an error saying could not locate Cmbuild_db

Can you advise what has gone wrong?

CMDBuild 3.3 and OpenMaint 2.1

Hi,

The new versions of OpenMaint and Ready2Use were released yesterday. Can you please update these so we can build containers with the new versions?

Thanks,
Justin

error openmaint-2.0-3.2.1

Help me, I have this error.

org.cmdbuild.dao.DaoException: error processing patch = Patch{version=3.3.0-02_etl_gate_upgrade, category=core, applied=false}, caused by: org.cmdbuild.dao.DaoException: error processing patch = core-3.3.0-02_etl_gate_upgrade (etl gate tables upgrade), caused by: org.springframework.jdbc.BadSqlGrammarException: StatementCallback; bad SQL grammar [ SET SESSION cmdbuild.ignore_tenant_policies = 'true'; SET SESSION cmdbuild.user_tenants = '{}'; DO $$ BEGIN RAISE NOTICE 'apply cmdbuild patch %', 'core-3.3.0-02_etl_gate_upgrade'; END $$ LANGUAGE PLPGSQL; -- etl gate tables upgrade SELECT _cm3_attribute_create('OWNER: _EtlGate|NAME: Handlers|TYPE: jsonb|DEFAULT: ''[]''::jsonb'); DO $$ DECLARE _record record; _handlers jsonb; _templates varchar; BEGIN PERFORM _cm3_class_triggers_disable('"_EtlGate"'); FOR _record IN SELECT * FROM "_EtlGate" LOOP _handlers = '[]'::jsonb; SELECT string_agg(_template, ',') FROM unnest(_record."Templates") _template INTO _templates; IF _cm3_utils_is_not_blank(_record."Script") THEN _handlers = _handlers || jsonb_build_object('type', 'script', 'script', _record."Script", 'templates', _templates); END IF; IF _record."Handler" = 'default' THEN IF _cm3_utils_is_not_blank(_templates) THEN _handlers = _handlers || jsonb_build_object('type', 'template', 'templates', _templates); END IF; ELSE _handlers = _handlers || jsonb_build_object('type', _record."Handler", 'templates', _templates); END IF; UPDATE "_EtlGate" SET "Handlers" = _handlers WHERE "Id" = _record."Id"; END LOOP; PERFORM _cm3_class_triggers_enable('"_EtlGate"'); END $$ LANGUAGE PLPGSQL; ALTER TABLE "_EtlGate" DROP COLUMN "Script"; ALTER TABLE "_EtlGate" DROP COLUMN "Templates"; ALTER TABLE "_EtlGate" DROP COLUMN "Handler"; ALTER TABLE "_EtlGate" ADD CONSTRAINT "_cm3_Handlers_check" CHECK ( "Status" <> 'A' OR _cm3_etl_handlers_check("Handlers") ); DO $$ BEGIN RAISE NOTICE 'applied cmdbuild patch %', 'core-3.3.0-02_etl_gate_upgrade'; END $$ LANGUAGE PLPGSQL; ]; nested exception is org.postgresql.util.PSQLException: ERROR: no existe la columna pg_attrdef.adsrc Where: función SQL «_cm3_attribute_default_get», durante expansión en línea sentencia SQL: «SELECT _cm3_attribute_default_get(_class, _attr)» función PL/pgSQL _cm3_attribute_default_set(regclass,character varying,character varying,boolean) en la línea 11 en asignación sentencia SQL: «SELECT _cm3_attribute_default_set(_class, _attr, _default, TRUE)» función PL/pgSQL _cm3_attribute_create(regclass,character varying,character varying,jsonb) en la línea 33 en PERFORM sentencia SQL: «SELECT _cm3_attribute_create(_class, _attr, _features->>'TYPE', _features - 'TYPE')» función PL/pgSQL _cm3_attribute_create(regclass,character varying,jsonb) en la línea 2 en PERFORM sentencia SQL: «SELECT _cm3_attribute_create(_cm3_utils_name_to_regclass(_features->>'OWNER'), _features->>'NAME', _features - 'OWNER' - 'NAME')» función PL/pgSQL _cm3_attribute_create(jsonb) en la línea 2 en PERFORM sentencia SQL: «SELECT _cm3_attribute_create(_cm3_comment_to_jsonb(_features))» función PL/pgSQL _cm3_attribute_create(character varying) en la línea 2 en PERFORM, caused by: org.postgresql.util.PSQLException: ERROR: no existe la columna pg_attrdef.adsrc Where: función SQL «_cm3_attribute_default_get», durante expansión en línea sentencia SQL: «SELECT _cm3_attribute_default_get(_class, _attr)» función PL/pgSQL _cm3_attribute_default_set(regclass,character varying,character varying,boolean) en la línea 11 en asignación sentencia SQL: «SELECT _cm3_attribute_default_set(_class, _attr, _default, TRUE)» función PL/pgSQL _cm3_attribute_create(regclass,character varying,character varying,jsonb) en la línea 33 en PERFORM sentencia SQL: «SELECT _cm3_attribute_create(_class, _attr, _features->>'TYPE', _features - 'TYPE')» función PL/pgSQL _cm3_attribute_create(regclass,character varying,jsonb) en la línea 2 en PERFORM sentencia SQL: «SELECT _cm3_attribute_create(_cm3_utils_name_to_regclass(_features->>'OWNER'), _features->>'NAME', _features - 'OWNER' - 'NAME')» función PL/pgSQL _cm3_attribute_create(jsonb) en la línea 2 en PERFORM sentencia SQL: «SELECT _cm3_attribute_create(_cm3_comment_to_jsonb(_features))» función PL/pgSQL _cm3_attribute_create(character varying) en la línea 2 en PERFORM

ERROR: manifest for itmicus/cmdbuild:app-3.2 not found: manifest unknown: manifest unknown

Hi,
I tried to deploy cmdbuild 3.2 by docker-compose, but I got the error as below.
I saw there was a similar issue has been closed. Could you please help me resolve this as well?

docker-compose up -d
Creating network "32_default" with the default driver
Creating volume "32_cmdbuild-db" with default driver
Creating volume "32_cmdbuild-tomcat" with default driver
Pulling cmdbuild_db (itmicus/cmdbuild:db-3.0)...
db-3.0: Pulling from itmicus/cmdbuild
...
Status: Downloaded newer image for itmicus/cmdbuild:db-3.0
Pulling cmdbuild_app (itmicus/cmdbuild:app-3.2)...
ERROR: manifest for itmicus/cmdbuild:app-3.2 not found: manifest unknown: manifest unknown

SQL Error when attempting to create users or groups

Receive the following error when running openmaint-2.3-3.4.1-d through docker compose when trying to create users or groups (potentially more but this is all I have tested and received the same error on so far)

org.cmdbuild.dao.DaoException: error executing insert for entry = CardImpl{id=null, type=User}, caused by: org.springframework.dao.DataIntegrityViolationException: StatementCallback; ERROR: null value in column "CurrentId" violates not-null constraint