The application log will not show using docker logs, only supervisord logs are showing
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 283
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
When MISP is started, application logs by default are located at /var/www/MISP/app/tmp/logs, I have changed bootstrap.php to use Console log instead of file log. However it could be because of supervisord, the docker logs will only show supervisord logs.
Here is what's in your supervisord configuration.
command=/bin/bash -c "source /etc/apache2/envvars && exec /usr/sbin/apache2 -DFOREGROUND"
I know docker will only collect logs from current console. So I have added the following based on this document.
http://veithen.io/2015/01/08/supervisord-redirecting-stdout.html
But it's still not working.
stdout_logfile=/dev/stdout
stdout_logfile_maxbytes=0
I think the reason might be because the command starts a new shell.
Could you find out why?
Thanks
Tao
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting bootstrap.php and the supervisord configuration, especially the Apache foreground command and stdout settings. Reproduce the container startup and trace where application logs are emitted versus collected; done means application logs are visible through docker logs rather than only in supervisord output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100