Hey, Each time we have a release we faced issues w...
# replication-ask-ai
w
Hey, Each time we have a release we faced issues with installing airbyte!!!!. Today I'm trying to install airbyte on windows and following the doc. but something raised exception and bootloader can't initialized @Marcos Marx (Airbyte) Could you give it a look here, please
Copy code
airbyte-bootloader                | 2023-08-13 12:35:05 ERROR i.a.b.Application(main):25 - Unable to bootstrap Airbyte environment.
airbyte-bootloader                | org.jooq.exception.DataAccessException: SQL [select distinct "public"."actor_definition"."id", "public"."actor_definition_version"."docker_repository", "public"."actor_definition"."actor_type", "public"."actor_definition_version"."protocol_version" from "public"."actor_definition" join "public"."actor" on "public"."actor"."actor_definition_id" = "public"."actor_definition"."id" join "public"."actor_definition_version" on "public"."actor_definition_version"."id" = "public"."actor_definition"."default_version_id"]; ERROR: relation "public.actor_definition_version" does not exist
airbyte-bootloader                |   Position: 342
airbyte-bootloader                |     at org.jooq_3.17.8.POSTGRES.debug(Unknown Source) ~[?:?]
airbyte-bootloader                |     at org.jooq.impl.Tools.translate(Tools.java:3313) ~[jooq-3.17.8.jar:?]
airbyte-bootloader                |     at org.jooq.impl.DefaultExecuteContext.sqlException(DefaultExecuteContext.java:678) ~[jooq-3.17.8.jar:?]
airbyte-bootloader                |     at org.jooq.impl.AbstractQuery.execute(AbstractQuery.java:355) ~[jooq-3.17.8.jar:?]
airbyte-bootloader                |     at org.jooq.impl.AbstractResultQuery.fetch(AbstractResultQuery.java:290) ~[jooq-3.17.8.jar:?]
airbyte-bootloader                |     at org.jooq.impl.SelectImpl.fetch(SelectImpl.java:2837) ~[jooq-3.17.8.jar:?]
airbyte-bootloader                |     at io.airbyte.config.persistence.ConfigRepository.getActorDefinitionsInUse(ConfigRepository.java:630) ~[io.airbyte.airbyte-config-config-persistence-0.50.16.jar:?]
airbyte-bootloader                |     at io.airbyte.config.persistence.ConfigRepository.lambda$getActorDefinitionToProtocolVersionMap$22(ConfigRepository.java:653) ~[io.airbyte.airbyte-config-config-persistence-0.50.16.jar:?]
airbyte-bootloader                |     at io.airbyte.db.Database.query(Database.java:23) ~[io.airbyte.airbyte-db-db-lib-0.50.16.jar:?]
airbyte-bootloader                |     at io.airbyte.db.ExceptionWrappingDatabase.query(ExceptionWrappingDatabase.java:31) ~[io.airbyte.airbyte-db-db-lib-0.50.16.jar:?]
airbyte-bootloader                |     at io.airbyte.config.persistence.ConfigRepository.getActorDefinitionToProtocolVersionMap(ConfigRepository.java:653) ~[io.airbyte.airbyte-config-config-persistence-0.50.16.jar:?]
airbyte-bootloader                |     at io.airbyte.bootloader.ProtocolVersionChecker.getConflictingActorDefinitions(ProtocolVersionChecker.java:142) ~[io.airbyte-airbyte-bootloader-0.50.16.jar:?]
airbyte-bootloader                |     at io.airbyte.bootloader.ProtocolVersionChecker.validate(ProtocolVersionChecker.java:96) ~[io.airbyte-airbyte-bootloader-0.50.16.jar:?]
airbyte-bootloader                |     at io.airbyte.bootloader.Bootloader.assertNonBreakingProtocolVersionConstraints(Bootloader.java:156) ~[io.airbyte-airbyte-bootloader-0.50.16.jar:?]
airbyte-bootloader                |     at io.airbyte.bootloader.Bootloader.load(Bootloader.java:105) ~[io.airbyte-airbyte-bootloader-0.50.16.jar:?]
airbyte-bootloader                |     at io.airbyte.bootloader.Application.main(Application.java:22) ~[io.airbyte-airbyte-bootloader-0.50.16.jar:?]
airbyte-bootloader                | Caused by: org.postgresql.util.PSQLException: ERROR: relation "public.actor_definition_version" does not exist
airbyte-bootloader                |   Position: 342
airbyte-bootloader                |     at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2676) ~[postgresql-42.5.4.jar:42.5.4]
airbyte-bootloader                |     at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2366) ~[postgresql-42.5.4.jar:42.5.4]
airbyte-bootloader                |     at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:356) ~[postgresql-42.5.4.jar:42.5.4]
airbyte-bootloader                |     at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:496) ~[postgresql-42.5.4.jar:42.5.4]
airbyte-bootloader                |     at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:413) ~[postgresql-42.5.4.jar:42.5.4]
airbyte-bootloader                |     at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:190) ~[postgresql-42.5.4.jar:42.5.4]
airbyte-bootloader                |     at org.postgresql.jdbc.PgPreparedStatement.execute(PgPreparedStatement.java:177) ~[postgresql-42.5.4.jar:42.5.4]
airbyte-bootloader                |     at com.zaxxer.hikari.pool.ProxyPreparedStatement.execute(ProxyPreparedStatement.java:44) ~[HikariCP-5.0.1.jar:?]
airbyte-bootloader                |     at com.zaxxer.hikari.pool.HikariProxyPreparedStatement.execute(HikariProxyPreparedStatement.java) ~[HikariCP-5.0.1.jar:?]
airbyte-bootloader                |     at org.jooq.tools.jdbc.DefaultPreparedStatement.execute(DefaultPreparedStatement.java:219) ~[jooq-3.17.8.jar:?]
airbyte-bootloader                |     at org.jooq.impl.Tools.executeStatementAndGetFirstResultSet(Tools.java:4571) ~[jooq-3.17.8.jar:?]
airbyte-bootloader                |     at org.jooq.impl.AbstractResultQuery.execute(AbstractResultQuery.java:236) ~[jooq-3.17.8.jar:?]
airbyte-bootloader                |     at org.jooq.impl.AbstractQuery.execute(AbstractQuery.java:341) ~[jooq-3.17.8.jar:?]
airbyte-bootloader                |     ... 12 more
airbyte-bootloader                | 2023-08-13 12:35:05 INFO i.m.r.Micronaut(lambda$start$0):115 - Embedded Application shutting down
airbyte-bootloader exited with code 255
service "bootloader" didn't completed successfully: exit 255
k
@Wajdi M That's a great question, but unfortunately it is too long. Can you ask me again but make it shorter? I'm here to help!
w
@kapa.ai I see not just me who face this issue bootloader issue
k
Yes, you're not alone. There have been instances where users have faced issues with the Airbyte bootloader. For example, in a [forum discussion](https://discuss.airbyte.io/t/3503), a user reported an issue where the bootloader couldn't complete an upgrade from a fresh git clone. The error message indicated that the system couldn't upgrade directly to the desired version and needed to upgrade to an intermediate version first. The issue was resolved by cleaning the Docker images and starting over. In another [Slack conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1672403402093859), a user faced a problem while trying to update Airbyte due to the bootloader failing because it tried to upgrade custom connectors that didn't follow semantic versioning for tag names. The user opened an issue for this on GitHub for further assistance. If you're facing a similar issue, you can follow the general troubleshooting steps provided in the [Airbyte troubleshooting guide](https://docs.airbyte.com/troubleshooting). These steps include checking the logs, referring to the documentation, reaching out to the community, and opening a Github ticket if necessary.
Yes, you're not alone. There have been instances where users have faced issues with the Airbyte bootloader. For example, in a [previous support conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1672403402093859), a user was trying to update Airbyte and encountered a failure in the bootloader because it was trying to upgrade custom connectors that didn't follow semantic versioning for tag names. In such cases, it's recommended to open a Github issue with the full bootloader logs to get visibility from the Airbyte platform team. You can also follow the [troubleshooting guide](https://docs.airbyte.com/troubleshooting) provided by Airbyte. The guide recommends checking the logs, consulting the documentation, reaching out to the community, and if all else fails, opening a Github ticket. Remember, the Airbyte community and support team are there to help you resolve any issues you're facing with Airbyte.