The Overleaf Toolkit comes with a handy `doctor` script, to help with debugging. Just run `bin/doctor` and the script will print out information about your host environment, your configuration, and the dependencies the toolkit needs. This output can also help the Overleaf support team to help you figure out what has gone wrong, in the case of a Server Pro installation.
The `Host Information` section contains information about the machine on which the toolkit is running. This includes information about the type of Linux system being used.
### Dependencies
The `Dependencies` section shows a list of tools which are required for the toolkit to work.
If the tool is present on the system, it will be listed as `status: present`, along with the version of the tool. For example:
```
- docker
- status: present
- version info: Docker version 19.03.6, build 369ce74a3c
```
However, if the tool is missing, it will be listed as `status: MISSING!`, and a warning will be added to the bottom of the `doctor` output. For example:
```
- docker
- status: MISSING!
```
If any of the dependencies are missing, the toolkit will almost certainly not work.
### Configuration
The `Configuration` section contains information about the files in the `config/` directory. In the case of `config/overleaf.rc`, the doctor also prints out some of the more important values from the file. If any of the files are not present, they will be listed as `status: MISSING!`, and a warning will be added to the bottom of the `doctor` output. For example:
- The `MONGO_ENABLED` variable is set to `false`, so the toolkit will not provision it's own MongoDB database. In this case, we had better be sure to set `MONGO_URL` to point to a MongoDB database managed outside of the toolkit
- the `config/variables.env` file is missing
### Warnings
The `Warnings` section shows a summary of problems discovered by the doctor script. Or, if there are no problems, this section will say so. For example: