-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
client loop: send disconnect: broken pipe; SFTP Failure 4 #90
Comments
If your .bashrc generates any output to the shell, the plugin may fail. You can easily check this by running source ~/.bashrc in a terminal on the server. If no output is generated, it should be fine, otherwise identify the lines generating the output and comment them out. In any case try caffe --help and caffe-unet --help Both should output a help message from shell. If this is the case, ensure that caffe is not installed via the ubuntu package manager. The ubuntu-Installation comes with a different caffe library which is incompatible to caffe packages in caffe-unet. |
Hello,
I am a PhD student attempting to train a 2D model to segment Purkinje cells using the u-net Fiji plugin. I am running this on a Mac mini OS with an M1 chip, so I am running the CPU only code (because there is no NIVIDIA graphics card) and am using the Ubuntu 18.04 AMI and g4dn instance type. I am very new to this and am having difficulty getting past two errors: after about 8% into fine-tuning, the terminal displays client_loop: send disconnect: broken pipe; soon after the u-net job manager will send an SFTP Failure 4 and abort the job. I am not having issues connecting to my instance, so I think it might be an issue with my bashrc file.
This is the code I have been using to connect and set up my instance:
I have been sourcing the bashrc file in the bash profile:
![Screen Shot 2022-08-24 at 1 23 05 PM](https://user-images.githubusercontent.com/112008487/186484235-b5ef2592-25b8-4389-a4ef-4f88dc2d022f.png)
But I think my issue is that the bashrc file may not ensure that no output to standard output is being generated in non-interactive mode. I have been running into this issue when running the instance with the bashrc file as is, so I tried to edit it to address this problem, but am still running into the same issue:
Any insight into this issue will be greatly appreciated.
Thank you!
The text was updated successfully, but these errors were encountered: