search

crowell / modpagespeed_tmp

Automatically exported from code.google.com/p/modpagespeed
Apache License 2.0
0 stars 0 forks source link

Segfault with mod_pagespeed 1.4 with no pagespeed.conf file. #670

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. I uninstalled long ago, about 4 months ago
2. and I'm still getting these errors

[error] [mod_pagespeed 1.4.26.2-2759 @26208] ServerContext: 1 
leaked_rewrite_drivers on destruction
[Thu Apr 11 23:30:20 2013] [error] [mod_pagespeed 1.4.26.2-2759 @25878] 
ServerContext: 1 leaked_rewrite_drivers on destruction
[Thu Apr 11 23:37:00 2013] [warn] [mod_pagespeed  @26806] 
[0411/233700:WARNING:queued_worker_pool.cc(377)] Adding function to sequence 
0x7fdefea04d50 after shutdown
[Thu Apr 11 23:57:24 2013] [notice] child pid 27715 exit signal Segmentation 
fault (11)
[Fri Apr 12 00:11:55 2013] [notice] child pid 28172 exit signal Segmentation 
fault (11)
[Fri Apr 12 00:38:07 2013] [warn] [mod_pagespeed  @29968] 
[0412/003807:WARNING:queued_worker_pool.cc(377)] Adding function to sequence 
0x7fdefe9e08b0 after shutdown
[Fri Apr 12 01:05:30 2013] [notice] child pid 31050 exit signal Segmentation 
fault (11)
[Fri Apr 12 01:07:27 2013] [notice] child pid 31042 exit signal Segmentation 
fault (11)
[Fri Apr 12 01:16:40 2013] [warn] [mod_pagespeed  @31735] 
[0412/011640:WARNING:queued_worker_pool.cc(430)] Canceling 196 functions on 
sequence Shutdown
[Fri Apr 12 01:16:42 2013] [error] [mod_pagespeed 1.4.26.2-2759 @31735] 
ServerContext: 1 leaked_rewrite_drivers on destruction
[Fri Apr 12 01:33:21 2013] [warn] [mod_pagespeed  @406] 
[0412/013321:WARNING:serf_url_async_fetcher.cc(1115)] Aborting fetch of 
http://10.168.28.226/main/wp-content/themes/widezine/assets/topnav_bg.gif
[Fri Apr 12 01:33:21 2013] [warn] [mod_pagespeed  @406] 
[0412/013321:WARNING:serf_url_async_fetcher.cc(1115)] Aborting fetch of 
http://10.168.28.226/main/wp-content/themes/widezine/assets/home_icon.png
[Fri Apr 12 01:33:21 2013] [warn] [mod_pagespeed  @406] 
[0412/013321:WARNING:serf_url_async_fetcher.cc(1115)] Aborting fetch of 
http://10.168.28.226/main/wp-content/themes/widezine/assets/home_icon_hover.png
[Fri Apr 12 01:33:22 2013] [warn] [mod_pagespeed  @406] 
[0412/013322:WARNING:queued_worker_pool.cc(430)] Canceling 12 functions on 
sequence Shutdown
[Fri Apr 12 01:33:24 2013] [error] [mod_pagespeed 1.4.26.2-2759 @406] 
ServerContext: 1 leaked_rewrite_drivers on destruction
[Fri Apr 12 02:08:50 2013] [notice] child pid 1911 exit signal Segmentation 
fault (11)

How do I completely uninstall

Thanks

Original issue reported on code.google.com by proyecto...@gmail.com on 12 Apr 2013 at 2:32

GoogleCodeExporter commented 9 years ago 
It doesn't seem like it's uninstalled; some of your error messages look like 
you've been updated to the latest version.   Questions:

1. What OS are you on (debian, ubuntu, redhat, centos etc)
2. Did you install from binary?
3. How did you install it?
4. How did you uninstall it?

We really should fix the segfaults (assuming they are ours) but I guess if 
you've decided to uninstall you are not motivated to help us track it down?  Or 
would you be willing to help us see what's going on?

Original comment by jmara...@google.com on 12 Apr 2013 at 3:47

GoogleCodeExporter commented 9 years ago 
I would love to give it a try once more.
I have CENTOS
I can't remember how I installed or uninstalled it.  I guess I did it with a 
guide here or in the web.

Is there a way I can completely uninstall it and start from scratch?

Original comment by proyecto...@gmail.com on 12 Apr 2013 at 11:14

GoogleCodeExporter commented 9 years ago 
I used this to install 
http://www.tecmint.com/install-mod_pagespeed-website-optimizer-for-apache-in-rhe
l-centos-and-fedora/

and I removed /etc/httpd/conf.d/pagespeed.conf

Original comment by proyecto...@gmail.com on 12 Apr 2013 at 11:20

GoogleCodeExporter commented 9 years ago 
Summary was: :  I'm getting errors in apache error log long long ago after 
uninstall

As that site says, to turn off the module use 

   ModPagespeed off

This turns off the module by default but leaves it in 'standby' mode.  To turn 
it off completely, "unplug" it:

   ModPagespeed unplugged

This is a new feature but based on the error message you've sent, you have the 
latest version.  Removing the .conf file might not help; it depends how the 
module is loaded.  To uninstall completely, you have to make sure that none of 
your.conf files load mod_pagespeed.so e.g.
  LoadModule pagespeed_module /usr/lib/httpd/modules/mod_pagespeed.so

Hope this helps.

I'm hijacking this bug, though to focus on the segfault.

Original comment by jmara...@google.com on 13 Apr 2013 at 2:59

GoogleCodeExporter commented 9 years ago 
Thanks for now I've used  ModPagespeed unplugged

Thank you for your time!

Original comment by proyecto...@gmail.com on 13 Apr 2013 at 6:10

GoogleCodeExporter commented 9 years ago 
now with Modspeed unplugged i'm getting this errors

[Sat Apr 13 16:15:27 2013] [error] [mod_pagespeed 1.4.26.2-2759 @15980] Attempt 
to destroy unknown SHM segment /var/cache/mod_pagespeed//named_locks.
[Sat Apr 13 16:15:27 2013] [error] [mod_pagespeed  @15980] 
[0413/161527:ERROR:google_message_handler.cc(39)] Attempt to destroy unknown 
SHM segment SharedCircularBuffer.:0.
[Sat Apr 13 16:23:57 2013] [error] [mod_pagespeed 1.4.26.2-2759 @16213] Attempt 
to destroy unknown SHM segment /var/cache/mod_pagespeed//named_locks.
[Sat Apr 13 16:23:57 2013] [error] [mod_pagespeed  @16213] 
[0413/162357:ERROR:google_message_handler.cc(39)] Attempt to destroy unknown 
SHM segment SharedCircularBuffer.:0.
[Sat Apr 13 16:23:58 2013] [error] [mod_pagespeed 1.4.26.2-2759 @16206] Attempt 
to destroy unknown SHM segment /var/cache/mod_pagespeed//named_locks.
[Sat Apr 13 16:23:58 2013] [error] [mod_pagespeed  @16206] 
[0413/162358:ERROR:google_message_handler.cc(39)] Attempt to destroy unknown 
SHM segment SharedCircularBuffer.:0.
[Sat Apr 13 16:23:59 2013] [error] [mod_pagespeed 1.4.26.2-2759 @18456] Attempt 
to destroy unknown SHM segment /var/cache/mod_pagespeed//named_locks.
[Sat Apr 13 16:23:59 2013] [error] [mod_pagespeed  @18456] 
[0413/162359:ERROR:google_message_handler.cc(39)] Attempt to destroy unknown 
SHM segment SharedCircularBuffer.:0.
[Sat Apr 13 16:24:00 2013] [error] [mod_pagespeed 1.4.26.2-2759 @16410] Attempt 
to destroy unknown SHM segment /var/cache/mod_pagespeed//named_locks.
[Sat Apr 13 16:24:00 2013] [error] [mod_pagespeed  @16410] 
[0413/162400:ERROR:google_message_handler.cc(39)] Attempt to destroy unknown 
SHM segment SharedCircularBuffer.:0.
[Sat Apr 13 16:24:02 2013] [error] [mod_pagespeed 1.4.26.2-2759 @17480] Attempt 
to destroy unknown SHM segment /var/cache/mod_pagespeed//named_locks.
[Sat Apr 13 16:24:02 2013] [error] [mod_pagespeed  @17480] 
[0413/162402:ERROR:google_message_handler.cc(39)] Attempt to destroy unknown 
SHM segment SharedCircularBuffer.:0.
[Sat Apr 13 16:24:11 2013] [error] [mod_pagespeed 1.4.26.2-2759 @15949] Attempt 
to destroy unknown SHM segment /var/cache/mod_pagespeed//named_locks.
[Sat Apr 13 16:24:11 2013] [error] [mod_pagespeed  @15949] 
[0413/162411:ERROR:google_message_handler.cc(39)] Attempt to destroy unknown 
SHM segment SharedCircularBuffer.:0.
[Sat Apr 13 16:24:14 2013] [error] [mod_pagespeed 1.4.26.2-2759 @13664] Attempt 
to destroy unknown SHM segment /var/cache/mod_pagespeed//named_locks.
[Sat Apr 13 16:24:14 2013] [error] [mod_pagespeed  @13664] 
[0413/162414:ERROR:google_message_handler.cc(39)] Attempt to destroy unknown 
SHM segment SharedCircularBuffer.:0.
[Sat Apr 13 16:40:41 2013] [notice] child pid 7512 exit signal Segmentation 
fault (11)
[Sat Apr 13 16:53:05 2013] [error] [mod_pagespeed 1.4.26.2-2759 @9898] Attempt 
to destroy unknown SHM segment /var/cache/mod_pagespeed//named_locks.
[Sat Apr 13 16:53:05 2013] [error] [mod_pagespeed  @9898] 
[0413/165305:ERROR:google_message_handler.cc(39)] Attempt to destroy unknown 
SHM segment SharedCircularBuffer.:0.

