Database Connection Error on Data Integration Maria 10.4.14

I can’t get past the setup script, it keeps throwing an error.

Here’s my system:

Centos 7
MariaDB 10.4.14
Java openjdk version “1.8.0_262”
SuiteCRM 7.11.15
Data Integration Server / Analytics Server V1.1

BEGIN ERROR MESSAGE


2020/09/27 04:17:01 - Check Source DB - ERROR (version 8.0.0.0-28, build 8.0.0.0-28 from 2017-11-05 07.27.50 by buildguy) : Cannot connect to database [SuiteCRM] (connection [SuiteCRM]). Exception : [org.pentaho.di.core.exception.KettleDatabaseException:

2020/09/27 04:17:01 - Check Source DB - Error occurred while trying to connect to the database

2020/09/27 04:17:01 - Check Source DB - Access denied for user ‘testing_suitecrm’@‘127.0.0.1’ (using password: YES)

2020/09/27 04:17:01 - Check Source DB - ]


From the log file:

INFO: New Caching Service registered
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/var/www/vhosts/site.net/subdomains/suitecrm-data-integration-server/client/launcher/…/lib/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/var/www/vhosts/site.net/subdomains/suitecrm-data-integration-server/client/plugins/pentaho-big-data-plugin/lib/slf4j-log4j12-1.7.7.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]
Sep 27, 2020 4:17:00 AM org.apache.cxf.endpoint.ServerImpl initDestination
INFO: Setting the server’s publish address to be /lineage
Sep 27, 2020 4:17:01 AM org.apache.cxf.endpoint.ServerImpl initDestination
INFO: Setting the server’s publish address to be /i18n
2020/09/27 04:17:01 - - ERROR (version 8.0.0.0-28, build 8.0.0.0-28 from 2017-11-05 07.27.50 by buildguy) : ETL LOG START
2020/09/27 04:17:01 - Check Source DB - ERROR (version 8.0.0.0-28, build 8.0.0.0-28 from 2017-11-05 07.27.50 by buildguy) : Cannot connect to database [SuiteCRM] (connection [SuiteCRM]). Exception : [org.pentaho.di.core.exception.KettleDatabaseException:
2020/09/27 04:17:01 - Check Source DB - Error occurred while trying to connect to the database
2020/09/27 04:17:01 - Check Source DB - Access denied for user ‘dsnet_suitecrm’@‘127.0.0.1’ (using password: YES)
2020/09/27 04:17:01 - Check Source DB - ]
2020/09/27 04:17:01 - - ERROR (version 8.0.0.0-28, build 8.0.0.0-28 from 2017-11-05 07.27.50 by buildguy) : ETL LOG END
2020/09/27 04:17:01 - Abort job - ERROR (version 8.0.0.0-28, build 8.0.0.0-28 from 2017-11-05 07.27.50 by buildguy) : Aborting job.
2020/09/27 04:17:01 - Kitchen - ERROR (version 8.0.0.0-28, build 8.0.0.0-28 from 2017-11-05 07.27.50 by buildguy) : Finished with errors

I checked the login credentials of both with the command line and they work for CRM and Analytics databases.

Any idea about other possible issues? Is my MariaDB version too high? I doubt that since they’re usually very backward compatible. Firewall maybe? Everything is hosted localhost though.

Thanks,
Brad

Hi, @ceopx
I have MariaDB version 10.3.21, it works without problem. If you shure that it isn’t problem with password, may be the post (https://mariadb.com/kb/en/access-denied-for-user-rootlocalhost/) to help you.

Hi, yeah I’ve quite a few things working with MariaDB and tested using the CLI and everything works with the credentials I’ve entered into the configuration files for both SuiteCRM and the Analytics databases.

I even purposely removed the SuiteCRM password to make it throw an error and reverted it to make sure it was actually referencing the information from the config file.

I’m baffled.

Try using a simpler password, without any characters that could get removed during a security clean-up (things like apostrophes, brackets, symbols, etc)

SuiteCRM has a nasty bug applying excessive security clean-ups where it really shouldn’t.

That thought crossed my mind. I just tried a simpler password and still had this same outcome.

I’m having a feeling it’s the database connector between Java and MariaDB. I just can’t find a good method of testing that.