-
Notifications
You must be signed in to change notification settings - Fork 29
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
End of script output before headers: mapserv_wrapper #179
Comments
It's looks strange, normally the message |
I just try to digg deepr and this is result from MS_DEBUGLEVEL=5 at first call:
this is a log from subsequent calls:
Probably something with PostGIS layers, maybe Postgres connection pooling related (different outputs based on calls order)... Attaching to docker logs probably won't have any effect here, probably just a coincidence with my tests... --- EDIT --- |
Probably yes :-) |
Unfortunately, i didn't receive any suggestions at MS mailing list about this issues. But I think it has to be related to hoe Apache interact with mapserver. When I exec mapserv directly or through wrapper inside container, everything works as expected. Issues appear only when I request something through Apache... Strange... |
Some outputs from mapserver_wrapper result in Apache 500 HTTP response. For example, querying browse mode without a defined template produce this log message and HTTP 500 response:
But when I try exec into container and execute mapserv_wrapper (or mapserv) directly, like this:
it produces correct HTML response:
It works a bit strange by my observations. For example, when I attach to container log (docker logs -f) it starts to produce correct HTML responses instead of 500
I also try to redirect error output to stdout or file, instead of stderr, but with no luck.
Probably the 'end of script output before headers: mapserv_wapper' is the key, but I dong know what can be wrong...
The text was updated successfully, but these errors were encountered: