зеркало из https://github.com/mozilla/treeherder.git
Bug 1178300 - Docs: Move Vagrant troubleshooting steps to their own page
Since most people will not require them, and the list is growing quite large.
This commit is contained in:
Родитель
85a6cfdec3
Коммит
3e248c5bf8
|
@ -17,36 +17,7 @@ Setting up Vagrant
|
|||
|
||||
>vagrant up
|
||||
|
||||
**Troubleshooting**: The Vagrant provisioning process during ``vagrant up`` assumes the presence of a stable internet connection. In the event of a connection interruption during provision, you may see errors similar to *"Temporary failure resolving.."* or *"E: Unable to fetch some archives.."* after the process has completed. In that situation, you can attempt to re-provision using the command:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
>vagrant provision
|
||||
|
||||
If that is still unsuccessful, you should attempt a ``vagrant destroy`` followed by another ``vagrant up``.
|
||||
|
||||
**Troubleshooting**: If you encounter an error saying *"It appears your machine doesn't support NFS, or there is not an adapter to enable NFS on this machine for Vagrant."*, then you need to install ``nfs-kernel-server`` using the command:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
apt-get install nfs-kernel-server
|
||||
|
||||
**Troubleshooting**: If you encounter an error saying *"mount.nfs: requested NFS version or transport protocol is not supported"*, you should restart the kernel server service using this sequence of commands:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
systemctl stop nfs-kernel-server.service
|
||||
systemctl disable nfs-kernel-server.service
|
||||
systemctl enable nfs-kernel-server.service
|
||||
systemctl start nfs-kernel-server.service
|
||||
|
||||
**Troubleshooting**: If you encounter an error saying *"The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'poweroff' state. Please verify everything is configured properly and try again."* you should should check your host machine's virtualization technology (vt-x) is enabled in the BIOS (see this guide_), then continue with ``vagrant up``.
|
||||
|
||||
.. _guide: http://www.sysprobs.com/disable-enable-virtualization-technology-bios
|
||||
|
||||
For the full list of available Vagrant commands, please see their command line documentation_.
|
||||
|
||||
.. _documentation: http://docs.vagrantup.com/v2/cli/
|
||||
If you experience any errors, see the :ref:`troubleshooting page <troubleshooting-vagrant>`.
|
||||
|
||||
* It will typically take 5 to 30 minutes for the vagrant up to complete, depending on your network performance.
|
||||
|
||||
|
@ -58,6 +29,10 @@ Setting up Vagrant
|
|||
|
||||
A python virtual environment will be activated on login, and the working directory will be the treeherder source directory shared from the host machine.
|
||||
|
||||
For the full list of available Vagrant commands, please see their command line documentation_.
|
||||
|
||||
.. _documentation: http://docs.vagrantup.com/v2/cli/
|
||||
|
||||
* If you just wish to :ref:`run the tests <running-tests>`, you can stop now without performing the remaining steps below.
|
||||
|
||||
Setting up a local Treeherder instance
|
||||
|
|
|
@ -1,6 +1,38 @@
|
|||
Troubleshooting
|
||||
===============
|
||||
|
||||
.. _troubleshooting-vagrant:
|
||||
|
||||
Errors during Vagrant setup
|
||||
---------------------------
|
||||
|
||||
* The Vagrant provisioning process during ``vagrant up`` assumes the presence of a stable internet connection. In the event of a connection interruption during provision, you may see errors similar to *"Temporary failure resolving.."* or *"E: Unable to fetch some archives.."* after the process has completed. In that situation, you can attempt to re-provision using the command:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
>vagrant provision
|
||||
|
||||
If that is still unsuccessful, you should attempt a ``vagrant destroy`` followed by another ``vagrant up``.
|
||||
|
||||
* If you encounter an error saying *"It appears your machine doesn't support NFS, or there is not an adapter to enable NFS on this machine for Vagrant."*, then you need to install ``nfs-kernel-server`` using the command:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
apt-get install nfs-kernel-server
|
||||
|
||||
* If you encounter an error saying *"mount.nfs: requested NFS version or transport protocol is not supported"*, you should restart the kernel server service using this sequence of commands:
|
||||
|
||||
.. code-block:: bash
|
||||
|
||||
systemctl stop nfs-kernel-server.service
|
||||
systemctl disable nfs-kernel-server.service
|
||||
systemctl enable nfs-kernel-server.service
|
||||
systemctl start nfs-kernel-server.service
|
||||
|
||||
* If you encounter an error saying *"The guest machine entered an invalid state while waiting for it to boot. Valid states are 'starting, running'. The machine is in the 'poweroff' state. Please verify everything is configured properly and try again."* you should should check your host machine's virtualization technology (vt-x) is enabled in the BIOS (see this guide_), then continue with ``vagrant up``.
|
||||
|
||||
.. _guide: http://www.sysprobs.com/disable-enable-virtualization-technology-bios
|
||||
|
||||
Using supervisord for development
|
||||
---------------------------------
|
||||
|
||||
|
|
Загрузка…
Ссылка в новой задаче