-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Spawner failed to start on PBS cluster #1081
Comments
cc @mbmilligan @zonca any idea for a cause for batchspawner to be failing to set env variables? |
It would be helpful if we could see the configuration file as well and let us know the Torque version being used. My guess is that either you customized the submit script (as most sites will) and omitted the keepvars line, or else your version of Torque uses a different option for passing environment variables into the job environment. |
@minrk actually I have the same problem on Comet, I fixed it with this commit: I thought it was something wrong with my environment but it looks like it might be a larger issue. |
@mbmilligan You pointed me in the right direction. I was missing the PBS -V option. @zonca I was going through your commits and did run into this. Fortunately, I cloned your git well after that commit date. At this point in time, the issue as been resolved. Thank you everyone for your help! |
@krak3nnn
|
How to reproduce the issue
Install the batchspawner plug-in and specify the Torque class.
What you expected to happen
After authentication, submit a single user notebook to the cluster and relay back the hub.
What actually happens
Job gets submitted and job id is seen in qstat but Jupyterhub returns this error:
"JUPYTERHUB_API_TOKEN env is required to run jupyterhub-singleuser. Did you launch it manually?"
Share what version of JupyterHub you are using
Jupyterhub 0.7.2
batchspawner 0.0.1.dev0
The text was updated successfully, but these errors were encountered: