topic Re: Commit Error: failed to handle CONFIG_UPDATE_START Issue in General Topics

Commit Error: failed to handle CONFIG_UPDATE_START Issue

Retired Member — Sun, 29 Sep 2019 13:44:59 GMT

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

Re: Commit Error: failed to handle CONFIG_UPDATE_START Issue

jdelio — Thu, 31 Oct 2019 22:05:32 GMT

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.

Re: Commit Error: failed to handle CONFIG_UPDATE_START Issue

Rajendra-S — Tue, 09 Jan 2024 03:56:20 GMT

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.