This article provides an example of how to clear a pending commit.
A user wants to edit the configuration and commit applied changes in the configuration, but the system rejects the changes as well as the commit due to a pending commit ( 'commit at ' command). The following message is displayed:
'commit at
[edit]user# commiterror: Another commit is pending
If you need to make any changes before the scheduled commit, you can use the command clear system commit .
clear system commit
The example below shows how a commit can cause problems and how to clear any pending commits:
'commit at'
user> configure Entering configuration mode [edit] user# show system login message message " \n\n ********** test ********** \n\n"; [edit] user# commit at "2006-12-31 23:59:59" configuration check succeeds commit at will be executed at 2006-12-31 23:59:59 CET The configuration has been changed but not committed Exiting configuration mode
user> configure Entering configuration mode Users currently editing the configuration: user terminal d0 (pid 15099) on since 2006-07-27 09:23:28 CEST commit-at The configuration has been changed but not committed [edit] user# set firewall family inet filter urgent term 1 then accept error: configuration database locked by: user terminal d0 (pid 15099) on since 2006-07-27 09:23:28 CEST, idle 00:00:38 commit at error: configuration database locked by: user terminal d0 (pid 15099) on since 2006-07-27 09:23:28 CEST, idle 00:00:38 commit at [edit] user# commit error: Another commit is pending
[edit] user# run clear system commit Pending commit cleared [edit] user# set firewall family inet filter urgent term 1 then accept [edit] user# set interfaces lo0 unit 0 family inet filter input urgent [edit] user# commit commit complete
2023-03-31: Article reviewed for accuracy, no changes required.2020-06-30: Removed J-Series reference.2019-07-06: Minor, non-technical edits.