Discussion:
[pid 13342:tid 139714573051648] (36)File name too long: [client 173.254.xx.xx:47163] AH00127: Cannot map GET
(too old to reply)
ekhlas mulla
2018-03-26 12:47:36 UTC
Permalink
I have irritating error [core:error] [pid 13342:tid 139714573051648] (36)File name too long: [client 173.254.24.18:47163] AH00127: Cannot map GET in my apache log.
I am not able to find where it come from and which url or user causes this error in apche2 log

below some detail of my server
Apache Version 2.4.XX
PHP Version 5.6.XX
MySQL Version 5.6.XX
Architecture x86_64
Operating System linux

Please Help someone who know about this.
I R A Darth Aggie
2018-03-26 21:28:34 UTC
Permalink
On Mon, 26 Mar 2018 05:47:36 -0700 (PDT),
Post by ekhlas mulla
I have irritating error [core:error] [pid 13342:tid 139714573051648]
(36)File name too long: [client 173.254.24.18:47163] AH00127: Cannot
map GET in my apache log.
I am not able to find where it come from and which url or user
causes this error in apche2 log
below some detail of my server
Apache Version 2.4.XX
PHP Version 5.6.XX
MySQL Version 5.6.XX
Architecture x86_64
Operating System linux
Please Help someone who know about this.
I found this, but *shrugs* I have a feeling it won't help.

https://magento.stackexchange.com/questions/43942/ah00127-cannot-map-head-and-blank-page

It will useful to see the actual log messages. Go to the apache logs
directory, and grep for AH00127. I run debian, I would with elevated
privileges do this:

cd /var/log/apache2/
grep AH00127 *.log

and see what pops up.
--
Consulting Minister for Consultants, DNRC
I can please only one person per day. Today is not your day. Tomorrow
isn't looking good, either.
I am BOFH. Resistance is futile. Your network will be assimilated.
ekhlas mulla
2018-03-27 04:46:53 UTC
Permalink
Hi Aggie

Your feeling it won't help and it not helping me at all.

Are you try this before?
cd /var/log/apache2/
grep AH00127 *.log

i am not trying anything like this before.

is it harmful to apache2 or any website?
I R A Darth Aggie
2018-03-28 13:01:06 UTC
Permalink
On Mon, 26 Mar 2018 21:46:53 -0700 (PDT),
Post by ekhlas mulla
Hi Aggie
Your feeling it won't help and it not helping me at all.
Are you try this before?
cd /var/log/apache2/
grep AH00127 *.log
i am not trying anything like this before.
is it harmful to apache2 or any website?
Yes, I have. It's not harmful at all. Here's an example. I'm not
suffering from the same problem you are, so I'm modifying the grep
search parameter a bit and just looking for "ah0", and I'm telling
grep to search in a case insensitive manner - "-i".

cd /var/log/apache2/
sudo grep -i ah0 *.log

This is what is returned (folded to 80 character width):

error.log:[Wed Mar 28 00:09:05.632745 2018] [core:notice] [pid 1866]
AH00094: Command line: '/usr/sbin/apache2'

You don't mention what OS you're running apache on (or I didn't make
note), but this will help you find your log files:

https://www.cyberciti.biz/faq/apache-logs/
--
Consulting Minister for Consultants, DNRC
I can please only one person per day. Today is not your day. Tomorrow
isn't looking good, either.
I am BOFH. Resistance is futile. Your network will be assimilated.
Loading...