supervisor-stdout | simple supervisord event listener to relay | Continuous Deployment library
kandi X-RAY | supervisor-stdout Summary
kandi X-RAY | supervisor-stdout Summary
A simple supervisord event listener to relay process output to supervisor's stdout. This is useful in situations where the output will be collected and set to external logging framework, such as Heroku.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Main event loop .
- Event handler .
- Write stdout to sys . stdout
- Write s to stderr .
supervisor-stdout Key Features
supervisor-stdout Examples and Code Snippets
Community Discussions
Trending Discussions on supervisor-stdout
QUESTION
I have a Dockerized Django application, which I'm orchestrating with Supervisor, which is not optimal but needed when hosting on Azure app services as their multi-app support with docker-compose is still in preview mode (aka. beta).
According to best-practises I have configured each application within supervisord to emit the logs to STDOUT. It works fine when I create the Docker image locally, run it and check the docker logs. However, when I have deployed it to Azure app services and check the logs, my web-application (Gunicorn) is logging as expected, however, the logs from NGINX don't appear at all.
I have tried different configurations in my Dockerfile for linking the log files generated by NGINX (linking to both /dev/stdout and /dev/fd/1 for example) and I have also gone into the the nginx.conf config and trying to log out directly to /dev/stdout. But whatever I do it work fine locally, but on Azure the logs don't show any NGINX-logs. I've pasted relevant configuration files, where you can see the commented lines with the options I've tried with. Hope someone can help me figure this one out.
EDIT: I've also tried logging the NGINX app to a log-file in the system, which also works fine locally, but not in Azure app-services. I tried deactivating the "user nginx" part in nginx.conf as I though it could have something to do with permissions, but that didn't help either.
EDIT 2: I also tried creating the log files in my home-directory in the web-app at Azure, thinking it may had to do with not being able to create logs in other directories - again, it works locally, but the logs in Azure are empty.
Dockerfile
...ANSWER
Answered 2022-Jan-25 at 11:27Solved it. The issue was that the Azure App service had the configuration setting WEBSITES_PORT=8000 set, which made the app go straight to gunicorn and bypsasing NGINX, thus not creating any logs. Simply removing the setting fixed the issue.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install supervisor-stdout
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page