-
Notifications
You must be signed in to change notification settings - Fork 18
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
Cannot run on lsf system, not sure if exit code 127 is the reason #196
Comments
Also encountering the same issue. Would appreciate any help regarding this. Thanks. |
Can you edit the conf like the following (adding -o and -e to redirect error logs to local files) and try again?
Define |
Hi! I am also dealing with this exact issue on an LSF cluster. I edited the conf file to include the line:
as suggested by leepc12. The output and error files are as follows: stderr.txt
stdout.txt
Thank you so much for any insight you might have as to how to fix this! Best, |
I'm truly sorry to hear about the difficulties you're experiencing with running CAPER. Unfortunately, due to our current bandwidth and personnel limitations, we are unable to provide immediate attention to resolving this particular issue. |
No problem! Thanks for letting us know. |
Bump - I am experiencing this same issue. Error logs show calls to supposedly generated shell script that system checks for and finds does not exist... |
Hi,
when I tried to run caper with encode-atac-pipeline, I could see the job was submitted to the lsf system, but the job disappear immediately without any reports.
when I looked into the detailed record of the job, I could find an "exit code 127", and I think maybe the shell script was never been created in the home directory, but I have no ideas how to solve it. Here are the command and the job reports:
Here is the config file for caper:
And here is the information about the software and environment:
Thanks for responding!
The text was updated successfully, but these errors were encountered: