Support Support Downloads Knowledge Base Apex Support Portal 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] Syslog message - "UI_EPHEMERAL_COMMIT: User 'root' has requested commit on 'junos-analytics' ephemeral database"

0

0

Article ID: KB37450 KB Last Updated: 02 Sep 2021Version: 1.0
Summary:

When the em0 interface flaps on the primary Routing Engine (RE) in MX Series routers, it can trigger a primary role switchover followed by an auto commit to sync the new primary RE's configuration to the previous primary RE. This event results in the "UI_EPHEMERAL_COMMIT: User 'root' has requested commit on 'junos-analytics' ephemeral database" syslog message.

This article clarifies that the message is for information purposes only and it can be safely ignored.

Symptoms:

If the em0 interface flaps on the primary RE, an RE role switchover occurs and the following log messages can be seen from the RE:

MX# run show log messages | match root | last

Aug 24 17:33:41.425  router-re0 mgd[14894]: UI_EPHEMERAL_COMMIT: User 'root' has requested commit on 'junos-analytics' ephemeral database
Aug 24 17:33:42.135  router-re0 mgd[14920]: UI_EPHEMERAL_COMMIT: User 'root' has requested commit on 'junos-analytics' ephemeral database
Aug 24 17:33:43.284  router-re0 mgd[14962]: UI_EPHEMERAL_COMMIT: User 'root' has requested commit on 'junos-analytics' ephemeral database
Aug 24 17:33:44.943  router-re0 mgd[15007]: UI_EPHEMERAL_COMMIT: User 'root' has requested commit on 'junos-analytics' ephemeral database
Cause:

This is expected behavior when the em0 interface flaps. The flap will trigger a primary role switchover on the RE followed by an automatic configuration sync from the new primary RE to the new backup RE.

Example

{MASTER}[edit]
MX # show logical-systems
Aug 24 17:33:07
r1   <<<  commit no-sync before em0 flap

{BACKUP}[edit]
MX # show logical-systems
Aug 24 17:32:56 <<<RE1 does not have such configuration.
 
MX > start shell
MX :~ # ifconfig em0 down
MX :~ # <<< This emulates em0 interface flap.
 
MX # run show log messages | match root | last
Aug 24 17:33:41.425  router-re0 mgd[14894]: UI_EPHEMERAL_COMMIT: User 'root' has requested commit on 'junos-analytics' ephemeral database
Aug 24 17:33:42.135  router-re0 mgd[14920]: UI_EPHEMERAL_COMMIT: User 'root' has requested commit on 'junos-analytics' ephemeral database
Aug 24 17:33:43.284  router-re0 mgd[14962]: UI_EPHEMERAL_COMMIT: User 'root' has requested commit on 'junos-analytics' ephemeral database
Aug 24 17:33:44.943  router-re0 mgd[15007]: UI_EPHEMERAL_COMMIT: User 'root' has requested commit on 'junos-analytics' ephemeral database <<< RE switchover happened and the above log messages can be seen. This indicates a commit sync from RE1(new primary RE) to RE0(new backup RE).
 
{BACKUP}[edit]
MX # show logical-systems | display set
Aug 24 17:34:55

{BACKUP}[edit]
MX # <<< After em0 flap and RE role switchover, RE1's configuration is synced to RE0. We do not see logical-system r1 anymore from RE0.
Solution:

This is expected behavior. The log messages are informational and only indicate the commit action after configuration sync between the two REs. No action is required.

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