Search code examples
sshamazon-ec2broken-pipe

What happens to a process in an EC2 instance when I get a 'Broken Pipe' error on ssh?

I am using some EC2 instances to run some large jobs I can not run locally. The issue I am seeing is that after a while (X hours since the process started) my connection on my shell gives me a broken pipe error

ubuntu@ip-10-122-xxx-xxx:~/stratto/ode$ Write failed: Broken pipe

The instance is still there because I can reconnect with no problems, but how can I reconnect and get back at seeing the logs of the process as before the 'Broken Pipe'

Any tip much appreciated, Thanks!

Solution

  • Redirect your output to a file and then run the program "nohup ..." to ensure the disconnect doesn't kill it. Use "tail -f" to monitor the redirected file.

    Note: Originally said to use "tee" but that won't work. I think a straight redirect and then tail on the file works.