kylo-services fails to start : unable to create schema

294 views
Skip to first unread message

Mathieu Marie

unread,
Aug 4, 2017, 5:58:05 AM8/4/17
to Kylo Community
I am installing kylo 0.8.2 on a new cluster.
I installed kylo from RPM and mariadb 5.5.52 using 'yum install mariadb-server' on centOS 7.

On mariadb I only created an empty kylo database, the same way I had done it on a virtualbox based cluster.

But when I start kylo-services, liquibase fails to create all of the tables and kylo-services does not start.

The tables that are created :

show tables;
+--------------------------------+
| Tables_in_kylo                 |
+--------------------------------+
| AUDIT_LOG                      |
| BATCH_EXECUTION_CONTEXT_VALUES |
| BATCH_JOB_EXECUTION            |
| BATCH_JOB_EXECUTION_CTX_VALS   |
| BATCH_JOB_EXECUTION_PARAMS     |
| BATCH_JOB_EXECUTION_SEQ        |
| BATCH_JOB_INSTANCE             |
| BATCH_JOB_SEQ                  |
| BATCH_NIFI_JOB                 |
| BATCH_NIFI_STEP                |
| BATCH_STEP_EXECUTION           |
| BATCH_STEP_EXECUTION_CTX_VALS  |
| BATCH_STEP_EXECUTION_SEQ       |
| DATABASECHANGELOG              |
| DATABASECHANGELOGLOCK          |
+--------------------------------+
15 rows in set (0.00 sec)

I do get one error in the kylo-services.log (in attachement) when creating the FEED table.

2017-08-04 11:31:20 WARN  main:AnnotationConfigEmbeddedWebApplicationContext:546 - Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'kyloUpgradeConfig': Injection of autowired dependencies failed; nested exception is org.springframework.beans.factory.BeanCreationException: Could not autowire field: private liquibase.integration.spring.SpringLiquibase com.thinkbiganalytics.server.upgrade.KyloUpgradeConfig.liquibase; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liquibase' defined in class path resource [com/thinkbiganalytics/server/upgrade/liquibase/LiquibaseConfiguration.class]: Invocation of init method failed; nested exception is liquibase.exception.MigrationFailedException: Migration failed for change set classpath:com/thinkbiganalytics/db/changelog/0.0.0/2017-03-24-1135-automated-export.xml::1490096811017-14::ru186002 (generated):
     Reason: liquibase.exception.DatabaseException: (conn:27) Invalid default value for 'modified_time'
Query is : CREATE TABLE kylo.FEED (id BINARY(16) NOT NULL, name VARCHAR(100) NOT NULL, description VARCHAR(255) NULL, FEED_TYPE VARCHAR(45) NULL, created_time timestamp DEFAULT NOW() NOT NULL, modified_time timestamp DEFAULT '1970-01-01 00:00:01' NOT NULL) [Failed SQL: CREATE TABLE kylo.FEED (id BINARY(16) NOT NULL, name VARCHAR(100) NOT NULL, description VARCHAR(255) NULL, FEED_TYPE VARCHAR(45) NULL, created_time timestamp DEFAULT NOW() NOT NULL, modified_time timestamp DEFAULT '1970-01-01 00:00:01' NOT NULL)]


Can someone help with this new issue?
Note that I completly uninstalled mariadb, deleted files on disk (/var/lib/mysql) and resinstalled it, but got the same behavior.

Regards,
Mathieu
kylo-services.log

Mathieu Marie

unread,
Aug 4, 2017, 9:13:52 AM8/4/17
to Kylo Community
Hello,

I found my issue, related to mariadb timezone configuration.
In order to fix it I add to:

1- load the timezone into mariadb :
    mysql_tzinfo_to_sql /usr/share/zoneinfo | mysql -u root -p mysql

2- Connect to mariadb using mysql and execute :
    SET GLOBAL time_zone = 'UTC'

Then it worked.
The root cause of my issue is that my TZ is GMT +2:00, and the default value of 1970-01-01 00:00:01 became invalid once converted into UTC.
The issue is probably encountered only in countries on the east side of UK.

Regards,
Mathieu



Greg Hart

unread,
Aug 4, 2017, 1:22:53 PM8/4/17
to Kylo Community
Hi Mathieu,

Glad you were able to resolve your issue and thanks for posting the solution!
Reply all
Reply to author
Forward
0 new messages