CMDBuild Forum

Database connection error, try to reset the connection parameters

Hi all,

i've new problem

when i finished install cmdbuild and start to login

this message show, why?

It is somehow hard to find a solution to your problem if we don't know what you have done. Have you done a manual ar automatic configuration? A manual or automatic database setup? Also there should be a more detailed message in cmdbuild.log.

 

There seems to be a problem with the database connection parameters.

 

Some hints on PostgreSQL...

 

  • is PostgreSQL correctly configured to accept TCP connections? (you should google for pg_hba.conf if you don't know what I'm talking about)
  • can you connect to that database using the command "psql -h <host> -p <port> -U <username> -W -d <database>" (using of course the parameters that you used during in the configuration steps). for a test try, you can safely use the user "postgres"
  • cmdbuild creates the database itself, so you should not create an empty database before configuring it (the "Existing" database type is intended to be used for an existing cmdbuild database)

 

IF you are able to manually connect to PostgreSQL, you should try with the following cmdbuild configuration parameters (on a fresh cmdbuild war with a clean tomcat work directory, with no cmdbuild database on postgres).

 

CMDBuild Database

Database type: Demo
Database name: cmdbuild
Create a Shark schema: yes

 

These other parameters should work if you have a local postgres server with the standard setup:

 

Database

Connection

Host: 127.0.0.1
Port: 5432
Super user: postgres
Password: postgres

Create restricted database user

User type: Super user

Administration account:

User name: admin
Password: admin
Confirm password: admin

 

Hope this helps.

 

Paolo

 

 

 

Hi,
 
I created postgresql in local and connected as "existing" and gave credentials for my local db. still I am seeing only default data source. What is the mistake I am doing. Should I build any new war file?
Pls advice.
 
Previously Tecnoteca wrote:

It is somehow hard to find a solution to your problem if we don't know what you have done. Have you done a manual ar automatic configuration? A manual or automatic database setup? Also there should be a more detailed message in cmdbuild.log.

 

There seems to be a problem with the database connection parameters.

 

Some hints on PostgreSQL...

 

  • is PostgreSQL correctly configured to accept TCP connections? (you should google for pg_hba.conf if you don't know what I'm talking about)
  • can you connect to that database using the command "psql -h <host> -p <port> -U <username> -W -d <database>" (using of course the parameters that you used during in the configuration steps). for a test try, you can safely use the user "postgres"
  • cmdbuild creates the database itself, so you should not create an empty database before configuring it (the "Existing" database type is intended to be used for an existing cmdbuild database)

 

IF you are able to manually connect to PostgreSQL, you should try with the following cmdbuild configuration parameters (on a fresh cmdbuild war with a clean tomcat work directory, with no cmdbuild database on postgres).

 

CMDBuild Database

Database type: Demo
Database name: cmdbuild
Create a Shark schema: yes

 

These other parameters should work if you have a local postgres server with the standard setup:

 

Database

Connection

Host: 127.0.0.1
Port: 5432
Super user: postgres
Password: postgres

Create restricted database user

User type: Super user

Administration account:

User name: admin
Password: admin
Confirm password: admin

 

Hope this helps.

 

Paolo