Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[EOL/EOE] On Junos device, IDP policy load fails with the error "Previous commit is in progress"

0

0

Article ID: KB16548 KB Last Updated: 29 Oct 2020Version: 2.0
Summary:

Note: A product listed in this article has either reached hardware End of Life (EOL) OR software End of Engineering (EOE).  Refer to End of Life Products & Milestones for the EOL, EOE, and End of Support (EOS) dates.


 

Performing a "device update" operation from NSM to a Junos device with the IDP feature can end with the error message "Previous commit is in progress".  This article explains why this happen and how to avoid it.

 

Symptoms:
IDP policy load fails on Junos with error "Previous commit is in progress".

The error message displayed in NSM Job Manager is similar to the following:
 
Error Text:
      Update fails UpdateDevice Results
sanityCheckCmd Success.
lock Success.
GenerateEditConfig Success.
validate Success.
confirmedCommit Success.
commit Failed .
<?xml version="1.0" encoding="UTF-8"?>
     <rpc-reply message-id="1" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" 
     xmlns:junos="http://xml.juniper.net/junos/9.6R2/junos" xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0">
        <rpc-error>
          <error-severity>error</error-severity>
          <source-daemon>
idpd
          </source-daemon>
          <error-path>
[edit security]
</error-path>
<error-info>
<bad-element>
idp
</bad-element>
</error-info>
<error-message>
Previous commit is in progress.
</error-message>
</rpc-error>
<rpc-error>
            <error-severity>error</error-severity>
      <error-message>
configuration check-out failed
      </error-message>
     </rpc-error>
</rpc-reply>


unlock  Success .


Solution:
This can happen if a background commit operation is still in progress.

Even though the CLI completes the commit operation with the message "Commit complete", the IDP policy compilation and installation still goes on in the background.  Also when the IDP daemon is started a commit automatically begins in the background.

In case of large policies, this may take few minute.  Any effort to commit another configuration will fail, since only one commit at a time can take place.

To resolve the issue, try the IDP policy update after sometime to verify that it succeeds.
 
 


 
Modification History:

2020-10-29: NSM is EOL and support on SRX is stopped after 15.1; content is still relevant so can be archived

 

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search