https://linen.dev logo
Join Slack
Powered by
Good afternoon! We are making advances, but we are...
# ask-community-for-troubleshooting
m
Good afternoon! We are making advances, but we are stuck now with
Copy code
POST /v1/connections/reset
We are obtaining an error about the 'configId'
Copy code
data: {
      message: 'Could not find configuration for STANDARD_SYNC_OPERATION: [uuid]'
}
Where can I retrieve the proper id? We also receive a similar error on sync-connection query. Thanks in advance
u
this is the connectionId value, the easier way to get this is: the URL in the connection page
https://demo.airbyte.io/connections/73172745-f7e7-435d-bc7b-873fbf837782 in this case the connectionId is 
73172745-f7e7-435d-bc7b-873fbf837782
. you need to get from your connection
other way is use the endpoint 
/v1/connections/list
https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html#post-/v1/connections/list using the default workspaceId {"workspaceId":"5ae6b09b-fdec-41af-aaf7-7d94cfc33ef6"} to retrieve all connections
m
@[DEPRECATED] Marcos Marx thanks for your quick answer. As we are working this flow with no-routes for now, I didn't focus on it.. In fact, we have the 
connections/list
ready, and we query it like this
Copy code
const { data } = await <http://axios.post|axios.post>(airbyteUrls.resetConnection, {
  connectionId
})
Also for list the jobs I find the same problem with the configId field
Copy code
POST /v1/jobs/list
{
  configTypes*: [enum]
  configId*: string
}
u
STANDARD_SYNC_OPERATION
this is a new field... was introducted for custom-dbt! I'll research about it. @Mané Rom what version of Airbyte are you using?
m
let me deploy it at local (we uploaded it to an own server for production)
0.25
let's pull at local and check
pulling from Docker is not working on take 0.26.2-alpha version... I'll see tomorrow (it's late). Thanks for your attention
u
ok! let me updated about any issue
m
Hi @[DEPRECATED] Marcos Marx. I'm getting this error, but I could say that my resources seem updated.. 
ERROR i.a.s.v.VersionMismatchServer(getServer):68 - {workspace_app_root=/tmp/workspace/server/logs} - Version mismatch between 0.26.2-alpha and 0.25.0-alpha.
Why it tells about versionMismatch, if they're 0.26.2 apparently?
u
you need to upgrade
m
okay, It's about the flag -v when I compose-down it.. I forgot it. It seems like this solved it, but now, when I try to do the 
/source_definition_specifications/get
giving a sourceDefinitionId, it responses a 500 error 
data: { message: 'internal server error' }
config: {
url: '<http://localhost:8000/api/v1/source_definition_specifications/get>',
method: 'post',
data: '{"sourceDefinitionId":"71607ba1-c0ac-4799-8049-7f4b90dd50f7"}',
headers: {
Accept: 'application/json, text/plain, */*',
'Content-Type': 'application/json;charset=utf-8',
'User-Agent': 'axios/0.21.1',
'Content-Length': 61
}
response: {
status: 500,
statusText: 'Internal Server Error',
headers: {
server: 'nginx/1.19.10',
date: 'Wed, 23 Jun 2021 14:19:01 GMT',
'content-type': 'application/json',
'content-length': '35',
connection: 'close',
'access-control-allow-origin': '*',
'access-control-allow-headers': 'Origin, Content-Type, Accept, Content-Encoding',
'access-control-allow-methods': 'GET, POST, PUT, DELETE, OPTIONS, HEAD'
},
ERROR i.a.s.RequestLogger(filter):105 - {workspace_app_root=/tmp/workspace/server/logs} - REQ 172.22.0.4 POST 500 /api/v1/source_definition_specifications/get - {"sourceDefinitionId":"71607ba1-c0ac-4799-8049-7f4b90dd50f7"}
u
@Mané Rom is possible to execute the command using the terminal?
Copy code
curl -X POST "<http://localhost:8000/api/v1/source_definitions/get>" \
 -H "Accept: application/json" \
 -H "Content-Type: application/json" \
 -d '{"sourceDefinitionId":"71607ba1-c0ac-4799-8049-7f4b90dd50f7"}'
this will help us discovering where the problem is
m
thx, let me see...
it works perfectly..
u
so probably is something in the payload you send to the server 😞
m
let me check anything again.. can't understand why it's working on our prod-server.. Sorry, I tell you later, thanks for your attention
Nope.. I tested with 0.25v and it's working, but not when I put the 0.26.2-alpha. I'm also sending the proper payload and headers: Error: Request failed with status code 500 
config: {
url: '<http://localhost:8000/api/v1/source_definition_specifications/get>',
method: 'post',
data: '{"sourceDefinitionId":"71607ba1-c0ac-4799-8049-7f4b90dd50f7"}',
headers: {
Accept: 'application/json',
'Content-Type': 'application/json',
'User-Agent': 'axios/0.21.1',
'Content-Length': 61
},
u
🤔 Manuel just checking: when you try to execute the CURL command you executed in the 0.26.2-alpha right?
m
yes, in that case, I opened the bash at project root folder
u
There any endpoint returning? or all are giving 500?
m
these are from postman directly.. 2nd gives a proper response
running docker images screenshot
u
@Mané Rom could you try 
docker logs airbyte-server
to see if there anything there?
maybe remove all fields that doenst belong to original header
only use
Copy code
-H "Accept: application/json" \
 -H "Content-Type: application/json" \
m
this is how I do
Copy code
const { data } = await <http://axios.post|axios.post>(
  airbyteUrls.sourceSpecification,
  {
    sourceDefinitionId
  },
  {
    headers: {
      'Accept': 'application/json',
      'Content-Type': 'application/json'
    }
  }
)
lets try the command.. thank you
it shows 2 errors: 
2021-06-23 17:28:05 ERROR i.a.s.e.UncaughtExceptionMapper(toResponse):42 - {workspace_app_root=/tmp/workspace/server/logs} - Uncaught exception
2021-06-23 17:28:05 ERROR i.a.s.RequestLogger(filter):105 - {workspace_app_root=/tmp/workspace/server/logs} - REQ 172.20.0.3 POST 500 /api/v1/source_definition_specifications/get - {"sourceDefinitionId":"71607ba1-c0ac-4799-8049-7f4b90dd50f7"}
u
@Mané Rom i added the Accept applicatoin/json and Content-Type application/json in Headers tab
please upgrade to latest version
m
it's obvious that I'm having some problem updating. I only can say, thanks for your patience... I hope to have today a more productive day
u
anything you can ping here
m
Thank you so much. I'll try to solve it, and let other mates the chance of your attention, but I aprettiate your labour
What's your opinion about this? docker logs airbyte-server screenshot
u
@Mané Rom looks you are running 0.26.2-alpha, this solve the API request using Postman?
m
Good afternoon @[DEPRECATED] Marcos Marx. The most amazing thing is that it works at postman (1), but from our UI it throws an error on server 
Error: Request failed with status code 422
querying this data (2). Console shows this error message response (3)
u
thats weird...
the Accept shouldnt be 'Accept'?
m
I really thought in that... even if I put with ' ', it sets Accept directly
more specific info error 
2021-06-24 18:52:53 ERROR i.a.s.a.JobScheduler(run):86 - {workspace_app_root=/tmp/workspace/scheduler/logs} - Job Scheduler Error
airbyte-scheduler   | java.lang.RuntimeException: io.airbyte.config.persistence.ConfigNotFoundException: config type: STANDARD_SYNC_OPERATION id: f8c3e6cb-a15a-40e6-aea0-58cc7368b36a
airbyte-scheduler   |   at io.airbyte.scheduler.persistence.job_factory.DefaultSyncJobFactory.create(DefaultSyncJobFactory.java:85) ~[io.airbyte.airbyte-scheduler-persistence-0.26.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.app.JobScheduler.scheduleSyncJobs(JobScheduler.java:98) ~[io.airbyte.airbyte-scheduler-app-0.26.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.app.JobScheduler.run(JobScheduler.java:82) ~[io.airbyte.airbyte-scheduler-app-0.26.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.app.SchedulerApp.lambda$start$0(SchedulerApp.java:145) ~[io.airbyte.airbyte-scheduler-app-0.26.3-alpha.jar:?]
airbyte-scheduler   |   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) [?:?]
airbyte-scheduler   |   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]
airbyte-scheduler   |   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]
airbyte-scheduler   |   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]
airbyte-scheduler   |   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]
airbyte-scheduler   |   at java.lang.Thread.run(Thread.java:832) [?:?]
airbyte-scheduler   | Caused by: io.airbyte.config.persistence.ConfigNotFoundException: config type: STANDARD_SYNC_OPERATION id: f8c3e6cb-a15a-40e6-aea0-58cc7368b36a
airbyte-scheduler   |   at io.airbyte.config.persistence.DefaultConfigPersistence.getConfigInternal(DefaultConfigPersistence.java:87) ~[io.airbyte.airbyte-config-persistence-0.26.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.config.persistence.DefaultConfigPersistence.getConfig(DefaultConfigPersistence.java:64) ~[io.airbyte.airbyte-config-persistence-0.26.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.config.persistence.ConfigRepository.getStandardSyncOperation(ConfigRepository.java:195) ~[io.airbyte.airbyte-config-persistence-0.26.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.persistence.job_factory.DefaultSyncJobFactory.create(DefaultSyncJobFactory.java:71) ~[io.airbyte.airbyte-scheduler-persistence-0.26.3-alpha.jar:?]
u
@Mané Rom can you enter the scheduler container 
docker exec -ti airbyte-scheduler bash
go into 
cd /data/config/STANDARD_SYNC_OPERATION
and execute 
ls
to list all files there?
m
Thank You. Let me check...
inside airbyte-scheduler I only can find /app /client /models /persistence
I cannot believe @[DEPRECATED] Marcos Marx but it seems like I have some few good news 😮 As I erased that 
operationsIds: [uuid(*on-the-fly-from-hell)*]
, it works as before. Here I attach the create-connection flow. Thank you so much for your patience, here is a happy man for your action, thank you very much!
u
octavia thanks you're welcome! but pay attention that probably for destinations like database you need that information
m
I erased for the credentials, I put it again, sorry
u
hahaha, no problem!
m
message has been deleted
yes.. I was going to ask you about the operationIds purpose, but of course, other mates have the right of receive your attention. Thank you so much and at your order 🤠🖖
Of course, feel free to let me some indications or tips about operationsIds field, if not I'll write in the publics channels as I'm doing.
u
But I'll search how and when you need to create them
m
Thank you so much for your help, Awesome good job
Open in Slack
PreviousNext
Powered by