Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Tracing RPM Operations on MX, M, T and ACX Series Routers

Tracing operations track all RPM operations and record them in a log file. The logged error descriptions provide detailed information to help you solve problems faster.

By default, no events are traced. If you include the traceoptions statement at the [edit services rpm] hierarchy level, the default tracing behavior is the following:

  • Important events are logged in a file called rmopd located in the /var/log directory.

  • When the log file reaches 128 kilobytes (KB), it is renamed rmopd.0, then rmopd.1, and so on, until there are three trace files. Then the oldest trace file (rmopd.2) is overwritten. (For more information about how log files are created, see the Junos OS System Log Messages Reference.)

  • Log files can be accessed only by the user who configures the tracing operation.

You can change this default behavior by using the traceoptions statements.

Configuring the RPM Log File Name

By default, the name of the file that records RPM trace output is rmopd. To specify a different file name:

Configuring the Number and Size of RPM Log Files

To configure the limits on the number and size of RPM trace files:

The number of files can be from 2 through 1000 files. The file size of each file can be from 10 KB through 1 gigabyte (GB).

For example, set the maximum file size to 2 MB, and the maximum number of files to 20 for a log file named rpmtrace:

When the rpmtrace file reaches 2 MB, it is renamed rpmtrace.0, and a new file called rpmtrace is created. When the new rpmtrace reaches 2 MB, rpmtrace.0 is renamed rpmtrace.1 and rpmtrace is renamed rpmtrace.0. This process repeats until there are 20 trace files. Then the oldest file (rpmtrace.19) is overwritten by rpmtrace.18.

Configuring Access to the Log File

By default, log files can be accessed only by the user who configures the tracing operation.

To specify that any user can read all log files:

To explicitly set the default behavior:

Configuring a Regular Expression for Lines to Be Logged

By default, the trace operation output includes all lines relevant to the logged events.

To refine the output by specifying a regular expression (regex) to be matched:

Configuring the Trace Operations

By default, if the traceoptions configuration is present, only important events are logged. You can configure the trace operations to be logged by including the following statements at the [edit services rpm traceoptions] hierarchy level:

Table 1 describes the meaning of the RPM tracing flags.

Table 1: RPM Tracing Flags



Default Setting


Trace all operations.



Trace configuration events.



Trace events related to catastrophic errors in daemon.



Trace IPC events.



Trace ppm events.



Trace statistics.