P4DEBUG

Set debug levels or configurables that affect Helix Core Server or proxies running as Windows services.

Usage Notes

Used by Client? Used by Server? Command-Line Alternative Can be set in P4CONFIG file?

No

Yes

None

No

Value if not Explicitly Set

Operating System Value

All

server=1 is the default setting.

Examples

See Using P4LOG in Helix Core Server Administrator Guide.

Notes

Important

  • Changes to P4DEBUG settings take effect when the server or proxy is restarted.

  • Changes to some configurables take effect when the server or proxy is restarted. See the "Server Restart Required for Change to Take Effect?" column of the table under Configurables - alphabetical list

To disable logging, set P4DEBUG to server=0.

The proxy does not set debugging by default.

For the proxy, the options can be set on the command line and in P4DEBUG.

Setting server debug levels on a Helix Server (p4d) by using P4DEBUG has no effect on the debug level of:

  • Helix Proxy (p4p) processes

  • downstream replicas or edge servers

Setting debug options

The best practice for setting debug options for the Helix Server on all platforms is to use p4 configure set and p4 configure unset. For example, p4 configure set server=3 and p4 configure unset server. These change the debug levels without requiring that the server be restarted.

Windows

Helix Server or proxies running as Windows services do not support setting debug levels or configurables on the command line used to start the service. However, administrators at Windows sites can use p4 set to set the debug levels or configurables with P4DEBUG.