Вы находитесь на странице: 1из 2

Problem Report

Number PR1415042

Title The user might not enter configure mode due to mgd is in lockf status

Release Note If "commit confirmed <timeout>" is executed, then issuing


another "commit" or "commit confirmed <timeout>" after around
the <timeout> minutes, in race condition, a rollback might be
hit. At last, it may cause the mgd process to enter and to stay
in lockf status. Thus, the user might not enter configure mode
anymore.

Severity Minor

Status Open

Last Modified 2019-04-09 04:13:31 EDT

Resolved In
Release junos
18.1R3-S4 x
18.2R3 x
18.3R2 x
18.4R2 x
16.2R3 x
17.4R3 x
19.1R2 x
19.2R1 x

Product J Series, M Series, T Series, MX-series, EX Series, SRX Series, QFX Series, NFX Series, PTX
Series

Functional Are software


a

Problem If "commit confirmed <timeout>" is executed, after around the


<timeout> minutes, issuing another "commit" or "commit confirmed
<timeout>", rollback might be hit in race condition. This issue
may cause the mgd process to enter and to stay in lockf status.
Hence, the user might not enter configure mode anymore.
For example, "commit confirmed 1" is executed, after around 1
minute 5 seconds, issuing another commit command, this issue may
be hit.

When this issue occurs, the following warning might be seen:


# commit confirmed will be rolled back in less than x minute

And later the mgd is not responding:


"Retry connection attempts ? [yes,no] (yes) could not open user
interface connection: management daemon not responding"

This issue can be identified through the following command:


user@device> show system processes extensive | match mgd
24945 root 20 0 734M 39684K select 2 0:00 0.00%
mgd
Problem Report

28956 root 52 0 737M 42580K lockf 1 0:00 0.00%


mgd <<<<<
25900 root 23 0 737M 40728K select 2 0:00 0.00%
mgd
25003 root 20 0 717M 8364K select 3 0:00 0.00%
mgd-api
32339 root 20 0 737M 40532K select 1 0:00 0.00%
mgd
32295 root 20 0 734M 40144K lockf 1 0:00 0.00%
mgd <<<<<

Triggers This issue might be seen if the following conditions are met:
* Command "commit confirmed " is executed
* The following up commit is issued at around the minute 5
seconds

Вам также может понравиться