https://linen.dev logo
Join Slack
Powered by
Okay, migration looked good; all my connections ca...
# ask-community-for-troubleshooting
p
Okay, migration looked good; all my connections came back. But they don't want to start running; the Sync History says "Pending" and 
Waiting for logs...
The console output shows this error repeating over and over:
Copy code
airbyte-scheduler   | 2021-05-14 00:04:23 ERROR i.a.c.l.Exceptions(swallow):84 - {workspace_app_root=/tmp/workspace/scheduler/logs} - Swallowed error.
airbyte-scheduler   | java.lang.IllegalArgumentException: Job type getSpec is not allowed!
airbyte-scheduler   |   at com.google.common.base.Preconditions.checkArgument(Preconditions.java:142) ~[guava-30.1-jre.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.persistence.job_tracker.JobTracker.lambda$trackSync$3(JobTracker.java:129) ~[io.airbyte.airbyte-scheduler-persistence-0.22.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.commons.lang.Exceptions.swallow(Exceptions.java:82) [io.airbyte-airbyte-commons-0.22.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.persistence.job_tracker.JobTracker.trackSync(JobTracker.java:126) [io.airbyte.airbyte-scheduler-persistence-0.22.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.app.JobSubmitter.trackSubmission(JobSubmitter.java:129) [io.airbyte.airbyte-scheduler-app-0.22.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.app.JobSubmitter.lambda$run$0(JobSubmitter.java:71) [io.airbyte.airbyte-scheduler-app-0.22.3-alpha.jar:?]
airbyte-scheduler   |   at java.util.Optional.ifPresent(Optional.java:176) [?:?]
airbyte-scheduler   |   at io.airbyte.scheduler.app.JobSubmitter.run(JobSubmitter.java:70) [io.airbyte.airbyte-scheduler-app-0.22.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.app.SchedulerApp.lambda$start$0(SchedulerApp.java:137) [io.airbyte.airbyte-scheduler-app-0.22.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   | 2021-05-14 00:04:23 ERROR i.a.s.a.JobSubmitter(run):78 - {workspace_app_root=/tmp/workspace/scheduler/logs} - Job Submitter Error
airbyte-scheduler   | java.lang.IllegalArgumentException: Does not support job type: GET_SPEC
airbyte-scheduler   |   at io.airbyte.scheduler.app.worker_run.TemporalWorkerRunFactory.createSupplier(TemporalWorkerRunFactory.java:78) ~[io.airbyte.airbyte-scheduler-app-0.22.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.app.worker_run.TemporalWorkerRunFactory.create(TemporalWorkerRunFactory.java:55) ~[io.airbyte.airbyte-scheduler-app-0.22.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.app.JobSubmitter.submitJob(JobSubmitter.java:84) ~[io.airbyte.airbyte-scheduler-app-0.22.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.app.JobSubmitter.lambda$run$0(JobSubmitter.java:72) ~[io.airbyte.airbyte-scheduler-app-0.22.3-alpha.jar:?]
airbyte-scheduler   |   at java.util.Optional.ifPresent(Optional.java:176) ~[?:?]
airbyte-scheduler   |   at io.airbyte.scheduler.app.JobSubmitter.run(JobSubmitter.java:70) [io.airbyte.airbyte-scheduler-app-0.22.3-alpha.jar:?]
airbyte-scheduler   |   at io.airbyte.scheduler.app.SchedulerApp.lambda$start$0(SchedulerApp.java:137) [io.airbyte.airbyte-scheduler-app-0.22.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) [?:?]
c
huh. that's not familiar. looking at the code path it seems like we're maybe not handling old job types smartly.
in the UI are you seeing it try to run old jobs?
if so can you hit cancel in the UI.
p
I just created this connection and clicked "Sync" to run it for the first time, and it's stuck.
Or do you mean that the mere existence of another old job could be causing new jobs to not get a chance to start?
Hmm, I deleted all my connections and it's still repeatedly throwing the same error.
Is there any way to see what jobs are running/pending? I'm looking for a way to 
psql
into the local database but not finding any.
c
Or do you mean that the mere existence of another old job could be causing new jobs to not get a chance to start?
yeah. this is my guess.
you should be able to 
psql
into the db with:
Copy code
docker exec -ti <container name> psql -U docker -d airbyte
I think what we want to do in this case is set any job that's not succeeded, cancelled, or failed, to cancelled
you can get those jobs with this query
Copy code
SELECT * FROM jobs where status NOT IN ('succeeded', 'cancelled', 'failed');
I think running this query should then set them all to cancelled
Copy code
UPDATE jobs set status='cancelled' where status NOT IN ('succeeded', 'cancelled', 'failed');
p
I didn't see this so I ended up wiping and reinstalling Airbyte from scratch.
Thanks for the help though—I'm sure knowing the Postgres login info will come in handy in the future. Is it in the docs somewhere?
c
it's not but let me add it!
6 Views
Open in Slack
PreviousNext
Powered by