Perform administrative operations on the server.
p4 [g-opts] admin checkpoint [-z | -Z] [prefix]
p4 [g-opts] admin journal [-z] [prefix]
p4 [g-opts] admin stop
p4 [g-opts] admin restart
p4 [g-opts] admin updatespecdepot [-a | -s type]
p4 [g-opts] admin resetpassword -a | -u user
p4 [g-opts] admin setldapusers
p4 [g-opts] admin end-journal
p4 admin command allows Helix Server users with the
super permission level to perform administrative tasks, even when working from a
different machine than the one running the shared
Helix Core Server service.
To stop the
p4 admin stop. This locks the database
to ensure that it is in a consistent state upon restart, and then shuts
To restart the service, use
p4 admin restart. The
database is locked, the service restarts, and some of the
p4 configure settings
that require a restart are applied.
When you look up the details of certain configurables under Configurables - alphabetical list, it might say:
After you change the value of this configurable, you must explicitly "stop" the server.
p4 admin restart is not sufficient.
For Windows, see Starting and stopping the Helix Server.
To take a checkpoint, use
p4 admin checkpoint
[prefix]. This is equivalent to logging in to the
server machine and taking a checkpoint with
[prefix]. A checkpoint is taken and the journal is
copied to a numbered file. If a prefix is specified, the files are
n is a sequence number. The MD5
checksum of the checkpoint is written to a separate file,
checkpoint., and the
lastCheckpointAction counter is updated to reflect
You must be connected to the server to issue the
You can store checkpoints and journals in the directory of your choice
by specifying the directory as part of the prefix. (Rotated journals are
stored in the
regardless of the directory in which the current journal is stored.) If
no prefix is specified, the default filenames
journal. are used.
p4 admin journal command is equivalent to
p4d -jj. For details, see Triggering on journal rotation in the
Helix Core Server Administrator Guide. The
files are created in the server root specified when the
service was started.
Checkpoints and journals use Unix epoch time. See the Timestamp information.
p4 admin updatespecdepot command causes the
service to archive stored forms into the spec depot.
- If the
-aoption is used, all of the form specification types are archived.
- If the
-soption option is used
- only those of the specified type are archived
- the other types are created in the spec depot
p4 admin resetpassword command forces specified
users with existing passwords to change their passwords before they can
run another command. This command works only for users whose
authMethod is set to
perforce. However, you can
use it in a mixed environment, that is an environment in which authentication is based both
on Helix Server and LDAP.
- To force password reset of all users with passwords (including the
superpermission who issued the command), use
p4 admin resetpassword -a.
- To force a single users to reset their password, use
p4 admin resetpassword -u user.
p4 admin setldapusers command allows you to
convert all existing non-super users to use LDAP authentication. The
command changes the
AuthMethod field in the user
specification for each user from
super users want to use LDAP
authentication, they must set their
See Global options.
|Can File Arguments Use Revision Specifier?||Can File Arguments Use Revision Range?||Minimal Access Level Required||Command Alias|
p4 admin checkpoint is equivalent to
To require all newly-created users with passwords to reset their passwords before invoking their first command, set the dm.user.resetpassword configurable:
p4 configure set dm.user.resetpassword=1
p4 admin resetpassword -aresets only the passwords of users who presently exist (and who have passwords).
p4 admin stopshuts down the Perforce service, you might see an error message indicating that the connection was closed unexpectedly. You can ignore this message.
- The spec depot must exist before running
p4 admin updatespecdepot.
- See the Helix Core Server Administrator Guide and Helix Core Server Administrator Guide.
Stop the shared service
Create a checkpoint named
Create a checkpoint named
In a failover scenario, this command:
||Rotates the active journal for an incremental backup between checkpoints.|
||This form of server restart is adequate for some, but not all, configurable changes to take effect. See the "Server Restart Required for Change to Take Effect?" column of the tables under Configurables - alphabetical list.|
To see the status of the last checkpoint