I just installed mod_pagespeed on my centos 7 and got tons of httpd errors
log in 1 minute. An example line of error:
<code>
[Tue Feb 10 11:05:14.311755 2015] [pagespeed:warn] [pid 21132:tid
139634310850304] [mod_pagespeed 1.9.32.3-4448 @21132] Waiting for
completion of URL http://exampledomain.com/example-slug/ for 45.001 sec
</code>
ALL requests got error, include image requests too.
My server hardware specs:
* Intel(R) Xeon(R) CPU E3-1246 v3 @ 3.50GHz, 8 cores
* 32 GB DDR3 RAM
* 2 x 2 TB SATA 6 Gb/s 7200 rpm HDD (Software-RAID 1) Class Enterprise
Software specs:
Operating system: CentOS Linux 7.0.1406
Kernel: Linux 3.10.0-123.20.1.el7.x86_64 on x86_64
Server Version: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips mod_fcgid/2.3.9
PHP/5.6.5 mod_perl/2.0.9dev Perl/v5.16.3
Server MPM: event
What version of the product are you using (please check X-Mod-Pagespeed
header)?
mod-pagespeed-stable-1.9.32.3-4448.x86_64
URL of broken page:
I removed module after 1 minute of terror. If a google developer want to
learn more of server information, mail me an ip address that i can give
permission to look mod_info print.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
modpag...@googlecode.com
unread,
Feb 19, 2015, 1:40:25 PM2/19/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
void ApacheFetch::Wait() {
MessageHandler* handler = server_context_->message_handler();
Timer* timer = server_context_->timer();
int64 start_ms = timer->NowMs();
{
ScopedMutex lock(mutex_.get());
while (!done_) {
condvar_->TimedWait(blocking_fetch_timeout_ms_);
if (!done_) {
int64 elapsed_ms = timer->NowMs() - start_ms;
handler->Message(
kWarning, "Waiting for completion of URL %s for %g sec",
mapped_url_.c_str(), elapsed_ms / 1000.0);
}
}
}
}
I think what we're supposed to be doing is blocking for a maximum of
blocking_fetch_timeout_ms_, but instead we block until Done() is called and
just log an error every blocking_fetch_timeout_ms_.
modpag...@googlecode.com
unread,
Feb 19, 2015, 3:42:53 PM2/19/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
// Blocks indefinitely waiting for the proxy fetch to complete.
// Every 'blocking_fetch_timeout_ms', log a message so that if
// we get stuck there's noise in the logs, but we don't expect this
// to happen because underlying fetch/cache timeouts should fire.
//
// Note that enforcing a timeout in this function makes debugging
// difficult.
void Wait();
Still not clear why the fetch/cache timeouts aren't firing.
modpag...@googlecode.com
unread,
Feb 19, 2015, 3:45:54 PM2/19/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
Have you set any of the pagespeed timeouts to strange values, like -1? Are
there any other ways your PageSpeed configuration or server setup is
unusual? Or is this pretty much a stock install?
modpag...@googlecode.com
unread,
Feb 19, 2015, 3:49:16 PM2/19/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
I'd like to mention that this bug is fairly important as it is triggered
all the time and its effect is apache2 hogging the CPU. The only fix is
killing the apache2 process.
Also, is it possible that using ModPagespeedBlockingRewriteKey could be a
cause of this bug?
I'm setting the X-PSA-Blocking-Rewrite header on all my requests.
modpag...@googlecode.com
unread,
Feb 28, 2015, 2:34:45 PM2/28/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
I suspect (but don't know for sure) that use of
ModPagespeedBlockingRewriteKey might not interact well with in-place
fetches. It would be better to set a longer rewrite deadline.
Nevertheless I think this is a real bug and we should figure out who should
tackle it.
modpag...@googlecode.com
unread,
Mar 8, 2015, 4:36:27 PM3/8/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
Looking at the code, the class in question (ApacheFetch) is used in three
different scenarios:
1. admin-page handling (which I think is not at issue here based on the log
messages)
2. ModPagespeedInPlaceResourceOptimization (on by default starting in 1.9)
3. ModPagespeedMapProxyDomain
It would be helpful if each person experiencing this bug let us know if
they are using any of the above features, specifying with or without a
BlockingRewriteKey.
modpag...@googlecode.com
unread,
Mar 11, 2015, 7:34:47 PM3/11/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
If I understand correctly ModPagespeedInPlaceResourceOptimization is
enabled by default on 1.9 without specifying it on the config file, so in
this case I have it enabled.
I'm not using ModPagespeedMapProxyDomain and netiher a BlockingRewriteKey.
If you need more information feel free to ask for it.
modpag...@googlecode.com
unread,
Mar 31, 2015, 3:21:10 PM3/31/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
I have this problem as well. I regularly need to restart the Apache2
service because I use 100% CPU. It happens almost twice a day. It's a
problem because the rest of the time mod_pagespeed benefits are real and
great....
modpag...@googlecode.com
unread,
Mar 31, 2015, 3:49:21 PM3/31/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
I have set ModPagespeedInPlaceResourceOptimization off and cleared the
cache (I am using memcached) I will come back in a few hours to let us know
how is working.
modpag...@googlecode.com
unread,
Apr 2, 2015, 8:38:33 AM4/2/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
BTW, forgot to mention that if you request the files (images in our case)
directly through a browser (chrome) they are downloaded in less than a
second. Not sure why it takes page speed so long to fetch them.
modpag...@googlecode.com
unread,
Apr 7, 2015, 4:12:24 AM4/7/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
Back from week end to see the server high loaded at 100% CPU since last
saturday. Bad.... I will have no choice but to uninstall the module. It's a
shame, because the benefits are real when it works. But I cannot have my
server going wild everytime I have to leave for a few hours so I have no
choice.
1/ images url suddenly were rewritten again, despite
ModPagespeedImagePreserveURLs on . It is wrong, I don;t want my image names
to be updated. The website exists for quite a long time, images must be
kept at the same url / name as before.
Other things that may shed some light:
1) Is everyone with the problem using memcached?
2) Any mentions of cache errors or the like in logs?
@other devs:
I am sort of wondering if we're deadlocking the CacheBatcher thread
again[1], as cache callback not getting invoked seems like the most obvious
reason we would get stuck for .html at least (though interestingly not all
reports mention .html --- there could be more than 1 issue, too...)...
Unfortunately attempts to reproduce this with loadtests failed...
will print out what modules are loaded at what address
(if you paste it, it's probably best to only include info on
mod_pagespeed.so or mod_pagespeed_ap24.so...) and what thread is doing
what. It may be hard to interpret, though since the modules in packages are
built release, so all it will have is addresses.
modpag...@googlecode.com
unread,
Apr 8, 2015, 2:17:26 PM4/8/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
Since last time I reported about this, I added the following config:
# Re-enable IPRO, it used to be off, but according to my
previous bug report, IPRO off did not fix the issue.
ModPagespeedInPlaceResourceOptimization on
gdb --pid 12345
(with PID of tasks that's eating cpu instead of 12345)
bt <enter>
c <enter>
Ctrl+C
bt <enter>
c <enter>
Ctrl+C
(repeat a few times)
then quit <enter>
That would roughly show where it's spending the time. My suspicion at this
point is that we are screwing up in memcached client code, but it's hard to
see how that would happen in a CPU-burning way.
modpag...@googlecode.com
unread,
Apr 14, 2015, 12:45:25 PM4/14/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
For debugging this, it would be useful to look at the pagespeed
configuration files for the different sites that are having this problem.
If this problem has happened to you, could you send your server
configuration file to jef...@google.com?
modpag...@googlecode.com
unread,
Apr 15, 2015, 1:58:35 PM4/15/15
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
In a previous comment (#7) I mentionned that the bug did not occur for
resources declared with ModPagespeedLoadFromFileMatch. Then in comment #9,
I backed out of this statement, saying that the bug still did occur.
Fast forward to a few days ago: I added a new ModPagespeedLoadFromFileMatch
configuration.
Since that day, the bug has not occurred once, which is unfortunate because
I really wanted to send the output I would get by following comment #51.
It could be completely coincidental, but I thought I'd be worth mentioning.