Riddle me this...
I just upgraded (oupgrade -f -l) two Omega2's. Now both of them won't accept ssh connections.
Looks like the F/W upgrade went well ...
root@Omega-D769:~/work/omega2_infrastructure# oupgrade -f -l
> Device Firmware Version: 0.2.2 b200
> Checking latest version online...
> Repo Firmware Version: 0.2.2 b201
> New firmware version available, need to upgrade device firmware
> Downloading new firmware ...
/usr/bin/oupgrade: local: line 378: not in a function
--2019-01-05 21:26:25-- http://repo.onion.io/omega2/images/omega2p-v0.2.2-b201.bin
Resolving repo.onion.io... 188.8.131.52
Connecting to repo.onion.io|184.108.40.206|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7864493 (7.5M) [application/octet-stream]
Saving to: '/tmp/omega2p-v0.2.2-b201.bin'
/tmp/omega2p-v0.2.2-b2 100%[==========================>] 7.50M 427KB/s in 23s
2019-01-05 21:26:48 (333 KB/s) - '/tmp/omega2p-v0.2.2-b201.bin' saved [7864493/7864493]
> Starting firmware upgrade....
Saving config files...
killall: watchdog: no process killed
Sending TERM to remaining processes ... udhcpc ap_client rpcd mosquitto mountd ntpd shellinaboxd oupgrade Terminated
root@Omega-D769:~/work/omega2_infrastructure# packet_write_wait: Connection to 192.168.1.115 port 22: Broken pipe
However, the devices won't complete a ssh connection. Here are several attempts.
Device [ omega-fdf5 ] is off line at IP_ADDR [ 192.168.1.110 ]
Device [ omega-24d5 ] is off line at IP_ADDR [ 192.168.1.111 ]
Device [ omega-de0b ] is off line at IP_ADDR [ 192.168.1.112 ]
Device [ omega-24d7 ] is off line at IP_ADDR [ 192.168.1.113 ]
Device [ omega-d749 ] is on line at IP_ADDR [ 192.168.1.114 ]
Device [ omega-d769 ] is on line at IP_ADDR [ 192.168.1.115 ]
bscott@aries:~$ ssh root@omega-d749
Connection to omega-d749 closed.
bscott@aries:~$ ssh email@example.com
Connection to 192.168.1.114 closed.
bscott@aries:~$ ssh root@omega-d769
Connection to omega-d769 closed.
bscott@aries:~$ ssh firstname.lastname@example.org
Connection to 192.168.1.115 closed.
The ldev program is nothing more than a shell script that looks for Omega2 devices in the local dhcpd config file to get their IP assignments, then pings them to see if they are willing to play. As you can see the two troubled units are responding to pings.
The failed password response is quite different.
Has anyone seen this issue on b201?