Replies: 1 comment
-
|
I checked the table, and 921 is listed as vic-gateway crash. I believe it is like almost all of the other error codes: unless you recently changed something, a reboot is your best best. It was probably just due to software bug
Hmm, but you’ve cleared the data, and can’t ssh in... but it sounds like you are in recovery mode? The recovery mode only uses a temporary file system, and doesn’t touch the regular user-data, like the ssh keys or your wifi settings. (I think that was meant as to help with security but it confused me a lot).
Definitely get out of recovery mode and go to the regular mode and download the logs there. Don’t do another unlock. I’m pretty sure that in regular mode you can either reuse your ssh keys from before or the log download will give you new keys. The EscapePod setup has everyone erasing the user data several times, so I think the ssh keys thing works.
On Feb 15, 2021, at 8:13 PM, Wizard-CPU ***@***.***> wrote:
Hello fellow robot enthusiasts,
When I woke up yesterday morning my OSKR bot displayed an error code 921. I thought that it was a software error being a 900 code but now am not so sure.. Anyways:
After clearing the user data and then booting into recovery and clearing the user data I downloaded the logs a bunch of different times with no success. Under the data directory in the logs there is supposed to be an ssh directory with the new id_rsa key and there isn’t.
Do I need a new OSKR image? I shouldn't because it wrote over the recovery partition, or should?
I attempted to At this point i'm not sure what to do without ssh access. I scanned the robot using this command:
nmap -p 1-65535 -T4 -A -v 192.168.1.23
The result was:
All 65535 scanned ports on 192.168.1.23 are closed
I scanned the robot again using this command to add UDP:
nmap -sS -sU -T4 -A -v 192.168.1.23
The result was the same essentially. No access to port 22
Does anyone know what's going on? My robot is down until then.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Randy
— Sent unencumbered by the thought process
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello fellow robot enthusiasts, when I woke up yesterday morning my OSKR bot displayed an error code 921. I thought that it was a software error being a 900 code but now am not so sure. After clearing the user data and then booting into recovery and clearing the user data I downloaded the logs a bunch of different times with no success. Under the data directory in the logs there is supposed to be an ssh directory with the new id_rsa key and there isn’t.
Do I need a new OSKR image? I shouldn't because it wrote over the recovery partition, or should?
I attempted to ssh in but at this point i'm not sure what to do without ssh access. I scanned the robot using this command:
nmap -p 1-65535 -T4 -A -v 192.168.1.23
The result was:
All 65535 scanned ports on 192.168.1.23 are closed
I scanned the robot again using this command to add UDP:
nmap -sS -sU -T4 -A -v 192.168.1.23
The result was the same essentially. No access to port 22
Does anyone know what's going on? My robot is down until then.
Beta Was this translation helpful? Give feedback.
All reactions