M-series and MX-series Devices
Figure 4: Failed Update Job Information Dialog Box
38
that shows
and
lock Failed
MX-series device, NSM attempts to acquire an exclusive lock on the candidate
configuration so that the update can proceed. In this instance, the root user was updating
the configuration, probably from the CLI, preventing NSM from locking and successfully
updating the configuration.
In the Job Information dialog box, the update:
Successfully checked sanity
Unsuccessfully attempted to lock the configuration that was already locked by the
root user
At the end of the error message, there are some suggestions as to how to proceed. In
this particular case, the second solution,
appropriate action. From the CLI, the
used to forcibly log out the root user. The root user is represented by
indicates the user session using the specified management process identifier (PID). After
the root user is locked out, you can try to update the configuration again. NSM should
lock the configuration and continue successfully.
configuration database locked by: root
> request system logout pid xxxx
request system logout pid pid
. For an M-series or
, is the
command can be
, which
pid pid
Copyright © 2010, Juniper Networks, Inc.