HPE XP7 User Manual page 122

In such a case, the appropriate reason for the failure is logged in the paservicesstatus.log
file located in the <Install_drive>:\HPSS\paMonitor\logs folder. You must contact HPE
Support for further assistance along with the paservicesstatus.log file.
If the PA Tomcat service is manually stopped, the PA Monitor service does not take any action, which
includes not sending any email notifications. The following messages appear in the
jakarta_service_<yyyyMMdd>.log file located in the <hppss_home>\pa\tomcat\logs folder if
the PA Tomcat service is manually stopped. These messages do not appear if the service has abruptly
stopped:
<Date_time>[info] Stopping service...
<Date_time>[info] Service stopped...
<Date_time>[info] Run service finished...
<Date_time>[info] Procrun finished...
The following illustration depicts the above mentioned conditions:
NOTE:
• If you configure the SMTP parameters but do not specify a retry count, the PA Monitor service
does not attempt to restart the PA Tomcat service. Also, it does not dispatch any notification to
the intended recipients.
• If you do not configure the SMTP parameters but specify the retry count, the PA Monitor service
attempts to restart the PA Tomcat service. But, email notification is not dispatched as the email
recipients are not configured. In such a case, if the PA Tomcat service fails to restart, manually
check the status logged in the paservicesstatus.log file.
Notification for PA Database and Database Listener services
During the course of monitoring, if the PA service identifies that the PA Database and Database Listener
services are manually stopped or have abruptly stopped or failed to start, it notifies the intended email
recipients. However, it does not attempt to restart these services in case of failure. You must manually
122 PA Settings