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

Some errors while processing a QC HeLa file #100

Open
rolivella opened this issue Oct 21, 2020 · 1 comment
Open

Some errors while processing a QC HeLa file #100

rolivella opened this issue Oct 21, 2020 · 1 comment
Labels
bug Something isn't working low-priority Low priority issue

Comments

@rolivella
Copy link

Hi,

Congratulations for the 1.0.0 release! I'm testing it with a QC HeLa sample but I got some errors. Could you help me? Thanks!

N E X T F L O W  ~  version 20.07.1
Launching `nf-core/proteomicslfq` [nauseous_perlman] - revision: eb5f7a004c [dev]
NOTE: Your local project version looks outdated - a different revision is available in the remote repository [43c77e50c9]
----------------------------------------------------
                                        ,--./,-.
        ___     __   __   __   ___     /,-._.--~'
  |\ | |__  __ /  ` /  \ |__) |__         }  {
  | \| |       \__, \__/ |  \ |___     \`-._,-`-,
                                        `._,._,'
  nf-core/proteomicslfq v1.0.0
----------------------------------------------------

Pipeline Release  : dev
Run Name          : nauseous_perlman
Max Resources     : 30 memory, 4 cpus, 10h time per job
Container         : singularity - nfcore/proteomicslfq:1.0.0
Output dir        : ./results
Launch dir        : /nfs/users/pr/qsample/test/proteomicslfq
Working dir       : /nfs/users/pr/qsample/test/proteomicslfq/work
Script dir        : /users/pr/qsample/.nextflow/assets/nf-core/proteomicslfq
User              : qsample
Config Profile    : singularity
Config Files      : /users/pr/qsample/.nextflow/assets/nf-core/proteomicslfq/nextflow.config, /nfs/users/pr/qsample/test/proteomicslfq/nextflow.config
----------------------------------------------------
[ca/d4dfbb] Submitted process > raw_file_conversion (1)
[bb/ba5b58] Submitted process > output_documentation
[be/5ec9e1] Submitted process > get_software_versions
Error executing process > 'output_documentation'

Caused by:
  Process `output_documentation` terminated with an error exit status (255)

Command executed:

  markdown_to_html.py output.md -o results_description.html

Command exit status:
  255

Command output:
  (empty)

Command wrapper:
  /usr/bin/id: error while loading shared libraries: libdl.so.2: failed to map segment from shared object: Cannot allocate memory
  /usr/bin/id: error while loading shared libraries: libdl.so.2: failed to map segment from shared object: Cannot allocate memory
  /usr/bin/id: error while loading shared libraries: libdl.so.2: failed to map segment from shared object: Cannot allocate memory
  /bin/ps: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Cannot allocate memory
  /bin/basename: missing operand
  Try '/bin/basename --help' for more information.
  id: error while loading shared libraries: libdl.so.2: failed to map segment from shared object: Cannot allocate memory
  /usr/bin/id: error while loading shared libraries: libdl.so.2: failed to map segment from shared object: Cannot allocate memory
  /etc/profile.d/vim.sh: line 4: [: : integer expression expected
  /usr/bin/lua: error while loading shared libraries: libm.so.6: failed to map segment from shared object: Cannot allocate memory
  /usr/bin/lua: error while loading shared libraries: libm.so.6: failed to map segment from shared object: Cannot allocate memory
  /usr/bin/lua: error while loading shared libraries: libm.so.6: failed to map segment from shared object: Cannot allocate memory
  /usr/bin/ps: error while loading shared libraries: libc.so.6: failed to map segment from shared object: Cannot allocate memory
  /usr/bin/basename: missing operand
  Try '/usr/bin/basename --help' for more information.
  mkfifo: error while loading shared libraries: libdl.so.2: failed to map segment from shared object: Cannot allocate memory
  mkfifo: error while loading shared libraries: libdl.so.2: failed to map segment from shared object: Cannot allocate memory
  /usr/share/univage/soldierantcluster/spool/node-hp0304/job_scripts/64482065: line 305: /dev/shm/nxf.5lNQ9ZrURa/.command.out: No such file or directory
  /usr/share/univage/soldierantcluster/spool/node-hp0304/job_scripts/64482065: line 307: /dev/shm/nxf.5lNQ9ZrURa/.command.err: No such file or directory

Work dir:
  /nfs/users/pr/qsample/test/proteomicslfq/work/bb/ba5b58cd1a499ded63b9395ebfd8ae

Tip: you can replicate the issue by changing to the process work dir and entering the command `bash .command.run`
@jpfeuffer
Copy link
Collaborator

jpfeuffer commented Oct 21, 2020

Hi! And thank you ;)

It is unfortunate, that it did not work out-of-the-box although we tried hard to design it like that. However, your specific problem sounds more like a complication between the containerization software and your user virtual memory space. It fails in a step which uses almost no memory at all and that is present in all nf-core pipelines.
Did the test data or other data work?
Things you could try are:

  • to run another nf-core pipeline with its test profile -profile test,singularity to completely rule out pipeline specific problems.
  • test the singularity+container setup by running some things in the container through singularity shell proteomicslfq-1.0.0.img/sif in your singularity cache folder (usually work/singularity I think).

@ypriverol ypriverol added bug Something isn't working low-priority Low priority issue labels Nov 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working low-priority Low priority issue
Projects
None yet
Development

No branches or pull requests

3 participants