Skip to content

troubleshooting.md

Latest commit

 

History

History
149 lines (102 loc) · 5.58 KB

troubleshooting.md

File metadata and controls

149 lines (102 loc) · 5.58 KB

Troubleshooting

Below is a list of known rare issues and ways to resolve them.

Failed creating Docksal virtual machine

Mostly on Windows 7, but sometimes on other OS-s, VirtualBox fails to create a new virtual machine on the first run. Errors might vary. Removing the failed machine and trying again usually helps.

fin vm remove
fin vm start

Error checking TLS connection (vm is not accessible)

Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "192.168.64.100:2376": dial tcp 192.168.64.100:2376: getsockopt: connection refused
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which will stop running containers.

Sometimes docker-machine certificates re-generation fails. This usually can be resolved with fin vm restart.

If a restart does not help try

fin docker-machine regenerate-certs docksal -f
fin vm restart

However in rare cases this may not help ether and the only solution would be to delete the existing Docksal VM and re-create it.

fin vm remove
fin vm start

Lack of memory

Composer on Drupal 8 projects might spawn this error:

The following exception is caused by a lack of memory and not having swap configured
Check https://getcomposer.org/doc/articles/troubleshooting.md#proc-open-fork-failed-errors for details

By default, a Docksal virtual machine is provisioned with 1GB (1024MB) of RAM. Drupal 8 tools sometimes require more that that.

Set a bigger amount of RAM for the VM, e.g. 2048 Mb

fin vm ram 2048

Conflicting exports (files are not accessible)

 ERROR:  conflicting exports for /Users, 192.168.64.100
exports:11: export option conflict for /Users
-----------------
/Users 192.168.64.100 -alldirs -mapall=0:0
# <ds-nfs docksal
/Users 192.168.64.100 -alldirs -mapall=501:20
# ds-nfs>

With NFS a single directory can only be exported once. It can not be exported several times with different settings.

Remove the conflicting export from /etc/exports (remove the non-docksal one), save the file, and run fin vm restart or fin vm start again.

Conflicting ports

Resetting Docksal services...
 * proxy
docker: Error response from daemon: driver failed programming external connectivity
on endpoint docksal-vhost-proxy (a7addf7797e6b0aec8e3e810c11775eb77508c9079e375c083b3650df2dff9a2):
Error starting userland proxy: listen tcp 0.0.0.0:443: listen: address already in use.

This usually happens on Linux because the default Apache server bind to 0.0.0.0:80 and 0.0.0.0:443 (all IPs).
This prevents Docksal from running properly.

You either need to stop Apache or reconfigure it to listen on different ports (e.g. 8080 and 4433) or different/specific IPs (e.g. 127.0.0.1:80 and 127.0.0.1:443).

Config permissions issue (vm does not start)

open /Users/John.Doe/.docker/machine/machines/docksal/config.json: permission denied

You careated the Docksal VM as the root user (probably using sudo).
This is not recommended in particular because of the problems like this.

Re-create vm as a regular user

sudo fin vm remove
fin vm start

Multiple host-only adapters (vm is not created)

Error with pre-create check: "VirtualBox is configured with multiple host-only adapters with the same IP \"192.168.64.1\". Please remove one."
  1. Open VirtualBox UI
  2. Open Preferences > Network tab
  3. Click "Host-only Networks" tab
  4. Click through adapters in list and delete the ones with the 192.168.64.1 IP

DNS server misbehaving

ERROR: error pulling image configuration: Get https://dseasb33srnrn.cloudfront.net/registry-v2/docker/registry/v2/blobs/sha256/9f/9fb8c0aed5fc7cc710884dc9cbd0974cc606053989b4f73f20e8b363e7d6cc7f/data?Expires=1490711517&Signature=SzvWOicPa6yZRxlBh1~vsl2xHtkOXR8xDj~usSP8aS9ZFhNQ8oH5pAcfZyx3sxgPgtqPgSOzuoaBtw5lT0~i0mpt~QCBpkgRhgyRQ8rzkbI1sG9ZRDXvRQ4sG49ckorbHyUT8isG5mEWl3Ar8kateU9he9fdlRhe5V5Zvn-et0s_&Key-Pair-Id=APKAJECH5M7VWIS5YZ6Q: dial tcp: lookup dseasb33srnrn.cloudfront.net on 10.0.2.3:53: server misbehaving

Pulling db (docksal/db:1.0-mysql-5.5)...
ERROR: Get https://registry-1.docker.io/v2/: dial tcp: lookup registry-1.docker.io on 10.0.2.3:53: server misbehaving

Your system DNS server does not properly resolve index.docker.io.

Use Google Public DNS server or Open DNS.

  1. Please refer to the doc on how to apply DNS on your operating system.
  2. fin vm restart after you apply your new DNS settings.

macOS DNS settings example:

macOS DNS settings

FastCGI: incomplete headers

web_1        | [Wed Apr 19 14:57:37 2017] [error] [client 172.19.0.6] (111)Connection refused: FastCGI: failed to connect to server "/usr/lib/cgi-bin/php5-fcgi": connect() failed
web_1        | [Wed Apr 19 14:57:37 2017] [error] [client 172.19.0.6] FastCGI: incomplete headers (0 bytes) received from server "/usr/lib/cgi-bin/php5-fcgi"
web_1        | 172.19.0.6 - - [19/Apr/2017:14:57:37 +0000] "GET / HTTP/1.1" 500 639 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36"

Errors like this appear when your Apache is misconfigured. Most often it happens because of misconfigured environment variables in docksal.yml. Sometimes it can be misconfiguration in .htaccess.

Check those files for errors, fix them and run fin start.