You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.
I have been running modpagespeed on my server for a while now, and noticed that
at 13:00:49 today, there was a raft of 34 errors in my logs (internal error) as
follows:
[Thu Nov 17 13:00:50 2011] [error] [mod_pagespeed 0.9.18.7-900 @6186]
http://www.sellmyretro.com:443/uploaded/img/1933_3_ZX81KBMembrane2008_8dcea_a8d_
505_efaa2_55_d8_3a70_dca4_90cec_3f_6dd02_f5a02_100px.jpg:0: serf_context_run
error status=20014 (Internal error)
[Thu Nov 17 13:00:51 2011] [error] [mod_pagespeed 0.9.18.7-900 @6186]
[1117/130051:ERROR:net/instaweb/apache/serf_url_async_fetcher.cc(944)] Serf
status 20014 (Internal error ) polling for 27: (threaded) (0x2b67b5294370) for
0.05 seconds
Any ideas on this - the server does not appear to have been overloaded at any
time...
Original issue reported on code.google.com by sexy.ric...@googlemail.com on 17 Nov 2011 at 2:02
The text was updated successfully, but these errors were encountered:
The change to add more diagnostics is in trunk as of
http://code.google.com/p/modpagespeed/source/detail?r=1563, gated on new
pagespeed.conf setting
ModPagespeedListOutstandingUrlsOnError on
Original comment by jmara...@google.com on 15 May 2012 at 3:35
The latest release (0.10.22.4) has a pagespeed.conf option:
ModPagespeedListOutstandingUrlsOnError on
Can you turn this on, see exactly what URLs are failing, and we can then help
you sort out what action to take?
If there's a general problem that requires a fix on our side of course we can
then take that up, or perhaps improved documentation/FAQ would help.
Thanks!
Original comment by jmara...@google.com on 5 Jun 2012 at 3:40
Original issue reported on code.google.com by
sexy.ric...@googlemail.com
on 17 Nov 2011 at 2:02The text was updated successfully, but these errors were encountered: