Nextflow stalls after version check

Hello,
I have run the RNA-seq pipeline in offline mode multiple times with success but after the HPC was updated, the process stalls after outputting “Nextflow 24.10.5 is available - Please consider updating your version to it”.
My version is 24.10.1.5930.
The only output file I get shows the time started, and the command used and that is all.
If I am remembering correctly, Since I set export NXF_OFFLINE=TRUE, there shouldn’t be any version checking involved.
I tried running nextflow run hello with NXF_OFFLINE=FALSE and I get the same problem. It outputs the same “Nextflow 24.10.5 is available - Please consider updating your version to it” as its only log.

Edit: I updated Nextflow to the newest version but I am still getting stalled after running the command.

Hi @Scheon1

How are you setting the NXF_OFFLINE environment variable? Check what I did below:

nextflow run hello

NXF_OFFLINE=true nextflow run hello

As you can see, it’s picking up my NXF_OFFLINE=true. Maybe in your case it has something to do with the way you’re setting the environment variable.

image

I tried running your code but it still isn’t giving me any output now that I have updated Nextflow.
image

This is the only output running NXF_OFFLINE=true nextflow run hello

I noticed that running nextflow produces these ghost files that are “hidden” but cannot be opened, deleted or interacted.
image

Please run again with the following command:

NXF_OFFLINE=TRUE nextflow -trace nextflow run hello

After that, please share the .nextflow.log file.

.nextflow.log (95 Bytes)
I ran the code and this is the resulting .nextflow.log

Hi @Scheon1

Could you please share the output of nextflow info?

Also try running a local pipeline with the NXF_OFFLINE=TRUE nextflow -trace nextflow run e.g.:

NXF_OFFLINE=TRUE nextflow -trace nextflow run main.nf

Make sure you have a main.nf Nextflow script file in the current directory). Then share the . nextflow.log file please

The next line that usually gets logged is the Nextflow version. So it made it past the version check but got stuck somewhere between these two points: