Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
- play_arrow Junos Automation Scripts Overview
- play_arrow Junos XML Management Protocol and Junos XML API Overview
play_arrow Automation Scripting Using XSLT
- play_arrow XSLT Overview
- play_arrow Standard XPath and XSLT Functions Used in Automation Scripts
- play_arrow Standard XSLT Elements and Attributes Used in Automation Scripts
play_arrow Automation Scripting Using SLAX
- play_arrow SLAX Overview
- play_arrow SLAX Statements
- play_arrow The libslax Distribution for Automation Scripting
play_arrow Automation Scripting Using Python
- play_arrow Python Overview
play_arrow Automation Script Input
- play_arrow Global Parameters in Automation Scripts
  - Global Parameters and Variables in Junos OS Automation Scripts
play_arrow Extension Functions and Named Templates for Automation Scripts
play_arrow Manage Automation Scripts
- play_arrow Store and Enable Scripts
- play_arrow Configure a Remote Source for Scripts
- play_arrow Configure the Session Protocol for Scripts
  - Understanding the Session Protocol in Automation Scripts
  - Example: Specify the Session Protocol for a Connection within Scripts
- play_arrow Control Execution of Scripts
- play_arrow Synchronize Scripts Between Routing Engines
- play_arrow Convert Scripts Between SLAX and XSLT
  - Convert Scripts Between SLAX and XSLT
play_arrow Commit Scripts
- play_arrow Commit Scripts Overview
  - Commit Script Overview
  - How Commit Scripts Work
- play_arrow Create and Execute Commit Scripts
- play_arrow Generate a Custom Warning, Error, or System Log Message Using Commit Scripts
- play_arrow Generate Persistent or Transient Configuration Changes Using Commit Scripts
- play_arrow Create Custom Configuration Syntax with Commit Script Macros
- play_arrow Commit Script Examples
- play_arrow Junos XML and XSLT Tag Elements Used in Commit Scripts
- play_arrow Troubleshoot Commit Scripts
play_arrow Op Scripts
- play_arrow Op Scripts Overview
  - Op Script Overview
  - How Op Scripts Work
- play_arrow Create and Execute Op Scripts
- play_arrow Op Script Examples
- play_arrow Provision Services Using Service Template Automation
  - Service Template Automation Overview
  - Example: Configure Service Template Automation
- play_arrow Troubleshoot Op Scripts
  - Trace Op Script Processing on Devices Running Junos OS
  - Trace Script Processing on Devices Running Junos OS Evolved
play_arrow Event Policies and Event Scripts
play_arrow SNMP Scripts
- play_arrow SNMP Scripts Overview
  - SNMP Scripts Overview
- play_arrow Create and Execute SNMP Scripts
- play_arrow SNMP Script Example
  - Example: Process Unsupported OIDs with an SNMP Script
- play_arrow Troubleshoot SNMP Scripts
  - Trace SNMP Script Processing on Devices Running Junos OS
  - Trace Script Processing on Devices Running Junos OS Evolved
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

keyboard_arrow_right

Troubleshoot Commit Scripts

date_range 29-Mar-24

arrow_backward

arrow_forward

After you enable a commit script and issue a commit command, the commit script takes effect immediately.

Table 1 describes some common problems that might occur.

Table 1: Troubleshooting Commit Scripts
Problem	Solution
The output of the `commit check \| display detail` command does not reference the expected commit scripts.	Make sure you have enabled all the scripts by including the `file` statement for each one at the `[edit system scripts commit]` hierarchy level.
The output contains the error message: error: could not open commit script: /var/db/scripts/commit/`filename`: No such file or directory	Make sure the commit script is present in the /var/db/scripts/commit/ directory on your Junos device.
The following error and warning messages appear: error: invalid transient change generated by commit script: `filename` warning: 1 transient change was generated without [system scripts commit allow-transients]	One of your commit scripts contains instructions to generate a transient change, but you have not enabled transient changes. To rectify this problem, take one of the following actions: Include the `allow-transients` statement at the `[edit system scripts commit]` or the `[edit system scripts commit file filename]` hierarchy level. Remove the code that generates a transient change from the indicated script. Disable the script in the configuration.
An expected action does not occur. For example, a warning message does not appear even though the configuration contains the problem that is supposed to evoke the warning message.	Make sure you have enabled the script. Scripts are ignored if they are not enabled. To enable a script, include the `file filename` statement at the `[edit system scripts commit]` hierarchy level.
	Make sure you have included the required boilerplate in your script. For more information, see Required Boilerplate for Commit Scripts.
	Make sure that the XPath expressions in the script contain valid configuration statements expressed as Junos XML protocol tag elements. You can verify the XML hierarchy by issuing the `show configuration \| display xml` operational mode command.
	Make sure that the programming instructions in the script are referencing the correct context node. If you nest one instruction inside another, the outer instruction changes the context node, so the inner instruction must be relative to the outer. For example, the `<xsl:for-each>` instruction contains an XPath expression, which changes the context node. So the nested `<xsl:if>` instruction uses an XPath expression that is relative to the `interfaces/interface[starts-with(name, 't1-')]` XPath expression. <xsl:for-each select="interfaces/ interface[starts-with(name, 't1-')]"> <xsl:if test="not(description)">
The commit operation fails, and an error message in the system log file indicates: Process (`pid`,cscript) attempted to exceed RLIMIT_DATA	When committing a configuration that is inspected by one or more commit scripts, you might need to increase the amount of memory allocated to the commit scripts to accommodate the processing of large configurations. To increase the maximum memory allocated for each executed commit script, configure the `max-datasize size` statement with an appropriate memory limit in bytes at the `[edit system scripts commit]` hierarchy level before committing the configuration.

arrow_backward PREVIOUS Trace Script Processing on Devices Running Junos OS Evolved

NEXT arrow_forward Op Script Overview

footer-navigation