Created attachment 32587 [details] Log files for error Hello I am using Redmine project management (www.redmine.org) software (similar to bugzilla) and I am using Bitnami (www.bitnami.com) bundle installer for Redmine instance for Windows. Bitnami uses Apache 2.4 for Redmine bundle installer. Starting from version 3.0.0 (and 3.0.1 too) I have found error, that a Redmine Wiki page, that has specific Russian word "Информация" (translation: Information) written from capital letter only! causes Internal server error while trying to open such page. Redmine itself seems not affected by this problem, because I am able to create such page at their official web site redmine.org , so its a problem with my installation. Its easy to reproduce, just get latest bitnami Redmine 3.0.1 installer (https://bitnami.com/redirect/to/51600/bitnami-redmine-3.0.1-0-windows-installer.exe), setup it, and try to access "http://localhost/redmine/%D0%98%D0%BD%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%86%D0%B8%D1%8F" page - it leads to internal server error. Below is my logs for this error, I dont know what to do really, because Redmine Team says its not their error and Bitnami Team seems dont know what to do too... bugreport: http://www.redmine.org/issues/193212 - on redmine.org here video recording for this problem: http://youtu.be/r3TITwOP_Fk Apache error logs: find 22:02:48 time, at error.log and access.log https://cloud.mail.ru/public/5fb423d7bb7e/updatedlogs.zip Bitnami support thread: https://community.bitnami.com/t/problems-with-3-0-1-installation-see-report-inside/30195 Help me please, I dont know where else to go with this :'(
Any news on my report?
Try LogLevel trace8 and attaching the errorlog directly to this bug report. Presumably the encoding of that character matches some blacklisted octet for the platform httpd is on.
https://cloud.mail.ru/public/b4d5322419d3/part1%20logs_24032015_11h21m50s%20event%20time.zip https://cloud.mail.ru/public/bd9b45aff45e/part2%20logs_24032015_11h26m00s%20event%20time.zip attached please find 2 log archives with trace8 level.
Created attachment 32598 [details] access part1 logs_24032015_11h21m50s event time
Created attachment 32599 [details] access part2 logs_24032015_11h26m00s event time
Created attachment 32600 [details] error part1 logs_24032015_11h21m50s event time
Created attachment 32601 [details] error part2 logs_24032015_11h26m00s event time
It seems that the redmine itself (127.0.0.1:3001) responds with status 500 (Internal Server Error) with path "/%D0%98%D0%BD%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%86%D0%B8%D1%8F", mod_proxy is simply forwarding that error response. You probably have to check redmine's logs for the original cause.
Here are some relevent log lines : [Tue Mar 24 11:21:50.890271 2015] [proxy_http:trace1] [pid 5360:tid 1364] mod_proxy_http.c(1944): [client ::1:62027] HTTP: serving URL http://127.0.0.1:3001/redmine/projects/fsfsdfds/wiki/%D0%98%D0%BD%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%86%D0%B8%D1%8F [Tue Mar 24 11:21:50.890271 2015] [proxy:debug] [pid 5360:tid 1364] proxy_util.c(2138): AH00942: HTTP: has acquired connection for (127.0.0.1) [Tue Mar 24 11:21:50.890271 2015] [proxy:debug] [pid 5360:tid 1364] proxy_util.c(2192): [client ::1:62027] AH00944: connecting http://127.0.0.1:3001/redmine/projects/fsfsdfds/wiki/%D0%98%D0%BD%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%86%D0%B8%D1%8F to 127.0.0.1:3001 [Tue Mar 24 11:21:50.890271 2015] [proxy:debug] [pid 5360:tid 1364] proxy_util.c(2393): [client ::1:62027] AH00947: connected /redmine/projects/fsfsdfds/wiki/%D0%98%D0%BD%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%86%D0%B8%D1%8F to 127.0.0.1:3001 [Tue Mar 24 11:21:50.890271 2015] [proxy:trace2] [pid 5360:tid 1364] proxy_util.c(2735): HTTP: fam 2 socket created to connect to 127.0.0.1 [Tue Mar 24 11:21:50.890271 2015] [proxy:debug] [pid 5360:tid 1364] proxy_util.c(2767): AH02824: HTTP: connection established with 127.0.0.1:3001 (127.0.0.1) [Tue Mar 24 11:21:50.891273 2015] [proxy:debug] [pid 5360:tid 1364] proxy_util.c(2921): AH00962: HTTP: connection complete to 127.0.0.1:3001 (127.0.0.1) [Tue Mar 24 11:21:50.891273 2015] [core:trace6] [pid 5360:tid 1364] core_filters.c(525): [remote 127.0.0.1:3001] core_output_filter: flushing because of FLUSH bucket [Tue Mar 24 11:21:50.897289 2015] [proxy_http:trace3] [pid 5360:tid 1364] mod_proxy_http.c(1423): [client ::1:62027] Status from backend: 500 [Tue Mar 24 11:21:50.897289 2015] [proxy_http:trace4] [pid 5360:tid 1364] mod_proxy_http.c(1098): [client ::1:62027] Headers received from backend: [Tue Mar 24 11:21:50.897289 2015] [proxy_http:trace4] [pid 5360:tid 1364] mod_proxy_http.c(1101): [client ::1:62027] Content-Type: text/plain [Tue Mar 24 11:21:50.897289 2015] [proxy_http:trace4] [pid 5360:tid 1364] mod_proxy_http.c(1101): [client ::1:62027] Connection: keep-alive [Tue Mar 24 11:21:50.897289 2015] [proxy_http:trace4] [pid 5360:tid 1364] mod_proxy_http.c(1101): [client ::1:62027] Content-Length: 21 [Tue Mar 24 11:21:50.897289 2015] [proxy_http:trace4] [pid 5360:tid 1364] mod_proxy_http.c(1101): [client ::1:62027] Server: thin 1.6.1 codename Death Proof
I have checked for redmine production log, but it does not make any recordings even at "debug" log mode. The last recording is "200 OK" for previous page that was loaded normally. Thanks for help anyway, Ill point Redmine team to this thread, probably they will find something...
Created attachment 32603 [details] redmine production log (debug mode)
Have you tried the "nocanon" option?
No, i have not tested nocanon. I have tried googling how to turn on nocanon option, but there is no clear info. I can try, pls tell me how to do it.
Look for the text here: http://httpd.apache.org/docs/2.4/mod/mod_proxy.html
Thanks to Toshi MARUYAMA from Redmine Team, this problem is resolved! "https://github.com/macournoyer/thin/issues/268" "https://github.com/marutosi/rails/commit/c53a49e0bbe615d5ff51620a993c4d3d79c73370" I have updated line 32 at my file\apps\redmine\htdocs\vendor\bundle\ruby\2.0.0\gems\actionpack-4.2.0\lib\action_dispatch\middleware\static.rb from "path = File.join(@root, p)" to "path = File.join(@root, p.force_encoding('UTF-8'))" And now links with capital "И" opens correctly! Thanks to everyone who take part in resolving this problem.