Original comment by proyecto...@gmail.com on 13 Apr 2013 at 5:23

GoogleCodeExporter commented 9 years ago 
and with unplugged my server is much much more stable. I think  this was 
messing my server for the last 2 months.

Original comment by proyecto...@gmail.com on 13 Apr 2013 at 5:24

GoogleCodeExporter commented 9 years ago 
For CentOS:
To find what mod_pagespeed you have install: rpm -qa | grep pagespeed
To remove the version you have installed: rpm -ev 
the-package-that-command-reports

Original comment by matterb...@google.com on 13 Apr 2013 at 5:26

GoogleCodeExporter commented 9 years ago 
i'm getting this

[ec2-user@ip-10-168-28-226 ~]$ rpm -qa | grep pagespeed
mod-pagespeed-beta-1.4.26.2-2759.x86_64
[ec2-user@ip-10-168-28-226 ~]$ rpm -ev mod-pagespeed-beta-1.4.26.2-2759.x86_64
error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Permission 
denied)
[ec2-user@ip-10-168-28-226 ~]$ sudo rpm -ev 
mod-pagespeed-beta-1.4.26.2-2759.x86_6
error: package mod-pagespeed-beta-1.4.26.2-2759.x86_6 is not installed
[ec2-user@ip-10-168-28-226 ~]$

Original comment by proyecto...@gmail.com on 13 Apr 2013 at 5:43

GoogleCodeExporter commented 9 years ago 
Ah, sorry about forgetting sudo.

Try rpm -qi mod-pagespeed-beta and see what it says.
Then try sudo rpm -ev mod-pagespeed-beta (without the version stuff).

Original comment by matterb...@google.com on 15 Apr 2013 at 4:17

GoogleCodeExporter commented 9 years ago

Original comment by jmara...@google.com on 15 Apr 2013 at 3:22

GoogleCodeExporter commented 9 years ago 
After marking pagespeed as unplugged in the configuration I got the 
aforementioned error in apache:

ERROR:google_message_handler.cc(39)] Attempt to destroy unknown SHM segment 
SharedCircularBuffer

Unfortunately after a few days, this seems to make a memory leak in Apache and 
the RAM assigned to apache started to increase until a certain level that made 
my server to hang (started to swap RAM to disk).

I have finally removed the configuration pagespeed.conf file from conf.d 
folder.

Original comment by mgonzc...@gmail.com on 17 May 2013 at 5:52

