New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

serf_url_async_fetcher.cc error messages using IP instead of domain name #786

Closed
GoogleCodeExporter opened this Issue Apr 6, 2015 · 9 comments

Comments

Projects
None yet
1 participant
@GoogleCodeExporter
Copy link

GoogleCodeExporter commented Apr 6, 2015

1. Enable mod_pagespeed
2. error.log shows flow of errors:
 [Mon Sep 23 12:36:58 2013] [warn] [mod_pagespeed  @419] [0923/123658:WARNING:serf_url_async_fetcher.cc(1115)] Aborting fetch of http://106.186.xxx.xxx/js/jquery/themes/some-path/ui-bg_flat_0_aaaaaa_40x100.png

mod_pagespeed is using IP instead of proper domain name, which results in an 
invalid URL (multiple vhosts on this server).

Relevant vhost conf bits:
 <VirtualHost *:80>
      ServerName mysite.com
      ServerAlias www.mysite.com
      DocumentRoot /srv/www/mysite.com/public_html/

I realise this might be fixable by using a ModPagespeedMapOriginDomain conf or 
even ModPagespeedLoadFromFile, but it seems like I shouldn't have to in this 
simple case.

Everything apart from that works fine... Any idea what might be causing this? 
DNS setup or other?

Happening with both latest beta and stable version, on apache2 using vhost 
config files (mod_pagespeed is enabled for all sites in the main conf file).

Original issue reported on code.google.com by zedrd...@gmail.com on 23 Sep 2013 at 4:29

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Could you post your pagespeed.conf please?

Original comment by matterb...@google.com on 23 Sep 2013 at 12:02

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

The IP showing up in the log is basically just a misleading log message: this 
is the IP we connect to, but Apache should still be seeing the proper hostname 
in the request (though that there are lots of abort messages is suspicious). Do 
you see errors other than 'aborting fetch', or wrong stuff in access_log?

Original comment by morlov...@google.com on 23 Sep 2013 at 12:18

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

pagespeed.conf is straight out of the box: nothing changed.

Vhosts don't have anything special either beside Analytics settings:
ModPagespeedEnableFilters insert_ga
ModPagespeedAnalyticsID etc.

Pretty certain  Apache is not using the domain right: I'm seeing dozens of 
these errors a minute... And the non-domain part of these URLs is valid, so it 
would stand to reason that the IP use is the problem.

Along with the string of serf_url_async_fetcher.cc warnings, I also get a large 
number of strange warnings (not sure whether that's related):

[Mon Sep 23 12:35:21 2013] [error] [mod_pagespeed 1.4.26.4-3396 @338] 
ServerContext: 1 leaked_rewrite_drivers on destruction
[Mon Sep 23 12:35:23 2013] [warn] [mod_pagespeed  @352] 
[0923/123523:WARNING:queued_worker_pool.cc(430)] Canceling 3 functions on 
sequence Shutdown

Anyway to know for sure which URL is being fetched?

Original comment by zedrd...@gmail.com on 23 Sep 2013 at 4:59

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Summary was: serf_url_async_fetcher.cc using IP instead of domain name

Maks -- can we update the error messages to reflect the hostname?

Original comment by jmara...@google.com on 23 Sep 2013 at 7:39

  • Changed title: serf_url_async_fetcher.cc error messages using IP instead of domain name
@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Issue 779 has been merged into this issue.

Original comment by jmara...@google.com on 23 Sep 2013 at 7:48

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

As I have pointed out, there is definitely an issue with the paths used by 
modpagespeed: there are way too many (obviously legit) paths generating errors, 
for it not to be a domain error. 

The updated title seems to work on the assumption this is only a display 
issue...

Original comment by zedrd...@gmail.com on 26 Sep 2013 at 7:29

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

I can confirm this issue, full external IP of server is used in logs from 
"serf_url_async_fetcher.cc"

[Mon Nov 18 06:48:05 2013] [warn] [mod_pagespeed  @25756] 
[1118/064805:WARNING:serf_url_async_fetcher.cc(1173)] Fetch failed to start: 
http://12.34.56.78/wp-content/plugins/jetpack/_inc/jquery.jetpack-resize.js?ver=
2.5


Original comment by Marek.Se...@gmail.com on 18 Nov 2013 at 11:56

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Fixed in r4196

Original comment by morlov...@google.com on 28 Aug 2014 at 8:00

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Apr 6, 2015

Original comment by jmara...@google.com on 18 Sep 2014 at 4:28

  • Changed state: Fixed
  • Added labels: Milestone-v32, release-note
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment