This article provides guidance on addressing commit script failure encountered while attempting to load a configuration to a new EX switch from a previously failed EX switch managed by the Mist Portal.
When attempting to commit the loaded configuration, an error message similar to the following may be displayed:
error: could not open commit script: /var/db/scripts/commit/mxoc_jet_app_optional_fix.slax: No such file or directory error: 1 error reported by commit scripts error: commit script failure
Identify the Issue:
The commit script failure is occurring due to the absence of the necessary script file on the new EX switch. This script file is related to the Mist Portal configuration.
Avoid Loading Event-Options and Mist Configurations:
To prevent encountering this issue, it's recommended to exclude configurations related to event-options and Mist Portal when loading the configuration onto the new EX switch. You can use the following command to identify and exclude these configurations:
show configuration | display set | match "event|mist"
This command filters the configuration to display only lines containing "event" or "mist," helping you identify configurations to exclude.
Manual Configuration Deletion:
If manually deleting the problematic configuration did not resolve the commit script failure, proceed with the following workaround.
1. Perform a Zeroize:
A zeroize operation resets the switch to its factory default settings. While this may seem drastic, it can effectively resolve the commit script failure issue. Please note that performing a zeroize will erase all configurations and settings on the switch, so ensure you have proper backups before proceeding.
2. Load Configuration Without Event-Options and Mist:
After performing the zeroize, load the configuration onto the switch without including event-options and Mist Portal configurations. This will help ensure a clean configuration without the problematic script reference.
By following these steps, you can successfully address the commit script failure issue that arises when loading a configuration to a new EX switch from a failed EX switch managed by the Mist Portal. Remember to exercise caution when performing a zeroize, and always have appropriate backups before making any significant changes to your network equipment.