Over 110% untilization

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Over 110% untilization

L4 Transporter

I am seeing my management plane spiking over 100% when do a preview and a commit, what could be causing that ? Also can a defrag be run or need to be run on the hard drive?

27 REPLIES 27

I will definitely try your suggestion and let you know what I see Thanks @BPry

Filesystem Size Used Avail Use% Mounted on
/dev/md3 3.8G 3.1G 509M 87% /
/dev/md5 7.6G 3.2G 4.0G 45% /opt/pancfg
/dev/md6 3.8G 2.6G 1019M 73% /opt/panrepo
tmpfs 2.0G 116M 1.9G 6% /dev/shm
cgroup_root 2.0G 0 2.0G 0% /cgroup
/dev/md8 198G 120G 69G 64% /opt/panlogs

 

It also showing me logged in twice on the CLI when I am only logged in once 

here are the processes when I am using the ACC

 

PID     USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
31021 root  20 0 953m 213m 6444 S 159.0 5.4 131:38.93 mgmtsrvr
4139 root 20 0 1272m 435m 7200 S 5.6 11.0 3977:01 logrcvr
26265 nobody 20 0 149m 26m 6032 S 0.7 0.7 13:39.07 appweb3
12839 root 20 0 12948 2352 1648 S 0.3 0.1 47:41.76 packet_path_pin
26411 nobody 20 0 114m 7648 4456 S 0.3 0.2 9:22.34 appweb3
1 ro


@Brandon_Wertz wrote:

Sorry about that I copied a URL from "page 2" apparently that doesn't work:

 

http://www.pcworld.com/article/2047513/fragging-wonderful-the-truth-about-defragging-your-ssd.html 


 

The URL had a '%C2%A0' suffixed at the end.  Drop that off and it will work.

Great that one works

From what I can tell I don't think my 5050 has SSD it looks like a regular hard drive. 

Forgive it this sound stupid, but can RAID be done on SSD? Thanks that was a very good spec sheet, these firewalls were purchased a year or so before I started this at my current job

I've never heard of a reason why a SSD drive couldn't be in a RAID, as long as the controller works with the SSD, I would think the drives would be capable of being used in a RAID config.

@jdprovine,

You can RAID an SSD perfectly fine. Your mgmtsvr process looks to be running at 159% in the output that you listed unless I'm misreading it, which would cause issues. Out of curiosity have you restarted device-server or mangement-server process sense you've started experiancing this?

 

@BPry That is correct the mangement CPU is 159% and I have seen it higher, and that is just by opening the ACC. I have not restarted the managment server process yet and I have records where I have been seeing this issue since Jan 2017, and even opened a TAC but they said there was nothing wrong

I would attempt to restart the management server by running 'debug software restart process device-server' and 'debug software restart process management-server'; since it's the mangement side of things you won't actually lose data flow but you will lose your management access to the device obviously, so I usually wait until everybody else is gone just incase something goes wrong. I find it weird that TAC would say that, unless you have an unsubstatial amount of logs ACC should never be causing that much of an additional load on your firewall. Certaintly ACC and reporting requires the load to go higher as it has to process the actual log files, but it shouldn't bring you that high unless you were already near 100% if not more just under a normal operational load.  

and by this information it does not show the log reciever as particularly high to me as for the volume of logs 

 

PID     USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
31021 root  20 0 953m 213m 6444 S 159.0 5.4 131:38.93 mgmtsrvr
4139 root 20 0 1272m 435m 7200 S  5.6 11.0 3977:01 logrcvr
26265 nobody 20 0 149m 26m 6032 S 0.7 0.7 13:39.07 appweb3
12839 root 20 0 12948 2352 1648 S 0.3 0.1 47:41.76 packet_path_pin
26411 nobody 20 0 114m 7648 4456 S 0.3 0.2 9:22.34 appweb3

 

Pluse the amount of logs that are listed on the disk 

 

Filesystem Size Used Avail Use% Mounted on
/dev/md3 3.8G 3.1G 519M 86% /
/dev/md5 7.6G 3.2G 4.0G 45% /opt/pancfg
/dev/md6 3.8G 2.6G 1019M 73% /opt/panrepo
tmpfs 2.0G 116M 1.9G 6% /dev/shm
cgroup_root 2.0G 0 2.0G 0% /cgroup
/dev/md8 198G 120G 69G 64% /opt/panlogs

 

Also that it occurs during the preview of a commit and the commit I am not sure may need to re-engage TAC. I have received a lot of good information from all of you with not real obvious problem

  • 6512 Views
  • 27 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!