volume not mounted after reboot droplet.
sda volume not mounted after reboot droplet.
A question can only have one accepted answer. Are you sure you want to replace the current answer with this one?
You previously marked this answer as accepted. Are you sure you want to unaccept it?
I wrote a c++ pgm and compiled it in console with g++ and have this error: cannot execute binary file: Exec format error
I have a droplet that works with SSH but the keys are named the default `id_rsa`. When I add new keys they do not work. I've copied and pasted the public key into the digital ocean control panel in the working droplet. In the non-working droplet I tried this, as well as going `ssh-copy-id root@206.***.***.104` but even this comes back as denied. I know the permission are okay since the app with the default key names work. I've tried simply naming them `id_rsa2` and `id_rsa_sinatra`, but this does not work. I tried to add the path to the private key `ssh -i /Users/me/.ssh/id_rsa2 root@206.***.**104`. No dice. I've tried adding a config file to the SSH folder as follows (I am not at all confident that this is correct. It is scavenged from other posts): ``` Host sinatra_app HostName 206.***.***.*04 AddKeysToAgent yes UseKeychain yes User root PubKeyAuthentication yes IdentityFile ~/.ssh/id_rsa2 User **** IdentitiesOnly yes ``` Using ssh -v email@example.com..... I get this: ```debug1: Reading configuration data /Users/me/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 48: Applying options for * debug1: Connecting to 206.***.***.104 port 22. debug1: Connection established. debug1: identity file /Users/me/.ssh/id_rsa type 0 debug1: key_load_public: No such file or directory debug1: identity file /Users/me/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/me/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/me/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/me/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/me/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/me/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /Users/me/.ssh/id_ed25519-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_7.6 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2p2 Ubuntu-4ubuntu2.4 debug1: match: OpenSSH_7.2p2 Ubuntu-4ubuntu2.4 pat OpenSSH* compat 0x04000000 debug1: Authenticating to 206.***.***.104:22 as 'root' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: firstname.lastname@example.org debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: email@example.com MAC: <implicit> compression: none debug1: kex: client->server cipher: firstname.lastname@example.org MAC: <implicit> compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: ecdsa-sha2-nistp256 SHA256:AfTvjUf8r80AyTpEkhrPShNm7viLZNwj0/lIlKxPM5E debug1: Host '206.***.***.104' is known and matches the ECDSA host key. debug1: Found key in /Users/me/.ssh/known_hosts:7 debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after 134217728 blocks debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512> debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:Ga8Ww/neSf7llHCfb3r6171pNb0RKyKVzdYFanRAo6o /Users/me/.ssh/id_rsa debug1: Authentications that can continue: publickey debug1: Trying private key: /Users/me/.ssh/id_dsa debug1: Trying private key: /Users/me/.ssh/id_ecdsa debug1: Trying private key: /Users/me/.ssh/id_ed25519 debug1: No more authentication methods to try. root@206.***.***.104: Permission denied (publickey).``` I'm stumped.
I have just set up a Kubernetes cluster on DigitalOcean. I have followed the suggested tutorial but when I try and run the commands I keep getting prompted for a username and password which I have not been provided with. I have seen a few posts where people say it will be emailed to me but it's been well over an hour since the set-up completed and I have still not been emailed with anything (yes, I checked the usual places) Commands I ran: $> doctl kubernetes cluster kubeconfig save MY-CLUSTER Notice: adding cluster credentials to kubeconfig file found in "/Users/anthonybudd/.kube/config" Notice: setting current-context to do-sfo2-ideea-prod $> kubctl get nodes Please enter Username: Tutorial https://www.digitalocean.com/docs/kubernetes/how-to/connect-to-cluster/ Any help or insights would be appreciated.
What's the bandwidth for different size of droplets?