Skip to content
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

error in running pipeline with singularity #121

Closed
nilesh-tawari opened this issue Nov 21, 2018 · 6 comments
Closed

error in running pipeline with singularity #121

nilesh-tawari opened this issue Nov 21, 2018 · 6 comments
Labels
duplicate This issue or pull request already exists

Comments

@nilesh-tawari
Copy link

Hi, Thanks for the wonderful pipeline.
I am trying to run pipeline first time but i am getting error.
Below is my command to run pipeline:

nextflow run nf-core/rnaseq --reads '*6206911_{1,2}.fastq.gz' --genome CanFam3.1 --saveReference --saveAlignedIntermediates  -with-singularity 
/hpcn/users/nil/00_pipelines/nfcore-rnaseq-1.1.img

I am getting error as,

ERROR ~ Error executing process > 'fastqc (SRR)'

Caused by:
  Process `fastqc (SRR)` terminated with an error exit status (127)

Command executed:

  fastqc -q SRR6206911_1.fastq.gz SRR6206911_2.fastq.gz

Command exit status:
  127

Command output:
  (empty)

Command error:
  /bin/bash: line 0: cd: /hpcn/users/nil/test/RNAseq-nf/work/b1/39c36ab709e094aba99fff7bec1140: No such file or directory
  /bin/bash: .command.stub: No such file or directory

Work dir:
  /hpcn/users/nil/test/RNAseq-nf/work/b1/39c36ab709e094aba99fff7bec1140

Tip: view the complete command output by changing to the process work dir and entering the command `cat .command.out`

 -- Check '.nextflow.log' file for details
[d8/2362b9] NOTE: Process `get_software_versions` terminated with an error exit status (127) -- Error is ignored
[nfcore/rnaseq] Pipeline Complete

Complete .nextflow.log file is attached herein.
.nextflow.log
Any suggestion what is going wrong? Please let me know if further information needed from my side.
Thanks,
-Nilesh

@ewels ewels added the duplicate This issue or pull request already exists label Nov 21, 2018
@ewels
Copy link
Member

ewels commented Nov 21, 2018

Duplicate of #113, fix in pull request #116

@nilesh-tawari - Thanks for reporting this. We'd seen the same error recently too and have hopefully just merged in a change to the pipeline that fixes the problem.

The fixed code is now available in the dev version of the pipeline and will be released soon. Until then, you can run the development version of the code by adding -r dev to your nextflow run command. Note that you will have to pull an updated singularity container too, with the dev tag: docker://nfcore/rnaseq:dev

I think we're overdue a new release for this pipeline, so an updated stable release should hopefully be ready soon.

Phil

@ewels ewels closed this as completed Nov 21, 2018
@nilesh-tawari
Copy link
Author

@ewels
Hi Phil thanks for the prompt reply. I tried the dev version, still I am getting same error. Below are the commands I used,

singularity pull docker://nfcore/rnaseq:dev

Run dev version

nextflow run nf-core/rnaseq --reads '*6206911_{1,2}.fastq.gz' --genome CanFam3.1 --saveReference --saveAlignedIntermediates -with-singularity rnaseq-dev.simg -profile standard,singularity -r dev

following version was used

Launching `nf-core/rnaseq` [adoring_lichterman] - revision: 90b42ca77e [dev]

I am missing something?
Thanks for the support.
-Nilesh

@ewels
Copy link
Member

ewels commented Nov 21, 2018

@nf-core/core - any ideas?

@nilesh-tawari we're really close to pushing the release, so maybe we can just wait for that and try again if that's ok.

Phil

@apeltzer
Copy link
Member

How is your Singularity configured in general? Sounds a bit like the path is not accessible from inside the container, maybe a bind-path issue?

@nilesh-tawari
Copy link
Author

How is your Singularity configured in general? Sounds a bit like the path is not accessible from inside the container, maybe a bind-path issue?

@apeltzer
Thanks, yes it seems the bind-path is issue. Singularity is installed system wide, I can use from as,

nil@aq-login-0001 $ singularity --version
2.5.2-dist

Can you suggest possible way to debug?
Thanks,
-Nilesh

@apeltzer
Copy link
Member

You could edit the /etc/singularity.conf and try to add bind paths for your cluster system and/or auto-mounts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants