CPU is pinned
(2018-06-11)
It should be obvious which process is using all the CPU. Note the PID of the offending process.If it is sslvpn, it is reasonably safe to restart (although connected clients may get kicked off -- so List SSLVPN Users first!):If it isn't sslvpn, it may be safer to reboot the firewall.
Problem
CPU on Fortigate is maxed out for a long period of time (hours, days).Solution
Identify the process using the CPU:get system performance top
diag sys kill 11 $PID
Commentary
This problem is not uncommon on 5.4.x, especially 5.4.6.
no comments |
post comment
Virtual Dave Megaplex:
Home Page- This wiki's start page
- Send Feedback To Dave
Logged in Users: (1)
Recently Changed
nmap- Seconds Since Epoch to Local Time
- Link Monitor
- DH group to OAKLEY_GROUP table
- Fire Eater
- start
- FortiClient Error Codes
- Scan For Newly Added Disk
- dhparams Generation
- SSL Certificate Bundles
- ufw
- Grow A LVM Partition
- Creating Users
- whoami
- list databases
- DH Selection For IPsec VPNs
- 2023
- 2022
- 2019
- 2018
- 2017
- 2011
- 2010
- 2008
- 2001
- 2000
- 1999
- 1991
- Custom '77 Dodge Van
- Bone Shaker
Editing: snipsnap-help, Image Macro(Et auditum est, et idcirco ego nunc simulare)
This is a collection of techical information, much of it learned the hard way. Consider it a lab book or a /info directory. I doubt much of it will be of use to anyone else.