- Is this your first time deploying Airbyte?: Yes
- OS Version / Instance: Amazon Linux
- Memory / Disk: you can use something like 32gb / 100 gb
- Deployment: Are you using Docker or Kubernetes deployment? no
- Airbyte Version: What version are you using now? latest
- Source name/version: Salesforce
- Destination name/version: Redshift
- Step: The issue is happening during sync, creating the connection or a new source? None of the above
when I look at the docker logs there are a lot of error messages, happening every few seconds, when there’s no work going on and the container is just sitting there.
Is there something I can do to reduce the noise in the log files? This one error message is about half of the total log file:
docker logs airbyte-server > server.log
2023-02-01 01:02:20 ERROR i.a.s.h.JobHistoryHandler(listJobsFor):138 - Missing stats for job 17 attempt 0
2023-02-01 01:02:22 ERROR i.a.s.h.JobHistoryHandler(listJobsFor):138 - Missing stats for job 17 attempt 0
2023-02-01 01:02:25 ERROR i.a.s.h.JobHistoryHandler(listJobsFor):138 - Missing stats for job 17 attempt 0
2023-02-01 01:02:28 ERROR i.a.s.h.JobHistoryHandler(listJobsFor):138 - Missing stats for job 17 attempt 0
2023-02-01 01:02:31 ERROR i.a.s.h.JobHistoryHandler(listJobsFor):138 - Missing stats for job 17 attempt 0
grep "JobHistoryHandler" server.log | wc
7392 88704 853534
13190 108690 1616145 server.log
Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:
- It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
- Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
- Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
- We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.
Thank you for your time and attention.
The Community Assistance Team
Hi @josephbrownskilljar, I need to look into this - I know the logs display quite a few errors that are meant as warnings. I’ll get back to you once I find something!