-
Notifications
You must be signed in to change notification settings - Fork 51
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
TORQUE trouble #149
Comments
Looks like the system is not set up properly. Can you submit and run jobs manually? |
Pretty much. For jobs that do not depend on other jobs (as opposed to drake with the future-powered parallel backend), the following
Then the job hangs in the
I was just using a simple |
So the manual job also gets stuch in the E state (E for exiting)? Then this is a configuration issue. |
Seems about right, I just wish I knew what the right configuration was. |
I am having trouble running
batchtools
jobs on a local installation of TORQUE on Ubuntu 16.04. I think TORQUE is working because the followingtest.pbs
produces the expected output.However, all my jobs hang in the
E
state. For example, the following R script waits indefinitely.In my case, the console message of
wait_for_jobs()
does not match
qstat
, which shows jobs hanging in theE
state.I am using the @HenrikBengtsson's torque.tmpl from future.batchtools.
Related: see my Stack Overflow post here and HenrikBengtsson/future.batchtools#12.
The text was updated successfully, but these errors were encountered: