Services
Overview
The Services view displays the status and configuration of services used by apps.
Services are shared between apps but remain isolated from each other. Services are provisioned and configured as and when apps are deployed. The platform manages automatic database upgrades and migration.
In app packaging context, database services are referred to as addons.
Configure
Service settings can be configured for memory limits and other parameters:
Logs
Service logs are available for viewing and troubleshooting.
Up to 10MB of logs are retained per service alongside 1 rotated log. Logs older than 14 days are removed.
The raw logs are located under /home/yellowtent/platformdata/logs/<servicename>.
Troubleshooting
The first step is to check the service logs for hints about why the service is not working as intended.
Often, restarting the service or increasing the memory limit fixes the problem.
Corrupt addon
These instructions apply to the following database addons:
| Database | Container name | Logs | Data Directory |
|---|---|---|---|
| MySQL | mysql | /home/yellowtent/platformdata/logs/mysql/app.log | /home/yellowtent/platformdata/mysql |
| PostgreSQL | postgresql | /home/yellowtent/platformdata/logs/postgresql/app.log | /home/yellowtent/platformdata/postgresql |
| MongoDB | mongodb | /home/yellowtent/platformdata/logs/mongodb/app.log | /home/yellowtent/platformdata/mongodb |
| Redis | redis-$appid | /home/yellowtent/platformdata/logs/redis-$appid/app.log | /home/yellowtent/platformdata/redis/$appid |
For disk corruption, start fresh and restore data from backups.
To restore a specific service:
docker stop <containername>
mv /home/yellowtent/platformdata/<service> /home/yellowtent/platformdata/<service>-copy # stash the database data directory. see table above
mkdir /home/yellowtent/platformdata/<service> # create a fresh database directory
docker restart <containername> # start the addon. this will re-initialize the addon with no data
Now, restore each app that uses the service.