Machine and ssh failures
A machine that cannot be reached, started or changed answers one of these. Each entry names the cause and the fix, in the order people meet them.
machine not found
Section titled “machine not found”Cause. The id belongs to a machine in another account, or its record has been retired. Machinery answers this same sentence for a machine that never existed and for one in another account, so the refusal does not say which.
Fix. List the machines in the account your CLI is using:
deployport machinery listIf the machine is in another account, switch the CLI to it and run the command again:
deployport iam accounts switch <account-name>Verify. The id appears in deployport machinery list, and the command that refused runs.
machine was deregistered
Section titled “machine was deregistered”Cause. The machine was deregistered. A retired machine cannot be reached or changed, and its record is deleted about an hour later, after which the same command answers machine not found. A retired record is left out of deployport machinery list from the moment it retires.
Fix. A deregistered machine does not come back. Create a new one:
deployport machinery createVerify. deployport machinery list shows the new machine’s id, and it reads Online in the console’s Machines list.
This machine runs on Deployport Compute or in a cluster you own. Terminate it to destroy the machine and its instance.
Section titled “This machine runs on Deployport Compute or in a cluster you own. Terminate it to destroy the machine and its instance.”Cause. Deregister retires the machine’s record only. The instance keeps running with nothing naming it, so deregister is refused for one.
Fix. Destroy the instance and the record together:
deployport machinery terminate <machine-id> --yesVerify. The id is gone from deployport machinery list, and the instance is gone from the platform that ran it.
This machine is still being created. Destroy it once the launch finishes.
Section titled “This machine is still being created. Destroy it once the launch finishes.”Cause. A machine is recorded first and launched after, so there is a window in which the record exists and the instance does not. Terminate is refused during that window, because there is nothing to destroy yet.
Fix. Wait for the launch to settle, then run the command again:
deployport machinery listVerify. The console’s Machines list stops reading Launching… for the machine. If the launch failed, the row reads Launch failed and the machine page names the step that refused.
This machine no longer offers a tunnel. Update the Deployport CLI to connect through the SSH gateway
Section titled “This machine no longer offers a tunnel. Update the Deployport CLI to connect through the SSH gateway”Cause. The CLI is older than the route machines are reached through now. Every machine answers ssh through the Deployport SSH gateway, and a CLI from before that route offers the machine’s old tunnel instead.
Fix. Update the CLI:
deployport version upgradeVerify. deployport machinery ssh <machine-id> connects.
This machine's agent reports no SSH server listening
Section titled “This machine's agent reports no SSH server listening”The whole sentence is:
This machine's agent reports no SSH server listening, so there is nothing to connect to.Cause. The machine answered, so it is reachable, and nothing on it is listening for ssh. This is a machine whose sshd is stopped or not installed, which is the one you can fix on the machine itself.
Fix. Run a command on the machine and look at the service:
deployport machinery commands run <machine-id> -- systemctl status sshdeployport machinery commands run <machine-id> -- systemctl start sshVerify. deployport machinery ssh <machine-id> connects.
machine <machine-id> has reported no login user
Section titled “machine <machine-id> has reported no login user”The whole sentence is:
machine <machine-id> has reported no login user, connect with "deployport machinery ssh <user>@<machine-id>"Cause. The machine has not reported which OS user a session lands as, and the CLI refuses rather than connecting as your own local username, which is almost never an account on the machine.
Fix. Name the user yourself, or stamp the one the machine should use from now on:
deployport machinery ssh <os-user>@<machine-id>deployport machinery set-login-user <machine-id> <os-user>Verify. A plain deployport machinery ssh <machine-id> connects.
Permission denied (publickey)
Section titled “Permission denied (publickey)”Cause. The machine answered and refused the key your ssh offered. A key reaches a machine through your Deployport user, and the gateway checks it on every connection, so this usually means the key is not on your user, or you connected with plain ssh using a key that is.
Fix. Add the key to your user, and check which keys are there:
deployport iam ssh-keys add ~/.ssh/id_ed25519.pubdeployport iam ssh-keys listdeployport machinery ssh <machine-id> adds the key this computer already uses to your user on its first connection. Nothing is installed on the machine, so a key removed from your user is refused everywhere at once.
Verify. deployport iam ssh-keys list names the key, and deployport machinery ssh <machine-id> connects.
A resize of this machine is already running
Section titled “A resize of this machine is already running”Cause. A machine may have one resize at a time. Two runs racing one stop and one start would each read the other’s state, so the second is refused rather than queued.
Fix. Follow the run in flight and wait for it to finish:
deployport machinery resize-runs <machine-id>Verify. The run’s STATUS reaches succeeded, and the machine’s size is the one the run asked for.
That machine name is not available
Section titled “That machine name is not available”Cause. The name is held by another machine, it is reserved, or another account released it too recently to be given out again. The refusal does not say which, because telling those apart would answer which names are live machines.
Fix. Choose another name:
deployport machinery set-name <machine-id> <another-name>Verify. deployport machinery list shows the new name on the machine’s row.
this machine has been renamed as many times as it may be
Section titled “this machine has been renamed as many times as it may be”Cause. A machine’s name is the subdomain it answers on, and a name may be changed three times in a machine’s life. The allowance is used up.
Fix. Create a machine with the name you want:
deployport machinery create --name <the name you want>Verify. deployport machinery list shows the new machine under that name.
Add funds to this account to start this machine
Section titled “Add funds to this account to start this machine”Cause. The account’s balance does not cover this, so a start is refused before it reaches the platform. A create is refused with Add funds to this account to run a Deployport Compute machine, and a worker pool’s create with Add funds to this account to create a worker pool.
Fix. Add funds in the console, on Billing, and run the command again. The CLI prints the same address under the message.
Verify. deployport machinery start <machine-id> prints the power transition, and the machine reads Starting and then Online in the console’s Machines list.
Still stuck
Section titled “Still stuck”Ask us at Contact and include:
- the machine id, from
deployport machinery list - the command you ran, and its output
- the time it happened, with your time zone