Cannot ssh into GCP instance
I cannot ssh into Google compute engine instance. Here is scenario.
I tried to ssh into an instance from ubuntu ssh client, so generated a private & public key in my local and added pubkey to metadata.
But got
Permission denied (publickey)
error message and the instance console was sayingNo space left on device
I then increased the size of the instance by 100GB more and then restart the instance.
After few mins later, tried to ssh into the instance again and getting the
Permission denied (publickey)
error again and the console saidNo usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/']
Now I can't connect to the instance by any tool such as browser console, ssh client etc.
Is there any solution to address this problem?
Thanks in advance.
ssh google-cloud-platform google-compute-engine
add a comment |
I cannot ssh into Google compute engine instance. Here is scenario.
I tried to ssh into an instance from ubuntu ssh client, so generated a private & public key in my local and added pubkey to metadata.
But got
Permission denied (publickey)
error message and the instance console was sayingNo space left on device
I then increased the size of the instance by 100GB more and then restart the instance.
After few mins later, tried to ssh into the instance again and getting the
Permission denied (publickey)
error again and the console saidNo usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/']
Now I can't connect to the instance by any tool such as browser console, ssh client etc.
Is there any solution to address this problem?
Thanks in advance.
ssh google-cloud-platform google-compute-engine
It sounds like you filled up your disk, and now stuff that needs to make new files is failing. Making it larger doesn't help automatically, you still need to grow the partition and expand the filesystem to use the new disk space. There are instructions for this here. You will also likely need to use the serial console since SSH doesn't have space to run.
– Dan
Nov 21 '18 at 23:54
add a comment |
I cannot ssh into Google compute engine instance. Here is scenario.
I tried to ssh into an instance from ubuntu ssh client, so generated a private & public key in my local and added pubkey to metadata.
But got
Permission denied (publickey)
error message and the instance console was sayingNo space left on device
I then increased the size of the instance by 100GB more and then restart the instance.
After few mins later, tried to ssh into the instance again and getting the
Permission denied (publickey)
error again and the console saidNo usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/']
Now I can't connect to the instance by any tool such as browser console, ssh client etc.
Is there any solution to address this problem?
Thanks in advance.
ssh google-cloud-platform google-compute-engine
I cannot ssh into Google compute engine instance. Here is scenario.
I tried to ssh into an instance from ubuntu ssh client, so generated a private & public key in my local and added pubkey to metadata.
But got
Permission denied (publickey)
error message and the instance console was sayingNo space left on device
I then increased the size of the instance by 100GB more and then restart the instance.
After few mins later, tried to ssh into the instance again and getting the
Permission denied (publickey)
error again and the console saidNo usable temporary directory found in ['/tmp', '/var/tmp', '/usr/tmp', '/']
Now I can't connect to the instance by any tool such as browser console, ssh client etc.
Is there any solution to address this problem?
Thanks in advance.
ssh google-cloud-platform google-compute-engine
ssh google-cloud-platform google-compute-engine
asked Nov 21 '18 at 8:12
Denis PetrenkoDenis Petrenko
1
1
It sounds like you filled up your disk, and now stuff that needs to make new files is failing. Making it larger doesn't help automatically, you still need to grow the partition and expand the filesystem to use the new disk space. There are instructions for this here. You will also likely need to use the serial console since SSH doesn't have space to run.
– Dan
Nov 21 '18 at 23:54
add a comment |
It sounds like you filled up your disk, and now stuff that needs to make new files is failing. Making it larger doesn't help automatically, you still need to grow the partition and expand the filesystem to use the new disk space. There are instructions for this here. You will also likely need to use the serial console since SSH doesn't have space to run.
– Dan
Nov 21 '18 at 23:54
It sounds like you filled up your disk, and now stuff that needs to make new files is failing. Making it larger doesn't help automatically, you still need to grow the partition and expand the filesystem to use the new disk space. There are instructions for this here. You will also likely need to use the serial console since SSH doesn't have space to run.
– Dan
Nov 21 '18 at 23:54
It sounds like you filled up your disk, and now stuff that needs to make new files is failing. Making it larger doesn't help automatically, you still need to grow the partition and expand the filesystem to use the new disk space. There are instructions for this here. You will also likely need to use the serial console since SSH doesn't have space to run.
– Dan
Nov 21 '18 at 23:54
add a comment |
1 Answer
1
active
oldest
votes
As Dan mentioned, you need to connect on serial console to expand the filesystem making use of the additional disk space allocated. You can also attempt to free up some space etc.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fstackoverflow.com%2fquestions%2f53407699%2fcannot-ssh-into-gcp-instance%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
As Dan mentioned, you need to connect on serial console to expand the filesystem making use of the additional disk space allocated. You can also attempt to free up some space etc.
add a comment |
As Dan mentioned, you need to connect on serial console to expand the filesystem making use of the additional disk space allocated. You can also attempt to free up some space etc.
add a comment |
As Dan mentioned, you need to connect on serial console to expand the filesystem making use of the additional disk space allocated. You can also attempt to free up some space etc.
As Dan mentioned, you need to connect on serial console to expand the filesystem making use of the additional disk space allocated. You can also attempt to free up some space etc.
answered Nov 22 '18 at 0:19
community wiki
Asif Tanwir
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53407699%2fcannot-ssh-into-gcp-instance%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
It sounds like you filled up your disk, and now stuff that needs to make new files is failing. Making it larger doesn't help automatically, you still need to grow the partition and expand the filesystem to use the new disk space. There are instructions for this here. You will also likely need to use the serial console since SSH doesn't have space to run.
– Dan
Nov 21 '18 at 23:54