I think I broke my local install. UI shows "Oops! ...
# replication-troubleshooting
s
I think I broke my local install. UI shows "Oops! Something went wrong… Unknown error occurred". and these logs were from Chrome console. This started happening after I clicked update all connectors. I can just nuke and retry but sharing here just in case
Copy code
manifest.json:1          GET <http://localhost:8000/manifest.json> 401 (Unauthorized)
manifest.json:1 Manifest: Line: 1, column: 1, Syntax error.
apiOverride.ts:57          POST <http://localhost:8000/api/v1/web_backend/connections/list> 500 (Internal Server Error)
(anonymous) @ apiOverride.ts:57
d @ regeneratorRuntime.js:86
(anonymous) @ regeneratorRuntime.js:66
(anonymous) @ regeneratorRuntime.js:117
r @ asyncToGenerator.js:3
s @ asyncToGenerator.js:25
(anonymous) @ asyncToGenerator.js:32
(anonymous) @ asyncToGenerator.js:21
(anonymous) @ apiOverride.ts:24
ae @ AirbyteClient.ts:3276
value @ WebBackendConnectionService.ts:17
(anonymous) @ useConnectionHook.tsx:243
fetchFn @ query.js:298
l @ retryer.js:95
c @ retryer.js:156
t.fetch @ query.js:330
n.fetchOptimistic @ queryObserver.js:180
(anonymous) @ useBaseQuery.js:84
A @ useQuery.js:7
o @ useSuspenseQuery.ts:19
O @ useConnectionHook.tsx:243
le @ AllConnectionsPage.tsx:23
sa @ react-dom.production.min.js:157
Gs @ react-dom.production.min.js:267
Au @ react-dom.production.min.js:250
Ou @ react-dom.production.min.js:250
Cu @ react-dom.production.min.js:250
_u @ react-dom.production.min.js:243
(anonymous) @ react-dom.production.min.js:123
t.unstable_runWithPriority @ scheduler.production.min.js:18
Vi @ react-dom.production.min.js:122
Ki @ react-dom.production.min.js:123
M @ scheduler.production.min.js:16
b.port1.onmessage @ scheduler.production.min.js:12
react_devtools_backend.js:4012 Error: Internal Server Error: Duplicate key 99a5b8cc-01ce-4a02-946c-a33d91b3d1b2 (attempted merging values io.airbyte.config.ActorCatalogFetchEvent@3825d1c9[id=<null>,actorId=99a5b8cc-01ce-4a02-946c-a33d91b3d1b2,actorCatalogId=5be6c2c9-692c-467b-a052-56ccc9915c7c,configHash=<null>,connectorVersion=<null>,createdAt=1670444899] and io.airbyte.config.ActorCatalogFetchEvent@4e9e2fd1[id=<null>,actorId=99a5b8cc-01ce-4a02-946c-a33d91b3d1b2,actorCatalogId=e1f51180-5fb3-4f7d-b509-17b6dbcf0675,configHash=<null>,connectorVersion=<null>,createdAt=1670444899])
    at apiOverride.ts:107:9
    at d (regeneratorRuntime.js:86:17)
    at Generator._invoke (regeneratorRuntime.js:66:24)
    at Generator.next (regeneratorRuntime.js:117:21)
    at r (asyncToGenerator.js:3:20)
    at s (asyncToGenerator.js:25:9)
overrideMethod @ react_devtools_backend.js:4012
onError @ query.js:356
h @ retryer.js:67
(anonymous) @ retryer.js:132
Promise.catch (async)
l @ retryer.js:116
c @ retryer.js:156
t.fetch @ query.js:330
n.fetchOptimistic @ queryObserver.js:180
(anonymous) @ useBaseQuery.js:84
A @ useQuery.js:7
o @ useSuspenseQuery.ts:19
O @ useConnectionHook.tsx:243
le @ AllConnectionsPage.tsx:23
sa @ react-dom.production.min.js:157
Gs @ react-dom.production.min.js:267
Au @ react-dom.production.min.js:250
Ou @ react-dom.production.min.js:250
Cu @ react-dom.production.min.js:250
_u @ react-dom.production.min.js:243
(anonymous) @ react-dom.production.min.js:123
t.unstable_runWithPriority @ scheduler.production.min.js:18
Vi @ react-dom.production.min.js:122
Ki @ react-dom.production.min.js:123
M @ scheduler.production.min.js:16
b.port1.onmessage @ scheduler.production.min.js:12
2react_devtools_backend.js:4012 Error: Internal Server Error: Duplicate key 99a5b8cc-01ce-4a02-946c-a33d91b3d1b2 (attempted merging values io.airbyte.config.ActorCatalogFetchEvent@3825d1c9[id=<null>,actorId=99a5b8cc-01ce-4a02-946c-a33d91b3d1b2,actorCatalogId=5be6c2c9-692c-467b-a052-56ccc9915c7c,configHash=<null>,connectorVersion=<null>,createdAt=1670444899] and io.airbyte.config.ActorCatalogFetchEvent@4e9e2fd1[id=<null>,actorId=99a5b8cc-01ce-4a02-946c-a33d91b3d1b2,actorCatalogId=e1f51180-5fb3-4f7d-b509-17b6dbcf0675,configHash=<null>,connectorVersion=<null>,createdAt=1670444899])
    at apiOverride.ts:107:9
    at d (regeneratorRuntime.js:86:17)
    at Generator._invoke (regeneratorRuntime.js:66:24)
    at Generator.next (regeneratorRuntime.js:117:21)
    at r (asyncToGenerator.js:3:20)
    at s (asyncToGenerator.js:25:9)
🙏 1
a
I’m struggling to nuke! I set up a local postgres docker to as source and destination. 🤷 any pointers would be appreciated!
s
seems I have to force delete some stuff with docker-compose . I'm gonna try with
docker-compose rm --volumes
💚 1
j
I have been trying for about a month to get it running locally and complete a flow form postgress to postgress (local) as well as a postgress to snowflake. I have been trying the update and change on the connectors and they fail with "something went wrong
s
didnt work for me. Inspecting the docker-compose file to see how state is stored. Looks like there is a special init container in compose that creates a directory on the host:
Copy code
/bin/sh -c "./scripts/create_mount_directories.sh /local_parent ${HACK_LOCAL_ROOT_PARENT} ${LOCAL_ROOT}"
however unclear where those directories are
not sure what the default is for local_root
nvm seems postgres uses a named volume called airbyte_db:
Copy code
docker volume ls
DRIVER    VOLUME NAME
local     1cc95ca61158f395724db0ec0abc7bdb77272fddce643c87e20e134f7ade54a5
local     308d1a56f94a4a186e0cd529e050d07f4b2be2ad9d1755771860e560d8038469
local     airbyte_data
local     airbyte_db
local     airbyte_workspace
local     cddd4c56b95bedc598ba527846150c4c6f825bbe9245d10f9e9efbe9beddd257
local     f49620fe60713afd4446ff5027f9569f2b337c90c642ad74fb80f33d6a430710
so need to manually delete those volumes
I ran
Copy code
docker-compose rm
docker volume rm airbyte_data
docker volume rm airbyte_db
docker volume rm airbyte_workspace
docker-compose up
after that airbyte started working again
e
Hi. I had this yesterday as well for the first time. the way I fixed it since it looked to me as a server error while trying fetch data. I fixed it by closing all docker services and restarting them
s
restarting wouldn't work for me. I had to delete all volumes as well.
s
Hey Sam, happy to hear you were able to able to restart the docker services and clear the volumes as well. Hopefully, this can help other users as well.