In this article we will discuss the following warning "changes cannot be committed while 'configure exclusive' is active" observed when user trying to modify the configuration using "configure private"
[email protected]> configure private
warning: changes cannot be committed while 'configure exclusive' is active
warning: uncommitted changes will be discarded on exit
Entering configuration mode
Users currently editing the configuration:
USER1 terminal pts/0 (pid 89635) on since 2025-04-17 03:14:14 EDT, idle 00:39:01
exclusive
USER1 terminal pts/0 (pid 90443) on since 2025-04-17 03:27:31 EDT, idle 00:25:44
You would notice the warning message as an active user is changing the configuration database with exclusive rights hence a user cannot make a private configuration change.
Using "configure exclusive" will also give an error for locked database by a user.
[email protected]> configure exclusive
error: configuration database locked by:
USER1 terminal pts/0 (pid 89635) on since 2025-04-17 03:14:14 EDT, idle 00:46:18
To fix this use "configure" and deactivate any event-option or system scripts and then attempt to commit changes using configure private.
Used "configure"
[email protected]> configure
initial (pid 91754) on since 2025-04-17 04:08:00 EDT, idle 00:06:26
The configuration has been changed but not committed
deactivate system scripts
deactivate event-options
[email protected]# show | compare
[edit system]
! inactive: scripts { ... }
[edit]
! inactive: event-options { ... }
[email protected]# commit check
re0:
configuration check succeeds
re1:
Now "configure private" should be working, upon changes made re-activate the deactivate event-options and system scripts as these scripts are actively polling the data with exclusive rights.