<@U04S8PLJWMT> i am getting this error in my airby...
# ask-ai
r
@kapa.ai i am getting this error in my airbyte bootloader:
Copy code
2025-12-03 18:18:04,553 [main]    ERROR    i.a.b.Application(main):32 - Unable to bootstrap Airbyte environment.                                                                                                                                                                                                │
│ java.lang.RuntimeException: com.fasterxml.jackson.core.JsonParseException: Invalid numeric value: Leading zeroes not allowed                                                                                                                                                                                    │
│  at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column: 2]                                                                                                                                                                                                            │
│     at io.airbyte.commons.json.Jsons.deserialize(Jsons.java:101)
what could be the issue here?
k
The error matches a known issue when deploying Airbyte 1.6.x: the bootloader fails while reading some JSON configuration because Jackson rejects a number with leading zeros (“Invalid numeric value: Leading zeroes not allowed”). [[Failed deploy 1.6.1](https://github.com/airbytehq/airbyte/issues/59177); [Deploy v1.6.0 error](https://github.com/airbytehq/airbyte/issues/58587)] From the linked issues, this happens very early in boot, right after: - Flyway reports the DB schema is up to date, and then - Bootloader tries to “Creating workspace (if none exists)” and crashes on JSON parsing. [[Deploy v1.6.0 error](https://github.com/airbytehq/airbyte/issues/58587)] That means some JSON the bootloader reads (from DB or config) contains a numeric field like
0123
or similar, which Jackson now rejects. However, the shared sources do not specify which field or table is responsible, nor a concrete step‑by‑step fix. They only show the same stack trace and confirm it blocks bootstrapping. [[Failed deploy 1.6.1](https://github.com/airbytehq/airbyte/issues/59177); [Deploy v1.6.0 error](https://github.com/airbytehq/airbyte/issues/58587)] So, based on the available information: - The root cause is malformed JSON with a number that has leading zeros, read during bootloader startup. - The knowledge sources do not explicitly document where that JSON lives or how to correct it (e.g., which DB row / config file to edit). To move forward, I recommend: 1. Check if you are on 1.6.0/1.6.1 and see the referenced issues above, as your error appears identical. 2. Inspect any custom configuration you may have added (env vars, JSON config files, seeded data) for numeric values with leading zeros. 3. If this is a fresh deploy with no custom data, open an issue or comment on the existing ones with your full bootloader logs and Airbyte version, since the current knowledge doesn’t include a documented workaround.
r
@kapa.ai i have fixed this by upgrading to 1.6.9. i am now getting this error:
Copy code
│ 2025-12-03 19:07:23,441 [main]    ERROR    i.m.r.Micronaut(handleStartupException):349 - Error starting Micronaut server: Failed to initialize data-plane                                                                                                                                                       │
│ java.lang.RuntimeException: Failed to initialize data-plane                                                                                                                                                                                                                                                     │
│     at io.airbyte.workload.launcher.authn.DataplaneIdentityService.initialize(DataplaneIdentityService.kt:56)                                                                                                                                                                                                   │
│     at io.airbyte.workload.launcher.StartupApplicationEventListener.onApplicationEvent(StartupApplicationEventListener.kt:34)                                                                                                                                                                                   │
│     at io.airbyte.workload.launcher.StartupApplicationEventListener.onApplicationEvent(StartupApplicationEventListener.kt:20)                                                                                                                                                                                   │
│     at io.micronaut.context.event.ApplicationEventPublisherFactory.notifyEventListeners(ApplicationEventPublisherFactory.java:266)                                                                                                                                                                              │
│     at io.micronaut.context.event.ApplicationEventPublisherFactory$2.publishEvent(ApplicationEventPublisherFactory.java:226)                                                                                                                                                                                    │
│     at io.micronaut.http.server.netty.discovery.NettyServiceDiscovery.onStart(NettyServiceDiscovery.java:54)                                                                                                                                                                                                    │
│     at io.micronaut.http.server.netty.discovery.$NettyServiceDiscovery$Definition$Exec.dispatch(Unknown Source)                                                                                                                                                                                                 │
│     at io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invoke(AbstractExecutableMethodsDefinition.java:456)                                                                                                                                                                 │
│     at io.micronaut.context.DefaultBeanContext$BeanExecutionHandle.invoke(DefaultBeanContext.java:3944)                                                                                                                                                                                                         │
│     at io.micronaut.aop.chain.AdapterIntroduction.intercept(AdapterIntroduction.java:87)                                                                                                                                                                                                                        │
│     at io.micronaut.aop.chain.MethodInterceptorChain.proceed(MethodInterceptorChain.java:143)                                                                                                                                                                                                                   │
│     at io.micronaut.http.server.netty.discovery.NettyServiceDiscovery$ApplicationEventListener$onStart1$Intercepted.onApplicationEvent(Unknown Source)                                                                                                                                                          │
│     at io.micronaut.context.event.ApplicationEventPublisherFactory.notifyEventListeners(ApplicationEventPublisherFactory.java:266)                                                                                                                                                                              │
│     at io.micronaut.context.event.ApplicationEventPublisherFactory$2.publishEvent(ApplicationEventPublisherFactory.java:226)                                                                                                                                                                                    │
│     at io.micronaut.http.server.netty.NettyHttpServer.fireStartupEvents(NettyHttpServer.java:692)                                                                                                                                                                                                               │
│     at io.micronaut.http.server.netty.NettyHttpServer.start(NettyHttpServer.java:314)                                                                                                                                                                                                                           │
│     at io.micronaut.http.server.netty.NettyHttpServer.start(NettyHttpServer.java:112)                                                                                                                                                                                                                           │
│     at io.micronaut.runtime.Micronaut.start(Micronaut.java:81)                                                                                                                                                                                                                                                  │
│     at io.airbyte.workload.launcher.ApplicationKt.main(Application.kt:10)                                                                                                                                                                                                                                       │
│ Caused by: java.io.IOException: HTTP error: 500 Internal Server Error
k
A message from kapa.ai
This error matches known dataplane initialization problems in 1.6.x and later: the workload launcher’s
DataplaneIdentityService
fails on startup because calls to the internal dataplane/auth APIs return HTTP 500. [[1.6.0 deploy issue](https://github.com/airbytehq/airbyte/issues/58587); [2.0.0 dataplane init](https://github.com/airbytehq/airbyte/issues/68134)] From the shared issues, common underlying causes are: - Dataplane service account / credentials problems - Errors like
Service account not found: <uuid>
have been seen when the service account / dataplane client credentials in the DB do not match what the workload launcher expects. [[1.6.0 deploy issue](https://github.com/airbytehq/airbyte/issues/58587)] - Deleting rows from
dataplane
or
dataplane_client_credentials
can leave the system unable to recreate the secrets automatically, causing repeated 500s when fetching tokens. [[1.6.0 deploy issue](https://github.com/airbytehq/airbyte/issues/58587)] - Dataplane access token failures - Logs such as
Failed to obtain or add dataplane access token ... Token request failed with HTTP code 500
appear when the internal API for issuing dataplane tokens returns 500. [[1.6.0 deploy issue](https://github.com/airbytehq/airbyte/issues/58587)] - Version-specific bugs - Several users report persistent dataplane / workload-launcher issues across 1.6.0–1.6.2, and one mentions that “1.8.x fixes some bugs related to this dataplane thing,” though 1.8 itself can introduce new service-account–related complexity. [[1.6.0 deploy issue](https://github.com/airbytehq/airbyte/issues/58587)] Given the knowledge: 1. Your stack trace is the same class (
DataplaneIdentityService.initialize
) as in the known dataplane failures. [[2.0.0 dataplane init](https://github.com/airbytehq/airbyte/issues/68134)] 2. We do not have a documented, reliable DB- or config-level fix in the provided sources; attempts like deleting from
dataplane*
tables made things worse for at least one user. [[1.6.0 deploy issue](https://github.com/airbytehq/airbyte/issues/58587)] Concrete next steps, based only on what’s documented: - Check for prior manual DB changes If you previously deleted from
dataplane
/
dataplane_client_credentials
, that’s a known way to break dataplane initialization; the sources do not document how to safely rebuild those rows, only that secrets stop being created afterward. [[1.6.0 deploy issue](https://github.com/airbytehq/airbyte/issues/58587)] - Check dataplane-related logs Look at: -
workload-launcher
logs for messages like “Failed to obtain or add dataplane access token” or “Service account not found”. -
platform
/
api-server
logs around HTTP 500 responses for
/dataplane
or service-account endpoints. This is where the underlying 500 will be logged, but the exact endpoint is not specified in the sources. - Consider a version change One user suggests moving to 1.8.x for more stable dataplane behavior, though another noted new issues there, so this is not guaranteed. [[1.6.0 deploy issue](https://github.com/airbytehq/airbyte/issues/58587)] The sources do not mention 1.6.9 specifically, so it’s unclear whether your exact error is a known, fixed, or new regression. Because the available documents stop at describing the symptoms (HTTP 500, service-account/dataplane credential issues) and do not provide a complete remediation procedure for your situation, I can’t give you a precise “run this SQL / set this env var” fix without guessing. If you can share: - Whether you ever modified or truncated
dataplane
/
dataplane_client_credentials
, and - The exact error body for the 500 from the platform/api logs, I may be able to match it more closely to one of the documented patterns (e.g., missing service account vs. malformed dataplane config) within the existing sources.