Troubleshoot P4 authentication

When trying to resolving a problem with P4 DAM authentication, start with running the following command as an admin user on the P4 DAM server:

hth-ctl tail

This command shows you an overview of what is going on in all P4 DAM log files. Following is a list of log file locations and descriptions.

Folder	Description
unicorn_backend	Unicorn logs for P4 DAM backend errors
mongodb	Mongo database logs for backend
redis	Redis storage logs used by backend
logrotate	logrotate logs for all log files
nginx	All HTTP requests
resque	Logs for background jobs
resque-scheduler	Logs for scheduled background jobs
streamer	Logs for streaming files from repositories

In addition, the following table might assist you in troubleshooting common issues experienced with P4 Server authentication.

	Issue	Root Cause/Resolution
For administrators	Sync with P4 Server seems to fail.	Ensure the P4 Server user is a valid user in P4 DAM. P4 DAM only supports user names up to 100 characters while P4 Server supports longer names. This gives an error during the sync operation that only appears in the log files. The P4 DAM UI does not indicate a problem.
	Authentication fails and the logs indicate Redis problems.	This might happen if Redis is configured to save snapshots but cannot persist on disk. You can either turn off snapshot saving or verify that Redis can save to the specified path.
	An administrator added a user in P4 Server, but the user is not available in the P4 DAM UI.	P4 DAM probably has not synced the data from P4 Server. By default, sync happens every 5 minutes.