Flood within Logfile

[jonathan maderer]

Hi i use NGINX Extras latest stable together with Pagespeed.

Currently Pagespeed is flooding my nginx Error Log with
2015/04/05 06:31:58 [error] 28697#0: [ngx_pagespeed 1.9.32.1-4238] Serf status 20014(Internal error) polling for 4 threaded fetches for 0.05 seconds

This message Repeats every Second but sometimes with variable Numbers like

2015/04/10 14:46:21 [error] 28817#0: [ngx_pagespeed 1.9.32.1-4238] Serf status 20014(Internal error) polling for 5 threaded fetches for 0.05 seconds
2015/04/10 14:46:22 [error] 28817#0: [ngx_pagespeed 1.9.32.1-4238] Serf status 20014(Internal error) polling for 3 threaded fetches for 0.05 seconds
2015/04/10 14:46:22 [error] 28817#0: [ngx_pagespeed 1.9.32.1-4238] Serf status 20014(Internal error) polling for 4 threaded fetches for 0.05 seconds
2015/04/10 14:46:26 [error] 28817#0: [ngx_pagespeed 1.9.32.1-4238] Serf status 20014(Internal error) polling for 4 threaded fetches for 0.05 seconds
2015/04/10 14:46:38 [error] 28818#0: [ngx_pagespeed 1.9.32.1-4238] Serf status 20014(Internal error) polling for 1 threaded fetches for 0.05 seconds
2015/04/10 14:46:38 [error] 28818#0: [ngx_pagespeed 1.9.32.1-4238] Serf status 20014(Internal error) polling for 2 threaded fetches for 0.05 seconds
2015/04/10 14:46:41 [error] 28817#0: [ngx_pagespeed 1.9.32.1-4238] Serf status 20014(Internal error) polling for 1 threaded fetches for 0.05 seconds

I used google to read a bit about and find that this might be a bug. Is there a way to fix this or stop that from logfiles without recompiling Nginx?

[Jeff Kaufman]

Could you try setting:

pagespeed ListOutstandingUrlsOnError on;

to help debug this?

> --
> You received this message because you are subscribed to the Google Groups
> "ngx-pagespeed-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ngx-pagespeed-di...@googlegroups.com.
> Visit this group at http://groups.google.com/group/ngx-pagespeed-discuss.
> For more options, visit https://groups.google.com/d/optout.

[jonathan maderer]

Hi Jefff, i activated this and this is the result

http://pastebin.com/2BKkskSu

[Jeff Kaufman]

Thanks!

Could you paste your pagespeed config?

[jonathan maderer]

Off course,

i use several configs.

On the first Level i use a pagespeed main config
http://pastebin.com/CK7uR7wy

On the Second level for vhosts i use
http://pastebin.com/yn9iShGd (Site1)

http://pastebin.com/0uLnqgei (Site 2)

Maybe i missed something in the config hmm,- sometimes i got the feeling there is something bugged, like he wont clear the memcache or purge it.

[Jeff Kaufman]

The code for this is in pagespeed/system/serf_url_async_fetcher.cc,
and we've had some issues with this error before:
* https://github.com/pagespeed/mod_pagespeed/issues/349
* https://github.com/pagespeed/mod_pagespeed/issues/940
* http://stackoverflow.com/questions/17355899/very-many-fetch-timed-out-errors-in-apache-log
* https://groups.google.com/forum/#!topic/mod-pagespeed-discuss/SE-3RToufgQ

Still looking into it.

[jonathan maderer]

If you need further information that could help please hit me a Message

Thanks a lot :)

[Joshua Marantz]

If you can load those resources via LoadFromFile or via MapOrigin to do a loopback fetch to localhost that might help take the stress off of Serf.

-Josh

On Fri, Apr 10, 2015 at 11:00 AM, jonathan maderer <maderer....@googlemail.com> wrote:

If you need further information that could help please hit me a Message

Thanks a lot :)

--

[jonathan maderer]

Hi Josh,

i think your refer to this https://developers.google.com/speed/pagespeed/module/domains#mapping_origin

This really looks complicated on the first look.But i will try to understand it.

Am Freitag, 10. April 2015 21:00:45 UTC+2 schrieb Joshua Marantz:

If you can load those resources via LoadFromFile or via MapOrigin to do a loopback fetch to localhost that might help take the stress off of Serf.

-Josh

On Fri, Apr 10, 2015 at 11:00 AM, jonathan maderer <maderer....@googlemail.com> wrote:

If you need further information that could help please hit me a Message

Thanks a lot :)

--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.

[jonathan maderer]

Okay i tried to figure out how this works, but i'm again seeing this messages within the log.

I hope i did this correctly, i added this to the second level configs for vhosts

pagespeed MapOriginDomain localhost *.gnetwork.eu;
pagespeed MapRewriteDomain localhost *.gnetwork.eu;

pagespeed LoadFromFile "http://gnetwork.eu" "/var/www/clients/client1/web12/web";
pagespeed LoadFromFile "https://gnetwork.eu" "/var/www/clients/client1/web12/web";
pagespeed LoadFromFile "https://wow.gnetwork.eu" "/var/www/clients/client1/web12/wow";
pagespeed LoadFromFile "http://wow.gnetwork.eu" "/var/www/clients/client1/web12/wow";


Is this the right way?

[Jeff Kaufman]

You shouldn't need both the MapOriginDomain and the LoadFromFile.
LoadFromFile is more efficient; what happens if you just use the
LoadFromFile commands you have?

I don't think you should need MapRewriteDomain either; could you try
removing that as well?

If you try this, and you still get the messages, could you give an
updated pastebin like this one? http://pastebin.com/2BKkskSu

> --
> You received this message because you are subscribed to the Google Groups
> "ngx-pagespeed-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to ngx-pagespeed-di...@googlegroups.com.

[jonathan maderer]

Thanks for your Response, i will try this out :)
Greetings from Germany

> email to ngx-pagespeed-discuss+unsub...@googlegroups.com.

[jonathan maderer]

Okay here is a update. I removed all lines with Rewrite and MapOrigin
The result is now really better. It is not flooding every second into the log, and now i think it is clear why this error occurred.
All left messages are because of the use of "timthumb" (http://www.binarymoon.co.uk/projects/timthumb/)

http://pastebin.com/L4u3rKZQ

I think the chance is big that this never will be fixed because timthumb is outdated meanwhile.
Thanks a lot Jeff, it is now really better and i know where this come from :)