-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Funnel responds with 'Closed explicitly' #611
Comments
Funnel wasn't handling mongo sessions properly. I'm guessing the session was becoming stale and was being closed by the mongo server. Try the fix referenced in the PR above. |
The new version does not seem to work properly. Using the previous version (v0.9.0 from DockerHub) which eventually gets to the 'Closed explicitly' state, the jobs are submitted as expected and go to states QUEUED and RUNNING etc |
The changes I made shouldn't have affected jobs being submitted to batch. Nonetheless I found a spot where I wasn't logging a potential error in the CreateTask method. I pushed up a new commit to that branch that should provide this missing error logging. |
Thanks, there is still the same problem
Thanks |
Are you running your funnel server in a docker container? If so, I think the problem may have been with the base image I was using. Try rebuilding the container ( |
I am using it in an image, but I compiled it myself.
Nevertheless, I will try your suggestion and let you know |
Ah ok, I think the source of the error is that the ubuntu:18.04 image doesn't com with ca-certificates installed. See http://vinceyuan.github.io/solving-ssl-root-certificates/ and https://stackoverflow.com/questions/45388934/how-do-i-make-an-https-call-in-a-busybox-docker-container-running-go |
Perfect, thanks for the pointer. |
For completion the dockerfile is now:
|
Hi,
I am getting the following message in the funnel logs, and neither command line requests nor the web interface work
When I try on the command line
The same queries used to work a day ago. If I restart the server it works, but eventually ends up in this state.
What does this mean? and what causes it?
Is there any configuration option that needs to be considered?
The funnel server is interacting with mongodb (located on a different server), and submits jobs to AWS batch.
Thanks
The text was updated successfully, but these errors were encountered: