-[nf-core/clipseq] Pipeline completed with errors- Waiting files transfer to complete (1 files) Error executing process > 'get_software_versions' Caused by: Process `get_software_versions` terminated with an error exit status (1) Command executed: echo 1.0.0 > v_pipeline.txt echo 21.10.6 > v_nextflow.txt fastqc --version > v_fastqc.txt multiqc --version > v_multiqc.txt cutadapt --version > v_cutadapt.txt bowtie2 --version > v_bowtie2.txt STAR --version > v_star.txt samtools --version > v_samtools.txt umi_tools --version > v_umi_tools.txt bedtools --version > v_bedtools.txt preseq 2> v_preseq.txt # subread-align -v 2> v_subread.txt bam2fq.py --version > v_rseqc.txt iCount --version > v_icount.txt pureclip --version > v_pureclip.txt Piranha -about 2> v_piranha.txt echo "9" > v_paraclu.txt # Paraclu does not output a version meme -version > v_meme.txt python --version > v_python.txt pygmentize -V > v_pygments.txt pigz --version 2> v_pigz.txt perl -v > v_perl.txt scrape_software_versions.py &> software_versions_mqc.yaml Command exit status: 1 Command output: (empty) Command error: -------------------------------------------------------------------------- A call to mkdir was unable to create the desired directory: Directory: /scratch Error: Read-only file system Please check to ensure you have adequate permissions to perform the desired operation. -------------------------------------------------------------------------- [shbli050:21702] [[0,1],0] ORTE_ERROR_LOG: Error in file util/session_dir.c at line 107 [shbli050:21702] [[0,1],0] ORTE_ERROR_LOG: Error in file util/session_dir.c at line 346 [shbli050:21702] [[0,1],0] ORTE_ERROR_LOG: Error in file ess_singleton_module.c at line 340 -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_session_dir failed --> Returned value Error (-1) instead of ORTE_SUCCESS -------------------------------------------------------------------------- -------------------------------------------------------------------------- It looks like MPI_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): ompi_mpi_init: ompi_rte_init failed --> Returned "Error" (-1) instead of "Success" (0) -------------------------------------------------------------------------- *** An error occurred in MPI_Init *** on a NULL communicator *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, *** and potentially your MPI job) [shbli050:21702] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! Work dir: /data/users/PATH/testPipelineNFCore/workingDir/67/9be1ee51f4ba9283bf1123bbdaa67e Tip: you can try to figure out what's wrong by changing to the process work dir and showing the script file named `.command.sh`