Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[MX] Commit fails with "error: remote commit-configuration failed on re1" message

0

0

Article ID: KB35514 KB Last Updated: 04 Mar 2020Version: 1.0
Summary:

This article explains that commit may fail on MX Series routers with the "error: remote commit-configuration failed on re1" error message when disk space is less on the Routing Engine and indicates that freeing disk space will resolve the problem.

 

Symptoms:

Commit is not successful as indicated by the following error message:

lab@MX# set system host-name R1

{MASTER}[edit]
lab@MX# commit
re0:
configuration check succeeds
re1:
error: could not open configuration database (juniper.data+)
re0:
error: remote commit-configuration failed on re1

The following log messages are also seen:

Jul 25 02:01:23.076 2019  MX kernel: %KERN-3: jsr_sdrl_setup_primary: Socket already has replication setup (state 0x1)
Jul 25 02:01:23.076 2019  MX kernel: %KERN-3: jsr_sdrl_pri_alloc: failed 17

Jul 25 02:08:02.857 2019  MX kernel: %KERN-3: pid 63755 (repd), uid 0 inumber 1767478 on /.mount: filesystem full
Jul 25 02:08:04.475 2019  MX kernel: %KERN-3: pid 63755 (repd), uid 0 inumber 1767462 on /.mount: filesystem full
Jul 25 02:08:05.689 2019  MX kernel: %KERN-3: pid 67126 (rcp), uid 0 inumber 2327533 on /.mount: filesystem full
Jul 25 02:08:08.935 2019  MX kernel: %KERN-3: pid 63755 (repd), uid 0 inumber 1767468 on /.mount: filesystem full
Jul 25 02:08:12.445 2019  MX kernel: %KERN-3: pid 63755 (repd), uid 0 inumber 1767462 on /.mount: filesystem full
Jul 25 02:08:12.605 2019  MX kernel: %KERN-3: pid 40716 (jdhcpd), uid 0 inumber 1845980 on /.mount: filesystem full

Because the filesystem is full, there will also be kernel synchronization issues between the two Routing Engines:

lab@MX> show task replication
        Stateful Replication: Enabled
        RE mode: Master
 
    Protocol                Synchronization Status
    BGP                     NotStarted

Jul 25 02:06:10.155 2019  MX ksyncd[4801]: %DAEMON-3-KSYNCD: resync error, issu_state[0], type ROUTE subtype 18 : Cannot allocate memory
Jul 25 02:06:10.155 2019  MX ksyncd[4801]: %DAEMON-3-KSYNCD: resync error, issu_state[0], type ROUTE subtype 18 : Cannot allocate memory‚Äč

 

Cause:

In this case, the backup Routing Engine has run out of memory due to which commit is failing.

>show system storage

Filesystem              Size       Used      Avail  Capacity   Mounted on

/dev/md0.uzip            21M        21M         0B      100%  /
devfs                   1.0K       1.0K         0B      100%  /dev
/dev/gpt/junos           19G        19G      -1.5G      109%  /.mount >>>>>

 

Solution:

To prevent commit from failing, perform the following:

  1. List the files by using the following command:

lab@MX> request system storage cleanup dry-run
  1. Identify any unwanted files and delete them by using the following command:

>file delete /<path>/file-name

When some disk space is freed, commit will be successful.

 

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search