commit failed with configurations invalid!

Reply
L4 Transporter

commit failed with configurations invalid!

Hi PA Community,

 

I got one issue with client where the commit is failing with details of only "Configurations Invalid" without any further details.

We wanted to change the management interface IP to a different one and the commit is not accepted, even the validation is failing.

I tried to made any other changes rather than mgm IP change and got the same result, commit failed.

 

I've checked the devsrv.log and found the following errors/warnings where I couldn't find any related article to explain:

 

mp        devsrv.log                         2016-12-08 15:07:27   2016-12-08 15:07:27.447 +0400 tdb compile flag is still up, abort thread wait 1 second
mp        devsrv.log                         2016-12-08 15:07:27   2016-12-08 15:07:27.452 +0400 Error:  cfgagent_modify_callback(pan_cfgagent.c:83): Modify string (sw.mgmt.runtime.clients.device.err) error: USER (1)
mp        devsrv.log                         2016-12-08 15:07:28   2016-12-08 15:07:28.451 +0400 tdb compile flag is still up, abort thread wait 1 second
mp        devsrv.log                         2016-12-08 15:07:29   2016-12-08 15:07:29.461 +0400 tdb compile flag is still up, abort thread wait 1 second
mp        devsrv.log                         2016-12-08 15:07:30   2016-12-08 15:07:30.471 +0400 tdb compile flag is still up, abort thread wait 1 second
mp        devsrv.log                         2016-12-08 15:07:31   2016-12-08 15:07:31.481 +0400 tdb compile flag is still up, abort thread wait 1 second
mp        devsrv.log                         2016-12-08 15:07:32   2016-12-08 15:07:32.491 +0400 tdb compile flag is still up, abort thread wait 1 second
mp        devsrv.log                         2016-12-08 15:07:33   2016-12-08 15:07:33.501 +0400 tdb compile flag is still up, abort thread wait 1 second
mp        devsrv.log                         2016-12-08 15:07:33   2016-12-08 15:07:33.938 +0400 End of parsing custom threat 
mp        devsrv.log                         2016-12-08 15:07:34   2016-12-08 15:07:34.511 +0400 tdb compile flag is still up, abort thread wait 1 second
mp        devsrv.log                         2016-12-08 15:07:35   2016-12-08 15:07:35.521 +0400 tdb compile flag is still up, abort thread wait 1 second
mp        devsrv.log                         2016-12-08 15:07:35   2016-12-08 15:07:35.990 +0400 [Cache] Load /opt/pancfg/mgmt/content//cache/70000//tdb.cache.ser-0 success
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.014 +0400 [TDB] stats virus pattern 815717 ,  104993 
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.014 +0400 [TDB] stats wildfire pattern 104748 ,  39999 
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.019 +0400 Warning:  pan_ctrl_compile_tdb(pan_config_handler_sysd.c:487): config commit aborted
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.020 +0400 TDB compilation done, return 0
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.148 +0400 Warning:  pan_ctrl_save_config(pan_config_handler_sysd.c:1686): config commit aborted
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.148 +0400 Error:  pan_ctrl_compile_cfg(pan_config_handler_sysd.c:1891): pan_ctrl_save_config() failed
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.149 +0400 Error:  pan_config_handler_sysd(pan_config_handler_sysd.c:2174): pan_ctrl_compile_cfg() failed
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.149 +0400 Error:  pan_ctrl_parse_config(pan_controller_proc.c:375): pan_config_handler_sysd() failed
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.345 +0400 Error:  pan_ctrl_config_phase1(pan_controller_proc.c:725): pan_ctrl_parse_config() failed
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.346 +0400 Config commit phase1 failed
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.352 +0400 Error:  cfgagent_modify_callback(pan_cfgagent.c:83): Modify string (sw.mgmt.runtime.clients.device.err) error: USER (1)
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.355 +0400 Error:  bool_modify_callback(pan_cfgagent.c:101): Modify boolean (sw.mgmt.runtime.clients.device.p1done) error USER (1)
mp        devsrv.log                         2016-12-08 15:07:36   2016-12-08 15:07:36.531 +0400 kill SIGUSR1 to pid 0

&

mp        devsrv.log                         2016-12-08 14:39:24   	}]2016-12-08 14:39:24.369 +0400 Config commit phase0 started
mp        devsrv.log                         2016-12-08 14:39:35   2016-12-08 14:39:35.827 +0400 Config commit phase0 done
mp        devsrv.log                         2016-12-08 14:40:02   2016-12-08 14:40:02.385 +0400 Config commit phase1 started
mp        devsrv.log                         2016-12-08 14:40:02   2016-12-08 14:40:02.410 +0400 flags 0x10002, content 0x0, not devsrvr only, not content only
mp        devsrv.log                         2016-12-08 14:40:02   2016-12-08 14:40:02.424 +0400 Get tdb_only from last committed config
mp        devsrv.log                         2016-12-08 14:40:02   2016-12-08 14:40:02.424 +0400 Get virus from last committed config
mp        devsrv.log                         2016-12-08 14:40:02   2016-12-08 14:40:02.427 +0400 Get wildfire from last committed config
mp        devsrv.log                         2016-12-08 14:40:02   2016-12-08 14:40:02.428 +0400 No TDB compilation needed
mp        devsrv.log                         2016-12-08 14:40:13   2016-12-08 14:40:13.304 +0400 [Cache] Load /opt/pancfg/mgmt/content//cache/70000//profile.cache.ser-0 success
mp        devsrv.log                         2016-12-08 14:40:21   2016-12-08 14:40:21.234 +0400 Config commit phase1 abort

Regards,

Sharief

Regards,
Sharief

Accepted Solutions
L4 Transporter

Hi Fozail,

 

Sorry forgot to update this thread.

 

The commit was successful after the FW reboot.

 

Regards,

Sharief

Regards,
Sharief

View solution in original post


All Replies
L7 Applicator

Hi Sharief

 

is that the only thing that changed ? (the mgmt IP)

 

can you try 'revert to running' and change the IP again ?

2016-12-12_09-43-17.png

Tom Piens - PANgurus.com
Like my answer? check out my book! amazon.com/dp/1789956374
L4 Transporter

Hi reaper,

 

I did and got the same commit failure, then tried to change the NTP servers IPs and still cannot commit.

Now I asked them to restart the managment plane and try again. Still waiting for a reply.

 

>debug software restart process management-server

 

>debug software restart process device-server

 

Regards,

Sharief

Regards,
Sharief
L4 Transporter

Hi, The client did the management plane restart and they still got the commit failure. >debug software restart process management-server Regards, Sharief

Regards,
Sharief
L7 Applicator

Hi Sharief

 

short of doing a full reboot, i'd recommend contacting TAC to have this investigated

 

usually a simple 'revert to running' does the trick

Tom Piens - PANgurus.com
Like my answer? check out my book! amazon.com/dp/1789956374
L4 Transporter

Hi reaper,

 

I opened a case with TAC. Will keep you updated.

 

Regards,

Sharief

 

 

Regards,
Sharief
L4 Transporter

TAC support restarted the device server & the management server and still the same error.

They request us to do a reboot.

 

Regards,

Sharief

Regards,
Sharief
L3 Networker

Hi Sharief, 

Can you just a give a try:- 

Click on "Revert to running configuration". 

Login to PA through CLI, navigate to configure mode and run the command "commit force". 

It might help you. 

Best Regards, 

Fozail

L4 Transporter

Hi Fozail,

 

Sorry forgot to update this thread.

 

The commit was successful after the FW reboot.

 

Regards,

Sharief

Regards,
Sharief

View solution in original post

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!