Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
miglogd eating CPU
On my 300C, the miglogd process is sucking up 80%+ of my CPU processes, and causing the unit to peg out at 80%+ all the time. My memory seems fine at about 25%.
When I issue the diag sys kill 11 [id-for-miglogd], it immediately shows up again (new process number, of course) running at 60% then 80%+. I have a call in to support, but thought I would ask here in case someone has seen this before.
I tried turning off Event Logging, but that didn' t change anything. We are using the web-based reporting service (that is, not a local FortiAnalyzer).
I have to reboot the the unit in order for the web GUI to come up (though, I' ve read that if I wait long enough, the gui should load).
Any thoughts/ideas greatly appreciated.
Specs:
Host Name FG300C [Change]
Serial Number FG300C
Operation Mode NAT [Change]
HA Status Standalone [Configure]
System Time Mon May 14 14:21:18 2012 [Change]
Firmware Version v4.0,build0521,120313 (MR3 Patch 6) [Update] [Details]
System Configuration Last Backup: Mon May 7 11:30:19 2012 [Backup] [Restore] [Revisions]
Current Administrator admin [Change Password] /1 in Total [Details]
Uptime 0 day(s) 6 hour(s) 32 min(s)
Virtual Domain Disabled [Enable]
4 REPLIES 4
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Perhaps try to format the logdisk ? (unit will reboot)
" execute formatlogdisk"
FCNSA, FCNSP
---
FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice, 60B/C/CX/D, 50B, 40C, 30B
FortiAnalyzer 100B, 100C
FortiMail 100,100C
FortiManager VM
FortiAuthenticator VM
FortiToken
FortiAP 220B/221B, 11C
FCNSA, FCNSP---FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice,
60B/C/CX/D, 50B, 40C, 30BFortiAnalyzer 100B, 100CFortiMail
100,100CFortiManager VMFortiAuthenticator VMFortiTokenFortiAP 220B/221B,
11C
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Okay, thanks! I will try that after hours today and see if I notice a difference.
I did see that my log is 90000+ screens long! Is there a way to clear the log after x days? That is, clear any entries older than 10 days?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
no, you cannot, however, there are some settings you can change:
FGT1234567890 # config log disk setting
FGT1234567890 (setting) # get
status : enable
ips-archive : enable
max-policy-packet-capture-size: 10
log-quota : 0
dlp-archive-quota : 0
report-quota : 0
upload : disable
upload-format : compact
drive-standby-time : 0
full-first-warning-threshold: 75
full-second-warning-threshold: 90
full-final-warning-threshold: 95
max-log-file-size : 100
storage : (null)
roll-schedule : daily
roll-time : 00:00
diskfull : overwrite
FCNSA, FCNSP
---
FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice, 60B/C/CX/D, 50B, 40C, 30B
FortiAnalyzer 100B, 100C
FortiMail 100,100C
FortiManager VM
FortiAuthenticator VM
FortiToken
FortiAP 220B/221B, 11C
FCNSA, FCNSP---FortiGate 200A/B, 224B, 110C, 100A/D, 80C/CM/Voice,
60B/C/CX/D, 50B, 40C, 30BFortiAnalyzer 100B, 100CFortiMail
100,100CFortiManager VMFortiAuthenticator VMFortiTokenFortiAP 220B/221B,
11C
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks! Once I can get my GUI to come up, I' ll compare notes and adjust. Hopefully, this will keep my CPU down to where it used to be - usable!
