You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The check_connector_status_running isn't properly parsing whether the connector is running, causing the start script to timeout. Same problem with host_check_schema_registered. The solution is to add the -T option to the docker-compose exec commands to disable teletype so the output is properly sent as stdout to the jq command. See this stackoverflow comment.
Here is an example where start.sh times out while retrying:
Start streaming from the Wikipedia SSE source connector:
...
{"name":"wikipedia-sse","connector":{"state":"RUNNING","worker_id":"connect:8083"},"tasks":[{"id":0,"state":"RUNNING","worker_id":"connect:8083"}],"type":"source"}
Troubleshooting
After adding the -T flag to the various docker-compose exec commands in functions.sh fixed the issue and CP Demo was able to start normally. PR incoming.
Environment
GitHub branch: [e.g. 7.0.1-post]
Operating System: Ubuntu 20.04
Version of Docker: 20.10.12
Version of Docker Compose: 2.2.3
The text was updated successfully, but these errors were encountered:
Description
The
check_connector_status_running
isn't properly parsing whether the connector is running, causing the start script to timeout. Same problem withhost_check_schema_registered
. The solution is to add the-T
option to thedocker-compose exec
commands to disable teletype so the output is properly sent as stdout to thejq
command. See this stackoverflow comment.Here is an example where start.sh times out while retrying:
Troubleshooting
After adding the
-T
flag to the variousdocker-compose exec
commands in functions.sh fixed the issue and CP Demo was able to start normally. PR incoming.Environment
7.0.1-post
]The text was updated successfully, but these errors were encountered: