Troubleshooting¶

Health Check¶

There are two simple ways to perform a basic health check on Helix Core:

p4d Process¶

The following commands will tell you if Helix Core is running:

[root@cloud]# pgrep -l p4d
8038 p4d_1_init
8039 p4d_base
8115 p4d_1

[root@cloud]# systemctl status p4d_1
● p4d_1.service - Helix Core Server Instance 1.
   Loaded: loaded (/etc/systemd/system/p4d_1.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2023-02-22 15:57:26 UTC; 6 days ago
     Docs: https://swarm.workshop.perforce.com/projects/perforce-software-sdp/view/main/doc/SDP_Guide.Unix.pdf
  Process: 7936 ExecStop=/p4/1/bin/p4d_1_init stop (code=exited, status=0/SUCCESS)
 Main PID: 8038 (p4d_1_init)
    Tasks: 3 (limit: 23343)
   Memory: 5.1M
   CGroup: /system.slice/p4d_1.service
           ├─8038 /bin/bash /p4/1/bin/p4d_1_init start
           ├─8039 /bin/bash /p4/common/bin/p4d_base 1 start
           └─8115 /p4/1/bin/p4d_1 -p ssl:1666 -r /p4/1/root -J /p4/1/logs/journal -L /p4/1/logs/log -q --pid-file

p4 info¶

p4 -p ssl:helix-core-public-ip-address:1666 trust -f y
p4 -p ssl:helix-core-public-ip-address:1666 info

You should expect to see output like the following:

$ p4 info
User name: perforce
Client name: bruno
Client host: bruno
Client unknown.
Current directory: /Users/bruno/
Peer address: 10.1.0.21:52302
Client address: 10.1.0.21
Server date: 2023/03/09 15:44:01 +0000 UTC
Server version: P4D/LINUX26X86_64/2022.2/2407422 (2023/02/14)
Server encryption: encrypted
Server cert expires: Feb 28 21:49:08 2033 GMT
ServerID: master.1
Server services: standard
Server license: none
Case Handling: sensitive

Deployment Logs¶

If there is an issue at deployment and the CloudFormation stack fails during creating the Helix Core VM review the output of the following command:

tail -100 /var/log/cloud-init-output.log

Helix Core Logs¶

All Helix Core logs can be found in /p4/1/logs/. To watch all client <-> service activity you can:

tail -f /p4/1/logs/log