1.4.5.5. AppServer Cache for AppServer
1.4.5.5.13. Troubleshooting
Prev  Next
1.4.5.5.13. Troubleshooting
SymptomCauseSolution
SSL Certificate Error on StartupNo valid certificate in memoryImport the certificate or set certname correctly
HTTP 502 Bad GatewayBackend app server not reachableCheck the backend server, Test the network connection
HTTP 403 ForbiddenBackend Denies AccessCheck permissions on the backend
HTTP 401 UnauthorizedAuthentication RequiredCheck login credentials; only Basic and Bearer are supported
The server won't startPort already in useChange the port configuration or stop another service
Unexpected RestartWatchdog has detected a DEAD statusCheck thread pool utilization in the PRTG metrics
"Health check returned ILL"Crash Counter > 1Analyze crash dumps, check log files
Configuration is not appliedBlock name does not match the hostname Block [server:<hostname>] check
The cache isn't growingrfsdataupdate = false or rfsdataseparated = trueCheck Cache Warming Configuration

For troubleshooting, it is recommended that you start the server in console mode. All log messages are then displayed directly on the console and can be analyzed in real time:

pappcache.exe -e

If you encounter cache corruption or other cache-related issues, follow these steps:

  1. Stop the server.

  2. Check the cache index:

    pappcache.exe -verifyAndCleanIndex C:\Path\to\rfs2

  3. If serious problems occur, rebuild the index:

    pappcache.exe -rebuildIndex C:\Path\to\rfs2

  4. Restart the server.

Prev Up Next
1.4.5.5.12.4. Logging Home 1.4.5.5.14. Environment variables