Webserver produces FAILED message at start as also unifstat doesn't show it is running

Products

• Autosys Workload Automation

Issue/Introduction

After upgrading to 12.1 SP1, the webserver start-up process displays a FAILED message, and the unifstat or ustat utilities indicate that the service is not running.
However, system-level checks confirm the webserver is operational: a ps -ef | grep java command shows the process running, netstat -tlnp | grep 9443 confirms a Java process is listening on the expected port, and a validation command (curl -k -u \<user\> https://\<hostname\>:9443/AEWS/machine) correctly returns the list of machines defined in Autosys.

The webserver is functional despite the conflicting status reports.

Environment

Autosys 12.x , 24.x
Linux

Cause

Corrupted $AUTOUSER/webserver/bin/waae_webserver.$AUTOSERV

Resolution

Follow below procedure to address the problem

1. Copied $AUTOUSER/webserver/bin/waae_webserver.$AUTOSERV file from a working environment.
2. Rename this file to correct instance name.
3. Edit the file and specify the correct instance name by replacing ??? . Total of 5 lines needs to adapted including 2 times the line PIDDIR

• • APP_NAME="waae_webserver.???"
  • WRAPPER_CONF="/opt/CA/WorkloadAutomationAE/autouser.???/webserver/conf/wrapper.conf"
  • PIDDIR="/opt/CA/WorkloadAutomationAE/autouser.???/webserver/bin"
  • PIDDIR="/opt/CA/WorkloadAutomationAE/autouser.???/webserver/bin"
  • WRAPPER_CONF="/opt/CA/WorkloadAutomationAE/autouser.???/webserver/conf/wrapper.conf"