Sometimes, when attempting to deploy a server, it might look as if the process has “hung”. Most times it has not – it just takes a while to deploy a server. The time could be from 20 minutes to as long as 45 minutes depending on the cloud provider and the size of the server being deployed. Our software stack alone can take 15+ minutes to install.
But, that doesn’t mean that you might not run into issues. Here are some common ones:
Symptom: You see the following message on your screen after attempting to create a server:
There are three common causes for this:
The malformed private key issue is the most common one. If you copy your key directly from the SSH console (eg: by CATing it out or opening in NANO/VIM and then copy-and-paste), it will end up with unwanted spaces when pasted into our settings screen. You should always download your original key-pair files and open the private key file in a notepad application (not a word-processing application) and then copy-and-paste from there.
Symptom: You see any of the following messages:
These mean what they say – something went wrong and it was serious enough that you need to delete the in-process server and start over again.
This tends to happen most often with Digital Ocean servers. What we have realized is that the droplets or VMs that these errors occur on are generally the most unstable. Getting the error now prevents you from more serious issues later on down the line when the VM or droplet really degrades and you lose data.
Most personal computers cannot be accessed from the public internet so the callbacks that the server deployment process uses will simply not work.
Symptom: You see the following message in the black “terminal” window:
This is the real deal – it is stuck. This tends to happen most often with Digital Ocean servers.
To resolve:
Symptom: You see the following messages in the black “terminal” window:
And, these messages are the last line in the “terminal” window – no more log entries are being printed.
This is the real deal – it is stuck. This tends to happen most often with Digital Ocean servers.
To resolve:
You see the following message in the “terminal” window:
Warning: 3 database(s) sources
were not found, (but were created)
please investigate.
This is just a warning and not an issue. You should see additional log entries printed immediately after this indicating that the installation is continuing.
You see the following message in the “terminal” window on a number of lines:
Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.
This is informational and not an issue. Its just complaining because the process isn’t really running in a terminal with a real screen.
You see the following message in the “terminal” window on a number of lines:
unable to initialize frontend: Dialog
This is informational and not an issue. Its just complaining because the process isn’t really running in a terminal with a real screen.