Useful commands and log files

Back to Endpoint Check the Check Point services running:

cpwd_admin list

Stop and Start UEPM services:

uepm_stop

uepm_start

UEPM Logs Directory:

$UEPMDIR/logs

server_messages.log - Sync Errors / Client issues

This file is very useful when determining if management/policy servers are able to sync

It's also useful to check for GIU client issues (see enable debug mode) and also endpoint client connectivity issues.

apache_access.log – Client Connectivity issues

tail -f $UEPMDIR/logs/apache_access.log

This is useful when checking if the EPM service is working correctly.

Checking the HTTP status code clients get when accessing the server give a good indication of server health.

HTTP 200 – Working

-, 172.16.0.1 - - [02/Nov/2016:15:49:18 +0000] "POST /cp/connectionPoint/hb HTTP/1.1" 200 662 0/1110 "-" "-"
-, 172.16.0.2 - - [02/Nov/2016:15:49:18 +0000] "POST /cp/connectionPoint/hb HTTP/1.1" 200 666 0/1057 "-" "-"
-, 172.16.0.1 - - [02/Nov/2016:15:49:18 +0000] "GET /cp/connectionPoint/syncreq HTTP/1.1" 200 159 0/561 "-" "-"
-, 172.16.0.2 - - [02/Nov/2016:15:49:18 +0000] "GET /cp/connectionPoint/syncreq HTTP/1.1" 200 159 0/422 "-" "-"

HTTP 500 – Not working - Internal Server Error

-, 172.16.0.1 - - [02/Nov/2016:15:55:11 +0000] "POST /cp/connectionPoint/hb HTTP/1.1" 500 670 0/1120 "-" "-"
-, 172.16.0.2 - - [02/Nov/2016:15:55:11 +0000] "POST /cp/connectionPoint/hb HTTP/1.1" 500 670 0/1058 "-" "-"
-, 172.16.0.1 - - [02/Nov/2016:15:55:11 +0000] "GET /cp/connectionPoint/syncreq HTTP/1.1" 500 159 0/606 "-" "-"
-, 172.16.0.2 - - [02/Nov/2016:15:55:11 +0000] "GET /cp/connectionPoint/syncreq HTTP/1.1" 500 159 0/642 "-" "-"