topic Server management cannot be restarted in General Topics

Server management cannot be restarted

Lutrija_Srbije — Fri, 13 Oct 2017 07:58:30 GMT

I cannot login to the web GUI, I receve error "Timed out while getting config lock. Please try again. ". I saw that it has to do with overloaded server managment plane so i tryed to restart it form CLI, ussing the comnad "debug software restart process management-server". The problem is that i get the same error in CLI "Server error : Timed out while getting config lock. Please try again.". In jobs list I see that ther is a Wildfire job that is active for 2 days and its on 54 percent whole time so i tryed to clear it, but i get the same error. PAN-OS version is 7.1.5 and model is PA-500.

Re: Server management cannot be restarted

reaper — Fri, 13 Oct 2017 08:34:26 GMT

hi @Lutrija_Srbije

I can suggest you try rebooting the firewall to regain access, but for proper troubleshooting you should reach out to support through your support partner

Re: Server management cannot be restarted

segap — Wed, 04 Nov 2020 08:38:38 GMT

First I have to put this command:

> request config-lock remove

and after that:

> debug software restart process management-server

If I just restart management plain it didn't help.

I hope it will helps to someone.

Re: Server management cannot be restarted

AlexandroDelAngel — Fri, 12 Feb 2021 02:40:34 GMT

That just happened to me on version 9.0.12 on a PA-5220, got a support case but recommendation was to reboot the device.

Re: Server management cannot be restarted

aleksandar.astardzhiev — Fri, 12 Feb 2021 07:51:04 GMT

Hi @AlexandroDelAngel ,

At the begining of the month we experiance the same on two of our firewalls running 9.0.11.

Our TAC support says that the problem is caused by EDL refresh job.

Issue: You reported issues with WebUI and SSH Access Issue. Yes, I have looked at the tech support file and I saw these, "mp ms.log 2021-02-01 10:00:02 2021-02-01 10:00:02.403 +0100 EDLRefresh job started processing. Dequeue time=2021/02/01 10:00:02 2021-02-01 10:00:02.777 +0100 EDL entry(0x7f49aed98000, 0x7f49f1450800, 0x7f49e6efc000 vsys1/Fab, 0, 1 ip) Entry not referenced by a rule mp ms.log 2021-02-01 10:00:02 2021-02-01 10:00:02.781 +0100 Error: pan_ebl_set_curl_proxy_info(pan_cfg_ebl.c:5930): failed to get proxy info mp ms.log 2021-02-01 10:00:02 2021-02-01 10:00:02.781 +0100 Error: pan_ebl_set_curl_proxy_info(pan_cfg_ebl.c:5930): failed to get proxy info mp ms.log 2021-02-01 10:00:02 2021-02-01 10:00:02.783 +0100 Error: pan_ebl_set_curl_proxy_info(pan_cfg_ebl.c:5930): failed to get proxy info." I saw that it matches a known issue, PAN-151808. EDL refresh job stuck when certificate profile used in the config for EDL server. Target Fix Version/s: 9.1.8, 10.0.5.

Note that this answer was provided at the begining of the month, back than bug ID PAN-151808 was not yet published publically. I can see it now in the addressed issues for the new 9.1.8, which was released yesterday.

Our support was not aware if this issue will be fixed in 9.0...

His only suggestion for workaround was to not use certificate profile for EDLs.

I am still not convinced that this is the actuall reason, because our firewalls are running 9.0.11 (upgraded from 9.0.9) since end of December. And we use EDL with cert profile for very long time. I was expecting to see such issue more often as our EDL refresh every hour.

On other hand we have two other firewalls also running 9.0.11, but they haven't experiance this issue and we don't use any EDL there...

Re: Server management cannot be restarted

Liviu_Bodeanu — Tue, 23 Mar 2021 15:49:22 GMT

Same issue is happening in my case, on a PA-3250 10.0.4.
I can see the same ELD errors, but I do not believe that this is related to the issue as I see them occurring in the past day prior to the incident as well.

Re: Server management cannot be restarted

Logesh — Wed, 14 Jul 2021 10:23:46 GMT

Hi,

Do you have any Kb article for this issue.

Re: Server management cannot be restarted

johnlinkowsky — Tue, 31 Aug 2021 16:51:07 GMT

Same issue on our PA5280 running v9.1.8. Cannot get "commit lock" - even though there are no other commit locks. Cannot do either of these commands, as it says "Timed out while getting config lock. Please try again."

> request config-lock remove

> debug software restart process management-server

There is a WF job hung at 54% for over an hour.

Seems the only way to clear this is to reboot the whole box.

Any other thoughts? Ideas?

Thanks,

John L.