https://linen.dev logo
Join Slack
Powered by
I’ve upgraded to 0.50.18 but now my Airbyte isn’t ...
# replication-ask-ai
d
I’ve upgraded to 0.50.18 but now my Airbyte isn’t picking up sources, destinations or connections from my external 
airbytedb
- I am not sure where to start the debugging as nothing has failed. I ran 
docker exec -it
on 
airbyte/db:0.50.18
container to psql to airbytedb, but they don’t show up. The connection do show up externally
✅ 1
k
Based on the information provided in the extracts, here are some steps you can take to debug your issue: 1. Check the Database Connection: Ensure that the credentials specified in the 
.env
file are correct. By default, these values are:
Copy code
bash DATABASE_USER=docker   DATABASE_PASSWORD=docker   DATABASE_DB=airbyte
If you have overridden these defaults, you will need to substitute them accordingly. You can access the database instance using 
psql
with the following command:
Copy code
bash docker exec -ti airbyte-db psql -U docker -d airbyte
2. Check the Database Tables: The following tables should be present in your database: 
workspace
, 
actor_definition
, 
actor
, 
actor_oauth_parameter
, 
operation
, 
connection
, 
connection_operation
, 
state
. If any of these tables are missing, it might be the reason why your sources, destinations, or connections are not showing up. 3. Check the Logs: Airbyte logs the resource requirements as part of the job logs as containers are created. Both source and destination containers are logged. If a job is running out-of-memory, you can navigate to the Job in the UI, and look for the log to confirm the right configuration is being detected. 4. Check for Errors: Look for any error messages in the logs or in the UI that might indicate what the issue is. If you're still having trouble, you might want to consider reaching out to the Airbyte community on [Slack](https://airbytehq.slack.com/archives/C021JANJ6TY/) or [Airbyte's discussion forum](https://discuss.airbyte.io) for further assistance. Sources: - [Configuring the Airbyte Database](https://docs.airbyte.com/operator-guides/configuring-airbyte-db) - [Configuring Connector Resources](https://docs.airbyte.com/operator-guides/configuring-connector-resources)
d
@kapa.ai running 
\dt
says 
Did not find any relations.
k
The 
\dt
command in PostgreSQL is used to list all tables in the current database. If you're getting the message 
Did not find any relations
, it means there are no tables in the current database you're connected to. In the context of Airbyte, you would typically use this command to view the tables in your destination database after a data synchronization operation. For example, in the [Incremental Data Synchronization](https://airbyte.com/tutorials/incremental-data-synchronization) and [Full Data Synchronization](https://airbyte.com/tutorials/full-data-synchronization) tutorials, the 
\dt
command is used to list the tables that have been created in the destination Postgres database after a sync operation. If you're not seeing any tables, it could be because: 1. The data synchronization operation has not completed yet. Make sure that the sync operation has completed successfully before trying to list the tables. 2. You're connected to the wrong database. Make sure you're connected to the correct Postgres database where Airbyte is writing the data. 3. There was an error during the data synchronization operation. Check the logs for any error messages. If you're still having trouble, you might want to ask for help in the [Airbyte Slack community](https://airbytehq.slack.com) or on the [Airbyte discussion forum](https://discuss.airbyte.io).
d
@kapa.ai I am told I need to switch to a different ‘workspace’. I am given a UUID for it. How does one do that?
k
A message from kapa.ai
New message text here
d
@kapa.ai thank you for your help I got it now
k
A message from kapa.ai
New message text here
d
@kapa.ai How do I update a connector? Does that happen automatically with an upgrade?
k
A message from kapa.ai
When Airbyte is upgraded, it attempts to upgrade some connector versions following these rules: 1. If a connector is not used, it will be upgraded to the latest version. 2. If a connector is used, it will NOT be upgraded to avoid disrupting working workflows. If you want to upgrade a connector, you need to do so manually in the settings page in the webapp [source](https://docs.airbyte.com/operator-guides/upgrading-airbyte). If you're updating an existing connector, the steps are: 1. Iterate on the connector to make the needed changes. 2. Run tests. 3. Add any needed docs updates. 4. Create a PR to get the connector published [source](https://docs.airbyte.com/connector-development). Remember to follow the best practices for maintaining connectors. Once a connector has been published for use within Airbyte, special care must be taken to account for the customer impact of updates to the connector [source](https://docs.airbyte.com/connector-development/best-practices). Also, note that the Configuration API caches connector specifications. If you update the specification of a connector and need to clear this cache so the API / UI picks up the change, you can go to the Admin page in the UI and update the version of the connector or restart the server from your local 
airbyte-platform
repository [source](https://docs.airbyte.com/contributing-to-airbyte/resources/developing-locally). If you need help from the Airbyte team for your upgrades, they offer premium support to their open-source users. You can [talk to their team](https://airbyte.com/talk-to-sales-premium-support) to get access to it.
d
@kapa.ai Got it thanks
k
A message from kapa.ai
You're welcome! If you have any more questions in the future, don't hesitate to ask. Happy data integrating with Airbyte!
d
@kapa.ai Hi, I’m getting Error: Failed to validate 
config/dynamicconfig/development.yaml
, permission denied. This is a reference to the file mentioned in the 
docker-compose.yaml
, this time, not the one that was missing, and I added by hand.
k
A message from kapa.ai
@Daniel E That's a great question, but unfortunately I am only capable of responding to a maximum of five questions per thread. Don't hesitate to create a new thread for any further questions you have though. I'm here to help!
2 Views
Open in Slack
PreviousNext
Powered by