Troubleshooting Commit Scripts
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
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:
Make sure the commit script is present in the
The following error and warning messages appear:
error: invalid transient change
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:
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.
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.
By default, the maximum amount of memory allocated for the data segment portion of an executed script is half of the total available memory of the system, up to a maximum value of 128 MB. 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.