Many "waiting for property cache fetch to complete" errors
994 views
Skip to first unread message
Miguel Gómez
Jan 8, 2014, 7:24:19 PM1/8/14
to mod-pagesp...@googlegroups.com
Hello, i'm using mod_pagespeed 1.7.30.1 on apache server with memcache and i'm having a huge amount of errors like this:
[error] [mod_pagespeed 1.7.30.1-3609 @18292] Waiting for property cache fetch to complete.
on my error_log. I suspect that this is also causing than randomly one httpd process is using 99% CPU and i must kill or restart apache to solve it. Can anyone help me about where to start to locate the source of this problem??
many thanks in advance,
Joshua Marantz
Jan 8, 2014, 10:25:32 PM1/8/14
to mod-pagespeed-discuss
Can you try upgrading to 1.7.30.2, which was just released today? It has a fix for this bug which might be related to what you are seeing.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/ce9a4ea1-0625-4296-8e3a-490e6b52d305%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Miguel Gómez
Jan 9, 2014, 7:38:50 AM1/9/14
to mod-pagesp...@googlegroups.com
Thanks, i've just updated a few hours ago and now all these errors are gone but httpd process still crashes randomly.
*** glibc detected *** /usr/sbin/httpd: corrupted double-linked list: 0x00002ae1ac1b85a0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x2ae1ade89845]
/lib64/libc.so.6(cfree+0x4b)[0x2ae1ade8da4b]
/usr/lib64/libapr-1.so.0(apr_allocator_destroy+0x1b)[0x2ae1ad7e57fb]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2ae1b676d918]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2ae1b664bb72]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2ae1b64e6bf2]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2ae1b6762d7c]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2ae1b64a7bcb]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2ae1b64bb23b]
/lib64/libc.so.6(exit+0xe5)[0x2ae1ade4b4f5]
/usr/sbin/httpd[0x2ae1abf28f01]
/usr/sbin/httpd[0x2ae1abf2939b]
this is part of the error_log
El jueves, 9 de enero de 2014 04:25:32 UTC+1, jmarantz escribió:
Can you try upgrading to 1.7.30.2, which was just released today? It has a fix for this bug which might be related to what you are seeing.
On Wed, Jan 8, 2014 at 7:24 PM, Miguel Gómez <fid...@gmail.com> wrote:
Hello, i'm using mod_pagespeed 1.7.30.1 on apache server with memcache and i'm having a huge amount of errors like this:[error] [mod_pagespeed 1.7.30.1-3609 @18292] Waiting for property cache fetch to complete.on my error_log. I suspect that this is also causing than randomly one httpd process is using 99% CPU and i must kill or restart apache to solve it. Can anyone help me about where to start to locate the source of this problem??many thanks in advance,
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Joshua Marantz
Jan 9, 2014, 7:57:39 AM1/9/14
to mod-pagespeed-discuss
You didn't see that prior to the upgrade? Was this a binary install? CentOS-64 I'm guessing?
-Josh
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/903c010f-0c87-435b-8ba6-a1e7eb501ae7%40googlegroups.com.
Miguel Gómez
Jan 9, 2014, 8:00:55 AM1/9/14
to mod-pagesp...@googlegroups.com
Yes, it's CentOS 5.10 and yes, the crashes also happened before the update but also with hundreds of errors like the one that i've posted on my first post.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsubscri...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/ce9a4ea1-0625-4296-8e3a-490e6b52d305%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Joshua Marantz
Jan 9, 2014, 8:07:32 AM1/9/14
to mod-pagespeed-discuss
We'd like to squash all the memory corruptions we see. Would it be convenient for you to try running with a debug build from source so we can get more debugging assertions into your flow, and get symbols in the stack trace?
Out of curiosity, did this release resolve the "waiting for property cache fetch" errors? Or are they still a problem?
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/01f8a8e1-6385-4737-8234-718c6e98bd1d%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
Miguel Gómez
Jan 9, 2014, 8:12:32 AM1/9/14
to mod-pagesp...@googlegroups.com
I've errors like this now:
[Thu Jan 09 05:56:09 2014] [warn] [mod_pagespeed 1.7.30.2-3702 @12043] Fetch failed for http://www.myserver.com/70x50ximagelink.jpg,qrel=aHR0cDovL3d3$
[Thu Jan 09 05:56:09 2014] [warn] [mod_pagespeed 1.7.30.2-3702 @12043] http://www.myserver.com/70x50ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY$
[Thu Jan 09 06:13:17 2014] [notice] child pid 12113 exit signal Segmentation fault (11)
but there is not 'waiting for property cache fetch' errors until now. And about running a debug build, well i'm not sure about how to install it.. there is not any flag that can be activated on the mod_pagespeed configuration file to provide aditional debug information?
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/903c010f-0c87-435b-8ba6-a1e7eb501ae7%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Joshua Marantz
Jan 9, 2014, 8:53:10 AM1/9/14
to mod-pagespeed-discuss
The instructions are here: https://developers.google.com/speed/pagespeed/module/build_mod_pagespeed_from_source
However I'm in the process of building a CentOS 64 debug binary for you which I'll put it on http://modpagespeed.com/debug_binaries and let you know when it's ready.
-Josh
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/62285f8a-bf5f-45d5-8e85-d20d119efd0d%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
Joshua Marantz
Jan 9, 2014, 8:55:52 AM1/9/14
to mod-pagespeed-discuss
One more question: which version and MPM of Apache are you using?
Miguel Gómez
Jan 9, 2014, 9:26:23 AM1/9/14
to mod-pagesp...@googlegroups.com
Apache is 2.2.3 and MPM is prefork
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/01f8a8e1-6385-4737-8234-718c6e98bd1d%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Joshua Marantz
Jan 9, 2014, 9:30:44 AM1/9/14
to mod-pagespeed-discuss
OK, please check http://modpagespeed.com/debug_binaries/ and let me know if you have questions or problems. Please be careful when you moving your .so files around to make sure you keep the release version intact.
The debug one will perform somewhat slower since it is compiled without any optimization, so run it just long enough to try to reproduce the stack trace and then switch back to the release binary for production traffic.
-Josh
Miguel Gómez
Jan 9, 2014, 9:42:03 AM1/9/14
to mod-pagesp...@googlegroups.com
Ok, i've downloaded the debug version and i get this error:
httpd: Syntax error on line 214 of /etc/httpd/conf/httpd.conf: Syntax error on line 7 of /etc/httpd/conf.d/pagespeed.conf: Cannot load /usr/lib64/httpd/modules/mod_pagespeed.so into server: /usr/lib64/httpd/modules/mod_pagespeed.so: wrong ELF class: ELFCLASS32
when restarting apache server.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/01f8a8e1-6385-4737-8234-718c6e98bd1d%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Joshua Marantz
Jan 9, 2014, 9:44:37 AM1/9/14
to mod-pagespeed-discuss
Sorry about this - it looks like I built the 32-bit version by mistake.
It will take me a bit of time as the Meetings start soon, but I'll rebuild you a 64-bit.
-Josh
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/893b456f-c32f-440c-ac94-8ee7bf2dca50%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
Miguel Gómez
Jan 9, 2014, 9:45:50 AM1/9/14
to mod-pagesp...@googlegroups.com
Ok, i'll wait for your message
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/62285f8a-bf5f-45d5-8e85-d20d119efd0d%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Joshua Marantz
Jan 9, 2014, 11:10:44 AM1/9/14
to mod-pagespeed-discuss
We've updated http://modpagespeed.com/debug_binaries/1.7.30.2/centos_64/ to contain actual 64-bit debug binaries now.
Please check again.
-Josh
Miguel Gómez
Jan 9, 2014, 2:31:19 PM1/9/14
to mod-pagesp...@googlegroups.com
Ok, i've downloaded the 64-bit version and now apache doesn't start. i get this error:
[emerg] (28)No space left on device: Couldn't create accept lock (/etc/httpd/logs/accept.lock.29746) (5)
:(
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/62285f8a-bf5f-45d5-8e85-d20d119efd0d%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Miguel Gómez
Jan 9, 2014, 2:37:14 PM1/9/14
to mod-pagesp...@googlegroups.com
Oops! Forget about this last comment, it was a problem with apache semaphores; i've solved it, now it's running with pagespeed debug version
El jueves, 9 de enero de 2014 17:10:44 UTC+1, jmarantz escribió:
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/62285f8a-bf5f-45d5-8e85-d20d119efd0d%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Miguel Gómez
Jan 9, 2014, 2:45:44 PM1/9/14
to mod-pagesp...@googlegroups.com
Ok, i've obtained the first error in my log:
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::Get error: Internal error (20014) on key http://www.myserver.com/imagelink.jpg?rel=L2ltYWdlcy9hdmF0YXIvdGh1bWJfN2FkNjRmOWM4NmE5MzUwZDlmNDMxZTZjLmpwZw==
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::Get key collision http://www.myserver.com/plugins/system/CssJsCompress/js.php,qjs=d6d77c3c705259e235868b2023011edc.js.pagespeed.jm.sooYiJTgMs.js != http://www.myserver.com/plugins/system/CssJsCompress/css.php?css=adc45f0868466a4a68f12159c7bc8759.css
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::Put error: Internal error (20014) on key http://www.myserver.com/imagelink.jpg?rel=L2ltYWdlcy9hdmF0YXIvdGh1bWJfN2FkNjRmOWM4NmE5MzUwZDlmNDMxZTZjLmpwZw==, value-size 3070
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/imagelink.jpg?rel=L2NvbXBvbmVudHMvY29tX2NvbW11bml0eS90ZW1wbGF0ZXMvdmFYZGVudHJvL2ltYWdlcy9rYXJtYS0yLTUucG5n@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/47x47ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY29tL2ltYWdlcy9waG90b3MvNTU2LzMxMS90aHVtYl8xNzY3OWIzMDg0MDNkZTU1Y2JiYzliOWMuanBn.pagespeed.ic.ziQ2rsngFU.jpg@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/47x47ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY29tL2ltYWdlcy9waG90b3MvMzMyLzMwOC90aHVtYl81NjQ0MDBiODYyNjgwYjY1ODA2MzEyNjEuanBn.pagespeed.ic.3s-zBqsPNK.jpg@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/47x47ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY29tL2ltYWdlcy9waG90b3MvNzk2LzMwMi90aHVtYl9kZGQ3ZGQwZDJkNmM4NDgwOTNiMDU4ZDMuanBn.pagespeed.ic.cDAyE0qCJl.jpg@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/47x47ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY29tL2ltYWdlcy9waG90b3MvNjA0LzI5OS90aHVtYl85ZmYzYjkwYTBiMDFiYzZhYmQ3ZjYyMjcuanBn.pagespeed.ic.SVX53h5Pf9.jpg@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/47x47ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY29tL2ltYWdlcy9waG90b3MvNzU2LzI5OC90aHVtYl84MTMzOGVkZDA3YTY4MDM4NTUxMTVkMWUuanBn.pagespeed.ic.4A5VZ9B7AU.jpg@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/47x47ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY29tL2ltYWdlcy9waG90b3MvNzU2LzI5Ny90aHVtYl81YWRiMGRjNjQwYjdjZDJiOGZmN2M5MmIuanBn.pagespeed.ic.sPV5TkQ5SJ.jpg@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/47x47ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY29tL2ltYWdlcy9waG90b3MvNzU2LzI5Ni90aHVtYl82NTVhNTIxMTc2MDhjYWJhNTkwN2MyZjguanBn.pagespeed.ic.uQnlIdR49o.jpg@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/47x47ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY29tL2ltYWdlcy9waG90b3MvNzU2LzI5NS90aHVtYl9jMGQxZmRlOWY2Yzg5OWFjOTFjNTkyMGMuanBn.pagespeed.ic.Dkb2Wp12ko.jpg@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/47x47ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY29tL2ltYWdlcy9waG90b3MvNzU2LzI5NC90aHVtYl83MjRmODkwNDhmZmU0NWYyOTFiMTdiNmYuanBn.pagespeed.ic.rRZzTWE3vE.jpg@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/47x47ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY29tL2ltYWdlcy9waG90b3MvNzU2LzI5My90aHVtYl8zYmI1NDc1NGVlY2Q5MzZhZjZiZDIxM2IuanBn.pagespeed.ic.LMmYeXJWNs.jpg@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/47x47ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY29tL2ltYWdlcy9waG90b3MvMTMyLzI5MC90aHVtYl8xNmUyNTkyZGEzNjAxODg1NGE1NGYyNDIuanBn.pagespeed.ic.0rE2zRt26n.jpg@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/47x47ximagelink.jpg,qrel=aHR0cDovL3d3dy52YXhkZW50cm8uY29tL2ltYWdlcy9waG90b3MvNzQzLzI4Ni90aHVtYl9hYjM4YjE3YTBmOTc3MTg4ZTkzZDI1YjAuanBn.pagespeed.ic.lQ3g1iWbeH.jpg@@_
[Thu Jan 09 20:37:22 2014] [error] [mod_pagespeed 1.7.30.2-3706 @30098] AprMemCache::MultiGet error: The timeout specified has expired (70007) on key rname/ce_SZ1lu4SHuTHJdjOHFyJy/http://www.myserver.com/imagelink.jpg?rel=L2NvbXBvbmVudHMvY29tX2NvbW11bml0eS9hc3NldHMvZGVmYXVsdF90aHVtYi5wbmc=@@_
*** glibc detected *** /usr/sbin/httpd: corrupted double-linked list: 0x00002aacace6a700 ***
El jueves, 9 de enero de 2014 17:10:44 UTC+1, jmarantz escribió:
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/62285f8a-bf5f-45d5-8e85-d20d119efd0d%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Miguel Gómez
Jan 9, 2014, 2:53:08 PM1/9/14
to mod-pagesp...@googlegroups.com
As you can notice, after the mod_pagespeed errors there was a httpd crash:
*** glibc detected *** /usr/sbin/httpd: corrupted double-linked list: 0x00002aacace6a700 ***
======= Backtrace: =========
/lib64/libc.so.6[0x2aacaeb25845]
/lib64/libc.so.6(cfree+0x4b)[0x2aacaeb29a4b]
/usr/lib64/libapr-1.so.0(apr_allocator_destroy+0x1b)[0x2aacae4817fb]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb762e21c]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb761c63d]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb746388a]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb71f8a47]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb7620f1b]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb715561b]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb71709fb]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb7170483]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb717058a]
/lib64/libc.so.6(exit+0xe5)[0x2aacaeae74f5]
/usr/sbin/httpd[0x2aacacbc4f01]
/usr/sbin/httpd[0x2aacacbc539b]
/usr/sbin/httpd[0x2aacacbc555a]
/usr/sbin/httpd(ap_mpm_run+0x78d)[0x2aacacbc5dbd]
/usr/sbin/httpd(main+0x818)[0x2aacacb9ffd8]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x2aacaead19c4]
/usr/sbin/httpd[0x2aacacb9f2f9]
Joshua Marantz
Jan 9, 2014, 3:29:21 PM1/9/14
to mod-pagespeed-discuss
Can you do two things for me please?
1. check your log for something like this:
"======= Memory map: ========"
and send me all the text around that
2. Put this in your pagespeed.conf and restart:
ModPagespeedInstallCrashHandler on
Thanks,
-Josh
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/d7933653-24fe-4579-a24e-5af2ad4b818a%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
Joshua Marantz
Jan 9, 2014, 3:48:22 PM1/9/14
to mod-pagespeed-discuss
Can you also describe your memcached configuration in more detail?
The timeouts you are seeing might in memcached might be due to a few different things. Some people use memcached proxies or implementations of memcached that talks to a real database. That's all fine, but then you will have a hard time meeting our timeout deadline default of 50 milliseconds, and will need to increase it. Please see the description of ModPagespeedMemcachedTimeoutUs in https://developers.google.com/speed/pagespeed/module/system#memcached
It's also possible that a burst of image rewriting might bog down your system and create these timeout warnings, and running a debug build will definitely increase the timeout risk as well. However I don't think that should cause a memory corruption, so we'd still like to see the memory map or see the results of running with the crash handler installed.
-Josh
Miguel Gómez
Jan 10, 2014, 3:13:01 AM1/10/14
to mod-pagesp...@googlegroups.com
This is memory map:
======= Backtrace: =========
/lib64/libc.so.6[0x2aacaeb25845]
/lib64/libc.so.6(cfree+0x4b)[0x2aacaeb29a4b]
/usr/lib64/libapr-1.so.0(apr_allocator_destroy+0x1b)[0x2aacae4817fb]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb762e21c]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb761c63d]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb746388a]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb71f8a47]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb7620f1b]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb715561b]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb71709fb]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb7170483]
/usr/lib64/httpd/modules/mod_pagespeed.so[0x2aacb717058a]
/lib64/libc.so.6(exit+0xe5)[0x2aacaeae74f5]
/usr/sbin/httpd[0x2aacacbc4f01]
/usr/sbin/httpd[0x2aacacbc539b]
/usr/sbin/httpd[0x2aacacbc555a]
/usr/sbin/httpd(ap_mpm_run+0x78d)[0x2aacacbc5dbd]
/usr/sbin/httpd(main+0x818)[0x2aacacb9ffd8]
/lib64/libc.so.6(__libc_start_main+0xf4)[0x2aacaead19c4]
/usr/sbin/httpd[0x2aacacb9f2f9]
======= Memory map: ========
2aacacb89000-2aacacbd7000 r-xp 00000000 00:15 65181209 /usr/sbin/httpd
2aacacbd7000-2aacacc55000 rw-s 00000000 00:6d 326604958
2aacacc55000-2aacacd7b000 rw-s 00000000 00:6d 4816896
2aacacd7b000-2aacacdb1000 rw-s 00000000 00:6d 326604964
2aacacdb1000-2aacacdca000 rw-s 00000000 00:6d 326604965
2aacacdd6000-2aacacdda000 rw-p 0004d000 00:15 65181209 /usr/sbin/httpd
2aacacdda000-2aacacddd000 rw-p 2aacacdda000 00:00 0
2aacacddd000-2aacacdf9000 r-xp 00000000 00:15 36129166 /lib64/ld-2.5.so
2aacacdf9000-2aacacefb000 rw-p 2aacacdf9000 00:00 0
2aacacff9000-2aacacffa000 r--p 0001c000 00:15 36129166 /lib64/ld-2.5.so
2aacacffa000-2aacacffb000 rw-p 0001d000 00:15 36129166 /lib64/ld-2.5.so
2aacacffb000-2aacad07d000 r-xp 00000000 00:15 36129171 /lib64/libm-2.5.so
2aacad07d000-2aacad27c000 ---p 00082000 00:15 36129171 /lib64/libm-2.5.so
2aacad27c000-2aacad27d000 r--p 00081000 00:15 36129171 /lib64/libm-2.5.so
2aacad27d000-2aacad27e000 rw-p 00082000 00:15 36129171 /lib64/libm-2.5.so
2aacad27e000-2aacad29c000 r-xp 00000000 00:15 36128065 /lib64/libpcre.so.0.0.1
2aacad29c000-2aacad49c000 ---p 0001e000 00:15 36128065 /lib64/libpcre.so.0.0.1
2aacad49c000-2aacad49d000 rw-p 0001e000 00:15 36128065 /lib64/libpcre.so.0.0.1
2aacad49d000-2aacad4b2000 r-xp 00000000 00:15 36127918 /lib64/libselinux.so.1
2aacad4b2000-2aacad6b2000 ---p 00015000 00:15 36127918 /lib64/libselinux.so.1
2aacad6b2000-2aacad6b4000 rw-p 00015000 00:15 36127918 /lib64/libselinux.so.1
2aacad6b4000-2aacad6b6000 rw-p 2aacad6b4000 00:00 0
2aacad6b6000-2aacad6cf000 r-xp 00000000 00:15 75678815 /usr/lib64/libaprutil-1.so.0.2.7
2aacad6cf000-2aacad8cf000 ---p 00019000 00:15 75678815 /usr/lib64/libaprutil-1.so.0.2.7
2aacad8cf000-2aacad8d0000 rw-p 00019000 00:15 75678815 /usr/lib64/libaprutil-1.so.0.2.7
2aacad8d0000-2aacad8d9000 r-xp 00000000 00:15 36128127 /lib64/libcrypt-2.5.so
2aacad8d9000-2aacadad8000 ---p 00009000 00:15 36128127 /lib64/libcrypt-2.5.so
2aacadad8000-2aacadad9000 r--p 00008000 00:15 36128127 /lib64/libcrypt-2.5.so
2aacadad9000-2aacadada000 rw-p 00009000 00:15 36128127 /lib64/libcrypt-2.5.so
2aacadada000-2aacadb08000 rw-p 2aacadada000 00:00 0
2aacadb08000-2aacadb41000 r-xp 00000000 00:15 75678581 /usr/lib64/libldap-2.3.so.0.2.31
2aacadb41000-2aacadd41000 ---p 00039000 00:15 75678581 /usr/lib64/libldap-2.3.so.0.2.31
2aacadd41000-2aacadd43000 rw-p 00039000 00:15 75678581 /usr/lib64/libldap-2.3.so.0.2.31
2aacadd43000-2aacadd44000 rw-p 2aacadd43000 00:00 0
2aacadd44000-2aacadd51000 r-xp 00000000 00:15 75678994 /usr/lib64/liblber-2.3.so.0.2.31
2aacadd51000-2aacadf51000 ---p 0000d000 00:15 75678994 /usr/lib64/liblber-2.3.so.0.2.31
2aacadf51000-2aacadf52000 rw-p 0000d000 00:15 75678994 /usr/lib64/liblber-2.3.so.0.2.31
2aacadf52000-2aacae043000 r-xp 00000000 00:15 36128178 /lib64/libdb-4.3.so
2aacae043000-2aacae243000 ---p 000f1000 00:15 36128178 /lib64/libdb-4.3.so
2aacae243000-2aacae248000 rw-p 000f1000 00:15 36128178 /lib64/libdb-4.3.so
2aacae248000-2aacae269000 r-xp 00000000 00:15 36128143 /lib64/libexpat.so.0.5.0
2aacae269000-2aacae468000 ---p 00021000 00:15 36128143 /lib64/libexpat.so.0.5.0
2aacae468000-2aacae46b000 rw-p 00020000 00:15 36128143 /lib64/libexpat.so.0.5.0
2aacae46b000-2aacae46c000 rw-p 2aacae46b000 00:00 0
2aacae46c000-2aacae492000 r-xp 00000000 00:15 75678483 /usr/lib64/libapr-1.so.0.2.7
2aacae492000-2aacae692000 ---p 00026000 00:15 75678483 /usr/lib64/libapr-1.so.0.2.7
2aacae692000-2aacae693000 rw-p 00026000 00:15 75678483 /usr/lib64/libapr-1.so.0.2.7
2aacae693000-2aacae6a9000 r-xp 00000000 00:15 36128062 /lib64/libpthread-2.5.so
2aacae6a9000-2aacae8a9000 ---p 00016000 00:15 36128062 /lib64/libpthread-2.5.so
2aacae8a9000-2aacae8aa000 r--p 00016000 00:15 36128062 /lib64/libpthread-2.5.so
2aacae8aa000-2aacae8ab000 rw-p 00017000 00:15 36128062 /lib64/libpthread-2.5.so
2aacae8ab000-2aacae8af000 rw-p 2aacae8ab000 00:00 0
2aacae8af000-2aacae8b1000 r-xp 00000000 00:15 36129170 /lib64/libdl-2.5.so
2aacae8b1000-2aacaeab1000 ---p 00002000 00:15 36129170 /lib64/libdl-2.5.so
2aacaeab1000-2aacaeab2000 r--p 00002000 00:15 36129170 /lib64/libdl-2.5.so
2aacaeab2000-2aacaeab3000 rw-p 00003000 00:15 36129170 /lib64/libdl-2.5.so
2aacaeab3000-2aacaeab4000 rw-p 2aacaeab3000 00:00 0
2aacaeab4000-2aacaec03000 r-xp 00000000 00:15 36128010 /lib64/libc-2.5.so
2aacaec03000-2aacaee03000 ---p 0014f000 00:15 36128010 /lib64/libc-2.5.so
2aacaee03000-2aacaee07000 r--p 0014f000 00:15 36128010 /lib64/libc-2.5.so
2aacaee07000-2aacaee08000 rw-p 00153000 00:15 36128010 /lib64/libc-2.5.so
2aacaee08000-2aacaee0d000 rw-p 2aacaee08000 00:00 0
2aacaee0d000-2aacaee48000 r-xp 00000000 00:15 36128135 /lib64/libsepol.so.1
2aacaee48000-2aacaf048000 ---p 0003b000 00:15 36128135 /lib64/libsepol.so.1
2aacaf048000-2aacaf049000 rw-p 0003b000 00:15 36128135 /lib64/libsepol.so.1
2aacaf049000-2aacaf053000 rw-p 2aacaf049000 00:00 0
2aacaf053000-2aacaf057000 r-xp 00000000 00:15 36128133 /lib64/libuuid.so.1.2
2aacaf057000-2aacaf256000 ---p 00004000 00:15 36128133 /lib64/libuuid.so.1.2
2aacaf256000-2aacaf257000 rw-p 00003000 00:15 36128133 /lib64/libuuid.so.1.2
2aacaf257000-2aacaf258000 rw-p 2aacaf257000 00:00 0
2aacaf258000-2aacaf269000 r-xp 00000000 00:15 36129176 /lib64/libresolv-2.5.so
2aacaf269000-2aacaf469000 ---p 00011000 00:15 36129176 /lib64/libresolv-2.5.so
2aacaf469000-2aacaf46a000 r--p 00011000 00:15 36129176 /lib64/libresolv-2.5.so
2aacaf46a000-2aacaf46b000 rw-p 00012000 00:15 36129176 /lib64/libresolv-2.5.so
2aacaf46b000-2aacaf46d000 rw-p 2aacaf46b000 00:00 0
2aacaf46d000-2aacaf485000 r-xp 00000000 00:15 75678524 /usr/lib64/libsasl2.so.2.0.22
2aacaf485000-2aacaf685000 ---p 00018000 00:15 75678524 /usr/lib64/libsasl2.so.2.0.22
2aacaf685000-2aacaf686000 rw-p 00018000 00:15 75678524 /usr/lib64/libsasl2.so.2.0.22
2aacaf686000-2aacaf6ce000 r-xp 00000000 00:15 36128138 /lib64/libssl.so.0.9.8e
2aacaf6ce000-2aacaf8ce000 ---p 00048000 00:15 36128138 /lib64/libssl.so.0.9.8e
2aacaf8ce000-2aacaf8d4000 rw-p 00048000 00:15 36128138 /lib64/libssl.so.0.9.8e
2aacaf8d4000-2aacaf8d5000 rw-p 2aacaf8d4000 00:00 0
2aacaf8d5000-2aacafa02000 r-xp 00000000 00:15 36128036 /lib64/libcrypto.so.0.9.8e
2aacafa02000-2aacafc01000 ---p 0012d000 00:15 36128036 /lib64/libcrypto.so.0.9.8e
2aacafc01000-2aacafc22000 rw-p 0012c000 00:15 36128036 /lib64/libcrypto.so.0.9.8e
2aacafc22000-2aacafc26000 rw-p 2aacafc22000 00:00 0
2aacafc26000-2aacafc52000 r-xp 00000000 00:15 36129710 /usr/lib64/libgssapi_krb5.so.2.2
2aacafc52000-2aacafe52000 ---p 0002c000 00:15 36129710 /usr/lib64/libgssapi_krb5.so.2.2
2aacafe52000-2aacafe54000 rw-p 0002c000 00:15 36129710 /usr/lib64/libgssapi_krb5.so.2.2
2aacafe54000-2aacafe55000 rw-p 2aacafe54000 00:00 0
2aacafe55000-2aacafee6000 r-xp 00000000 00:15 36129724 /usr/lib64/libkrb5.so.3.3
2aacafee6000-2aacb00e6000 ---p 00091000 00:15 36129724 /usr/lib64/libkrb5.so.3.3
2aacb00e6000-2aacb00ea000 rw-p 00091000 00:15 36129724 /usr/lib64/libkrb5.so.3.3
2aacb00ea000-2aacb00ec000 r-xp 00000000 00:15 36128040 /lib64/libcom_err.so.2.1
2aacb00ec000-2aacb02eb000 ---p 00002000 00:15 36128040 /lib64/libcom_err.so.2.1
2aacb02eb000-2aacb02ec000 rw-p 00001000 00:15 36128040 /lib64/libcom_err.so.2.1
2aacb02ec000-2aacb0310000 r-xp 00000000 00:15 36129714 /usr/lib64/libk5crypto.so.3.1
2aacb0310000-2aacb050f000 ---p 00024000 00:15 36129714 /usr/lib64/libk5crypto.so.3.1
2aacb050f000-2aacb0511000 rw-p 00023000 00:15 36129714 /usr/lib64/libk5crypto.so.3.1
2aacb0511000-2aacb0512000 rw-p 2aacb0511000 00:00 0
2aacb0512000-2aacb0526000 r-xp 00000000 00:15 36127927 /lib64/libz.so.1.2.3
2aacb0526000-2aacb0725000 ---p 00014000 00:15 36127927 /lib64/libz.so.1.2.3
2aacb0725000-2aacb0726000 rw-p 00013000 00:15 36127927 /lib64/libz.so.1.2.3
2aacb0726000-2aacb072e000 r-xp 00000000 00:15 36129726 /usr/lib64/libkrb5support.so.0.1
2aacb072e000-2aacb092d000 ---p 00008000 00:15 36129726 /usr/lib64/libkrb5support.so.0.1
2aacb092d000-2aacb092e000 rw-p 00007000 00:15 36129726 /usr/lib64/libkrb5support.so.0.1
2aacb092e000-2aacb0930000 r-xp 00000000 00:15 36128011 /lib64/libkeyutils-1.2.so
2aacb0930000-2aacb0b2f000 ---p 00002000 00:15 36128011 /lib64/libkeyutils-1.2.so
2aacb0b2f000-2aacb0b30000 rw-p 00001000 00:15 36128011 /lib64/libkeyutils-1.2.so
2aacb0b30000-2aacb0b33000 rw-p 2aacb0b30000 00:00 0
2aacb0b33000-2aacb0b35000 r-xp 00000000 00:15 36130075 /usr/lib64/httpd/modules/mod_auth_basic.so
2aacb0b35000-2aacb0d34000 ---p 00002000 00:15 36130075 /usr/lib64/httpd/modules/mod_auth_basic.so
2aacb0d34000-2aacb0d36000 rw-p 00001000 00:15 36130075 /usr/lib64/httpd/modules/mod_auth_basic.so
2aacb0d36000-2aacb0d3c000 r-xp 00000000 00:15 36130809 /usr/lib64/httpd/modules/mod_auth_digest.so
2aacb0d3c000-2aacb0f3b000 ---p 00006000 00:15 36130809 /usr/lib64/httpd/modules/mod_auth_digest.so
2aacb0f3b000-2aacb0f3d000 rw-p 00005000 00:15 36130809 /usr/lib64/httpd/modules/mod_auth_digest.so
2aacb0f3d000-2aacb0f3f000 r-xp 00000000 00:15 36130813 /usr/lib64/httpd/modules/mod_authn_file.so
2aacb0f3f000-2aacb113e000 ---p 00002000 00:15 36130813 /usr/lib64/httpd/modules/mod_authn_file.so
2aacb113e000-2aacb1140000 rw-p 00001000 00:15 36130813 /usr/lib64/httpd/modules/mod_authn_file.so
2aacb1140000-2aacb1142000 r-xp 00000000 00:15 36130810 /usr/lib64/httpd/modules/mod_authn_alias.so
2aacb1142000-2aacb1341000 ---p 00002000 00:15 36130810 /usr/lib64/httpd/modules/mod_authn_alias.so
2aacb1341000-2aacb1343000 rw-p 00001000 00:15 36130810 /usr/lib64/httpd/modules/mod_authn_alias.so
2aacb1343000-2aacb1344000 r-xp 00000000 00:15 36130811 /usr/lib64/httpd/modules/mod_authn_anon.so
2aacb1344000-2aacb1544000 ---p 00001000 00:15 36130811 /usr/lib64/httpd/modules/mod_authn_anon.so
2aacb1544000-2aacb1546000 rw-p 00001000 00:15 36130811 /usr/lib64/httpd/modules/mod_authn_anon.so
2aacb1546000-2aacb1547000 r-xp 00000000 00:15 36129828 /usr/lib64/httpd/modules/mod_authn_default.so
2aacb1547000-2aacb1746000 ---p 00001000 00:15 36129828 /usr/lib64/httpd/modules/mod_authn_default.so
2aacb1746000-2aacb1748000 rw-p 00000000 00:15 36129828 /usr/lib64/httpd/modules/mod_authn_default.so
2aacb1748000-2aacb174a000 r-xp 00000000 00:15 36130816 /usr/lib64/httpd/modules/mod_authz_host.so
2aacb174a000-2aacb1949000 ---p 00002000 00:15 36130816 /usr/lib64/httpd/modules/mod_authz_host.so
2aacb1949000-2aacb194b000 rw-p 00001000 00:15 36130816 /usr/lib64/httpd/modules/mod_authz_host.so
2aacb194b000-2aacb194c000 r-xp 00000000 00:15 36130818 /usr/lib64/httpd/modules/mod_authz_user.so
2aacb194c000-2aacb1b4b000 ---p 00001000 00:15 36130818 /usr/lib64/httpd/modules/mod_authz_user.so
2aacb1b4b000-2aacb1b4d000 rw-p 00000000 00:15 36130818 /usr/lib64/httpd/modules/mod_authz_user.so
2aacb1b4d000-2aacb1b4f000 r-xp 00000000 00:15 36130817 /usr/lib64/httpd/modules/mod_authz_owner.so
2aacb1b4f000-2aacb1d4e000 ---p 00002000 00:15 36130817 /usr/lib64/httpd/modules/mod_authz_owner.so
2aacb1d4e000-2aacb1d50000 rw-p 00001000 00:15 36130817 /usr/lib64/httpd/modules/mod_authz_owner.so
2aacb1d50000-2aacb1d52000 r-xp 00000000 00:15 36130815 /usr/lib64/httpd/modules/mod_authz_groupfile.so
2aacb1d52000-2aacb1f51000 ---p 00002000 00:15 36130815 /usr/lib64/httpd/modules/mod_authz_groupfile.so
2aacb1f51000-2aacb1f53000 rw-p 00001000 00:15 36130815 /usr/lib64/httpd/modules/mod_authz_groupfile.so
2aacb1f53000-2aacb1f54000 r-xp 00000000 00:15 36129832 /usr/lib64/httpd/modules/mod_authz_default.so
2aacb1f54000-2aacb2153000 ---p 00001000 00:15 36129832 /usr/lib64/httpd/modules/mod_authz_default.so
2aacb2153000-2aacb2155000 rw-p 00000000 00:15 36129832 /usr/lib64/httpd/modules/mod_authz_default.so
2aacb2155000-2aacb215e000 r-xp 00000000 00:15 36129857 /usr/lib64/httpd/modules/mod_include.so
2aacb215e000-2aacb235e000 ---p 00009000 00:15 36129857 /usr/lib64/httpd/modules/mod_include.so
2aacb235e000-2aacb2360000 rw-p 00009000 00:15 36129857 /usr/lib64/httpd/modules/mod_include.so
2aacb2360000-2aacb2365000 r-xp 00000000 00:15 36130562 /usr/lib64/httpd/modules/mod_log_config.so
2aacb2365000-2aacb2564000 ---p 00005000 00:15 36130562 /usr/lib64/httpd/modules/mod_log_config.so
2aacb2564000-2aacb2566000 rw-p 00004000 00:15 36130562 /usr/lib64/httpd/modules/mod_log_config.so
2aacb2566000-2aacb2568000 r-xp 00000000 00:15 36130563 /usr/lib64/httpd/modules/mod_logio.so
2aacb2568000-2aacb2767000 ---p 00002000 00:15 36130563 /usr/lib64/httpd/modules/mod_logio.so
2aacb2767000-2aacb2769000 rw-p 00001000 00:15 36130563 /usr/lib64/httpd/modules/mod_logio.so
2aacb2769000-2aacb276a000 r-xp 00000000 00:15 36130555 /usr/lib64/httpd/modules/mod_env.so
2aacb276a000-2aacb296a000 ---p 00001000 00:15 36130555 /usr/lib64/httpd/modules/mod_env.so
2aacb296a000-2aacb296c000 rw-p 00001000 00:15 36130555 /usr/lib64/httpd/modules/mod_env.so
2aacb296c000-2aacb2970000 r-xp 00000000 00:15 36130829 /usr/lib64/httpd/modules/mod_ext_filter.so
2aacb2970000-2aacb2b6f000 ---p 00004000 00:15 36130829 /usr/lib64/httpd/modules/mod_ext_filter.so
2aacb2b6f000-2aacb2b71000 rw-p 00003000 00:15 36130829 /usr/lib64/httpd/modules/mod_ext_filter.so
2aacb2b71000-2aacb2b76000 r-xp 00000000 00:15 36130838 /usr/lib64/httpd/modules/mod_mime_magic.so
2aacb2b76000-2aacb2d75000 ---p 00005000 00:15 36130838 /usr/lib64/httpd/modules/mod_mime_magic.so
2aacb2d75000-2aacb2d77000 rw-p 00004000 00:15 36130838 /usr/lib64/httpd/modules/mod_mime_magic.so
2aacb2d77000-2aacb2d79000 r-xp 00000000 00:15 36130828 /usr/lib64/httpd/modules/mod_expires.so
2aacb2d79000-2aacb2f78000 ---p 00002000 00:15 36130828 /usr/lib64/httpd/modules/mod_expires.so
2aacb2f78000-2aacb2f7a000 rw-p 00001000 00:15 36130828 /usr/lib64/httpd/modules/mod_expires.so
2aacb2f7a000-2aacb2f7f000 r-xp 00000000 00:15 36130552 /usr/lib64/httpd/modules/mod_deflate.so
2aacb2f7f000-2aacb317e000 ---p 00005000 00:15 36130552 /usr/lib64/httpd/modules/mod_deflate.so
2aacb317e000-2aacb3180000 rw-p 00004000 00:15 36130552 /usr/lib64/httpd/modules/mod_deflate.so
2aacb3180000-2aacb3183000 r-xp 00000000 00:15 36130559 /usr/lib64/httpd/modules/mod_headers.so
2aacb3183000-2aacb3383000 ---p 00003000 00:15 36130559 /usr/lib64/httpd/modules/mod_headers.so
2aacb3383000-2aacb3385000 rw-p 00003000 00:15 36130559 /usr/lib64/httpd/modules/mod_headers.so
2aacb3385000-2aacb3387000 r-xp 00000000 00:15 36130846 /usr/lib64/httpd/modules/mod_usertrack.so
2aacb3387000-2aacb3587000 ---p 00002000 00:15 36130846 /usr/lib64/httpd/modules/mod_usertrack.so
2aacb3587000-2aacb3589000 rw-p 00002000 00:15 36130846 /usr/lib64/httpd/modules/mod_usertrack.so
2aacb3589000-2aacb358b000 r-xp 00000000 00:15 36130841 /usr/lib64/httpd/modules/mod_setenvif.so
2aacb358b000-2aacb378b000 ---p 00002000 00:15 36130841 /usr/lib64/httpd/modules/mod_setenvif.so
2aacb378b000-2aacb378d000 rw-p 00002000 00:15 36130841 /usr/lib64/httpd/modules/mod_setenvif.so
2aacb378d000-2aacb3791000 r-xp 00000000 00:15 36130837 /usr/lib64/httpd/modules/mod_mime.so
2aacb3791000-2aacb3990000 ---p 00004000 00:15 36130837 /usr/lib64/httpd/modules/mod_mime.so
2aacb3990000-2aacb3992000 rw-p 00003000 00:15 36130837 /usr/lib64/httpd/modules/mod_mime.so
2aacb3992000-2aacb39a7000 r-xp 00000000 00:15 36130550 /usr/lib64/httpd/modules/mod_dav.so
2aacb39a7000-2aacb3ba6000 ---p 00015000 00:15 36130550 /usr/lib64/httpd/modules/mod_dav.so
2aacb3ba6000-2aacb3ba8000 rw-p 00014000 00:15 36130550 /usr/lib64/httpd/modules/mod_dav.so
2aacb3ba8000-2aacb3bac000 r-xp 00000000 00:15 36130843 /usr/lib64/httpd/modules/mod_status.so
2aacb3bac000-2aacb3dab000 ---p 00004000 00:15 36130843 /usr/lib64/httpd/modules/mod_status.so
2aacb3dab000-2aacb3dad000 rw-p 00003000 00:15 36130843 /usr/lib64/httpd/modules/mod_status.so
2aacb3dad000-2aacb3db5000 r-xp 00000000 00:15 36130819 /usr/lib64/httpd/modules/mod_autoindex.so
2aacb3db5000-2aacb3fb4000 ---p 00008000 00:15 36130819 /usr/lib64/httpd/modules/mod_autoindex.so
2aacb3fb4000-2aacb3fb6000 rw-p 00007000 00:15 36130819 /usr/lib64/httpd/modules/mod_autoindex.so
2aacb3fb6000-2aacb3fba000 r-xp 00000000 00:15 36130833 /usr/lib64/httpd/modules/mod_info.so
2aacb3fba000-2aacb41b9000 ---p 00004000 00:15 36130833 /usr/lib64/httpd/modules/mod_info.so
2aacb41b9000-2aacb41bb000 rw-p 00003000 00:15 36130833 /usr/lib64/httpd/modules/mod_info.so
2aacb41bb000-2aacb41c6000 r-xp 00000000 00:15 36130823 /usr/lib64/httpd/modules/mod_dav_fs.so
2aacb41c6000-2aacb43c5000 ---p 0000b000 00:15 36130823 /usr/lib64/httpd/modules/mod_dav_fs.so
2aacb43c5000-2aacb43c7000 rw-p 0000a000 00:15 36130823 /usr/lib64/httpd/modules/mod_dav_fs.so
2aacb43c7000-2aacb43c9000 r-xp 00000000 00:15 36130848 /usr/lib64/httpd/modules/mod_vhost_alias.so
2aacb43c9000-2aacb45c8000 ---p 00002000 00:15 36130848 /usr/lib64/httpd/modules/mod_vhost_alias.so
2aacb45c8000-2aacb45ca000 rw-p 00001000 00:15 36130848 /usr/lib64/httpd/modules/mod_vhost_alias.so
2aacb45ca000-2aacb45d1000 r-xp 00000000 00:15 36130839 /usr/lib64/httpd/modules/mod_negotiation.so
2aacb45d1000-2aacb47d0000 ---p 00007000 00:15 36130839 /usr/lib64/httpd/modules/mod_negotiation.so
2aacb47d0000-2aacb47d2000 rw-p 00006000 00:15 36130839 /usr/lib64/httpd/modules/mod_negotiation.so
2aacb47d2000-2aacb47d4000 r-xp 00000000 00:15 36130825 /usr/lib64/httpd/modules/mod_dir.so
2aacb47d4000-2aacb49d3000 ---p 00002000 00:15 36130825 /usr/lib64/httpd/modules/mod_dir.so
2aacb49d3000-2aacb49d5000 rw-p 00001000 00:15 36130825 /usr/lib64/httpd/modules/mod_dir.so
2aacb49d5000-2aacb49d7000 r-xp 00000000 00:15 36129818 /usr/lib64/httpd/modules/mod_actions.so
2aacb49d7000-2aacb4bd6000 ---p 00002000 00:15 36129818 /usr/lib64/httpd/modules/mod_actions.so
2aacb4bd6000-2aacb4bd8000 rw-p 00001000 00:15 36129818 /usr/lib64/httpd/modules/mod_actions.so
2aacb4bd8000-2aacb4bda000 r-xp 00000000 00:15 36130842 /usr/lib64/httpd/modules/mod_speling.so
2aacb4bda000-2aacb4dda000 ---p 00002000 00:15 36130842 /usr/lib64/httpd/modules/mod_speling.so
2aacb4dda000-2aacb4ddc000 rw-p 00002000 00:15 36130842 /usr/lib64/httpd/modules/mod_speling.so
2aacb4ddc000-2aacb4dde000 r-xp 00000000 00:15 36130573 /usr/lib64/httpd/modules/mod_userdir.so
2aacb4dde000-2aacb4fdd000 ---p 00002000 00:15 36130573 /usr/lib64/httpd/modules/mod_userdir.so
2aacb4fdd000-2aacb4fdf000 rw-p 00001000 00:15 36130573 /usr/lib64/httpd/modules/mod_userdir.so
2aacb4fdf000-2aacb4fe2000 r-xp 00000000 00:15 36130807 /usr/lib64/httpd/modules/mod_alias.so
2aacb4fe2000-2aacb51e1000 ---p 00003000 00:15 36130807 /usr/lib64/httpd/modules/mod_alias.so
2aacb51e1000-2aacb51e3000 rw-p 00002000 00:15 36130807 /usr/lib64/httpd/modules/mod_alias.so
2aacb51e3000-2aacb51f1000 r-xp 00000000 00:15 36129874 /usr/lib64/httpd/modules/mod_rewrite.so
2aacb51f1000-2aacb53f0000 ---p 0000e000 00:15 36129874 /usr/lib64/httpd/modules/mod_rewrite.so
2aacb53f0000-2aacb53f2000 rw-p 0000d000 00:15 36129874 /usr/lib64/httpd/modules/mod_rewrite.so
2aacb53f2000-2aacb53f9000 r-xp 00000000 00:15 36130820 /usr/lib64/httpd/modules/mod_cache.so
2aacb53f9000-2aacb55f8000 ---p 00007000 00:15 36130820 /usr/lib64/httpd/modules/mod_cache.so
2aacb55f8000-2aacb55fa000 rw-p 00006000 00:15 36130820 /usr/lib64/httpd/modules/mod_cache.so
2aacb55fa000-2aacb55fb000 r-xp 00000000 00:15 36130572 /usr/lib64/httpd/modules/mod_suexec.so
2aacb55fb000-2aacb57fb000 ---p 00001000 00:15 36130572 /usr/lib64/httpd/modules/mod_suexec.so
2aacb57fb000-2aacb57fd000 rw-p 00001000 00:15 36130572 /usr/lib64/httpd/modules/mod_suexec.so
2aacb57fd000-2aacb5801000 r-xp 00000000 00:15 36130826 /usr/lib64/httpd/modules/mod_disk_cache.so
2aacb5801000-2aacb5a01000 ---p 00004000 00:15 36130826 /usr/lib64/httpd/modules/mod_disk_cache.so
2aacb5a01000-2aacb5a03000 rw-p 00004000 00:15 36130826 /usr/lib64/httpd/modules/mod_disk_cache.so
2aacb5a03000-2aacb5a05000 r-xp 00000000 00:15 36130830 /usr/lib64/httpd/modules/mod_file_cache.so
2aacb5a05000-2aacb5c04000 ---p 00002000 00:15 36130830 /usr/lib64/httpd/modules/mod_file_cache.so
2aacb5c04000-2aacb5c06000 rw-p 00001000 00:15 36130830 /usr/lib64/httpd/modules/mod_file_cache.so
2aacb5c06000-2aacb5c0c000 r-xp 00000000 00:15 36130836 /usr/lib64/httpd/modules/mod_mem_cache.so
2aacb5c0c000-2aacb5e0b000 ---p 00006000 00:15 36130836 /usr/lib64/httpd/modules/mod_mem_cache.so
2aacb5e0b000-2aacb5e0d000 rw-p 00005000 00:15 36130836 /usr/lib64/httpd/modules/mod_mem_cache.so
2aacb5e0d000-2aacb5e12000 r-xp 00000000 00:15 36130549 /usr/lib64/httpd/modules/mod_cgi.so
2aacb5e12000-2aacb6012000 ---p 00005000 00:15 36130549 /usr/lib64/httpd/modules/mod_cgi.so
2aacb6012000-2aacb6014000 rw-p 00005000 00:15 36130549 /usr/lib64/httpd/modules/mod_cgi.so
2aacb6014000-2aacb6016000 r-xp 00000000 00:15 36130847 /usr/lib64/httpd/modules/mod_version.so
2aacb6016000-2aacb6215000 ---p 00002000 00:15 36130847 /usr/lib64/httpd/modules/mod_version.so
2aacb6215000-2aacb6217000 rw-p 00001000 00:15 36130847 /usr/lib64/httpd/modules/mod_version.so
2aacb6217000-2aacb6226000 r-xp 00000000 00:15 81118597 /usr/lib64/httpd/modules/mod_h264_streaming.so
2aacb6226000-2aacb6426000 ---p 0000f000 00:15 81118597 /usr/lib64/httpd/modules/mod_h264_streaming.so
2aacb6426000-2aacb6427000 rw-p 0000f000 00:15 81118597 /usr/lib64/httpd/modules/mod_h264_streaming.so
2aacb6427000-2aacb6450000 r-xp 00000000 00:15 36130519 /usr/lib64/httpd/modules/mod_ssl.so
2aacb6450000-2aacb6650000 ---p 00029000 00:15 36130519 /usr/lib64/httpd/modules/mod_ssl.so
2aacb6650000-2aacb6652000 rw-p 00029000 00:15 36130519 /usr/lib64/httpd/modules/mod_ssl.so
2aacb6652000-2aacb6654000 rw-p 2aacb6652000 00:00 0
2aacb6663000-2aacb6667000 r-xp 00000000 00:15 75679021 /usr/lib64/libdistcache.so.1.0.1
2aacb6667000-2aacb6866000 ---p 00004000 00:15 75679021 /usr/lib64/libdistcache.so.1.0.1
2aacb6866000-2aacb6867000 rw-p 00003000 00:15 75679021 /usr/lib64/libdistcache.so.1.0.1
2aacb6867000-2aacb686f000 r-xp 00000000 00:15 75679109 /usr/lib64/libnal.so.1.0.1
2aacb686f000-2aacb6a6f000 ---p 00008000 00:15 75679109 /usr/lib64/libnal.so.1.0.1
2aacb6a6f000-2aacb6a70000 rw-p 00008000 00:15 75679109 /usr/lib64/libnal.so.1.0.1
2aacb6a70000-2aacb6a85000 r-xp 00000000 00:15 36129172 /lib64/libnsl-2.5.so
2aacb6a85000-2aacb6c84000 ---p 00015000 00:15 36129172 /lib64/libnsl-2.5.so
2aacb6c84000-2aacb6c85000 r--p 00014000 00:15 36129172 /lib64/libnsl-2.5.so
2aacb6c85000-2aacb6c86000 rw-p 00015000 00:15 36129172 /lib64/libnsl-2.5.so
2aacb6c86000-2aacb6c88000 rw-p 2aacb6c86000 00:00 0
2aacb6c88000-2aacb6c9a000 r-xp 00000000 00:15 36129666 /usr/lib64/httpd/modules/mod_fastcgi.so
2aacb6c9a000-2aacb6e9a000 ---p 00012000 00:15 36129666 /usr/lib64/httpd/modules/mod_fastcgi.so
2aacb6e9a000-2aacb6e9b000 r--p 00012000 00:15 36129666 /usr/lib64/httpd/modules/mod_fastcgi.so
2aacb6e9b000-2aacb6e9c000 rw-p 00013000 00:15 36129666 /usr/lib64/httpd/modules/mod_fastcgi.so
2aacb6e9c000-2aacb6ea0000 rw-p 2aacb6e9c000 00:00 0
2aacb6ea0000-2aacb6eb5000 r-xp 00000000 00:15 36130441 /usr/lib64/httpd/modules/mod_fcgid.so
2aacb6eb5000-2aacb70b5000 ---p 00015000 00:15 36130441 /usr/lib64/httpd/modules/mod_fcgid.so
2aacb70b5000-2aacb70b7000 rw-p 00015000 00:15 36130441 /usr/lib64/httpd/modules/mod_fcgid.so
2aacb70b7000-2aacb7b04000 r-xp 00000000 00:15 36129671 /usr/lib64/httpd/modules/mod_pagespeed.so
2aacb7b04000-2aacb7d04000 ---p 00a4d000 00:15 36129671 /usr/lib64/httpd/modules/mod_pagespeed.so
2aacb7d04000-2aacb7d62000 rw-p 00a4d000 00:15 36129671 /usr/lib64/httpd/modules/mod_pagespeed.so
2aacb7d62000-2aacb7d7e000 rw-p 2aacb7d62000 00:00 0
2aacb7d8d000-2aacb7d94000 r-xp 00000000 00:15 36129177 /lib64/librt-2.5.so
2aacb7d94000-2aacb7f94000 ---p 00007000 00:15 36129177 /lib64/librt-2.5.so
2aacb7f94000-2aacb7f95000 r--p 00007000 00:15 36129177 /lib64/librt-2.5.so
2aacb7f95000-2aacb7f96000 rw-p 00008000 00:15 36129177 /lib64/librt-2.5.so
2aacb7f96000-2aacb807c000 r-xp 00000000 00:15 75678980 /usr/lib64/libstdc++.so.6.0.8
2aacb807c000-2aacb827b000 ---p 000e6000 00:15 75678980 /usr/lib64/libstdc++.so.6.0.8
2aacb827b000-2aacb8281000 r--p 000e5000 00:15 75678980 /usr/lib64/libstdc++.so.6.0.8
2aacb8281000-2aacb8284000 rw-p 000eb000 00:15 75678980 /usr/lib64/libstdc++.so.6.0.8
2aacb8284000-2aacb8296000 rw-p 2aacb8284000 00:00 0
2aacb8296000-2aacb82a3000 r-xp 00000000 00:15 36128166 /lib64/libgcc_s-4.1.2-20080825.so.1
2aacb82a3000-2aacb84a3000 ---p 0000d000 00:15 36128166 /lib64/libgcc_s-4.1.2-20080825.so.1
2aacb84a3000-2aacb84a4000 rw-p 0000d000 00:15 36128166 /lib64/libgcc_s-4.1.2-20080825.so.1
2aacb84a4000-2aacb84da000 r-xp 00000000 00:15 81118680 /usr/lib64/httpd/modules/mod_perl.so
2aacb84da000-2aacb86d9000 ---p 00036000 00:15 81118680 /usr/lib64/httpd/modules/mod_perl.so
2aacb86d9000-2aacb86dd000 rw-p 00035000 00:15 81118680 /usr/lib64/httpd/modules/mod_perl.so
2aacb86dd000-2aacb8809000 r-xp 00000000 00:15 36131766 /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so
2aacb8809000-2aacb8a08000 ---p 0012c000 00:15 36131766 /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so
2aacb8a08000-2aacb8a11000 rw-p 0012b000 00:15 36131766 /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so
2aacb8a11000-2aacb8a13000 rw-p 2aacb8a11000 00:00 0
2aacb8a22000-2aacb8a24000 r-xp 00000000 00:15 36128179 /lib64/libutil-2.5.so
2aacb8a24000-2aacb8c23000 ---p 00002000 00:15 36128179 /lib64/libutil-2.5.so
2aacb8c23000-2aacb8c24000 r--p 00001000 00:15 36128179 /lib64/libutil-2.5.so
2aacb8c24000-2aacb8c25000 rw-p 00002000 00:15 36128179 /lib64/libutil-2.5.so
2aacb8c25000-2aacb8f3d000 r-xp 00000000 00:15 36129655 /usr/lib64/httpd/modules/libphp5.so
2aacb8f3d000-2aacb913c000 ---p 00318000 00:15 36129655 /usr/lib64/httpd/modules/libphp5.so
2aacb913c000-2aacb9192000 rw-p 00317000 00:15 36129655 /usr/lib64/httpd/modules/libphp5.so
2aacb9192000-2aacb91ab000 rw-p 2aacb9192000 00:00 0
2aacb91ba000-2aacb91f2000 r-xp 00000000 00:15 75678964 /usr/lib64/libgmp.so.3.3.3
2aacb91f2000-2aacb93f2000 ---p 00038000 00:15 75678964 /usr/lib64/libgmp.so.3.3.3
2aacb93f2000-2aacb93f3000 rw-p 00038000 00:15 75678964 /usr/lib64/libgmp.so.3.3.3
2aacb93f3000-2aacb9402000 r-xp 00000000 00:15 75678788 /usr/lib64/libbz2.so.1.0.3
2aacb9402000-2aacb9601000 ---p 0000f000 00:15 75678788 /usr/lib64/libbz2.so.1.0.3
2aacb9601000-2aacb9603000 rw-p 0000e000 00:15 75678788 /usr/lib64/libbz2.so.1.0.3
2aacb9603000-2aacb9737000 r-xp 00000000 00:15 36129804 /usr/lib64/libxml2.so.2.6.26
2aacb9737000-2aacb9937000 ---p 00134000 00:15 36129804 /usr/lib64/libxml2.so.2.6.26
2aacb9937000-2aacb9940000 rw-p 00134000 00:15 36129804 /usr/lib64/libxml2.so.2.6.26
2aacb9940000-2aacb9941000 rw-p 2aacb9940000 00:00 0
2aacb9941000-2aacb9943000 r-xp 00000000 00:15 36130275 /usr/lib64/httpd/modules/mod_rpaf.so
2aacb9943000-2aacb9b42000 ---p 00002000 00:15 36130275 /usr/lib64/httpd/modules/mod_rpaf.so
2aacb9b42000-2aacb9b43000 rw-p 00001000 00:15 36130275 /usr/lib64/httpd/modules/mod_rpaf.so
2aacb9b52000-2aacb9b5c000 r-xp 00000000 00:15 36129174 /lib64/libnss_files-2.5.so
2aacb9b5c000-2aacb9d5b000 ---p 0000a000 00:15 36129174 /lib64/libnss_files-2.5.so
2aacb9d5b000-2aacb9d5c000 r--p 00009000 00:15 36129174 /lib64/libnss_files-2.5.so
2aacb9d5c000-2aacb9d5d000 rw-p 0000a000 00:15 36129174 /lib64/libnss_files-2.5.so
2aacb9d5d000-2aacb9d5e000 ---p 2aacb9d5d000 00:00 0
2aacb9d5e000-2aacba85e000 rw-p 2aacb9d5e000 00:00 0
2aacba85e000-2aacba85f000 ---p 2aacba85e000 00:00 0
2aacba85f000-2aacbb25f000 rw-p 2aacba85f000 00:00 0
2aacc0c56000-2aacc104f000 rw-p 2aacc0c56000 00:00 0 [heap]
2aacc104f000-2aacc904f000 rw-s 00000000 00:6d 326604966
2aacc904f000-2aacc914f000 rw-p 2aacc904f000 00:00 0
2aacc914f000-2aaccc353000 rw-s 00000000 00:6d 326604975
2aaccc353000-2aaccc39b000 rw-s 00000000 00:6d 326604983
2aaccc39b000-2aaccc49b000 rw-p 2aaccc39b000 00:00 0
2aacd641d000-2aacd661d000 rw-p 2aacd641d000 00:00 0
2aacd881d000-2aacd881e000 rw-s 00000000 00:6d 326605014
2aacd881e000-2aacd881f000 ---p 2aacd881e000 00:00 0
2aacd881f000-2aacd921f000 rw-p 2aacd881f000 00:00 0
2aacd927a000-2aacd927e000 r-xp 00000000 00:15 36128159 /lib64/libnss_dns-2.5.so
2aacd927e000-2aacd947d000 ---p 00004000 00:15 36128159 /lib64/libnss_dns-2.5.so
2aacd947d000-2aacd947e000 r--p 00003000 00:15 36128159 /lib64/libnss_dns-2.5.so
2aacd947e000-2aacd947f000 rw-p 00004000 00:15 36128159 /lib64/libnss_dns-2.5.so
2aacd9e80000-2aacd9e81000 ---p 2aacd9e80000 00:00 0
2aacd9e81000-2aacda881000 rw-p 2aacd9e81000 00:00 0
2aacdc000000-2aacdc2f7000 rw-p 2aacdc000000 00:00 0
2aacdc2f7000-2aace0000000 ---p 2aacdc2f7000 00:00 0
2aace0000000-2aace03f4000 rw-p 2aace0000000 00:00 0
2aace03f4000-2aace4000000 ---p 2aace03f4000 00:00 0
2aace4000000-2aace4200000 rw-p 2aace4000000 00:00 0
2aace8000000-2aace818e000 rw-p 2aace8000000 00:00 0
2aace818e000-2aacec000000 ---p 2aace818e000 00:00 0
7fffca1e4000-7fffca1f9000 rw-p 7ffffffe9000 00:00 0 [stack]
7fffca1fd000-7fffca200000 r-xp 7fffca1fd000 00:00 0 [vdso]
ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0 [vsyscall]
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/893b456f-c32f-440c-ac94-8ee7bf2dca50%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Miguel Gómez
Jan 10, 2014, 3:15:16 AM1/10/14
to mod-pagesp...@googlegroups.com
This is my memcached config:
PORT="11211"
USER="memcached"
MAXCONN="2048"
CACHESIZE="1024"
OPTIONS="-l 127.0.0.1"
It's installed on same local server than apache and it's only serving one website / domain
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/893b456f-c32f-440c-ac94-8ee7bf2dca50%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Miguel Gómez
Jan 10, 2014, 3:34:11 AM1/10/14
to mod-pagesp...@googlegroups.com
I forgot to say that there is again the same error than before updating this new release:
[Fri Jan 10 08:51:35 2014] [error] [mod_pagespeed 1.7.30.2-3702 @30338] Waiting for property cache fetch to complete. Elapsed time: 42378s
A hundred errors like this one.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/893b456f-c32f-440c-ac94-8ee7bf2dca50%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Miguel Gómez
Jan 10, 2014, 4:27:38 AM1/10/14
to mod-pagesp...@googlegroups.com
Another crash (this one with crashhandler installed): http://pastebin.com/amMDVD1e
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/893b456f-c32f-440c-ac94-8ee7bf2dca50%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Joshua Marantz
Jan 11, 2014, 7:00:54 PM1/11/14
to mod-pagespeed-discuss
Hi,
Thanks for all the stack trace data. Based on it, these crashes occur during child shutdown -- as the process was in the process of exiting, nothing is lost by crashing. We do need to clean these up as they look bad in the logs, but they will not affect traffic.
If you are seeing a lot of them, this is and indication that child processes are frequently spinning up and shutting down, which is a cause for concern. In the past we've seen this correlated with excessive CPU usage. That can also cause system slowdown and thus memcached timeouts.
Is it possible that the traffic patterns or Apache configuration have affected things?
Thanks,
-Josh
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/d5625348-3862-4c57-a00b-a2e97ab98295%40googlegroups.com.To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
Miguel Gómez
Jan 12, 2014, 2:16:44 PM1/12/14
to mod-pagesp...@googlegroups.com
I'm sorry Josh but i'm not sure to fully understand your answer. There is a problem with mod_pagespeed or not? Why is suddenly my apache process using 100% or more CPU? Why there is that HUGE amount of messages 'waiting for property...' that are filling my logs with data? There is something that i could make to solve it?
thanks again,
This is memory map:
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/d7933653-24fe-4579-a24e-5af2ad4b818a%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Joshua Marantz
Jan 12, 2014, 2:22:55 PM1/12/14
to mod-pagespeed-discuss
There is at least one thing wrong with mod_pagespeed: it crashes sometimes during shutdown and we need to fix it. But that's not the source of the problem. I am not sure if the "waiting for property cache" problems are the result of something else going wrong. I'm pretty sure the "cache key collision" problems are since the keys you pasted don't actually collide.
I apologize as well that I don't yet have an answer; only questions: Is it possible that the traffic patterns or Apache configuration have affected things somehow? Can you paste your pagespeed.conf setting?
Can you -- as an experiment -- try disabling the use of memcached and instead just use a file-cache as your L2 cache?
Thanks,
-Josh
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/2df11cf1-6abb-4f96-8640-179595eccb3f%40googlegroups.com.
Joshua Marantz
Jan 13, 2014, 8:17:21 AM1/13/14
to mod-pagespeed-discuss
One more question for you: what version of memcached are you using? The one I test with is 1.4.13. I got this by typing "memcached -help".
-Josh
Miguel Gómez
Jan 13, 2014, 8:19:18 AM1/13/14
to mod-pagesp...@googlegroups.com
memcached is 1.4.5
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/d5625348-3862-4c57-a00b-a2e97ab98295%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Joshua Marantz
Jan 13, 2014, 8:23:35 AM1/13/14
to mod-pagespeed-discuss
1.4.5 was released Date: 2010-04-03 and the release notes for later versions indicate lots of problems fixed:
etc
Can you upgrade memcached to the latest in 1.4.x (looks like it is 1.4.15) and see if that improves things?
-Josh
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/573b66c9-ed6e-4e0d-9713-fe4956ab6c32%40googlegroups.com.
Miguel Gómez
Jan 13, 2014, 8:33:42 AM1/13/14
to mod-pagesp...@googlegroups.com
Hmmm... i'm sorry but i'm not sure about how to update my memcached version. Doing 'yum update' does not works... can you help me with this?
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/2df11cf1-6abb-4f96-8640-179595eccb3f%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Joshua Marantz
Jan 13, 2014, 9:30:02 AM1/13/14
to mod-pagespeed-discuss
I think rebuilding from source is the easiest way. Something like this:
tar xzf memcached-1.4.15.tar.gzcd memcached./configure --prefix=/usr/localmakesudo make install
When I did this just now for 1.4.5, to try to repro the problems, it told me I needed libevent, which I did using the same flow as above, with this implementation of libevent:
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/06f3f3ec-cf4e-42be-a1a4-b9ab1d12b2d1%40googlegroups.com.
Miguel Gómez
Jan 13, 2014, 9:37:51 AM1/13/14
to mod-pagesp...@googlegroups.com
Many thanks Josh; finally i've installed memcached using the remi repo as described here: http://www.if-not-true-then-false.com/2010/install-memcached-on-centos-fedora-red-hat/ Now i've memcache 1.4.15 running. Let's see if this solves something...
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/573b66c9-ed6e-4e0d-9713-fe4956ab6c32%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Miguel Gómez
Jan 13, 2014, 1:28:13 PM1/13/14
to mod-pagesp...@googlegroups.com
After some time running with new version of memcached it seems that there are no crashes (for the moment) but i already have some other errors that may be it could be useful for you; here they are: http://pastebin.com/8XGXExPM
El lunes, 13 de enero de 2014 15:30:02 UTC+1, jmarantz escribió:
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/573b66c9-ed6e-4e0d-9713-fe4956ab6c32%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Huibao Lin
Jan 13, 2014, 1:40:27 PM1/13/14
to mod-pagesp...@googlegroups.com
You can ignore this message:
"pagespeed/kernel/image/gif_reader.cc:729: SCANLINE_STATUS_UNSUPPORTED_FEATURE:SCANLINE_GIFREADERRAW: multiple-frame GIF"
It says that the image is a multiple-frame GIF (i.e., GIF image with animation) which mod_pagespeed does not optimize.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/64401353-dd11-409d-a299-90ce7106a6dd%40googlegroups.com.
Joshua Marantz
Jan 13, 2014, 5:01:05 PM1/13/14
to mod-pagespeed-discuss
RE memcached version: this is great news. Others have reported similar memcached issues, but we've never been able to reproduce it, and it didn't occur to me to ask about memcached version until now. Please let us know if any of the related problems show up again. E.g the shutdown crash is fundamentally our bug, but it wouldn't surprise me if it never shows up when memcached is functioning properly.
RE "pagespeed/kernel/image/gif_reader.cc:729: SCANLINE_STATUS_UNSUPPORTED_FEATURE:SCANLINE_GIFREADERRAW: multiple-frame GIF": this message is not useful to people running servers and should not be printed. I believe it will be demoted to an Info in the next release, and hence not printed by default, and also annotated with the URL of the image. Huibao -- can you confirm?
-Josh
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/CALg8Q9xf8S%2BuZMH3XGPtobzGHahEwtTEcj08y2qhd0k_VSKP9A%40mail.gmail.com.
Huibao Lin
Jan 13, 2014, 5:25:20 PM1/13/14
to mod-pagesp...@googlegroups.com
Yes, the "multiple-frame GIF" message should be an "info" instead of an "error" in the next release.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/CAGKR%2BED8ON_mGwFh7ov-m1_j87-rgwfP_tEzyB8GOZNeWQkAJw%40mail.gmail.com.
Miguel Gómez
Jan 14, 2014, 11:40:46 AM1/14/14
to mod-pagesp...@googlegroups.com
Unfortunately the problem is present again (after some hours running with new version of memcache), you can find full error_log here: http://cl.ly/0e0B121B0116/error_log
This is the first apache crash: http://pastebin.com/unqCMQa6 There are other crashes after this one in my error_log
There is a huge amount of errors like this one (i've pasted here only the last one):
[Tue Jan 14 17:17:32 2014] [error] [mod_pagespeed 1.7.30.2-3702 @32707] Waiting for property cache fetch to complete. Elapsed time: 14268s
when i noticed this, httpd process usage was 99% and i must restart the apache service to restore normal operation and performance again.
This is memory map:
...
For more options, visit <a href="h
Joshua Marantz
Jan 14, 2014, 11:53:25 AM1/14/14
to mod-pagespeed-discuss
Too bad -- I thought I had a convenient scapegoat.
Can you try running using a file-cache for now just to see if that eliminates the problem?
Can you try running using a file-cache for now just to see if that eliminates the problem?
-Josh
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/03089a56-69c2-4fb6-823c-770a55532dea%40googlegroups.com.
Miguel Gómez
Jan 14, 2014, 12:55:59 PM1/14/14
to mod-pagesp...@googlegroups.com
Ok, i've commented out the line to disable the memcache server in pagespeed.conf Now we'll see...
...
Miguel Gómez
Jan 16, 2014, 12:38:33 PM1/16/14
to mod-pagesp...@googlegroups.com
After almost 48 hours running with memcached disabled in pagespeed.conf (and using a filecache instead) there are no crashes at all... there are already some other mod_pagespeed errors, all related to failed conversions (GIF and JPEG) and also with some files not found, but no apache crashes and no abnormal high cpu usage in httpd processes. So i must conclude that memcache is causing problems with latest release of mod_pagespeed.
regards,
El martes, 14 de enero de 2014 17:53:25 UTC+1, jmarantz escribió:
...
Joshua Marantz
Jan 21, 2014, 8:27:14 AM1/21/14
to mod-pagespeed-discuss
Thanks very much for your continued investigation into this. We really need to fix this problem but we can't reproduce it. Miguel, can you share with me more details of your setup?
Which Apache version? Which Linux distribution? Which MPM? Which other modules are enabled in Apache?
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/b7ff9fc7-0f44-4118-b754-5890c7f68f1e%40googlegroups.com.
Miguel Gómez
Jan 21, 2014, 10:35:52 AM1/21/14
to mod-pagesp...@googlegroups.com
In my previous posts i've shared apache version and my linux distro. Please, let me know if you need more details
This is memory map:
...<blockquote style="margin:0px 0px 0px 0.8ex;bo
Miguel Gómez
Jan 23, 2014, 10:08:22 PM1/23/14
to mod-pagesp...@googlegroups.com
May be that i'm running apache 2.2.3 and i could need to upgrade to 2.2.4?? CentOS 5.10 comes with 2.2.3 and yum update does not upgrade my apache to that version.
El martes, 21 de enero de 2014 14:27:14 UTC+1, jmarantz escribió:
This is memory map:
<blockquote style="margin:0px 0px 0px 0.8ex;bo
...
Joshua Marantz
Jan 23, 2014, 10:17:55 PM1/23/14
to mod-pagespeed-discuss
I have been running tests with Apache 2.2.3 on a CentOS 5.4 Virtual Machine and cannot reproduce the problem. It's still possible that it's related to Apache 2.2.3, but I can't say for sure.
However if you don't mind I'd love it if you could run a test with a small code edit. In pagespeed/kernel/cache/cache_batcher.h, about line 69, can you change
static const size_t kDefaultMaxQueueSize = 1000;
to
static const size_t kDefaultMaxQueueSize = 100;
and rebuild and test? My theory is that the problem is very large response bodies may get mis-handled by the Apache socket code in older versions of Apache.
Thanks,
-Josh
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/0e4a44e9-2e2f-4836-add4-fa6b97d92fc9%40googlegroups.com.
Miguel Gómez
Jan 24, 2014, 7:55:08 AM1/24/14
to mod-pagesp...@googlegroups.com
Ok, i'll try to test this code edit. I want also to notice here that using the latest release there is a lot of errors like this one:
ReferenceError: mod_pagespeed_cS0EEQzQ1R is not defined
error source line:
<script>eval(mod_pagespeed_cS0EEQzQ1R);</script> |
This is displayed into the javascript browser console.
...
Miguel Gómez
Jan 30, 2014, 8:48:38 AM1/30/14
to mod-pagesp...@googlegroups.com
Hi again, can't rebuild source with these changes, but i'm having a lot of errors like this:
ReferenceError: mod_pagespeed_iMEc5Ofc$h is not defined
error source line:
<script>eval(mod_pagespeed_KEuGhPrC8A);</script> |
in my browser console. That errors does not happen with previous release.
Joshua Marantz
Jan 30, 2014, 5:21:46 PM1/30/14
to mod-pagespeed-discuss
Re the ReferenceError -- we've seen a few of these and we believe we understand the problem and will have a fix coming soon.
In the meantime, please disable combine_javascript.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/a2626256-af7e-4894-8b73-51ba83298310%40googlegroups.com.
Miguel Gómez
Feb 12, 2014, 7:36:44 AM2/12/14
to mod-pagesp...@googlegroups.com
Hello again Josh, there is any updates for this bug? there is another release coming soon? thanks
El jueves, 30 de enero de 2014 23:21:46 UTC+1, jmarantz escribió:
Re the ReferenceError -- we've seen a few of these and we believe we understand the problem and will have a fix coming soon.In the meantime, please disable combine_javascript.
On Thu, Jan 30, 2014 at 8:48 AM, Miguel Gómez <fid...@gmail.com> wrote:
Hi again, can't rebuild source with these changes, but i'm having a lot of errors like this:ReferenceError: mod_pagespeed_iMEc5Ofc$h is not definederror source line:
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Miguel Gómez
Mar 16, 2014, 8:24:43 AM3/16/14
to mod-pagesp...@googlegroups.com
Hi again Josh
I've updated mod pagespeed to latest version. I've enabled memcached support in pagespeed.conf again with the hope that the issue was resolved and it seems that still doesn't works. I'm having 99% cpu usage in httpd process and many errors like these:
[Sun Mar 16 13:11:49 2014] [warn] [mod_pagespeed 1.7.30.4-3847 @22131] RateController: drop deferred fetch of https://xxx.xxx.xxx.xxx/imagesrc.jpg?rel=aHR0cHM6Ly93d3cudmF4ZGVudHJvLmNvbS9pbWFnZXMvbG9mdGh1bWJzLzUyNXgyODQv$
and also this:
[warn] [mod_pagespeed 1.7.30.4-3847 @22009] Unable to insert object of size: 23383, cache limit is: 16016
i've noticed that it always happens when using SSL, it seems to work with http adresses so may be it has something to do with https connections. Can you help? it's necessary to provide the certs path in pagespeed.conf? i've these lines commented out...
El jueves, 30 de enero de 2014 23:21:46 UTC+1, jmarantz escribió:
Re the ReferenceError -- we've seen a few of these and we believe we understand the problem and will have a fix coming soon.In the meantime, please disable combine_javascript.
...
Joshua Marantz
Mar 16, 2014, 9:38:46 AM3/16/14
to mod-pagespeed-discuss
There is still tuning to be done, for sure. But there was a functional issue which was that "waiting for property cache to finish" messages were being logged 1 per second, with httpd processes spinning at 100%. I'm certain the "waiting for property cache to finish" messages are gone now because the code that printed them was deleted. But the better question is whether you still get spinning httpd processes. If there are, then the original problem you reported is still unresolved.
RE "Unable to insert object of size: ..." warning. That should be an INFO message at best, and in any case it should print the key. How frequently is this one occurring? This is related to the shared memory metadata cache, not memcached. I added https://code.google.com/p/modpagespeed/issues/detail?id=907 to track the issue.
The rate-limiting issue might be tunable:
[Sun Mar 16 13:11:49 2014] [warn] [mod_pagespeed 1.7.30.4-3847 @22131] RateController: drop deferred fetch of https://xxx.xxx.xxx.xxx/imagesrc.jpg?rel=aHR0cHM6Ly93d3cudmF4ZGVudHJvLmNvbS9pbWFnZXMvbG9mdGh1bWJzLzUyNXgyODQv$
Can you tell me how frequently they are occurring? E.g., how many per minute?
This might happen in HTTPS and not HTTP because HTTPS requests take longer to decode. But I'm concerned about the query-param ?rel=aHR0cHM6Ly93d3cudmF4ZGVudHJvLmNvbS9pbWFnZXMvbG9mdGh1bWJzLzUyNXgyODQv$. Is that for cache-busting? It's better not to use other cache-busting techniques with mod_pagespeed, because that will force mod_pagespeed to re-fetch and re-optimize the same images multiple times. It's better to use a short origin TTL (e.g. 10 minutes to 1 hour) and let mod_pagespeed sign the URLs.
-Josh
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/8a0da9a7-641b-4e65-8c60-31aa4965763c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Miguel Gómez
Mar 16, 2014, 10:11:18 AM3/16/14
to mod-pagesp...@googlegroups.com
The message "Unable to insert object of size..." is very frequent in my logs. I'm having problems now because mod_pagespeed does not process images being served using PHP and previously it was working. I'm not sure what i've changed in my pagespeed.conf file and i'm unable to get it working again.
What's the recommended procedure to serve resources when using SSL? what pagespeed configuration? i've readed the documentation but it's a bit confusing because there is several methods....
El domingo, 16 de marzo de 2014 14:38:46 UTC+1, jmarantz escribió:
There is still tuning to be done, for sure. But there was a functional issue which was that "waiting for property cache to finish" messages were being logged 1 per second, with httpd processes spinning at 100%. I'm certain the "waiting for property cache to finish" messages are gone now because the code that printed them was deleted. But the better question is whether you still get spinning httpd processes. If there are, then the original problem you reported is still unresolved.RE "Unable to insert object of size: ..." warning. That should be an INFO message at best, and in any case it should print the key. How frequently is this one occurring? This is related to the shared memory metadata cache, not memcached. I added https://code.google.com/p/modpagespeed/issues/detail?id=907 to track the issue.The rate-limiting issue
...
Miguel Gómez
Mar 16, 2014, 10:19:23 AM3/16/14
to mod-pagesp...@googlegroups.com
Some of my images are being served using PHP in this way www.myserver.com/myimage.jpg?code=34637 or also www.myserver.com/myimage.php?code=34637 it was previously working and pagespeed was optimizing the images the same way that a direct link to a 'real' image, but now it doesn't work. Can you help me with this issue? How can i configure pagespeed to work with this¿
El domingo, 16 de marzo de 2014 14:38:46 UTC+1, jmarantz escribió:
There is still tuning to be done, for sure. But there was a functional issue which was that "waiting for property cache to finish" messages were being logged 1 per second, with httpd processes spinning at 100%. I'm certain the "waiting for property cache to finish" messages are gone now because the code that printed them was deleted. But the better question is whether you still get spinning httpd processes. If there are, then the original problem you reported is still unresolved.RE "Unable to insert object of size: ..." warning. That should be an INFO message at best, and in any case it should print the key. How frequently is this one occurring? This is related to the shared memory metadata cache, not memcached. I added https://code.google.com/p/modpagespeed/issues/detail?id=907 to track the issue.The rate-limiting issue
...
Miguel Gómez
Mar 16, 2014, 11:15:23 AM3/16/14
to mod-pagesp...@googlegroups.com
"But I'm concerned about the query-param ?rel=aHR0cHM6Ly93d3cudmF4ZGVudHJvLmNvbS9pbWFnZXMvbG9mdGh1bWJzLzUyNXgyODQv$. Is that for cache-busting?"
No, it's to locate the image resource, the image is being served with php. imagesrc.jpg is really imagesrc.php with changed extension to allow pagespeed to cache it. But it's not working now (previously it was)
El domingo, 16 de marzo de 2014 14:38:46 UTC+1, jmarantz escribió:
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Joshua Marantz
Mar 16, 2014, 5:08:54 PM3/16/14
to mod-pagespeed-discuss
Thanks for the clarification about the jpeg query params. That's fine, but can you tell me HTTP response headers for those jpeg files are, and how of them there are on your site? Also, your files don't have to end with ".jpg" for PageSpeed to cache them. PageSpeed doesn't care what extension you have, just what the HTTP headers are.
Hope this helps,
You said "Unable to insert object of size..." is very frequent in your logs. Can you quantify that? How many per minute? I'm trying to understand whether they are just annoying or will actually cause problems because of their frequency.
There are lots of options for dealing with SSL, as described in the doc you've already read. I am responsible for the doc and if there are specific sections you need me to make clear, or specific questions that the doc does not answer, please let me know.
Could you paste the current version of your pagespeed.conf file? Maybe there's something else going on there that might jump out at me.
The fact that rate-limiting is kicking in is not necessarily a problem. Let's say you have 10000 images on your server. When your mod_pagespeed cache is cold, or was partially flushed due to a configuration change, we don't want to fetch and optimize all 10000 images at once, but we want to kind of cycle through them. We keep a bounded-size queue of outstanding fetches. When the queue gets over its fixed size, we start dropping image rewrites to keep the system stable and healthy. Eventually, all the images on your server will be fetched and optimized and the images in the queue will eventually be fetched and optimized. The ones that had to be dropped will get another chance the next time someone visits a page that references those images. I think in my testing I found that putting 2000 images on a single page we wound up having to visit the page 4 times before they were all optimized.
The other variables in this equation are:
- For how long can we cache the images
- Is your cache big enough to hold all your content.
If you can't quite cache all your content then you are going to be constantly refetching it and suffering these errors.
Hope this helps,
-Josh
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/f93928e5-b1eb-4286-a246-6e138c8d5641%40googlegroups.com.
Miguel Gómez
Mar 16, 2014, 5:36:09 PM3/16/14
to mod-pagesp...@googlegroups.com
This is one response header for imgsrc.php:
- Cache-Control:public, max-age=2592000
- Content-Encoding:gzip
- Content-Length:2502
- Content-Type:image/jpeg
- Date:Sun, 16 Mar 2014 19:52:10 GMT
- Expires:Tue, 15 Apr 2014 19:52:10 GMT
- Last-Modified:Sun, 16 Mar 2014 19:21:33 GMT
- MS-Author-Via:DAV
- Pragma:public
- Server:Apache
- Vary:Accept-Encoding
- X-Content-Type-Options:nosniff
Page speed is ignoring that files when using https and i don't know why.
"Unable to insert object of size: 22584, cache limit is: 16016" messages are about 4 per minute aprox.
Also there are many of this errors:
[Sun Mar 16 16:31:35 2014] [error] [mod_pagespeed 1.7.30.4-3847 @1285] Failed to stat /var/www/vhosts/myserver.com/httpdocs/imagesrc.jpg: No such file or directory
regards,
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-discuss+unsub...@googlegroups.com.
Miguel Gómez
Mar 16, 2014, 5:44:18 PM3/16/14
to mod-pagesp...@googlegroups.com
The same imagesrc.jpg (or .php) works fine when NOT using http. So there is something wrong with pagespeed https configuration. I've this:
ModPagespeedFetchHttps enabled (also i've tried with allow_self_signed)
i also have this line: ModPagespeedMapOriginDomain "http://www.myserver.com" "https://www.myserver.com" but currently is commented out cause i'm not sure if to enable it or it's not necessary.
regards,
El domingo, 16 de marzo de 2014 22:08:54 UTC+1, jmarantz escribió:
Thanks for the clarification about the jpeg query params. That's fine, but can you tell me HTTP response headers for those jpeg files are, and how of them there are on your site? Also, your files don't have to end with ".jpg" for PageSpeed to cache them. PageSpeed doesn't care what extension you have, just what the HTTP headers are.You said "Unable to insert object of size..." is very frequent in your logs. Can you quantify that? How many per minute? I'm trying to understand whether they are just annoying or will actually cause problems because of their frequency.There are lots of options for dealing with SSL, as described in the doc you've already read. I am responsible for the doc and if there are specific sections you need me to make clear, or specific questions that the doc does not answer, please let me know.
...<span style="font-family:arial
Joshua Marantz
Mar 16, 2014, 9:34:36 PM3/16/14
to mod-pagespeed-discuss
Can you post the entire contents of your pagespeed.conf?
It also might help to get a look at your apache error.log file. If we are having trouble doing the HTTPS fetches then I'm hoping some warnings will be printed there. It might help to drop to "loglevel info" to get more detail about why fetches are not occurring.
To contrast the various methods of getting HTTPS data into mod_pagespeed, mapping origin to HTTP is certainly a good way if the transport between the server running mod_pagespeed and the server providing the image files is secure. If it's the same physical machine then I think it's totally fine, and is probably more efficient than doing the loopback fetch over TLS, which requires running encryption/decryption software on both ends of the socket.
At 4 messages per minute, I think the "value too big" warning is very annoying and I consider it a bug, but is probably not causing direct harm to your system. ~104 bytes per message, * (60*4 = 240) messages per hour * 24 hours/day = ~600 k per day. This won't break your disk, and warnings are buffered so it won't make your Apache process I/O bound. We'll definitely fix it for 1.8 (due soon).
This message:
[Sun Mar 16 16:31:35 2014] [error] [mod_pagespeed 1.7.30.4-3847 @1285] Failed to stat /var/www/vhosts/myserver.com/httpdocs/imagesrc.jpg: No such file or directory
makes me think you might have LoadFromFile enabled, but that won't work with your query params. If I see your pagespeed.conf I'll get a better idea.
-Josh
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/4d5e3dfc-d58b-48f2-b26e-c98161aaa23f%40googlegroups.com.
Miguel Gómez
Mar 24, 2014, 3:49:49 PM3/24/14
to mod-pagesp...@googlegroups.com
Just a little update here. Now i have memcached enabled again in mod_pagespeed, working for a few weeks and not problems. I believe that may be it was related to the https config and how the data is retrieved when using https, i bet that i was a combination of some parameters in my pagespeed.conf but i've no time to experiment with this more in deep.
Other than the repeated messages in my logs, that i've posted here before, i'm not having big problems with this latest release (crossing fingers :D)
cheers,
...
Joshua Marantz
Mar 24, 2014, 5:23:43 PM3/24/14
to mod-pagespeed-discuss
Thanks for the update, Miguel! Glad things are working better.
The repeated message issue, captured in https://code.google.com/p/modpagespeed/issues/detail?id=907, is now fixed.
The repeated message issue, captured in https://code.google.com/p/modpagespeed/issues/detail?id=907, is now fixed.
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/9e5d954f-2fb5-46be-a8b2-cf7a9d98ad9e%40googlegroups.com.
chrone
Mar 26, 2014, 2:13:42 AM3/26/14
to mod-pagesp...@googlegroups.com
Hi guys,
I still get these AprMemcache repeated messages on Ubuntu 12.04.4 LTS running Apache 2.2.22-1ubuntu1.5 and mod-pagespeed-stable 1.7.30.4-r3847.
[Wed Mar 26 12:06:49 2014] [error] [mod_pagespeed 1.7.30.4-3847 @15837] AprMemCache::Get error: The timeout specified has expired (70007) on key prop_page/https://www.example.com/ajax/promo/0_9GmCrW26SS@Desktop@beacon_cohort
[Wed Mar 26 12:06:49 2014] [error] [mod_pagespeed 1.7.30.4-3847 @15837] AprMemCache::MultiGet error: Internal error (20014) on 1 keys
[Wed Mar 26 12:06:49 2014] [error] [mod_pagespeed 1.7.30.4-3847 @16040] AprMemCache::Get error: The timeout specified has expired (70007) on key prop_page/https://www.example.com/ajax/promo/0_9GmCrW26SS@Desktop@beacon_cohort
[Wed Mar 26 12:06:49 2014] [error] [mod_pagespeed 1.7.30.4-3847 @16040] AprMemCache::MultiGet error: Internal error (20014) on 1 keys
[Wed Mar 26 12:07:22 2014] [error] [mod_pagespeed 1.7.30.4-3847 @14785] AprMemCache::Get error: The timeout specified has expired (70007) on key prop_page/https://www.example.com/ajax/promo/0_9GmCrW26SS@Desktop@beacon_cohort
[Wed Mar 26 12:07:22 2014] [error] [mod_pagespeed 1.7.30.4-3847 @14785] AprMemCache::MultiGet error: Internal error (20014) on 1 keys
[Wed Mar 26 12:07:22 2014] [error] [mod_pagespeed 1.7.30.4-3847 @17148] AprMemCache::Get error: The timeout specified has expired (70007) on key prop_page/https://www.example.com/ajax/news_9GmCrW26SS@Desktop@beacon_cohort
[Wed Mar 26 12:07:22 2014] [error] [mod_pagespeed 1.7.30.4-3847 @17148] AprMemCache::MultiGet error: Internal error (20014) on 1 keys
chrone
Mar 26, 2014, 4:33:01 AM3/26/14
to mod-pagesp...@googlegroups.com
Hi Josh,
I still get the occassionally AprMemcache repeated messages on Ubuntu 12.04 LTS running Apache 2.2.22-1ubuntu1.5 and mod-pagespeed-stable 1.7.30.4-r3847 as follows:
[Wed Mar 26 12:06:49 2014] [error] [mod_pagespeed 1.7.30.4-3847 @15837] AprMemCache::Get error: The timeout specified has expired (70007) on key prop_page/https://somedomain/ajax/promo/0_9GmCrW26SS@Desktop@beacon_cohort
[Wed Mar 26 12:06:49 2014] [error] [mod_pagespeed 1.7.30.4-3847 @15837] AprMemCache::MultiGet error: Internal error (20014) on 1 keys
[Wed Mar 26 12:06:49 2014] [error] [mod_pagespeed 1.7.30.4-3847 @16040] AprMemCache::Get error: The timeout specified has expired (70007) on key prop_page/https://somedomain/ajax/promo/0_9GmCrW26SS@Desktop@beacon_cohort
[Wed Mar 26 12:06:49 2014] [error] [mod_pagespeed 1.7.30.4-3847 @16040] AprMemCache::MultiGet error: Internal error (20014) on 1 keys
[Wed Mar 26 12:07:13 2014] [error] [client 91.200.14.48] File does not exist: /var/www/proxyc, referer: http://gas-avto.com/proxyc/http/engine.php
[Wed Mar 26 12:07:22 2014] [error] [mod_pagespeed 1.7.30.4-3847 @14785] AprMemCache::Get error: The timeout specified has expired (70007) on key prop_page/https://somedomain/ajax/promo/0_9GmCrW26SS@Desktop@beacon_cohort
[Wed Mar 26 12:07:22 2014] [error] [mod_pagespeed 1.7.30.4-3847 @14785] AprMemCache::MultiGet error: Internal error (20014) on 1 keys
[Wed Mar 26 12:07:22 2014] [error] [mod_pagespeed 1.7.30.4-3847 @17148] AprMemCache::Get error: The timeout specified has expired (70007) on key prop_page/https://somedomain/ajax/news_9GmCrW26SS@Desktop@beacon_cohort
[Wed Mar 26 12:07:22 2014] [error] [mod_pagespeed 1.7.30.4-3847 @17148] AprMemCache::MultiGet error: Internal error (20014) on 1 keys
On Tuesday, March 25, 2014 4:23:43 AM UTC+7, jmarantz wrote:
Thanks for the update, Miguel! Glad things are working better.
The repeated message issue, captured in https://code.google.com/p/modpagespeed/issues/detail?id=907, is now fixed.
On Mon, Mar 24, 2014 at 3:49 PM, Miguel Gómez <fid...@gmail.com> wrote:
Just a little update here. Now i have memcached enabled again in mod_pagespeed, working for a few weeks and not problems. I believe that may be it was related to the https config and how the data is retrieved when using https, i bet that i was a combination of some parameters in my pagespeed.conf but i've no time to experiment with this more in deep.Other than the repeated messages in my logs, that i've posted here before, i'm not having big problems with this latest release (crossing fingers :D)cheers,
El lunes, 17 de marzo de 2014 02:34:36 UTC+1, jmarantz escribió:
Can you post the entire contents of your pagespeed.conf?It also might help to get a look at your apache error.log file. If we are having trouble doing the HTTPS fetches then I'm hoping some warnings will be printed there. It might help to drop to "loglevel info" to get more detail about why fetches are not occurring.To contrast the various methods of getting HTTPS data into mod_pagespeed, mapping origin to HTTP is certainly a good way if the transport between the server running mod_pagespeed and the server providing the image files is secure. If it's the same physical machine then I think it's totally fine, and is probably more efficient than doing the loopback fetch over TLS, which requires running encryption/decryption software on both ends of the socket.At 4 messages per minute, I think the "value too big" warning is very annoying and I consider it a bug, but is probably not causing direct harm to your system. ~104 bytes per message, * (60*4 = 240) messages per hour * 24 hours/day = ~600 k per day. This won't break your disk, and warnings are buffered so it won't make your Apache process I/O bound. We'll definitely fix it for 1.8 (due soon).This message:
...[Sun Mar 16 16:31:35 2014] [error] [mod_pagespeed 1.7.30.4-3847 @1285] Failed to stat /var/www/vhosts/<a href="http://myserver.com/httpdocs/imagesrc.jpg" style="font-family:ari
Joshua Marantz
Mar 26, 2014, 8:04:56 AM3/26/14
to mod-pagespeed-discuss
Can you verify what memcached server you are using? If you are using raw memcached and your system is not to heavily loaded, then timeouts are a surprise. But if you are you using a more complicated server setup that speaks memcached protocol, such as one that uses a real database, then our timeout might be too tight, and you might need to loosen it. This might also be necessary if your system is highly loaded.
-Josh
--
You received this message because you are subscribed to the Google Groups "mod-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mod-pagespeed-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mod-pagespeed-discuss/badad3e4-abd0-4a84-b506-49c350ef9d64%40googlegroups.com.
Joshua Marantz
Mar 27, 2014, 10:31:01 AM3/27/14
to mod-pagespeed-discuss
I have confirmed there is still a problem, and have a candidate fix (emailed on a different -discuss thread). I re-opened https://code.google.com/p/modpagespeed/issues/detail?id=885 to track it.
-Josh
Reply all
Reply to author
Forward
0 new messages