We noticed that last week all of a sudden our apache access times jumped significantly (quadrupled) from what had basically been a flatline (via monitoring graphs provided by our host). We were looking at these charts because we had in fact been noticing longer load times. We're on the latest mu and buddypress 1.0.3.
Our host said in the last week the error below had been occurring frequently in the last week.... it indicates a redirect error, but looks like the referrer is our CSS stylesheet and an external site, which indicates that it might be a situation where when a bad link is accessed, a 404 is not 404'ing, but redirecting...... something I've read a little about on buddypress.org and mu.wordpress.com where no resolution seems to have been found.
I'm not completely convinced that this redirect is the cause of our increased apache response times as the increased times occur day and night on the charts, where I would expect them to lower at night when the server is accessed less, but this is not the case.
Besides learning how to use SSH (learning later this week), any places we might want to look first in order to troubleshoot?
[Mon Oct 26 01:00:01 2009] [error] [client 71.140.144.54] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://leadpress.com/wp-content/themes/leadpress/css/base.css
[Mon Oct 26 01:00:10 2009] [error] [client 71.140.144.54] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://leadpress.com/wp-content/themes/leadpress/css/base.css
[Mon Oct 26 01:00:10 2009] [error] [client 71.140.144.54] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://leadpress.com/wp-content/themes/leadpress/css/base.css
[Mon Oct 26 01:06:38 2009] [error] [client 140.114.193.89] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://www.wretch.cc/blog/tsuziai
[Mon Oct 26 01:06:38 2009] [error] [client 140.114.193.89] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://www.wretch.cc/blog/tsuziai
We noticed that last week all of a sudden our apache access times jumped significantly (quadrupled) from what had basically been a flatline (via monitoring graphs provided by our host). We were looking at these charts because we had in fact been noticing longer load times. We're on the latest mu and buddypress 1.0.3.
Our host said in the last week the error below had been occurring frequently in the last week.... it indicates a redirect error, but looks like the referrer is our CSS stylesheet and an external site, which indicates that it might be a situation where when a bad link is accessed, a 404 is not 404'ing, but redirecting...... something I've read a little about on buddypress.org and mu.wordpress.com where no resolution seems to have been found.
I'm not completely convinced that this redirect is the cause of our increased apache response times as the increased times occur day and night on the charts, where I would expect them to lower at night when the server is accessed less, but this is not the case.
Besides learning how to use SSH (learning later this week), any places we might want to look first in order to troubleshoot?
[Mon Oct 26 01:00:01 2009] [error] [client 71.140.144.54] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://leadpress.com/wp-content/themes/leadpress/css/base.css
[Mon Oct 26 01:00:10 2009] [error] [client 71.140.144.54] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://leadpress.com/wp-content/themes/leadpress/css/base.css
[Mon Oct 26 01:00:10 2009] [error] [client 71.140.144.54] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://leadpress.com/wp-content/themes/leadpress/css/base.css
[Mon Oct 26 01:06:38 2009] [error] [client 140.114.193.89] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://www.wretch.cc/blog/tsuziai
[Mon Oct 26 01:06:38 2009] [error] [client 140.114.193.89] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace., referer: http://www.wretch.cc/blog/tsuziai
Founder & CEO
—
10th February 2010 (2 years ago)
#
BTW, thanks for posting this, it's an excellent topic, did things work out (sorry there were no replies at the time) or are you still looking for assistance?
We are facing a similar problem with a number of our clients and our own website as well but we still have not been able to find a solution to this problem.
Responses (3)
Founder & CEO — 10th February 2010 (2 years ago) #
BTW, thanks for posting this, it's an excellent topic, did things work out (sorry there were no replies at the time) or are you still looking for assistance?
Member — 26th March 2011 (1 year ago) #
We are facing a similar problem with a number of our clients and our own website as well but we still have not been able to find a solution to this problem.
Member — 31st May 2011 (11 months ago) #
I'm seeing the same issue and curious to know if anybody has any recommendations for resolving this issue.
Thank you.
Become a member