| Description | This article describes the issue of being unable to obtain data from the app server after the restoration of a snapshot due to a failed upgrade (or any other reason). The article provides a step-by-step guide to resolving the issue by changing the permissions of the server.log file and re-deploying the App Server. |
| Scope | FortiSIEM v7.x+. |
| Solution |
The errors below are usually seen in /opt/phoenix/log/phoenix.log:
2026-01-21T22:30:53.096209-05:00 SupervisorHostname phMonitorSupervisor[12812]: [PH_HTTP_CLIENT_GET_DATA_FROM_CACHE_FAILED]:[eventSeverity]=PHL_ERROR,[procName]=phMonitorSupervisor,[fileName]=phHttpClient.cpp,[lineNumber]=1704,[errReason]=Cannot open HTTP cache file ,[phLogDetail]=Failed to get data from cache
This is likely due to the backend processes (Phoenix) not being able to communicate with the GlassFish Application Server.
To resolve the issue of being unable to obtain data from the app server after a failed upgrade, follow these steps:
tail -f /opt/glassfish/domains/domain1/logs/phoenix.log
ll /opt/glassfish/domains/domain1/logs/phoenix.log* ll /opt/glassfish/domains/domain1/logs/server.log*
-rw-rw-r-- 1 admin admin <-- For the .log files. -rwxr-xr-x 1 admin admin <-- For the .gz files.
chown -R admin:admin /opt/glassfish/domains/domain1/logs/ chmod 755 /opt/glassfish/domains/domain1/logs/server.log chmod 755 /opt/glassfish/domains/domain1/logs/phoenix.log chmod 664 /opt/glassfish/domains/domain1/logs/server.log chmod 664 /opt/glassfish/domains/domain1/logs/phoenix.log
su admin cd /opt/phoenix/deployment ./deploy-fresh.sh phoenix.ear |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2026 Fortinet, Inc. All Rights Reserved.