GoogleCodeExporter commented 9 years ago 
I have the same error with stable version after apache2 update. I removed 
stable version of mod_pagespeed and installed beta. I do not see any errors 
right now.

Original comment by Yukko.Se...@gmail.com on 29 Jan 2014 at 2:37

GoogleCodeExporter commented 9 years ago 
I believe there was a SEGV relating to global 'unplugged' behavior which was 
fixed for 1.7.  I'm assuming that fixes the segfault reported here.  Please 
re-open if it still happens.

Original comment by jmara...@google.com on 31 Jan 2014 at 10:35

GoogleCodeExporter commented 9 years ago 
I've same problem with 1.7:

[Thu Feb 20 12:52:01 2014] [error] [mod_pagespeed 1.7.30.3-3721 @28053] Attempt 
to destroy unknown SHM segment [1]/var/cache/mod_pagespeed//named_locks.
[Thu Feb 20 12:52:01 2014] [error] [mod_pagespeed 1.7.30.3-3721 @28053] Attempt 
to destroy unknown SHM segment [1]pagespeed_default_shm/metadata_cache.
[Thu Feb 20 12:52:01 2014] [error] [mod_pagespeed 1.7.30.3-3721 @28053] Attempt 
to destroy unknown SHM segment [1]globalstatistics.
[Thu Feb 20 12:52:01 2014] [error] [mod_pagespeed  @28053] 
[0220/125201:ERROR:google_message_handler.cc(42)] Attempt to destroy unknown 
SHM segment [1]SharedCircularBuffer.:0.
[Thu Feb 20 12:52:01 2014] [notice] caught SIGTERM, shutting down

Original comment by ce...@uakix.com on 20 Feb 2014 at 11:54

GoogleCodeExporter commented 9 years ago 
I have the same error in production, but not on testing servers
[Thu Apr 03 17:55:06 2014] [warn] module php5_module is already loaded, skipping
[Thu Apr 03 17:55:06 2014] [notice] Digest: generating secret for digest 
authentication ...
[Thu Apr 03 17:55:06 2014] [notice] Digest: done
PHP Warning:  Module 'gd' already loaded in Unknown on line 0
[Thu Apr 03 17:55:06 2014] [notice] Apache/2.2.15 (Unix) DAV/2 mod_rpaf/0.6 
configured -- resuming normal operations
[Thu Apr 03 17:55:07 2014] [error] [mod_pagespeed 1.7.30.4-3847 @32596] Attempt 
to destroy unknown SHM segment [1]/var/cache/mod_pagespeed//named_locks.
[Thu Apr 03 17:55:07 2014] [error] [mod_pagespeed 1.7.30.4-3847 @32596] Attempt 
to destroy unknown SHM segment [1]pagespeed_default_shm/metadata_cache.
[Thu Apr 03 17:55:07 2014] [error] [mod_pagespeed  @32596] 
[0403/175507:ERROR:google_message_handler.cc(42)] Attempt to destroy unknown 
SHM segment [1]SharedCircularBuffer.:0.
[Thu Apr 03 17:55:08 2014] [error] [mod_pagespeed 1.7.30.4-3847 @32598] Attempt 
to destroy unknown SHM segment [1]/var/cache/mod_pagespeed//named_locks.
[Thu Apr 03 17:55:08 2014] [error] [mod_pagespeed 1.7.30.4-3847 @32598] Attempt 
to destroy unknown SHM segment [1]pagespeed_default_shm/metadata_cache.
[Thu Apr 03 17:55:08 2014] [error] [mod_pagespeed  @32598] 
[0403/175508:ERROR:google_message_handler.cc(42)] Attempt to destroy unknown 
SHM segment [1]SharedCircularBuffer.:0.
[Thu Apr 03 17:55:09 2014] [error] [mod_pagespeed 1.7.30.4-3847 @32602] Attempt 
to destroy unknown SHM segment [1]/var/cache/mod_pagespeed//named_locks.
[Thu Apr 03 17:55:09 2014] [error] [mod_pagespeed 1.7.30.4-3847 @32602] Attempt 
to destroy unknown SHM segment [1]pagespeed_default_shm/metadata_cache.

Original comment by calvinxa...@gmail.com on 7 Apr 2014 at 8:35

