You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Customer reports that an SSH session became unresponsive and they needed to reboot their device to regain access.
They've observed that every 5m or so the connection from sshnpd to its atServer fails and needs to be re-established:
Nov 18 09:15:27 router sshnpd[2350]: SEVERE|2024-11-18 09:15:27.684479|AtLookup|Exception in sending to server, Exception: Waited for 10000 millis. No response after 2024-11-18 09:15:17.672609
Nov 18 09:15:27 router sshnpd[2350]: SHOUT|2024-11-18 09:15:27.688202| sshnpd |connection lost
Nov 18 09:15:32 router sshnpd[2350]: INFO|2024-11-18 09:15:32.672239|AtLookup|Creating new connection
Nov 18 09:15:33 router sshnpd[2350]: INFO|2024-11-18 09:15:33.170159|AtLookup|New connection created OK
Nov 18 09:15:33 router sshnpd[2350]: SHOUT|2024-11-18 09:15:33.353140| sshnpd |connection available
Nov 18 09:20:42 router sshnpd[2350]: INFO|2024-11-18 09:20:42.681929|OutboundConnectionImpl|close(): calling socket.destroy() on connection to InternetAddress('35.224.23.101', IPv4):7454
Nov 18 09:20:42 router sshnpd[2350]: SEVERE|2024-11-18 09:20:42.691957|AtLookup|Exception in sending to server, Exception: Waited for 10000 millis. No response after 2024-11-18 09:20:32.673361
Nov 18 09:20:42 router sshnpd[2350]: SHOUT|2024-11-18 09:20:42.692465| sshnpd |connection lost
Nov 18 09:20:47 router sshnpd[2350]: INFO|2024-11-18 09:20:47.672539|AtLookup|Creating new connection
Nov 18 09:20:48 router sshnpd[2350]: INFO|2024-11-18 09:20:48.201517|AtLookup|New connection created OK
Nov 18 09:20:48 router sshnpd[2350]: SHOUT|2024-11-18 09:20:48.383361| sshnpd |connection available
Steps to reproduce
We need to create a test environment to reproduce.
Expected behavior
sshnpd works reliably
Additional context
Customer has been asked for more details of the device (e.g. RAM)
The text was updated successfully, but these errors were encountered:
Describe the bug
Customer reports that an SSH session became unresponsive and they needed to reboot their device to regain access.
They've observed that every 5m or so the connection from sshnpd to its atServer fails and needs to be re-established:
Steps to reproduce
We need to create a test environment to reproduce.
Expected behavior
sshnpd works reliably
Additional context
Customer has been asked for more details of the device (e.g. RAM)
The text was updated successfully, but these errors were encountered: