Skip to content
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.

Sign up for GitHub

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

Jump to bottom

500 internal error,but i can't found out the log #549

Closed
marion2016 opened this issue Oct 16, 2018 · 1 comment
Closed

500 internal error,but i can't found out the log #549

marion2016 opened this issue Oct 16, 2018 · 1 comment

Comments

@marion2016
Copy link
Contributor

Actual results

there is no log in the system

Expected results

log in the /var/log/httpd

Additional info (Python traceback, logs, etc.)
@marion2016
Copy link
Contributor Author

because i can't find the log file ,so i dont even know what happen on the server.
there is someone can tell me where is the log file?

atodorov added a commit that referenced this issue Oct 31, 2018
@atodorov
Update Apache config to print logs on the console. Fixes #549
31e0b51 
because the previous configuration was not properly redirecting
access and errors to stdout/stderr.

Also add a warning section in the docs to make it clear that
using -d for docker-compose will not show you the logs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@marion2016