You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: