This week I had a Nano delivered and which I set it up using SD and then shifted over to 2TB NVMe drive using the jetsonhacks scripts. There’s a problem I’m running into where when I ssh into the box, after about 30s the session hangs, irrespective of whatever I’m doing, or which SSH client I use. It’s consistent, and there’s no issues coming up looking at journalctl -u ssh, or in syslog. I can log in with multiple SSH sessions, but they hang around the 30s mark. Interestingly, any commands that were running seem to run to completion, just the terminal session becomes unresponsive.
If I’m logged in via the GUI and have a terminal running there doesn’t seem to be a problem.
If I log in to ssh from the same Nano from a terminal in the GUI, it hangs after the password it entered.
Update this only seems to be an issue if I’m using wired ethernet. When using wifi I don’t seem to have the problem.
Has anyone seen this behavior before, or know how to resolve it?
I got confused by some comments here.
I can log in with multiple SSH sessions, but they hang around the 30s mark. Interestingly, any commands that were running seem to run to completion, just the terminal session becomes unresponsive.
What does that mean here? The ssh is hang but you could still input to it?
If I log in to ssh from the same Nano from a terminal in the GUI, it hangs after the password it entered.
What does that mean here? ssh to the device itself?
When I say into the box over (I’ve narrowed it down to just via Ethernet, WiFi doesn’t seem to have a problem) the terminal on the client stops getting any response. The cursor in my linux terminal or putty on windows just flashes as if the connection is still up but is completely unresponsive to any input and no further output is received.
I tried different variations of ssh’ing into the box. From remote machines, different OS, different clients, trying to rule out possible variables. When I said I ssh’d from the Nano, yes, one of the variations I tried was ssh’ing back into itself from a terminal, but when I did that I couldn’t get passed the point of entering the password. After logging into the password I would get the same none responsive terminal. This only happens when ssh’ing in via eth and not in WiFi.
Have you ever tried another Ubuntu host to ssh to your Jetson?
I have several Jetsons in remote lab but didn’t see any of such issue ever reported.
Yes, my linux machines are all running Ubuntu. When the Nano is plugged into ethernet I get the problem regardless of the OS or ssh client.
I mean could you try to flash your board with sdkmanager first?
I’m trying to find how to do that from the command line, as all my linux machines are headless. I’ve got the sdkmanager installed, and I’ve downloaded the components. Can’t seem to find in the docs whether it’s going to flash the nvme drive if I’ve got that hooked up via a usb adapter, or if the nano needs to be running, etc.
Hi,
The command is in this document:
And just to clarify, this is command for jetpack6.2. If you are using jp5, then it will be different document to refer to.
Arghhh… I picked up a new NVMe drive to rule that out of the equation, went through the steps for flashing the NVMe drive via the Linux host, was able to log in, everything looking good, logged into the newly flashed OS and then ssh’d in via the ethernet interface and snap… same problem! Has no problem working on wifi, but SSH sessions hang after about 30 seconds of being logged in if they’re via the ethernet interface. I’ve even tried plugging it into a different switch, no joy, same behavior. Really frustrating!