problems SSHing after MemoryError
Clash Royale CLAN TAG#URR8PPP
I am running a Compute Engine on Google Cloud Platform, which has been functioning perfectly for over a month now.
Recently I was running a Jupyter Lab instance in which I ended up with a MemoryError. My SSH connection to the VM was dropped and I was unable to reconnect, however restarting the VM (several times) seemed to do the trick.
This problem is still occuring now. I will be able to SSH into the VM perfectly fine, and then whenever I shutdown the VM and turn it back on, I will suddenly find myself unable to SSH in, unless I restart the VM an arbitrary amount of times (sometimes once is enough, sometimes it takes more than 4).
The attempt to SSH results in:ssh: connect to host xx.xxx.xx.xxx port 22: Connection timed out.
Several things I can rule out:
- The network I am on has no proxy issues.
- The VM is definitely up and running (with sufficient time to fully start up) by the time I am trying to SSH into it. I know this because I can ssh onto the machine via the Google Cloud web console.
- The VM has 86GB of disk available and so it is not a disk issue.
The fact that this works sometimes but not all times is making this very tricky for me to diagnose what the problem is. How might I determine and fix this problem?
ssh google-cloud
edited Feb 13 at 10:06
Bodo
2,048416
asked Feb 12 at 15:33
quantum285quantum285
573
|
show 1 more comment
I am running a Compute Engine on Google Cloud Platform, which has been functioning perfectly for over a month now.
Recently I was running a Jupyter Lab instance in which I ended up with a MemoryError. My SSH connection to the VM was dropped and I was unable to reconnect, however restarting the VM (several times) seemed to do the trick.
This problem is still occuring now. I will be able to SSH into the VM perfectly fine, and then whenever I shutdown the VM and turn it back on, I will suddenly find myself unable to SSH in, unless I restart the VM an arbitrary amount of times (sometimes once is enough, sometimes it takes more than 4).
The attempt to SSH results in:ssh: connect to host xx.xxx.xx.xxx port 22: Connection timed out.
Several things I can rule out:
- The network I am on has no proxy issues.
- The VM is definitely up and running (with sufficient time to fully start up) by the time I am trying to SSH into it. I know this because I can ssh onto the machine via the Google Cloud web console.
- The VM has 86GB of disk available and so it is not a disk issue.
The fact that this works sometimes but not all times is making this very tricky for me to diagnose what the problem is. How might I determine and fix this problem?
ssh google-cloud
edited Feb 13 at 10:06
Bodo
2,048416
asked Feb 12 at 15:33
quantum285quantum285
573
How do you detect that "The VM is definitely up and running"? Maybe it has not yet startedsshd. Is there anything suspicious in syslog?
– Bodo
Feb 12 at 18:13
Apologies, I've provided more information in my question. I can ssh onto the compute engine via the Google Cloud web console, but not via ConEmu
– quantum285
Feb 12 at 22:18
Nothing suspicious in syslog as far as I can see but I'm not sure what I'm looking for.
– quantum285
Feb 12 at 22:25
1
When you have the situation that you can SSH from the Google Cloud web console but not from your local system, runtcptraceroute yourserver 22, bring the system to a usable state again, run thetcptracerouteagain and compare the output. This should help to find out if there is some intermediate system dropping the packets. Another thought: Does the VM have a fixed IP address or does it get a new dynamic IP address when it's restarted?
– Bodo
Feb 13 at 9:46
Thanks, I'm running Windows locally so will have to install a tcptraceroute equivalent, in the meantime would just like to respond that yes the IP address if fixed. Thanks for your help so far, would like to get to the bottom of this.
– quantum285
Feb 13 at 10:59
|
show 1 more comment
I am running a Compute Engine on Google Cloud Platform, which has been functioning perfectly for over a month now.
Recently I was running a Jupyter Lab instance in which I ended up with a MemoryError. My SSH connection to the VM was dropped and I was unable to reconnect, however restarting the VM (several times) seemed to do the trick.
This problem is still occuring now. I will be able to SSH into the VM perfectly fine, and then whenever I shutdown the VM and turn it back on, I will suddenly find myself unable to SSH in, unless I restart the VM an arbitrary amount of times (sometimes once is enough, sometimes it takes more than 4).
The attempt to SSH results in:ssh: connect to host xx.xxx.xx.xxx port 22: Connection timed out.
Several things I can rule out:
- The network I am on has no proxy issues.
- The VM is definitely up and running (with sufficient time to fully start up) by the time I am trying to SSH into it. I know this because I can ssh onto the machine via the Google Cloud web console.
- The VM has 86GB of disk available and so it is not a disk issue.
The fact that this works sometimes but not all times is making this very tricky for me to diagnose what the problem is. How might I determine and fix this problem?
ssh google-cloud
edited Feb 13 at 10:06
Bodo
2,048416
asked Feb 12 at 15:33
quantum285quantum285
573
I am running a Compute Engine on Google Cloud Platform, which has been functioning perfectly for over a month now.
Recently I was running a Jupyter Lab instance in which I ended up with a MemoryError. My SSH connection to the VM was dropped and I was unable to reconnect, however restarting the VM (several times) seemed to do the trick.
This problem is still occuring now. I will be able to SSH into the VM perfectly fine, and then whenever I shutdown the VM and turn it back on, I will suddenly find myself unable to SSH in, unless I restart the VM an arbitrary amount of times (sometimes once is enough, sometimes it takes more than 4).
The attempt to SSH results in:ssh: connect to host xx.xxx.xx.xxx port 22: Connection timed out.
Several things I can rule out:
- The network I am on has no proxy issues.
- The VM is definitely up and running (with sufficient time to fully start up) by the time I am trying to SSH into it. I know this because I can ssh onto the machine via the Google Cloud web console.
- The VM has 86GB of disk available and so it is not a disk issue.
The fact that this works sometimes but not all times is making this very tricky for me to diagnose what the problem is. How might I determine and fix this problem?
ssh google-cloud
ssh google-cloud
edited Feb 13 at 10:06
Bodo
2,048416
asked Feb 12 at 15:33
quantum285quantum285
573
edited Feb 13 at 10:06
Bodo
2,048416
asked Feb 12 at 15:33
quantum285quantum285
573
edited Feb 13 at 10:06
Bodo
2,048416
edited Feb 13 at 10:06
Bodo
2,048416
edited Feb 13 at 10:06
Bodo
2,048416
2,048416
asked Feb 12 at 15:33
quantum285quantum285
573
asked Feb 12 at 15:33
quantum285quantum285
573
asked Feb 12 at 15:33
quantum285quantum285
573
573
How do you detect that "The VM is definitely up and running"? Maybe it has not yet startedsshd. Is there anything suspicious in syslog?
– Bodo
Feb 12 at 18:13
Apologies, I've provided more information in my question. I can ssh onto the compute engine via the Google Cloud web console, but not via ConEmu
– quantum285
Feb 12 at 22:18
Nothing suspicious in syslog as far as I can see but I'm not sure what I'm looking for.
– quantum285
Feb 12 at 22:25
1
When you have the situation that you can SSH from the Google Cloud web console but not from your local system, runtcptraceroute yourserver 22, bring the system to a usable state again, run thetcptracerouteagain and compare the output. This should help to find out if there is some intermediate system dropping the packets. Another thought: Does the VM have a fixed IP address or does it get a new dynamic IP address when it's restarted?
– Bodo
Feb 13 at 9:46
Thanks, I'm running Windows locally so will have to install a tcptraceroute equivalent, in the meantime would just like to respond that yes the IP address if fixed. Thanks for your help so far, would like to get to the bottom of this.
– quantum285
Feb 13 at 10:59
|
show 1 more comment
How do you detect that "The VM is definitely up and running"? Maybe it has not yet startedsshd. Is there anything suspicious in syslog?
– Bodo
Feb 12 at 18:13
Apologies, I've provided more information in my question. I can ssh onto the compute engine via the Google Cloud web console, but not via ConEmu
– quantum285
Feb 12 at 22:18
Nothing suspicious in syslog as far as I can see but I'm not sure what I'm looking for.
– quantum285
Feb 12 at 22:25
1
When you have the situation that you can SSH from the Google Cloud web console but not from your local system, runtcptraceroute yourserver 22, bring the system to a usable state again, run thetcptracerouteagain and compare the output. This should help to find out if there is some intermediate system dropping the packets. Another thought: Does the VM have a fixed IP address or does it get a new dynamic IP address when it's restarted?
– Bodo
Feb 13 at 9:46
Thanks, I'm running Windows locally so will have to install a tcptraceroute equivalent, in the meantime would just like to respond that yes the IP address if fixed. Thanks for your help so far, would like to get to the bottom of this.
– quantum285
Feb 13 at 10:59
How do you detect that "The VM is definitely up and running"? Maybe it has not yet started
sshd. Is there anything suspicious in syslog?– Bodo
Feb 12 at 18:13
How do you detect that "The VM is definitely up and running"? Maybe it has not yet started
sshd. Is there anything suspicious in syslog?– Bodo
Feb 12 at 18:13
Apologies, I've provided more information in my question. I can ssh onto the compute engine via the Google Cloud web console, but not via ConEmu
– quantum285
Feb 12 at 22:18
Apologies, I've provided more information in my question. I can ssh onto the compute engine via the Google Cloud web console, but not via ConEmu
– quantum285
Feb 12 at 22:18
Nothing suspicious in syslog as far as I can see but I'm not sure what I'm looking for.
– quantum285
Feb 12 at 22:25
Nothing suspicious in syslog as far as I can see but I'm not sure what I'm looking for.
– quantum285
Feb 12 at 22:25
1
1
When you have the situation that you can SSH from the Google Cloud web console but not from your local system, run
tcptraceroute yourserver 22, bring the system to a usable state again, run the tcptraceroute again and compare the output. This should help to find out if there is some intermediate system dropping the packets. Another thought: Does the VM have a fixed IP address or does it get a new dynamic IP address when it's restarted?– Bodo
Feb 13 at 9:46
When you have the situation that you can SSH from the Google Cloud web console but not from your local system, run
tcptraceroute yourserver 22, bring the system to a usable state again, run the tcptraceroute again and compare the output. This should help to find out if there is some intermediate system dropping the packets. Another thought: Does the VM have a fixed IP address or does it get a new dynamic IP address when it's restarted?– Bodo
Feb 13 at 9:46
Thanks, I'm running Windows locally so will have to install a tcptraceroute equivalent, in the meantime would just like to respond that yes the IP address if fixed. Thanks for your help so far, would like to get to the bottom of this.
– quantum285
Feb 13 at 10:59
Thanks, I'm running Windows locally so will have to install a tcptraceroute equivalent, in the meantime would just like to respond that yes the IP address if fixed. Thanks for your help so far, would like to get to the bottom of this.
– quantum285
Feb 13 at 10:59
|
show 1 more comment
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500198%2fproblems-sshing-after-memoryerror%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f500198%2fproblems-sshing-after-memoryerror%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
How do you detect that "The VM is definitely up and running"? Maybe it has not yet started
sshd. Is there anything suspicious in syslog?– Bodo
Feb 12 at 18:13
Apologies, I've provided more information in my question. I can ssh onto the compute engine via the Google Cloud web console, but not via ConEmu
– quantum285
Feb 12 at 22:18
Nothing suspicious in syslog as far as I can see but I'm not sure what I'm looking for.
– quantum285
Feb 12 at 22:25
1
When you have the situation that you can SSH from the Google Cloud web console but not from your local system, run
tcptraceroute yourserver 22, bring the system to a usable state again, run thetcptracerouteagain and compare the output. This should help to find out if there is some intermediate system dropping the packets. Another thought: Does the VM have a fixed IP address or does it get a new dynamic IP address when it's restarted?– Bodo
Feb 13 at 9:46
Thanks, I'm running Windows locally so will have to install a tcptraceroute equivalent, in the meantime would just like to respond that yes the IP address if fixed. Thanks for your help so far, would like to get to the bottom of this.
– quantum285
Feb 13 at 10:59