Pipeline could not start

[MPourjam]

Describe the bug After selecting files and running the analysis, it shows 'Waiting for logs' and at the bottom of page it says 'Pipeline could not start'

Screenshots

System

• Are you using Windows or Linux? Windows

[zsewa]

Could you please try which distros show up when running wsl -l -v.

[zsewa]

I managed to replicate this(?) on my Windows machine. When opening the developer console while running this, I get the following logs:

Logs like this are also raised when starting the WSL distribution from the command line, and the command returns immediately:

PS C:\Users\Zeno> wsl -d tum-core-facility-microbiome.tic-pipeline_0.3.0
<3>WSL (9) ERROR: CreateProcessParseCommon:711: Failed to translate C:\Users\Zeno
<3>WSL (9) ERROR: CreateProcessParseCommon:757: getpwuid(0) failed 2
<3>WSL (9) ERROR: UtilTranslatePathList:2866: Failed to translate C:\WINDOWS\system32
<3>WSL (9) ERROR: UtilTranslatePathList:2866: Failed to translate C:\WINDOWS
<3>WSL (9) ERROR: UtilTranslatePathList:2866: Failed to translate C:\WINDOWS\System32\Wbem
<3>WSL (9) ERROR: UtilTranslatePathList:2866: Failed to translate C:\WINDOWS\System32\WindowsPowerShell\v1.0\
<3>WSL (9) ERROR: UtilTranslatePathList:2866: Failed to translate C:\WINDOWS\System32\OpenSSH\
<3>WSL (9) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files\nodejs\
<3>WSL (9) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Program Files\Git\cmd
<3>WSL (9) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Zeno\AppData\Local\Microsoft\WindowsApps
<3>WSL (9) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Zeno\AppData\Roaming\npm
<3>WSL (9) ERROR: UtilTranslatePathList:2866: Failed to translate C:\Users\Zeno\AppData\Local\Programs\Microsoft VS Code\bin
Processing fstab with mount -a failed.
Failed to mount C:\, see dmesg for more details.

<3>WSL (9) ERROR: CreateProcessEntryCommon:334: getpwuid(0) failed 2
<3>WSL (9) ERROR: CreateProcessEntryCommon:505: execvpe /bin/sh failed 2
<3>WSL (9) ERROR: CreateProcessEntryCommon:508: Create process not expected to return

A similar issue at AskUbuntu says that using Linux shutdown methods on a WSL2 distribution may cause this. However, it is a slightly different error number (but they seem to change frequently), and the proposed fix (running wsl --shutdown) didn't do the trick in my case. Also, at least the GUI shouldn't cause the problems described in AskUbuntu as it does not use commands like systemctl poweroff|halt|reboot for the shutdown of the distribution, e.g., it does not shut down the distribution explicitly at all using Linux commands.

Running one of the older distributions (v0.1.3) worked fine without raising this issue, so this doesn't seem to be a problem with the WSL setup in general.

[zsewa]

@MPourjam It would be great if you could recheck the affected system if this is also the case. (Running wsl -d tum-core-facility-microbiome.tic-pipeline_0.3.0 and check if the distro starts or fails with errors like this; and running the GUI with developer console open.)

P.S. Sorry, I just saw that you also sent me the developer console output in the chat. As there are no messages like mine, I suppose it is a different issue at the machine where you ran it...

[zsewa]

Tested fixes

• Deleting the distribution and cache files and downloading it again did not work
• Rebuilding the tar and importing this works

P.S. I have rebuild the tar, uploaded it to the server and restarted with the replaced image. After deleting the registered WSL distribution and the cached tar file in Temp (C:\Users\<username>\AppData\Local\Temp), I restarted the application and started a new run, which then succeeded.