GoogleCodeExporter commented 9 years ago 
re: comments #15/#16: what apache versions and MPMs are these? What other 
modules are you running?

Original comment by morlov...@google.com on 7 Apr 2014 at 1:15

GoogleCodeExporter commented 9 years ago 
fixed via increase 
ModPagespeedFileCacheSizeKb 1024000
ModPagespeedFileCacheCleanIntervalMs 3600000
ModPagespeedMaxCombinedCssBytes 1024000
ModPagespeedMaxCombinedJsBytes 1024000

Original comment by calvinxa...@gmail.com on 9 Apr 2014 at 6:37

GoogleCodeExporter commented 9 years ago 
rpm -qa | grep httpd
httpd-devel-2.2.15-30.el6.centos.x86_64
httpd-tools-2.2.15-30.el6.centos.x86_64
httpd-2.2.15-30.el6.centos.x86_64

my pagespeed.conf:

# Attempt to load mod_version if it wasn't loaded or compiled in (eg on Debian)
<IfModule !mod_version.c>
  LoadModule version_module /usr/lib64/httpd/modules/mod_version.so
</IfModule>

<IfVersion < 2.4>
  LoadModule pagespeed_module /usr/lib64/httpd/modules/mod_pagespeed.so
</IfVersion>
<IfVersion >= 2.4.2>
  LoadModule pagespeed_module /usr/lib64/httpd/modules/mod_pagespeed_ap24.so
</IfVersion>

# Only attempt to load mod_deflate if it hasn't been loaded already.
<IfModule !mod_deflate.c>
 LoadModule deflate_module /usr/lib64/httpd/modules/mod_deflate.so
