-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
logs and service names need documentation #17
Comments
basically one uses the CLI provided by Supervisor. For example, to see the status of all processes, try:
@ned-kelly correct? if so let's close this one. |
Hi @frecuencialibre - yep, the docker build is using supervisor - It's probably worth quickly skimming over the supervisor docs here. You can also access the interactive supervisor shell by running On the subject of accessing logs, it's probably also worth adding in that all services log to the stderr/stdout of the docker container, so it's best to easily access logs using the docker daemon i.e. Hope this helps shed some light. |
the libretime troubleshooting docs don't apply to this docker install. two parts:
LOGS:
i see some in
/var/log/supervisor
and some in/var/log/airtime
. and then there are docker logs. is that it?SERVICES:
we should document their names ( libretime-airtime_analyzer? etc.) and how check their status/restart them, ie. what's the best replacement for
invoke-rc.d
?@ned-kelly if you can give me some guidance here i'd take a crack at drafting this.
The text was updated successfully, but these errors were encountered: