Alexis Blandin
12/27/2022, 2:48 PMMicronaut (v3.7.4)
2022-12-27 13:31:29 INFO i.m.c.e.DefaultEnvironment(<init>):159 - Established active environments: [ec2, cloud, control-
plane]
2022-12-27 13:31:29 INFO c.z.h.HikariDataSource(<init>):71 - HikariPool-1 - Starting...
2022-12-27 13:31:30 INFO c.z.h.HikariDataSource(<init>):73 - HikariPool-1 - Start completed.
2022-12-27 13:31:30 INFO c.z.h.HikariDataSource(<init>):71 - HikariPool-2 - Starting...
2022-12-27 13:31:30 INFO c.z.h.HikariDataSource(<init>):73 - HikariPool-2 - Start completed.
2022-12-27 13:31:30 INFO i.m.l.PropertiesLoggingLevelsConfigurer(configureLogLevelForPrefix):107 - Setting log level 'DE
BUG' for logger: 'io.airbyte.bootloader'
2022-12-27 13:31:31 INFO i.a.w.c.DatabaseBeanFactory(configsDatabaseMigrationCheck):119 - Configs database configuration
: 0.35.15.001 60000
2022-12-27 13:31:31 ERROR i.m.r.Micronaut(handleStartupException):338 - Error starting Micronaut server: Error instantia
ting bean of type [io.airbyte.persistence.job.factory.OAuthConfigSupplier]
Message: SQL [select * from airbyte_metadata where key = ?]; ERROR: relation "airbyte_metadata" does not exist
Position: 15
Before starting the container, db was empty, and after the relation/table was created and filled with this values (user has all privileges on database)
airbyte_config=> select * from airbyte_metadata ;
key | value
------------------------------+-------
airbyte_protocol_version_min | 0.0.0
airbyte_protocol_version_max | 0.3.0
(2 rows)
On the docker-compose.yml i put in comments the db service as well as other services depencences and volumes related to it. If somebody can help me on this. Thanks !Sunny Hashmi (Airbyte)
01/18/2023, 2:56 PM