- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
04-12-2017 03:03 AM
I have job stuck in queue . Tried clearing job,restart mgmt getting same error.
Server error : Timed out while getting config lock. Please try again.
04-12-2017 04:33 AM
This might be helpful
04-12-2017 01:14 PM
Did you forget to add something ?
04-12-2017 01:30 PM
Word "This" is a hyperlink 😉
04-12-2017 05:36 PM
Hi Inder,
From the CLI, please enter the following command and then start the commit. Log everything and attach/paste it here.
> tail follow yes mp-log ms.log
Regards,
Anurag
04-12-2017 11:09 PM
you can try #commit force from CLI
04-13-2017 12:55 AM
what version of PAN-OS are you on? may want to consider upgrading to a more recent version if you're running an older version
04-16-2017 08:25 PM
2017-04-17 13:14:05.384 +1000 client dagger reported op command was SUCCESSFUL
2017-04-17 13:15:00.588 +1000 Checking to purge appstatdb logtype
2017-04-17 13:17:22.007 +1000 Error: pan_cfg_engine_take_rwlock(pan_cfg_engine.c:675): CONFIG_LOCK: read lock TIMEDOUT for cmd: clear_job, req: <request cmd="op" cookie="1538422974869041" uid="502"><operations><clear><job><id>135</id></job></clear></operations></request>
2017-04-17 13:19:57.717 +1000 dnscfgmod: FQDN Refresh: Periodic TTL Expiry Refresh
2017-04-17 13:19:57.718 +1000 dnscfgmod: Main refresh function: (TTL Expiry)
2017-04-17 13:19:57.718 +1000 dnscfgmod: No fqdns used in this config. Skip config push to device
2017-04-17 13:22:24.334 +1000 Getting authorization info for user inderjit succeeded.
2017-04-17 13:22:54.007 +1000 Error: pan_cfg_engine_take_rwlock(pan_cfg_engine.c:675): CONFIG_LOCK: read lock TIMEDOUT for cmd: get_motd_info_from_candidate_config, req: <auth-request username="inderjit" pid="30305" passwd="" ip-address="192.168.1.22"></auth-request>
2017-04-17 13:22:54.008 +1000 Error: _cfg_get_motd(pan_cfg_auth_handler.c:354): Timed out while getting config lock
2017-04-17 13:23:24.017 +1000 Error: pan_cfg_engine_take_rwlock(pan_cfg_engine.c:675): CONFIG_LOCK: read lock TIMEDOUT for cmd: show_system_setting_multivsys_handler, req: <request cmd="op" cookie="5961361060393522"><operations><show><system><setting><multi-vsys></multi-vsys></setting></system></show></operations></request>
04-17-2017 06:29 AM
The logs are not enough.
As stated, from the CLI, please enter the following command and then start the commit. Log everything and attach/paste it here.
> tail follow yes mp-log ms.log
You should see commit phase 0, phase 1, phase 2 in the logs. Paste everything till you see commit phase 2 completed.
Regards,
Anurag
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!