Commit Error: failed to handle CONFIG_UPDATE_START Issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

Commit Error: failed to handle CONFIG_UPDATE_START Issue

L1 Bithead

Hi All,

 

I think  most of you had experienced this failure issue once in your worklife 🙂 🙂This error reason is mostly because config memory usage is too high.

>debug dataplane show cfg-memstat statistics

As we all know the number of custom url is limited and we will likely face this commit issue after this limit exceed. But we can not be aware whether the limit exceed unless this commit issue occured. Therefore this issue might become annoying to figure out. 

I would like to ask for your advice there is any method to detect early diagnosis before this limit exceed. Also do you know a way or command to clear config memory?

 

I believe this topic will be helpful to so many of you to overcome this issue if we can find out some solution 🙂🙂

 

Thanks

Regards

1 accepted solution

Accepted Solutions

L7 Applicator

There can be many causes to this, EDL's sometimes are the cause.. but you can always look at what the current config size.. and go from there.

 

the command "show system resources", can show you the memory usage. The Current config memory usage and last config memory usage.

 

 

LIVEcommunity team member
Stay Secure,
Joe
Don't forget to Like items if a post is helpful to you!

View solution in original post

2 REPLIES 2

L7 Applicator

There can be many causes to this, EDL's sometimes are the cause.. but you can always look at what the current config size.. and go from there.

 

the command "show system resources", can show you the memory usage. The Current config memory usage and last config memory usage.

 

 

LIVEcommunity team member
Stay Secure,
Joe
Don't forget to Like items if a post is helpful to you!

L1 Bithead

Hello guys it is a known issue as well fixed in 9.1.16, 10.1.9, and 10.2.4.
PAN Bug Id: PAN-201910.

 I hope this clarifies your doubts regarding this issue.

  • 1 accepted solution
  • 15130 Views
  • 2 replies
  • 1 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!