Difference between revisions of "AWS VMs behaving weirdly especially trying to open vim hangs the ssh connection"
From Notes_Wiki
(Created page with "<yambe:breadcrumb>Troubleshooting_AWS_issues|Troubleshooting AWS issues</yambe:breadcrumb> =AWS VMs behaving weirdly especially trying to open vim hangs the ssh connection= T...") |
m |
||
Line 8: | Line 8: | ||
Steps learned from http://askubuntu.com/questions/381062/terminal-freezes-on-running-apt-get-or-vim | Steps learned from http://askubuntu.com/questions/381062/terminal-freezes-on-running-apt-get-or-vim | ||
Similar problem faced while using top described at http://serverfault.com/questions/390604/amazon-ec2-instance-issuing-top-command-just-goes-blank-on-the-ssh-terminal |
Revision as of 09:27, 11 January 2014
<yambe:breadcrumb>Troubleshooting_AWS_issues|Troubleshooting AWS issues</yambe:breadcrumb>
AWS VMs behaving weirdly especially trying to open vim hangs the ssh connection
This is among the most bizarre errors and problems that I have encountered. It is possible that AWS VMs behaving weirdly especially trying to open vim hangs the ssh connection. Other symptoms include unable to run ls in a folder without any problem with disks. This problem can be solved by reducing MTU from 1500 to 1492 using:
sudo /sbin/ifconfig eth0 mtu 1492
Steps learned from http://askubuntu.com/questions/381062/terminal-freezes-on-running-apt-get-or-vim Similar problem faced while using top described at http://serverfault.com/questions/390604/amazon-ec2-instance-issuing-top-command-just-goes-blank-on-the-ssh-terminal