</IfModule>
<IfModule pagespeed_module>                                                     

    # Turn on mod_pagespeed. To completely disable mod_pagespeed, you                                                                                                                                                                          
    # can set this to "off".                                                                                                                                                                                                                   
    ModPagespeed off                                                                                                                                                                                                                           

    # We want VHosts to inherit global configuration.                                                                                                                                                                                          
    # If this is not included, they'll be independent (except for inherently                                                                                                                                                                   
    # global options), at least for backwards compatibility.                                                                                                                                                                                   
    ModPagespeedInheritVHostConfig on                                                                                                                                                                                                          

    # Direct Apache to send all HTML output to the mod_pagespeed                                                                                                                                                                               
    # output handler.                                                                                                                                                                                                                          
    AddOutputFilterByType MOD_PAGESPEED_OUTPUT_FILTER text/html                                                                                                                                                                                

    # If you want mod_pagespeed process XHTML as well, please uncomment this                                                                                                                                                                   
    # line.
    # AddOutputFilterByType MOD_PAGESPEED_OUTPUT_FILTER application/xhtml+xml

    # The ModPagespeedFileCachePath directory must exist and be writable
    # by the apache user (as specified by the User directive).
    ModPagespeedFileCachePath            "/var/cache/mod_pagespeed/"

    # LogDir is needed to store various logs, including the statistics log
    # required for the console.
    ModPagespeedLogDir "/var/log/pagespeed"

    # The locations of SSL Certificates is distribution-dependent.
    #ModPagespeedSslCertDirectory "/etc/pki/tls/certs"
    #ModPagespeedSslCertFile /etc/pki/tls/cert.pem

    # If you want, you can use one or more memcached servers as the store for
    # the mod_pagespeed cache.
    # ModPagespeedMemcachedServers localhost:11211

    # A portion of the cache can be kept in memory only, to reduce load on disk
    # (or memcached) from many small files.
    # ModPagespeedCreateSharedMemoryMetadataCache "/var/cache/mod_pagespeed/" 51200

    # Override the mod_pagespeed 'rewrite level'. The default level
    # "CoreFilters" uses a set of rewrite filters that are generally
    # safe for most web pages. Most sites should not need to change
    # this value and can instead fine-tune the configuration using the
    # ModPagespeedDisableFilters and ModPagespeedEnableFilters
    # directives, below. Valid values for ModPagespeedRewriteLevel are
    # PassThrough, CoreFilters and TestingCoreFilters.
    #
    # ModPagespeedRewriteLevel PassThrough

    # Explicitly disables specific filters. This is useful in
    # conjuction with ModPagespeedRewriteLevel. For instance, if one
    # of the filters in the CoreFilters needs to be disabled for a
    # site, that filter can be added to
    # ModPagespeedDisableFilters. This directive contains a
    # comma-separated list of filter names, and can be repeated.
    #
    ModPagespeedDisableFilters rewrite_images

    # Explicitly enables specific filters. This is useful in
    # conjuction with ModPagespeedRewriteLevel. For instance, filters
    # not included in the CoreFilters may be enabled using this
    # directive. This directive contains a comma-separated list of
    # filter names, and can be repeated.
    #
     ModPagespeedEnableFilters rewrite_javascript,rewrite_css
     ModPagespeedEnableFilters combine_javascript,combine_css
     ModPagespeedEnableFilters collapse_whitespace,elide_attributes
    #ModPagespeedEnableFilters combine_css,combine_javascript,extend_cache,rewrite_css,rewrite_javascript,remove_comments,collapse_whitespace

    # Explicitly forbids the enabling of specific filters using either query
    # parameters or request headers. This is useful, for example, when we do
    # not want the filter to run for performance or security reasons. This
    # directive contains a comma-separated list of filter names, and can be
    # repeated.
    #
    # ModPagespeedForbidFilters rewrite_images

    # How long mod_pagespeed will wait to return an optimized resource
    # (per flush window) on first request before giving up and returning the
    # original (unoptimized) resource. After this deadline is exceeded the
    # original resource is returned and the optimization is pushed to the
    # background to be completed for future requests. Increasing this value will
    # increase page latency, but might reduce load time (for instance on a
    # bandwidth-constrained link where it's worth waiting for image
    # compression to complete). If the value is less than or equal to zero
    # mod_pagespeed will wait indefinitely for the rewrite to complete before
    # returning.
    #
    # ModPagespeedRewriteDeadlinePerFlushMs 10

    # ModPagespeedDomain
    # authorizes rewriting of JS, CSS, and Image files found in this
    # domain. By default only resources with the same origin as the
    # HTML file are rewritten. For example:
    #
    #   ModPagespeedDomain cdn.myhost.com
    #
    # This will allow resources found on http://cdn.myhost.com to be
    # rewritten in addition to those in the same domain as the HTML.
    #
    # Other domain-related directives (like ModPagespeedMapRewriteDomain
    # and ModPagespeedMapOriginDomain) can also authorize domains.
    #
    # Wildcards (* and ?) are allowed in the domain specification. Be
    # careful when using them as if you rewrite domains that do not
    # send you traffic, then the site receiving the traffic will not
    # know how to serve the rewritten content.

    # Other defaults (cache sizes and thresholds):
    #
    ModPagespeedFileCacheSizeKb          1024000
    ModPagespeedFileCacheCleanIntervalMs 3600000
    # ModPagespeedLRUCacheKbPerProcess     1024
    # ModPagespeedLRUCacheByteLimit        16384
    # ModPagespeedCssFlattenMaxBytes       2048
    # ModPagespeedCssInlineMaxBytes        2048
    # ModPagespeedCssImageInlineMaxBytes   0
    # ModPagespeedImageInlineMaxBytes      3072
    # ModPagespeedJsInlineMaxBytes         2048
    # ModPagespeedCssOutlineMinBytes       3000
    # ModPagespeedJsOutlineMinBytes        3000
    ModPagespeedMaxCombinedCssBytes      1024000
    ModPagespeedMaxCombinedJsBytes       1024000

    # Limit the number of inodes in the file cache. Set to 0 for no limit.
    # The default value if this paramater is not specified is 0 (no limit).
    ModPagespeedFileCacheInodeLimit        500000

    # Bound the number of images that can be rewritten at any one time; this
    # avoids overloading the CPU.  Set this to 0 to remove the bound.
    #
    # ModPagespeedImageMaxRewritesAtOnce      8

    # You can also customize the number of threads per Apache process
    # mod_pagespeed will use to do resource optimization. Plain
    # "rewrite threads" are used to do short, latency-sensitive work,
    # while "expensive rewrite threads" are used for actual optimization
    # work that's more computationally expensive. If you live these unset,
    # or use values <= 0 the defaults will be used, which is 1 for both
    # values when using non-threaded MPMs (e.g. prefork) and 4 for both
    # on threaded MPMs (e.g. worker and event). These settings can only
    # be changed globally, and not per virtual host.
    #
    # ModPagespeedNumRewriteThreads 4
    # ModPagespeedNumExpensiveRewriteThreads 4

    # Randomly drop rewrites (*) to increase the chance of optimizing
    # frequently fetched resources and decrease the chance of optimizing
    # infrequently fetched resources. This can reduce CPU load. The default
    # value of this parameter is 0 (no drops).  90 means that a resourced
    # fetched once has a 10% probability of being optimized while a resource
    # that is fetched 50 times has a 99.65% probability of being optimized.
    #
    # (*) Currently only CSS files and images are randomly dropped.  Images
    # within CSS files are not randomly dropped.
    #
    # ModPagespeedRewriteRandomDropPercentage 90

    # Many filters modify the URLs of resources in HTML files. This is typically
    # harmless but pages whose Javascript expects to read or modify the original
    # URLs may break. The following parameters prevent filters from modifying
    # URLs of their respective types.
    #
    # ModPagespeedJsPreserveURLs on
     ModPagespeedImagePreserveURLs on
    # ModPagespeedCssPreserveURLs on

    # Settings for image optimization:
    #
    # Lossy image recompression quality (0 to 100, -1 just strips metadata):
    # ModPagespeedImageRecompressionQuality 85
    #
    # Jpeg recompression quality (0 to 100, -1 uses ImageRecompressionQuality):
    # ModPagespeedJpegRecompressionQuality -1
    # ModPagespeedJpegRecompressionQualityForSmallScreens 70
    #
    # WebP recompression quality (0 to 100, -1 uses ImageRecompressionQuality):
    # ModPagespeedImageWebpRecompressionQuality 80
    # ModPagespeedImageWebpRecompressionQualityForSmallScreens 70
    #
    # Timeout for conversions to WebP format, in
    # milliseconds. Negative values mean no timeout is applied. The
    # default value is -1:
    # ModPagespeedImageWebpTimeoutMs 5000
    #
    # Percent of original image size below which optimized images are retained:
    # ModPagespeedImageLimitOptimizedPercent 100
    #
    # Percent of original image area below which image resizing will be
    # attempted:
    # ModPagespeedImageLimitResizeAreaPercent 100

    # Settings for inline preview images
    #
    # Setting this to n restricts preview images to the first n images found on
    # the page.  The default of -1 means preview images can appear anywhere on
    # the page (if those images appear above the fold).
    # ModPagespeedMaxInlinedPreviewImagesIndex -1

    # Sets the minimum size in bytes of any image for which a low quality image
    # is generated.
    # ModPagespeedMinImageSizeLowResolutionBytes 3072

    # The maximum URL size is generally limited to about 2k characters
    # due to IE: See http://support.microsoft.com/kb/208427/EN-US.
    # Apache servers by default impose a further limitation of about
    # 250 characters per URL segment (text between slashes).
    # mod_pagespeed circumvents this limitation, but if you employ
    # proxy servers in your path you may need to re-impose it by
    # overriding the setting here.  The default setting is 1024
    # characters.
    #
    # ModPagespeedMaxSegmentLength 250

    # Uncomment this if you want to prevent mod_pagespeed from combining files
    # (e.g. CSS files) across paths
    #
    # ModPagespeedCombineAcrossPaths off

    # Renaming JavaScript URLs can sometimes break them.  With this
    # option enabled, mod_pagespeed uses a simple heuristic to decide
    # not to rename JavaScript that it thinks is introspective.
    #
    # You can uncomment this to let mod_pagespeed rename all JS files.
    #
    # ModPagespeedAvoidRenamingIntrospectiveJavascript off

    # Certain common JavaScript libraries are available from Google, which acts
    # as a CDN and allows you to benefit from browser caching if a new visitor
    # to your site previously visited another site that makes use of the same
    # libraries as you do.  Enable the following filter to turn on this feature.
    #
    ModPagespeedEnableFilters canonicalize_javascript_libraries

    # The following line configures a library that is recognized by
    # canonicalize_javascript_libraries.  This will have no effect unless you
    # enable this filter (generally by uncommenting the last line in the
    # previous stanza).  The format is:
    #    ModPagespeedLibrary bytes md5 canonical_url
    # Where bytes and md5 are with respect to the *minified* JS; use
    # js_minify --print_size_and_hash to obtain this data.
    # Note that we can register multiple hashes for the same canonical url;
    # we do this if there are versions available that have already been minified
    # with more sophisticated tools.
    #
    # Additional library configuration can be found in
    # pagespeed_libraries.conf included in the distribution.  You should add
    # new entries here, though, so that file can be automatically upgraded.
    # ModPagespeedLibrary 43 1o978_K0_LNE5_ystNklf http://www.modpagespeed.com/rewrite_javascript.js

    # Explicitly tell mod_pagespeed to load some resources from disk.
    # This will speed up load time and update frequency.
    #
    # This should only be used for static resources which do not need
    # specific headers set or other processing by Apache.
    #
    # Both URL and filesystem path should specify directories and
    # filesystem path must be absolute (for now).
    #
    # ModPagespeedLoadFromFile "http://example.com/static/" "/var/www/static/"

    # Enables server-side instrumentation and statistics.  If this rewriter is
    # enabled, then each rewritten HTML page will have instrumentation javacript
    # added that sends latency beacons to /mod_pagespeed_beacon.  These
    # statistics can be accessed at /mod_pagespeed_statistics.  You must also
    # enable the mod_pagespeed_statistics and mod_pagespeed_beacon handlers
    # below.
    #
    # ModPagespeedEnableFilters add_instrumentation

    # The add_instrumentation filter sends a beacon after the page onload
    # handler is called. The user might navigate to a new URL before this. If
    # you enable the following directive, the beacon is sent as part of an
    # onbeforeunload handler, for pages where navigation happens before the
    # onload event.
    #
    ModPagespeedReportUnloadTime off

    # Uncomment the following line so that ModPagespeed will not cache or
    # rewrite resources with Vary: in the header, e.g. Vary: User-Agent.
    # Note that ModPagespeed always respects Vary: headers on html content.
    # ModPagespeedRespectVary on

    # Uncomment the following line if you want to disable statistics entirely.
    #
    # ModPagespeedStatistics off

    # This page lets you view statistics about the mod_pagespeed module.
    <Location /mod_pagespeed_statistics>
        Order allow,deny
        # You may insert other "Allow from" lines to add hosts you want to
        # allow to look at generated statistics.  Another possibility is
        # to comment out the "Order" and "Allow" options from the config
        # file, to allow any client that can reach your server to examine
        # statistics.  This might be appropriate in an experimental setup or
        # if the Apache server is protected by a reverse proxy that will
        # filter URLs in some fashion.
        Allow from localhost
        Allow from 127.0.0.1
        Allow from 95.131.24.44
        Allow from 80.250.216.218
        SetHandler mod_pagespeed_statistics
    </Location>

    # Enable logging of mod_pagespeed statistics, needed for the console.
    ModPagespeedStatisticsLogging on

    <Location /pagespeed_console>
        Order allow,deny
        Allow from localhost
        Allow from 127.0.0.1
        Allow from 95.131.24.44
        Allow from 80.250.216.218
        SetHandler pagespeed_console
    </Location>

    # Page /mod_pagespeed_message lets you view the latest messages from
    # mod_pagespeed, regardless of log-level in your httpd.conf
    # ModPagespeedMessageBufferSize is the maximum number of bytes you would
    # like to dump to your /mod_pagespeed_message page at one time,
    # its default value is 100k bytes.
    # Set it to 0 if you want to disable this feature.
    ModPagespeedMessageBufferSize 100000

    <Location /mod_pagespeed_message>
        Order allow,deny
        Allow from localhost
        Allow from 127.0.0.1
        Allow from 95.131.24.44
        Allow from 80.250.216.218
        SetHandler mod_pagespeed_message
    </Location>
</IfModule>

Original comment by calvinxa...@gmail.com on 9 Apr 2014 at 6:40

GoogleCodeExporter commented 9 years ago 
sorry, fixed in update httpd-2.2.15-30.el6.centos.x86_64.rpm

Original comment by calvinxa...@gmail.com on 9 Apr 2014 at 11:29