Hey team, I have been working with <@U04KJAWV2MS> ...
# help-connector-development
r
Hey team, I have been working with @Francesco F on an Aircall Connector via the Connector builder UI, and he has gotten stuck loading it into the platform. Can you provide some thoughts on what else to check here? @Francesco F can you upload a copy of your YAML?
@Francesco F do you have the server logs for this? That would have the more informative error message so we can try to get to the bottom of it.
f
hey @Ryan (Airbyte), thanks for starting this thread. Please find attached my YAML file. Do you know where I could get the server logs specifically from there?
gratitude thank you 1
r
You can find that under settings/configuration
f
I am currently not able to do that. Maybe because I am re-trying to load the info as per your screenshot above? I will let you know if I am able to download the Server Logs as soon as the loading ends
Ok, it just finished now with the same
non-json response
response error, but I am still not able to download the Server Logs unfortunately
m
@Francesco F are’nt you able to download the logs right?
can you open a terminal and type
docker logs airbyte-server > server.logs
and share the logs
f
I get
-bash: server.logs: Permission denied
When trying that command and still not able to download the logs on the UI
I've tried relaunching the terminal and now it runs, but it doesn't seem to give any result? 🤔
image.png
@Marcos Marx (Airbyte)
m
It should generate a file
Ohh, maybe try only
docker logs airbyte-server
f
It gives a lot lines of code, but no specific file
that I can see
m
maybe try to find a error line
f
Hmm here it is: 2023-02-15 192035 ERROR i.m.h.s.RouteExecutor(logException):444 - Unexpected error occurred: Could not find file
😭 2
I'll need to disconnect in 5 mins, but let me know if there is a way we can troubleshoot this at some point in the next days maybe?
m
Of course, I’ll try to add a custom connector in my side too
Thanks for entering the huddle!
f
Thank you!
Hey @Marcos Marx (Airbyte), sorry I was just wondering if you had managed to replicate the error on your end?