-
Notifications
You must be signed in to change notification settings - Fork 4
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
qsub command failed with exit status: 172 #60
Comments
Are you running on a torque/qsub system or a SLURM system (or indeed another OS)? |
I am running on a torque/qsub system. Which system does RedDog use?
El martes, 18 de diciembre de 2018, d-j-e <[email protected]>
escribió:
… Are you running on a torque/qsub system or a SLURM system (or indeed
another OS)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#60 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Ar2QjJETL5FUOGjmFHIrh_i8PaSf-Z71ks5u6WZLgaJpZM4ZY2Le>
.
--
Lic. Verónica E. Álvarez
Laboratorio de Investigaciones
en Mecanismos de Resistencia a Antibióticos
IMPAM (UBA/CONICET)
Facultad de Medicina
Universidad de Buenos Aires
+54 11 5950-9500 x 2182
|
RedDog is actually 'system neutral'; it is Rubra that controls the job submissions to the relevant queue. Though reddog was originally written on a 'qsub' system so it should have no problems... I cannot find a description of qsub exit status 172 - it is not a 'reserved' code so you may have to seek the help of a local system administrator to work out what the error means. This first step creates all the output directories required for the run, so it might be a permissions error of some kind, but that is only a guess. You could also try raising the issue on the rubra github page. |
Ok, thank you for your suggestions.
Regards.
El mié., 19 dic. 2018 a las 19:23, d-j-e (<[email protected]>)
escribió:
… RedDog is actually 'system neutral'; it is Rubra that controls the job
submissions to the relevant queue. Though reddog was originally written on
a 'qsub' system so it should have no problems...
I cannot find a description of qsub exit status 172 - it is not a
'reserved' code so you may have to seek the help of a local system
administrator to work out what the error means. This first step creates all
the output directories required for the run, so it might be a permissions
error of some kind, but that is only a guess. You could also try raising
the issue on the rubra github page.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#60 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Ar2QjBTylwW4XT2vnHoaZV88S24iR9cXks5u6rxfgaJpZM4ZY2Le>
.
--
Lic. Verónica E. Álvarez
Laboratorio de Investigaciones
en Mecanismos de Resistencia a Antibióticos
IMPAM (UBA/CONICET)
Facultad de Medicina
Universidad de Buenos Aires
+54 11 5950-9500 x 2182
|
Hello, I am running the pipeline and I am getting this error, could you help me? Thanks!
Starting pipeline...
155 jobs to be executed in total
Traceback (most recent call last):
File "/usr/local/bin/rubra", line 11, in
load_entry_point('Rubra==0.1.5', 'console_scripts', 'rubra')()
File "build/bdist.linux-x86_64/egg/rubra/rubra.py", line 66, in main
File "build/bdist.linux-x86_64/egg/ruffus/task.py", line 2680, in pipeline_run
ruffus.ruffus_exceptions.RethrownJobError:
The text was updated successfully, but these errors were encountered: