Was there a conflict in hostname, i.e., two BBB with the same name? For me, I would rather to have fixed IP addresses: a) More CPU efficient without avahi and bonjour running around b) Avoid name lookup
On Fri, Feb 21, 2014 at 8:33 AM, <afe...@gmail.com> wrote: > Me and my colleague spent a day or two trying to fix issues like this that > kept creeping up on our beaglebone black boards. We would be unable to SSH > to them or it would hang at: > debug1: identity file /Users/cmicali/.ssh/id_dsa-cert type -1 > It wouldn't always say connection closed. I tried every single idea I saw > posted in this thread and others. > > In the end it seemed Avahi daemon was causing issues. I found this through > the following: > 1.) I ran "top" which showed me that systemd and systemd-journal were > running at 100% of the CPU combined. > 2.) I used "journalctl -b" to see what journal output was being created > for this boot. This showed error after error for Avahi at full CPU speed. > 3.) I stopped avahi-daemon, which I haven't yet seen the ramifications of > using: > systemctl disable avahi-daemon.service > 4.) I ran "df -h" which showed me that my storage was completely used up! > 5.) I located the log in /var/log/journal/<some weird string of numbers > and letters> > 6.) I deleted all the files in the aforementioned directory > 7.) I did as this thread suggests for the 20th time and deleted the > dropbear_rsa_host_key file > 8.) I stopped dropbear using: "/etc/init.d/dropbear stop" > 9.) I started dropbear using "/etc/init.d/dropbear start" > 10.) It proceeded to generate a new key. > 11.) At this point I tried connecting again from a client which was > successful. > > Perhaps I could have stopped at step 6 and just stopped and restarted > dropbear but that's what I did to make it work! Hope this saves someone > else a day -.- > > 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: 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* >> >> >> >> Any ideas what could be going on? >> >> -chris >> >> -- > 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+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
