p4 monitor

Display Perforce process information; control long-running tasks.

Syntax

p4 [g-opts] monitor show [-a -l -e -L -s R | T | P | B | F | I ]
p4 [g-opts] monitor terminate id
p4 [g-opts] monitor clear [id | all]
p4 [g-opts] monitor pause id
p4 [g-opts] monitor resume id

Description

p4 monitor allows a system administrator to observe and control Helix Core-related processes running on a Helix server machine. Processes are tracked using a dedicated table that is constantly updated; this has a minor impact on server performance.

To use p4 monitor, you must enable monitoring on the Perforce service by setting the monitor configurable with p4 configure. You control process monitoring by setting the monitor configurable to one of the following values:

Changes to the monitor configurable affect all new p4 processes that connect to the server; restarting the server is not required.

Command syntax variants provide the following alternatives:

Output format

Each line of p4 monitor output consists of the following fields:

pidstatusownerhh:mm:sscommand [args]

pid

The process ID under Unix (or thread ID under Windows)

status

R, T, P, B, F, or I, depending on whether the process is Running, marked for Termination, Paused, Background, Finish or Idle.

Finish and Background occur only in replica servers.

owner

The Helix Core user name of the user who invoked the command.

hh:mm:ss

The time elapsed since the command was called.

command [args]

The command and arguments as received by the Perforce service.

For example, consider the following output to the p4 monitor show -L command, which displays information about locked files:

8764 R user 00:00:00 edit
      [server.locks/clients/88,d/ws4(W),db.locks(R),db.rev(R)]
8766 R user 00:00:00 edit
      [server.locks/clients/89,d/ws5(W),db.locks(R),db.rev(R)]
8768 R user 00:00:00 monitor

Following pid, status, owner, and time information, this shows two edit commands that have various files locked, including the client workspace lock in exclusive mode for the workspaces ws4 and ws5, and db.locks and db.rev tables in read-only mode.

If you have enabled idle process monitoring (by setting the monitor configurable to 2), idle processes appear with a status of R, but with a command of IDLE.

Some commands (for instance, p4 submit) invoke multiple processes. For example, dm_CommitSubmit or dm_SubmitChange may appear in the output of p4 monitor as two separate phases of the p4 submit command.

Getting pull thread information for replicas

If you are running a replica with monitoring enabled and you have not configured the monitor table to be disk-resident, you can run the following command to get more precise information about what pull threads are doing. (Remember to set monitor.lsof).

$ p4 monitor show -sB -la -L

Command output would look like this:

31701 B uservice-edge3 00:07:24 pull sleeping 1000 ms
    [server.locks/replica/49,d/pull(W)]

Options

You must be an operator or have super access to use the following options.

-a

Show all arguments associated with the process (for example, edit file.c, or sync -f //depot/src/...).

Helix Core user names are truncated to 10 characters, and each line is limited to a total of 80 characters of output.

Requires that the user be an operator or have super access.

-e

Show environment information including invoking Helix Core application (if known), host IP address, and workspace name.

Requires that the user be an operator or have super access.

-l

Show all arguments in long form; that is, without truncating user names or the list of command line arguments.

Requires that the user be an operator or have super access.

-L

Show information about locked files. The information is collected only for the duration of the p4 monitor command, and is not persisted.

Requires that the user be an operator or have super access.

Pre-requisites for using this option vary with the platform on which the server is running.

  • On Unix platforms, you must set the monitor.lsof configurable to the following value:

    $ path/lsof -F pln

    The value for path varies with the version of Unix you are using. For example, /usr/bin/lsof.

    There are circumstances in which monitor.lsof might not work for you: your Linux machine does not support lsof, the version of lsof might not work with the Helix server, or the administrator might not be willing to run the lsof command for security reasons. If this is the case, you can still get information about locked files by setting the monitor configurable, described next.

  • On non-Unix platforms or if monitor.lsof cannot be used, you must set the monitor configurable to 5, 10, or 25:

    5: monitor both active commands and idle connections, including a list of the files locked by the command for more than one second.

    10: monitor both active commands and idle connections, including a list of the files locked by the command for more than one second, with lock wait times included in the lock information.

    25: monitor both active commands and idle connections, including a list of the files locked by the command for any duration, with lock wait times included in the lock information.

    Using the monitor level to display information about locked files has a non-trivial impact on performance; the monitor.lsof option is preferred for Unix platforms.

You can use the -z tag option with this option. In that case, the p4 monitor show command will return one lockinfo tag for each file that the process has locked.

-s status

Restrict the display to processes in the Running, Terminated, Paused, Background, Finish, or Idle states.

Requires that the user be an operator or have super access.

g-opts

See Global Options.

Usage Notes

Can File Arguments Use Revision Specifier? Can File Arguments Use Revision Range? Minimal Access Level Required

No

No

list, super

Examples

p4 monitor show

Show Helix Core process information (commands only). Requires list access only.

p4 monitor show -l

Show arguments and commands, without limits on line length. Requires super access.

p4 monitor show -a

Show arguments and commands, limited to 80 characters per line of output. Requires super access.

p4 monitor terminate 123

Instruct the Perforce service to mark process 123 for termination. Requires super access.

p4 monitor clear all

Clears the monitor table of all entries. Requires super access.

Related Commands

To turn on monitoring

p4 configure set monitor=1

To turn off monitoring

p4 configure set monitor=0