cmicali@imac ~> ssh -vvv root@beaglebone.local
OpenSSH_5.9p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 53: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to beaglebone.local [192.168.1.32] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/Users/cmicali/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /Users/cmicali/.ssh/id_rsa type 1
debug1: identity file /Users/cmicali/.ssh/id_rsa-cert type -1
debug1: identity file /Users/cmicali/.ssh/id_dsa type -1
debug1: identity file /Users/cmicali/.ssh/id_dsa-cert type -1
ssh_exchange_identification: Connection closed by remote host
host> ssh-keygen -R beaglebone.local
host> ssh-keygen -R 192.168.1.32
I don't have a BBB yet, but I imagine that your ~/.ssh/known_hosts file has an entry in it for beaglebone.local. remove that line and then you should be able to ssh to the second BBB. Now when you go back to the original BBB it won't match the entry in .ssh/known_hosts (it now matches the second board). Delete the line again for beaglebone.local and you can ssh to the first one.
Jimmy
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
cmicali@cmicali-imac ~ [255]> ssh-keygen -R beaglebone.local
/Users/cmicali/.ssh/known_hosts updated.
Original contents retained as /Users/cmicali/.ssh/known_hosts.old
cmicali@cmicali-imac ~> ssh-keygen -R 192.168.1.32
/Users/cmicali/.ssh/known_hosts updated.
Original contents retained as /Users/cmicali/.ssh/known_hosts.old
cmicali@cmicali-imac ~> ssh -vvv root@192.168.1.32
OpenSSH_5.9p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 53: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 192.168.1.32 [192.168.1.32] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/Users/cmicali/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /Users/cmicali/.ssh/id_rsa type 1
debug1: identity file /Users/cmicali/.ssh/id_rsa-cert type -1
debug1: identity file /Users/cmicali/.ssh/id_dsa type -1
debug1: identity file /Users/cmicali/.ssh/id_dsa-cert type -1
ssh_exchange_identification: Connection closed by
remote host
cmicali@cmicali-imac ~ [255]>
inspired by this post a have a simple solution for those who have the problem and can't connect via serial consoleopen the cloud9 and create a new file with the following script and start it, or place the script in any textbox where you can interact with your beaglebone and press run
var fs = require('fs');var destroyed_key_file = '/etc/dropbear/dropbear_rsa_host_key';
fs.readFile(destroyed_key_file, function (err, data) {if (err) throw err;if( data===null || data.length===0 ){console.log("we have a corrupted host key file... try do delete it");fs.unlink(destroyed_key_file, function (err) {if (err) throw err;console.log('successfully deleted ' + destroyed_key_file);console.log('you should now reboot your beaglebone.');console.log('the /etc/init.d/dropbear script will create a new rsa host key file for you.');console.log('after the reboot you should be able to login over ssh');});} else {console.log("it seems that you have another problem, sorry");}});
inspired by this post a have a simple solution for those who have the problem and can't connect via serial consoleopen the cloud9 and create a new file with the following script and start it, or place the script in any textbox where you can interact with your beaglebone and press run
var fs = require('fs');var destroyed_key_file = '/etc/dropbear/dropbear_rsa_host_key';
fs.readFile(destroyed_key_file, function (err, data) {if (err) throw err;if( data===null || data.length===0 ){console.log("we have a corrupted host key file... try do delete it");fs.unlink(destroyed_key_file, function (err) {if (err) throw err;console.log('successfully deleted ' + destroyed_key_file);console.log('you should now reboot your beaglebone.');console.log('the /etc/init.d/dropbear script will create a new rsa host key file for you.');console.log('after the reboot you should be able to login over ssh');});} else {console.log("it seems that you have another problem, sorry");}});
Am Samstag, 4. Mai 2013 05:27:26 UTC+2 schrieb Glen H:
inspired by this post a have a simple solution for those who have the problem and can't connect via serial consoleopen the cloud9 and create a new file with the following script and start it, or place the script in any textbox where you can interact with your beaglebone and press run
var fs = require('fs');var destroyed_key_file = '/etc/dropbear/dropbear_rsa_host_key';
fs.readFile(destroyed_key_file, function (err, data) {if (err) throw err;if( data===null || data.length===0 ){console.log("we have a corrupted host key file... try do delete it");fs.unlink(destroyed_key_file, function (err) {if (err) throw err;console.log('successfully deleted ' + destroyed_key_file);console.log('you should now reboot your beaglebone.');console.log('the /etc/init.d/dropbear script will create a new rsa host key file for you.');console.log('after the reboot you should be able to login over ssh');});} else {console.log("it seems that you have another problem, sorry");}});
Am Samstag, 4. Mai 2013 05:27:26 UTC+2 schrieb Glen H:
inspired by this post a have a simple solution for those who have the problem and can't connect via serial consoleopen the cloud9 and create a new file with the following script and start it, or place the script in any textbox where you can interact with your beaglebone and press run
var fs = require('fs');var destroyed_key_file = '/etc/dropbear/dropbear_rsa_host_key';
fs.readFile(destroyed_key_file, function (err, data) {if (err) throw err;if( data===null || data.length===0 ){console.log("we have a corrupted host key file... try do delete it");fs.unlink(destroyed_key_file, function (err) {if (err) throw err;console.log('successfully deleted ' + destroyed_key_file);console.log('you should now reboot your beaglebone.');console.log('the /etc/init.d/dropbear script will create a new rsa host key file for you.');console.log('after the reboot you should be able to login over ssh');});} else {console.log("it seems that you have another problem, sorry");}});
Am Samstag, 4. Mai 2013 05:27:26 UTC+2 schrieb Glen H:
inspired by this post a have a simple solution for those who have the problem and can't connect via serial consoleopen the cloud9 and create a new file with the following script and start it, or place the script in any textbox where you can interact with your beaglebone and press run
var fs = require('fs');var destroyed_key_file = '/etc/dropbear/dropbear_rsa_host_key';
fs.readFile(destroyed_key_file, function (err, data) {if (err) throw err;if( data===null || data.length===0 ){console.log("we have a corrupted host key file... try do delete it");fs.unlink(destroyed_key_file, function (err) {if (err) throw err;console.log('successfully deleted ' + destroyed_key_file);console.log('you should now reboot your beaglebone.');console.log('the /etc/init.d/dropbear script will create a new rsa host key file for you.');console.log('after the reboot you should be able to login over ssh');});} else {console.log("it seems that you have another problem, sorry");}});
Am Samstag, 4. Mai 2013 05:27:26 UTC+2 schrieb Glen H:
I don't have a BBB yet, but I imagine that your ~/.ssh/known_hosts file has an entry in it for beaglebone.local. remove that line and then you should be able to ssh to the second BBB. Now when you go back to the original BBB it won't match the entry in .ssh/known_hosts (it now matches the second board). Delete the line again for beaglebone.local and you can ssh to the first one.
Jimmy
On Wednesday, May 1, 2013 2:39:49 PM UTC-7, cmicali wrote:
Hi,I got two BBBs in the mail - I plugged one in and everything has been working fine. SSHed to it, moved my s/w to it, etc. I then powered it off and plugged the other one in and can't SSH to it. I get a ssh_exchange_identification: Connection closed by remote host error. I get this error no matter what machine I am trying to connect from. Someone on IRC had this same problem and didn't think much of it then, but this is a board that is right out of the box and exhibiting this issue. The LEDs appear that it has booted fine.
cmicali@imac ~> ssh -vvv root@beaglebone.local
OpenSSH_5.9p1, OpenSSL 0.9.8r 8 Feb 2011
debug1: Reading configuration data /etc/ssh_config
debug1: /etc/ssh_config line 20: Applying options for *
debug1: /etc/ssh_config line 53: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to beaglebone.local [192.168.1.32] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/Users/cmicali/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /Users/cmicali/.ssh/id_rsa type 1
debug1: identity file /Users/cmicali/.ssh/id_rsa-cert type -1
...
debug1:<spa
var exec = require('child_process').exec;function puts(error, stdout, stderr) { console.log(error); console.log(stdout); console.log(stderr); }
// 1 - Clear journal spaceexec("df -h; rm -rf /var/log/journal/; df -h", puts);
// 2 - Remove Dropbear fileexec("rm /etc/dropbear/dropbear_rsa_host_key", puts);
// 3 - Stop Dropbearexec("/etc/init.d/dropbear stop", puts);
// 4 - Start Dropbearexec("/etc/init.d/dropbear start", puts);
inspired by this post a have a simple solution for those who have the problem and can't connect via serial consoleopen the cloud9 and create a new file with the following script and start it, or place the script in any textbox where you can interact with your beaglebone and press run
var fs = require('fs');var destroyed_key_file = '/etc/dropbear/dropbear_rsa_host_key';
fs.readFile(destroyed_key_file, function (err, data) {if (err) throw err;if( data===null || data.length===0 ){console.log("we have a corrupted host key file... try do delete it");fs.unlink(destroyed_key_file, function (err) {if (err) throw err;console.log('successfully deleted ' + destroyed_key_file);console.log('you should now reboot your beaglebone.');console.log('the /etc/init.d/dropbear script will create a new rsa host key file for you.');console.log('after the reboot you should be able to login over ssh');});} else {console.log("it seems that you have another problem, sorry");}});
Am Samstag, 4. Mai 2013 05:27:26 UTC+2 schrieb Glen H:
...
inspired by this post a have a simple solution for those who have the problem and can't connect via serial console
open the cloud9 and create a new file with the following script and start it, or place the script in any textbox where you can interact with your beaglebone and press run
var fs = require('fs');var destroyed_key_file = '/etc/dropbear/dropbear_rsa_host_key';
fs.readFile(destroyed_key_file, function (err, data) {if (err) throw err;if( data===null || data.length===0 ){console.log("we have a corrupted host key file... try do delete it");fs.unlink(destroyed_key_file, function (err) {if (err) throw err;console.log('successfully deleted ' + destroyed_key_file);console.log('you should now reboot your beaglebone.');console.log('the /etc/init.d/dropbear script will create a new rsa host key file for you.');console.log('after the reboot you should be able to login over ssh');});} else {console.log("it seems that you have another problem, sorry");}});
Am Samstag, 4. Mai 2013 05:27:26 UTC+2 schrieb Glen H: