Commit 63b1c518 authored by Daniel Seybold's avatar Daniel Seybold
Browse files

extended troubleshooting

parent 5df40072
......@@ -61,8 +61,7 @@ series = {SAC '20}
doi = {10.1145/3297663.3310303},
acmid = {3310303},
publisher = {ACM},
address = {New York, NY, USA},
keywords = {benchmarking, cloud, distributed database, nosql, scalability},
address = {New York, NY, USA}
}
```
......
......@@ -63,7 +63,7 @@ Execute the following steps to deploy the Mowgli framework:
**Task 4:** create the folder for the Cloudiator data: ```sudo mkdir -p /var/lib/cloudiator/cloudiator-store/```
**Task 5:** checkout the repository which includes the docker-compose.yml: ```git clone https://omi-gitlab.e-technik.uni-ulm.de/mowgli/docker.git mowgli```
**Task 6:** create the .env file based on the env-template: ```cd mowgli && cp env-template .env```
**Task 7:** add the public IP of the host the .env
**Task 7:** add the **publicly accessible IP** of the host to the .env
**Task 8 (optional):** In case the host is running in an enterprise network and requires certificates please check the [wiki](https://omi-gitlab.e-technik.uni-ulm.de/mowgli/getting-started/wikis/Add-Certificates)
**Task 9:** start the Mowgli services via: ```sudo docker-compose up -d```
**Task 10:** open your browser and check if the Mowgli framework started successfully at: `http://MOWGLI_HOST:8282` or `http://MOWGLI_HOST:8282/explorer`
......
## Troubleshooting
#### Containers fail on start-up
Please make sure you have set the **public IP** in `.env` file for the docker-compose, see also [here](../setup/README.md)
#### Logging
All logs can be viewed via the portainer service on http://MOWGLI_HOST:9001/#/auth with the default credentials user: `admin` and password `mowgli19`.
All logs can be viewed via the Portainer service on http://MOWGLI_HOST:9001/#/auth with the default credentials user: `admin` and password `mowgli19`.
The relevant service containers are:
......@@ -24,17 +28,36 @@ Triggers the DBMS deployment via Cloudiator.
Fetches the cloud offerings, creates VMs and deploys applications on the VMs.
*Error regarding the cloud provider will be found in this container logs!*
*Errors regarding the cloud provider will be found in this container logs!*
#### Reset Mowgli
In case you have registered invalid cloud credentials (check the Cloudiator-Service logs) you have to reset the state of the Mowgli framework. This will not affect the collected evaluation results but delete all data in Cloudiator. Hence, you need to register the Cloud again and fetch the VM templates again.
To reset Mowgli run the following commands
To reset Mowgli run the following script from the docker folder:
```
# change into the directory of the docker-composer
./resetMowgli
```
#### Update Mowgli
In case you want to update Mowgli to the **latest** release run the following script from the docker folder:
```
# change into the directory of the docker-compose
docker-compose down
rm -r /var/lib/cloudiator/cloudiator-store/*
docker-compose up -d
```
\ No newline at end of file
# change into the directory of the docker-composer
./updateMowgli
```
In case you want to update Mowgli to a specific release you need to adapt the `updateMowgli` script accordingly!
## Support
In case of any issues with setting up Mowgli or running experiments feel free to subscribe the the Mowgli mailing list and/or post your issue at
mowgli@lists.uni-ulm.de
In order to ease the support process, please provide the latest docker logs of the following containers:
`evaluation-orchestrator`, `application-catalogue` and `cloudiator-service`
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment