Hello at all.
I got a problem with WebGateway 7.3.2.4.0, Build 16508.
Since a time I cannot define the Web-Gateways writes URLFilter-logs in the partition ( /opt ) and brings this partition to an overflow. The files are written every 10 minutes but did not get deleted after a time. Those files are really big, so I have to delete them by hand every 14 days.
Can anyone tell me where to configure this files in the way I can do in "Policy > settings" or " Troubleshooting > Log File Manager" ?
Thanks a lot for your answers
Michael
Solved! Go to Solution.
Okay... somewhere you have turned on some debug log which should not be enabled 🙂
Can you please look at
Policy -> Settings -> URL Filter -> <any setting> -> Advanced Settings -> Logging
Logging should not be enabled here, see here:
Then go to Configuration -> GTI URL Feedback -> Advanced Settings
Make sure no logging is enabled there.
I am not sure which settings exactly is writing those files, but I assume its maybe one of these two 🙂
Best,
Andre
Hello,
can you tell me the exact path and name the logs are written to?
Best,
Andre
Hi Andre,
thank you for your posting.
The path is "/opt/mwg/log/debug"... and there I found hundreds of URLFilterxxx.log.gz. The "xxx" means the date and time, each file is about 15 to 16 MB, per day 61 files, and that as I can remember from first of January.
Greetings from Wuppertal
Michael
Okay... somewhere you have turned on some debug log which should not be enabled 🙂
Can you please look at
Policy -> Settings -> URL Filter -> <any setting> -> Advanced Settings -> Logging
Logging should not be enabled here, see here:
Then go to Configuration -> GTI URL Feedback -> Advanced Settings
Make sure no logging is enabled there.
I am not sure which settings exactly is writing those files, but I assume its maybe one of these two 🙂
Best,
Andre
Hi Andre,
again you are my hero for today!!!
As shown in your screenshot there was a marking for enable the logging. But I promise that I did not mark this section. As I wrote starts the logging at the beginning of January, and we would know it, if there had be a reason to activate it.
If you got an idea, please write it, otherwise I will thank you very much for solving my "problem".
Greetings from Wuppertal
Michael
Hey Michael,
I cannot think of a real reason to activate the logging. The logging is very detailled and usually it should not be helpful for any user. Maybe it was activated accidentally or on request for a support case?
If you like you could have a look at the audit.log, maybe you find an entry who/when the log was enabled?
Best regards from (cold) PAderborn 🙂
Andre
Hi Andre,
the audit.log from beginning of January does not longer exist, so I cannot have a look at the entries.
But it does not matter. If this happens the next time I will notice it earlier.
Again a big "Thank you very much" to you!
Greeting from Wuppertal
Michael
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA