Created on 01-05-2009 05:09 AM
miglogd 28 R 98.6 4.1it seems that the logging daemon is the evil guy here. Try re-checking all log related things, maybe disable it for a while. Ensure that you have not enabled ' loglocaldeny' (CLI commands:
config system global set loglocaldeny disable end-check if the following bug descriptions could apply to your situation: Description: The CPU usage of the FortiGate' s HTTP proxy (httpd) may go unexpectedly high after it handles more than 1024 requests to go to servers that are listening on port 8008 or 8010. Models Affected: All Bug ID: 73416 Status: Fixed in MR6 – Patch Release 3. Description: CPU usage by urlfilter daemon may unexpectedly rise to 100%, even when its not in use. Models Affected: All Bug ID: 76950 Status: Fixed in MR6 – Patch Release 3. - consider also reboot your box and upgrade to MR6 patch4 good luck
regards
/ Abel
Created on 01-06-2009 06:25 AM
regards
/ Abel
Created on 01-20-2009 06:33 AM
Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com
Created on 01-20-2009 06:42 AM
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1738 | |
1108 | |
752 | |
447 | |
240 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.