"Set Area" error in logs

Permalink
It seems with one of my concrete sites, I see the same reoccurring error in the logs of my site pertaining to "Set Area". It doesn't seem to harm anything, but it happens thousands of times a day which makes the logs fill up pretty quick. The error message is always something similar to:

[Tue Jun 08 08:46:10 2010] [error] [client 98.174.248.xxx] Set Area, referer:http://mydomain.com/some-page/

Anybody else get this or know what could be causing it?

hursey013
 
nteaviation replied on at Permalink Reply
nteaviation
Do you have anything fancy in your .htaccess or httpd.conf? I am guessing that error message in coming out of your apache log, correct?
hursey013 replied on at Permalink Reply
hursey013
With the exception of the pretty url rewrite code concrete generates, I have probably 30-40 basic 301 redirects from when we switched the site over from ASP to concrete. For example:

RewriteRule /Page/2020/Show.aspx /contacts/ [R=301]

Do you think those could be the problem?
hursey013 replied on at Permalink Reply
hursey013
Reviving an old thread here... I never was able to get a solution to this. Just to simplify things I replaced my previous .htaccess with the standard pretty url information from concrete and nothing else. Anybody also get this error in their apache logs?

This only seems to appear on one site in particular, but the site does get 150-200k page hits a month. Every day there is about a hundred "Set Area" errors in the log, which would only be a small fraction of the daily traffic.
nteaviation replied on at Permalink Reply
nteaviation
I have never seen any error message with regard to "Set Area". Funny, I don't see the releative URL/file request path usually seen in a log entry. I see the referer. Not sure what's up with that.

For some reason I am thinking "multiview configuration" is throwing that error (Wild A$$ Guess on my part).

What web server are you running? Apache? Apache2?
hursey013 replied on at Permalink Reply
hursey013
Current configuration:

* CentOS release 5 (Final)
* Apache (version 2.2.3)
* Perl (version 5.8.8)
* PHP (version 5.2.5)
* MySQL (version 5.0.22)

Some of the log entries have referrers, some don't it's weird. Here's another sample of what I'm dealing with:

[Thu Sep 30 22:13:48 2010] [error] [client 98.247.40.xxx] Set Area
[Thu Sep 30 22:14:43 2010] [error] [client 72.208.173.xxx] Set Area, referer: http://pimasheriff.org/jail-info/
[Thu Sep 30 22:14:47 2010] [error] [client 174.18.210.xxx] Set Area, referer: http://pimasheriff.org/department-services/
[Thu Sep 30 22:15:34 2010] [error] [client 68.2.178.xx] Set Area, referer: http://pimasheriff.org/jail-info/inmate-lookup/
[Thu Sep 30 22:17:57 2010] [error] [client 69.171.161.xxx] Set Area, referer: http://pimasheriff.org/jail-info/inmate-lookup/
[Thu Sep 30 22:19:51 2010] [error] [client 69.171.161.xxx] Set Area, referer: http://pimasheriff.org/jail-info/inmate-lookup/
[Thu Sep 30 22:19:56 2010] [error] [client 97.204.185.xxx] Set Area, referer: http://pimasheriff.org/
rainmaker replied on at Permalink Reply
rainmaker
I'm having this issue, too. I have 13886 entries of "[24-May-2011 11:04:11] Set Area" in my error log (the date changes, of course). I don't have client IP or referrer like you do, though.

I'm having issues with Highslide Web Albums (an addon) crashing some of my pages. That's why I looked in my error log and found all the "Set Area"s. Is this related?

[edit] That's 13,886 "Set Area" entries in 48 days.
nteaviation replied on at Permalink Reply
nteaviation
The entries without referrers did not have one, meaning someone went straight to the URL instead of clicking on a referring link on a page somewhere else.
I am thinking that someone left some debugging code in either apache, apache mod, or php. rainmaker, what versions are you running?
mx2solutions replied on at Permalink Reply
This happens for us too. I'm quite certain the package "Area Splitter" causes this.

To get rid of this message:
* open: /packages/matogertel_area_splitter/blocks/matogertel_area_splitter/controller.php
* find: error_log('Set Area'); (line 142)
* comment out: //error_log('Set Area');
* save

Otherwise, on a Unix system in the c5-folder do this:
grep -R "'Set Area" *
to find any files that print this message.