PAM- Unexpected token END OF FILE at position 0 viewing the dashboard

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

After upgrading to PAM 4.1.3, the following error is observed in the dashboard for all PAM appliances except the primary site leader.

When checking the Tomcat logs, the error is present:

2023-03-16T11:09:23.425+0000 WARNING [TP6] com.ca.pam.RestAuthenticationFilter.doFilter RestAuthenticationFilter.doFilter T439 No Session in database for PHPSESSID f708de932bfa732749d65bfdce788c3d
2023-03-16T11:09:23.426+0000 WARNING [TP4] com.ca.pam.gk.connection.ServerConnection.requestService Server returned HTTP response code: 401 for URL: http://127.0.0.1:8000/cspm/rest/UISettingsUserPreferences/dateTimePatterns
2023-03-16T11:10:42.626+0000 WARNING [TP2] com.ca.pam.gk.connection.ServerConnection.requestService PHPSESSID=null, Server returned HTTP response code: 500 for URL: http://127.0.0.1:8000/serviceController.php
2023-03-16T11:10:42.626+0000 SEVERE [TP2] com.ca.pam.rest.DashboardService.get Call to Gatekeeper service controller failed: Unexpected token END OF FILE at position 0.

Environment

Privileged Access Manager 4.1.3

Cause

Cluster configuration with server names in FQDN format and ip addresses caused an issue with how PAM was resolving the individual node names.

Resolution

This problem is fixed in published hotfix 4.1.3.03. The documentation page includes installation instructions and a link to the PAM Solutions & Patches page, where the patch can be downloaded from.

Workaround w/o applying the hotfix: Configure your cluster with just the IP addresses.

 

Additional Information

In addition to the EOF error on the dashboard, the following error can occur when trying to view session recordings from appliances other than the primary leader.

PAM-UI-2106: Failed to run the precheck for session recording: communication failure