Skip to content
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.

LogLevel seems to be ignored #18

Closed
GoogleCodeExporter opened this issue Apr 6, 2015 · 25 comments
Closed

LogLevel seems to be ignored #18

GoogleCodeExporter opened this issue Apr 6, 2015 · 25 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Apache LogLevel set to alert
2. ErrorLog fills with info and warning messages

What is the expected output? What do you see instead?
I would expect the module logging to respect the LogLevel definition; instead 
if seems to log anything.



On what operating system?
Debian 2.6.26-2-amd64


Which version of Apache?
Server version: Apache/2.2.9 (Debian)
Server built:   Nov 14 2009 21:07:23

Which MPM?
prefork

Please provide any additional information below, especially a URL or an
HTML file that exhibits the problem.



Original issue reported on code.google.com by fxres...@gmail.com on 4 Nov 2010 at 6:19

@GoogleCodeExporter
Copy link
Author

Adding a few of these log entries:


[Thu Nov 04 19:21:26 2010] [warn] 
[1104/192126:WARNING:net/instaweb/util/google_message_handler.cc(32)] 
http://s2.bmedien.eu/4/images/buttons/collapse_40b.png: Invalid url relative to 
'http://www.html.de/'
[Thu Nov 04 19:21:26 2010] [notice] 
[1104/192126:INFO:net/instaweb/util/google_message_handler.cc(48)] 
http://www.html.de/vbseo.php:1: 47622us: 
HtmlParse::ApplyFilter:HtmlAttributeQuoteRemoval
[Thu Nov 04 19:21:26 2010] [notice] 
[1104/192126:INFO:net/instaweb/util/google_message_handler.cc(48)] 
http://www.html.de/vbseo.php:1: 47809us: HtmlParse::ApplyFilter:HtmlWriter
[Thu Nov 04 19:21:26 2010] [notice] 
[1104/192126:INFO:net/instaweb/util/google_message_handler.cc(48)] 
http://www.html.de/vbseo.php:1: 50323us: HtmlParse::FinishParse
[Thu Nov 04 19:21:26 2010] [warn] 
[1104/192126:WARNING:net/instaweb/util/google_message_handler.cc(32)] Fetching 
resource 
http://www.html.de/customavatars/ce.d522f0f7185919e7e893e3f6f30f5c37.avatar8427_
2,g.gif...
[Thu Nov 04 19:21:26 2010] [notice] 
[1104/192126:INFO:net/instaweb/util/google_message_handler.cc(29)] Fetch 
succeeded for 
http://www.html.de/customavatars/ce.d522f0f7185919e7e893e3f6f30f5c37.avatar8427_
2,g.gif, status=200

The logfile grew to 60Mb in 10minutes; I am going to disable the module for now 
but I can re-enable it for debugging any time.

Original comment by fxres...@gmail.com on 4 Nov 2010 at 6:22

@GoogleCodeExporter
Copy link
Author

I'm seeing the same behavior. Similar config. LogLevel set to "Error" and 
getting Warn and Notices filling up log files very rapidly. Had to disable most 
modules to prevent server from overloading on I/O. 

Original comment by skyhawk...@gmail.com on 4 Nov 2010 at 7:33

@GoogleCodeExporter
Copy link
Author

I had the same issue,

CentOS release 5.5; x86_64
Server version: Apache/2.2.8 (Unix)
MPM: prefork

Original comment by expert...@gmail.com on 4 Nov 2010 at 7:45

@GoogleCodeExporter
Copy link
Author

same here, confirmed. Loglevel is at "warn" but logs are spammed with INFO 
messages.

Apache/2.2.14 (Ubuntu) 
X-Mod-Pagespeed 0.9.0.0-128
mpm/prefork

Original comment by solariz...@gmail.com on 5 Nov 2010 at 9:47

@GoogleCodeExporter
Copy link
Author

Same here. More than 400 MB of error log file in less than 2 minutes. Server 
usage goes to 95 in top (never seen that without the box dying).

CentOS release 5.5; x86_64
Server version: Apache/2.2.16
PHP/5.2.14
prefork

Original comment by areyero...@gmail.com on 5 Nov 2010 at 12:53

@GoogleCodeExporter
Copy link
Author

We're looking into this, thanks for you patience, guys.

Original comment by sligocki@google.com on 5 Nov 2010 at 3:22

  • Added labels: Priority-Critical
  • Removed labels: Priority-Medium

@GoogleCodeExporter
Copy link
Author

Original comment by sligocki@google.com on 5 Nov 2010 at 6:16

@GoogleCodeExporter
Copy link
Author

http://code.google.com/p/modpagespeed/source/detail?r=146

Note: this fix has not been made available in binary form yet.  We will release 
new binary distributions incorporating these changes on Monday Nov 8.

Those building using the open-source instructions on 
http://code.google.com/p/modpagespeed/wiki/HowToBuild can try out these 
improvements immediately.

Original comment by jmara...@google.com on 5 Nov 2010 at 10:50

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

Did this go out today ?  Not sure how to tell if there was a new release posted.



Original comment by dob...@gmail.com on 8 Nov 2010 at 7:49

@GoogleCodeExporter
Copy link
Author

This hasn't been released yet.  The wheels are turning.  Will post when the 
release is out.

Original comment by jmara...@google.com on 8 Nov 2010 at 7:52

@GoogleCodeExporter
Copy link
Author

Fixed & verified with the new release. Thank you guys.

Original comment by fxres...@gmail.com on 9 Nov 2010 at 8:44

@GoogleCodeExporter
Copy link
Author

Your welcome, glad to make us respect user settings.

Original comment by sligocki@google.com on 9 Nov 2010 at 3:41

@GoogleCodeExporter
Copy link
Author

mod-pagespeed-beta 0.9.8.1-r215
VineLinux x64 5.1
Apache/2.2.16 (Unix) mod_ssl/2.2.16 OpenSSL/0.9.8k DAV/2 PHP/5.3.3

confirm the same problem.

Original comment by teama....@gmail.com on 19 Nov 2010 at 1:41

@GoogleCodeExporter
Copy link
Author

Teama -- you are still seeing messages in your error_log that should not be 
there, based on the log level?   Can you paste one of them into this bug?

Original comment by jmara...@google.com on 19 Nov 2010 at 1:56

@GoogleCodeExporter
Copy link
Author

Sorry for lack of information.
LogLevel was "warn", but "notice" was written into the "error_log"
<httpd.conf>
LogLevel warn

<Error_log>
3774 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 
7307us: HtmlParse::ApplyFilter:Javascript
3775 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 
Found script with src https://***
3776 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 
Found script with src ****.js
3777 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/apache/serf_url_async_fetcher.cc(632)] 
Initiating async fetch for http://****  /****.js
3778 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(29)] http://** 
Couldn't fetch resource getdata.js to rewrite.
3779 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 
7776us: HtmlParse::SanityCheck
3780 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 
7918us: HtmlParse::CoalesceAdjacentCharactersNodes
3781 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 
7975us: HtmlParse::ApplyFilter:InlineCss




Original comment by teama....@gmail.com on 20 Nov 2010 at 8:13

@GoogleCodeExporter
Copy link
Author

Teams.Ken: please update to the latest release; binary or source

Original comment by jmara...@google.com on 20 Nov 2010 at 1:41

@GoogleCodeExporter
Copy link
Author

Thank you for your advise.
I apologise for mistake.
The cause is thing that I used an old rpm unpack modules.
I re-unpack latest release rpm and store it on folders, and confirmed this 
issue was resolved.

Original comment by teama....@gmail.com on 21 Nov 2010 at 9:42

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

bug in Apache 2.2.x Win32 (in 2.2.17 too)

pls reopen bug

Original comment by sowingsa...@gmail.com on 4 Dec 2010 at 2:11

@GoogleCodeExporter
Copy link
Author

Win32 version has been moved to bug 132. Please let us know if this is an issue 
for other platforms as well.

Original comment by sligocki@google.com on 4 Dec 2010 at 6:11

@GoogleCodeExporter
Copy link
Author

Hi All,

Is this already fixed? In what version of Apache? 
COz I am also having problems with this. Loglevel is set to warn but
[notices] and all are still showing in error.log

Regards,
Cerebro911

Original comment by c.biton...@gmail.com on 5 Dec 2011 at 1:52

@GoogleCodeExporter
Copy link
Author

Can you paste a fragment from your error log?  This was fixed quite some time 
ago, probably in mod_pagespeed 0.9.11.*.

I'm not I understand the comment about the apache version; apache is versioned 
separately from mod_pagespeed and this bug is mod_pagespeed-specific.

Original comment by jmara...@google.com on 5 Dec 2011 at 1:59

@GoogleCodeExporter
Copy link
Author

Hi,

Sorry newbie here.
Oh I thought it is an apache bug.

My issue is something like this:
Sorry for lack of information.
LogLevel was "warn", but "notice" was written into the "error_log"
<httpd.conf>
LogLevel warn

<Error_log>
3774 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 
7307us: HtmlParse::ApplyFilter:Javascript
3775 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 
Found script with src https://***
3776 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 
Found script with src ****.js
3777 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/apache/serf_url_async_fetcher.cc(632)] 
Initiating async fetch for http://****  /****.js
3778 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(29)] http://** 
Couldn't fetch resource getdata.js to rewrite.
3779 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 
7776us: HtmlParse::SanityCheck
3780 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 
7918us: HtmlParse::CoalesceAdjacentCharactersNodes
3781 [Fri Nov 19 21:59:18 2010] [notice] 
[1119/215918:INFO:net/instaweb/util/google_message_handler.cc(48)] http://** 
7975us: HtmlParse::ApplyFilter:InlineCss

I got this from comment 15.This is exactly my issue. I set loglevel to warn but 
then [notices] and other log messages are showing in error.log. SO what do I 
need to do? Install mod_pagespeed?

Regards. 

Original comment by c.biton...@gmail.com on 5 Dec 2011 at 2:38

@GoogleCodeExporter
Copy link
Author

hi

and this is running in Windows 7 environment.

Thanks

Original comment by c.biton...@gmail.com on 5 Dec 2011 at 2:40

@GoogleCodeExporter
Copy link
Author

This is pretty interesting.  We have heard hints on the discussion forum of 
people running mod_pagespeed in Windows.  But we have never attempted to 
compile it on Windows ourselves.

But based on your message, someone did indeed once get this working, and 
evidently a copy of it is still floating around.  However, I can tell by the 
error log fragments that the version is very old & out of date.  It's quite 
possible that the version you are using pre-dates our bug fix for this issue, 
which occurred over a year ago.

Can you tell use the origin of your mod_pagespeed installation?

Original comment by jmara...@google.com on 5 Dec 2011 at 3:24

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant