The log file is 600 KB for only two seconds. It has 2600 lines and 1950 match the following URL:
It seems that you are running Open Office on several Clients, and they are attempting to update again and again and again. The Response code is 403, so MWG does not allow them to upgrade, but it seems that this does not prevent them from asking for updates.
I see a couple of options here:
- Browse to the URL mentioned above, you should see an MWG error page. Remove blocking the URL and allow the Clients to update. This may prevent them from asking again all the time
- Turn off automatic updates in Open Office for all installations
- Add a criteria to the log handler which causes the Access log to be only written if the URL does not match "*update.services.openoffice.org/ProductUpdateService*"
The easiest way is to prevent the Log Handler from writing the lines to the log. The bad thing is that the requests will still be there, but simply "hidden". I would personally try to find out why Open Office is flooding MWG with requests and try to turn it off, either by option 1 or 2.
I hope that helps.
I found two job running so another jobs must waiting. My customer have 100MB log every 5 minutes (over 1000 users). So web gateway must push logs to web reporter every 5 minutes. To import success for 100MB logs into web reporter need 15 days . So can not create reporters... Anyone here can advise me how to make this run smooth? Thanks!
I think something else must be going on... my general rule of thumb is 10,000 users should produce about 1GB of log data a day.
1000 users should not produce 100MB every 5 minutes...
I would advise opening an SR to investigate further to see if there is a log pushing problem. Include a feedback and a Web Reporter server.log file when you open the SR.
What versions are you running for (Web Reporter and Web Gateway)?
Hi Jon, Assume 100Mb/day so to import 100Mb into reporter need 17days (see image above). So it too long time to create reports when we need... . Thanks for advance!
Can you attach a server.log and a screenshot of Administration -> Options -> Performance -> Database Statistics
Warning: there might be sensitive data in the server.log. If you can use grep, I'm interested in seeing the lines that contain these classes.
One more useful thing, each physical appliance needs to be using a different log source. On the log sources, do you know which options are enabled for the processing tab?
Message was edited by: sroering on 8/2/11 7:55:26 AM CDTMessage was edited by: sroering on 8/2/11 7:56:17 AM CDT
i just make default settings. Now i reinstall and web reporter process 100Mb file on 2 minutes. Don't why before it process files with long time. Thanks!
And last question: my customers still have 100MB logs every 5 minutes on web gateway. I think logs include just text (100Mb text is too large). So could you show me how to configurate on web gateway that can reduce size logs smaller? Thanks!
can you state which log files are growing so much on your Web Gateway? Is it the access.log?
It would be interesting to understand what data you are logging for each request, maybe you are logging too much information. Can you let us know in detail what logs seem to be too large?
Can you provide us with a line of this log, so that we can see what data you are writing?