topic Re: Commit failed in General Topics

Commit failed

indevis — Mon, 04 Apr 2011 12:21:25 GMT

Hi everybody,

Device: PA-2050

Firmware: 4.0.1

we are getting this error message when we try a commit.

What is happening when this appears and what can we do?

A rollback to a further config version is not helping.

Error message:

Management server failed to send ID request to client device

Commit failed

On Web-Gui and on CLI!

Reagrds

Christian

Re: Commit failed

indevis — Mon, 04 Apr 2011 14:30:39 GMT

We have solved the problem by restarting the device-server

> debug software restart device-server

Re: Commit failed

rroberts — Mon, 04 Apr 2011 14:40:06 GMT

I had the exact same issue last week so I spoke with support and they winded up just resetting the management and device servers.

I was never given a root cause or told how to prevent it from happening in the future.

Prior to having this issue I noticed a failed AV update job so it looked like that may have caused it.

Hope this helps

//rr

Re: Commit failed

ExclusiveNetworksGermany — Mon, 04 Apr 2011 15:01:44 GMT

There seems to be a Problem with the Memory Management

of the Process "mgmtsrvr"

Keep an eye on the Memory usage of mgmtsrv (show system resources)

and restart the Process if it exceeds >700meg

Regards

Marco

Re: Commit failed

samsk — Tue, 05 Apr 2011 02:25:44 GMT

Yes. I experienced the same issue.. Called PAN support and they said this is memory leaked issue.. Its a bug.

It will be fixed is PAN OS 4.0.3.. In the mean while, use back the stable version PAN OS 3.1.7 as advised by PAN support..

Re: Commit failed

srommens — Tue, 10 May 2011 09:29:24 GMT

Hi,

Do you by accident use Firefox 4?

I had exactly the same issue with F4. Using IE did not return any error anymore.

Make sure to revert the candidate config to the running config (or reboot) to remove 'the bad stuff', although I don't know exactly what the bad stuff was

Cheers,

Stijn.

Re: Commit failed

SkIKT — Mon, 27 Jun 2011 06:51:46 GMT

How do I restart the mgmtsrv process only?

EDIT: Found it in the CLI Reference Guide

admin@PA-500> debug software restart management-server

Re: Commit failed

paulhambleton — Tue, 12 Jul 2011 13:44:13 GMT

Will the debug software restart management-server command affect traffic flowing through the Palo Alto?

Thanks

Paul

Re: Commit failed

rroberts — Tue, 12 Jul 2011 14:03:03 GMT

Restarting the management server process will not affect user traffic at all.

Re: Commit failed

paulhambleton — Wed, 13 Jul 2011 07:15:54 GMT

Thanks for the response

Will restarting the device-server impact user traffic?

Re: Commit failed

nrice — Wed, 13 Jul 2011 15:44:38 GMT

No, restarting the device server won't impact traffic.

Re: Commit failed

paulhambleton — Thu, 14 Jul 2011 06:46:21 GMT

Thanks. Executing the following commands fixed it for me also

debug software restart management-server

debug software restart device-server

This is the 2nd bug I have found in 4.0.1, does anybody know if this is fixed in 4.0.2?

Re: Commit failed

ExclusiveNetworksGermany — Thu, 14 Jul 2011 07:25:25 GMT

i suggest to take a look in the release notes

There are more than 50 Bugs fixed between 4.0.1 and 4.0.3

Regards

Marco

Re: Commit failed

imperva — Sat, 29 Oct 2011 04:14:32 GMT

'debug software restart device-server' fixed it for me on PA500 with 4.0.5 installed.

Re: Commit failed

santonic — Tue, 22 Jan 2013 09:44:39 GMT

Can someone please clarify what exactly gets restarted in each of the following 2 cases:

- debug software restart management-server

- debug software restart device-server

Not much info about those commands in admin or CLI guide.

Re: Commit failed

mikand — Tue, 22 Jan 2013 20:07:25 GMT

The quickref over at https://live.paloaltonetworks.com/docs/DOC-4254 says:

Monitor Management or Device Server

Display management server messages for commit failures, updates, licenses, link status, policy details, etc.

show system resources follow

tail follow yes mp-log ms.log

Display device server message for commit failures, updates, licenses, link status, policy details, etc.

tail follow yes mp-log devsrv.log

Unfortently it doesnt tell you the difference between the two, however until someone from PA clears this out you should be able to see some stuff comparing: