WPCloud Deploy Documentation

Common Server Deployment Issues & Error Messages

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:

Message: Unfortunately we could not start deploying this server – most likely because of an error from the provider api.

Symptom: You see the following message on your screen after attempting to create a server:

  • Unfortunately we could not start deploying this server – most likely because of an error from the provider api (an example of this is shown below)

Example of error message that can appear when attempting to deploy a server from WPCD

There are usually two causes for this:

  1. The private key is malformed in the settings screen
  2. The API Keys or other credentials for the provider are not correct

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.

Message: Error updating xxx or Error installing xxx. Please delete this server and restart the process.

Symptom: You see any of the following messages:

  • Error updating repositories. Please delete this server and restart the process.
  • Error installing dos2unix. Please delete this server and restart the process.
  • Error installing vnstat. Please delete this server and restart the process.

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.

Attempting To Use Your Local PC For Deployment

Most personal computers cannot be accessed from the public internet so the callbacks that the server deployment process uses will simply not work.

Stuck at “sudo: dos2unix: command not found

Symptom: You see the following message in the black “terminal” window:

  • sudo: dos2unix: command not found

This is the real deal – it is stuck.  This tends to happen most often with Digital Ocean servers.

To resolve:

  1. Click on the ALL CLOUD SERVERS Main menu to see the server list.
  2. DELETE the server that you were trying to create – you can do this by hovering over the server record and clicking the TRASH link.  This should also delete the in-process server at the cloud provider.
  3. Retry creating the server again.

Stuck at “E: Could not get lock /var/lib/dpkg/lock-frontend – open (11: Resource temporarily unavailable)”

Symptom: You see the following messages in the black “terminal” window:

  • E: Could not get lock /var/lib/dpkg/lock-frontend – open (11: Resource temporarily unavailable)
  • E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

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:

  1. Click on the ALL CLOUD SERVERS Main menu to see the server list.
  2. DELETE the server that you were trying to create – you can do this by hovering over the server record and clicking the TRASH link.  This should also delete the in-process server at the cloud provider.
  3. Retry creating the server again.

Message In “terminal”: Warning: 3 database(s) sources were not found

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.

Message In “terminal”: Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal

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.

Message In “terminal”: unable to initialize frontend: Dialog

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.

Share: