The commands commit check or commit do not work on either routing engine after downgrade/upgrade of Junos OS on the machine that is running scripts.
commit check
commit
The following error may be seen:
re0: configuration check succeeds re1: /var/db/scripts/import/junos.xsl:failed to load external entity "/var/db/scripts/import/junos.xsl" error: compilation error: file /var/db/scripts/commit/check-ldp.slax line 9 element import error: xsl:import : unable to load /var/db/scripts/import/junos.xsl error: error reading stylesheet: check-ldp.slax error: 3 errors reported by commit scripts error: commit script failure re0: error: remote commit-configuration failed on re1
In Junos OS import, symlink was changed from /usr/libdata/cscript/import to /usr/libexec/scripts/import , but was backed out later from Junos OS 12.3 release.
/usr/libdata/cscript/import
/usr/libexec/scripts/import
If any router first loads any Junos OS image that does not have the reverted changes and then upgrades to any other image that has the reverted changes, it will be still pointing to /usr/libexec/scripts/import .
How to verify
m320-re0> file list /var/db/scripts detail /var/db/scripts: total 64 drwxrwS--- 2 root wheel 1024 May 1 04:39 commit/ drwxrwS--- 2 root wheel 20992 May 1 04:39 event/ lrwxr-xr-x 1 root wheel 27 Feb 24 01:00 import@ -> /usr/libexec/scripts/import drwxrwS--- 2 root wheel 512 Dec 13 02:23 lib/ drwxrwS--- 2 root wheel 512 May 1 04:39 op/ /code>
Manually remove import symlink as shown below:
import
>Start shell %cd /var/db/scripts %rm import %ln -sf /usr/libdata/cscript/import import
Commit your changes. Make sure you do the same on both routing engines if you see the problem on both routing engines.
If the problem continues, please contact JTAC.