Closed euhruska closed 5 years ago
Hi Eugen - the issues (pilot fails, fetch fails) might be related. The message Could not detect shell prompt (timeout)
really means exactly that: Some layer attempted to connect to the target host, but could not find a prompt when opening a shell. So, either the connection got stuck in some way completely, or the target system was slow (memory swapping, file system issues, etc) that the shell prompt detection timed out.
I would like to ask you to try once more. If the same problem persists, can you please confirm you can login to the machine interactively? What is the target machine?
Thanks, Andre.
I can login to bluewaters no problem. I restarted the client host and it looks like it works now. Maybe just didn't clean properly on client host side. I will reopen if this happens again
Got an issue with
Could not detect shell prompt (timeout)
, any indications what a timeout happened? Local directory re.session.leonardo.rice.edu.eh22.017910.0004.zipMaybe separate issue, when I fetched the logfiles I got
logiles tarball doesnt exist