The exit status of the task that caused the workflow execution to fail was: 1.
The full error message was:
Error executing process > 'NFCORE_CHIPSEQ:CHIPSEQ:MULTIQC'
Caused by:
Process `NFCORE_CHIPSEQ:CHIPSEQ:MULTIQC` terminated with an error exit status (1)
Command executed:
multiqc \
-f \
\
\
.
cat <<-END_VERSIONS > versions.yml
"NFCORE_CHIPSEQ:CHIPSEQ:MULTIQC":
multiqc: $( multiqc --version | sed -e "s/multiqc, version //g" )
END_VERSIONS
Command exit status:
1
Command output:
--no-mount strings disable one or more 'mount xxx'
options set in apptainer.conf and/or
specify absolute destination path to
disable a bind path entry, or
'bind-paths' to disable all bind
path entries.
--no-pid do not run container in a new PID
namespace
--no-privs drop all privileges from root user
in container)
--no-umask do not propagate umask to the
container, set default 0022 umask
--nv enable Nvidia support
--nvccli use nvidia-container-cli for GPU
setup (experimental)
--oom-kill-disable Disable OOM killer
-o, --overlay strings use an overlayFS image for
persistent data storage or as
read-only layer of container
--passphrase prompt for an encryption passphrase
--pem-path string enter an path to a PEM formatted RSA
key for an encrypted container
-p, --pid run container in a new PID namespace
--pids-limit int Limit number of container PIDs, use
-1 for unlimited
--rocm enable experimental Rocm support
-S, --scratch strings include a scratch directory within
the container that is linked to a
temporary dir (use -W to force location)
--security strings enable security features (SELinux,
Apparmor, Seccomp)
--sharens share the namespace and image with
other containers launched from the
same parent process
--unsquash Convert SIF file to temporary
sandbox before running
-u, --userns run container in a new user namespace
--uts run container in a new UTS namespace
-W, --workdir string working directory to be used for
/tmp, /var/tmp and $HOME (if
-c/--contain was also used)
-w, --writable by default all Apptainer containers
are available as read only. This
option makes the file system
accessible as read/write.
--writable-tmpfs makes the file system accessible as
read-write with non persistent data
(with overlay support only)
Run 'apptainer --help' for more detailed usage information.
Command error:
--no-mount strings disable one or more 'mount xxx'
options set in apptainer.conf and/or
specify absolute destination path to
disable a bind path entry, or
'bind-paths' to disable all bind
path entries.
--no-pid do not run container in a new PID
namespace
--no-privs drop all privileges from root user
in container)
--no-umask do not propagate umask to the
container, set default 0022 umask
--nv enable Nvidia support
--nvccli use nvidia-container-cli for GPU
setup (experimental)
--oom-kill-disable Disable OOM killer
-o, --overlay strings use an overlayFS image for
persistent data storage or as
read-only layer of container
--passphrase prompt for an encryption passphrase
--pem-path string enter an path to a PEM formatted RSA
key for an encrypted container
-p, --pid run container in a new PID namespace
--pids-limit int Limit number of container PIDs, use
-1 for unlimited
--rocm enable experimental Rocm support
-S, --scratch strings include a scratch directory within
the container that is linked to a
temporary dir (use -W to force location)
--security strings enable security features (SELinux,
Apparmor, Seccomp)
--sharens share the namespace and image with
other containers launched from the
same parent process
--unsquash Convert SIF file to temporary
sandbox before running
-u, --userns run container in a new user namespace
--uts run container in a new UTS namespace
-W, --workdir string working directory to be used for
/tmp, /var/tmp and $HOME (if
-c/--contain was also used)
-w, --writable by default all Apptainer containers
are available as read only. This
option makes the file system
accessible as read/write.
--writable-tmpfs makes the file system accessible as
read-write with non persistent data
(with overlay support only)
Run 'apptainer --help' for more detailed usage information.
Work dir:
/abyss/gibcus/gibcus_mnt_genomics/basespace/LY_Chip-seq/work/60/1915c2595de3bfa32d008b99e2fdf1
Container:
/abyss/gibcus/gibcus_mnt_genomics/basespace/LY_Chip-seq/work/singularity/depot.galaxyproject.org-singularity-multiqc-1.23--pyhdfd78af_0.img
Tip: you can replicate the issue by changing to the process work dir and entering the command `bash .command.run`
nextflow run nf-core/chipseq -r 2.1.0 --input ./20250718_ChIP.csv --outdir ./results --genome GRCh38 --read_length 150 --narrow_peak -resume -profile custom_singularity23b304ebac3425a89ad32293fc2c277e81d6e63f-b074-4ac1-b86f-c35fa983b604https://github.com/nf-core/chipseq, revision 2.1.0 (commit hash 76e2382b6d443db4dc2396e6831d1243256d80b0)These plots give an overview of the distribution of resource usage for each process.
This table shows information about each task in the workflow. Use the search box on the right to filter rows for specific values. Clicking headers will sort the table by that value and scrolling side to side will reveal more columns.