WAAE Web Server service fails to start after upgrade to 11.3.6 SP6
Article ID: 91689
Updated On:
Products
CA Workload Automation AE - Business Agents (AutoSys)
CA Workload Automation AE - Scheduler (AutoSys)
Workload Automation Agent
Issue/Introduction
The WAAE Web Server service does not start after the upgrade to 11.3.6 SP6 and there is no log (waae_webservices_wrapper.log) generated in $AUTOUSER/out directory.
Environment
CA Workload Automation AE 11.3.6 SP6 on Linux platforms.
Cause
The RUN_AS_USER parameter/variable in the /opt/CA/WorkloadAutomationAE/webserver/bin/waae_webserver.$AUTOSERV file was set to a different user than the user owning the /opt/CA/WorkloadAutomationAE/webserver directory, and the run as user does not have appropriate permissions on the /opt/CA/WorkloadAutomationAE/webserver/ directory.
For example:
The Webserver directory is owned by user "autosys_prd", however the RUN_AS_USER parameter in the /opt/CA/WorkloadAutomationAE/webserver/bin/waae_webserver.$AUTOSERV is set to "autosys"
# ls -ld /opt/CA/WorkloadAutomationAE/webserver/
drwxr-x---. 9 autosys_prd autosys_prd 183 Feb 26 01:18 /opt/CA/WorkloadAutomationAE/webserver/
#
# ls -l /opt/CA/WorkloadAutomationAE/webserver/
total 108
drwxr-x---. 3 autosys_prd autosys_prd 4096 Apr 16 00:36 bin
drwx------. 2 autosys_prd autosys_prd 4096 Feb 26 01:18 conf
drwxr-x---. 2 autosys_prd autosys_prd 4096 Mar 6 03:33 lib
-rw-r-----. 1 autosys_prd autosys_prd 57092 Nov 27 08:33 LICENSE
drwxr-x---. 2 autosys_prd autosys_prd 6 Feb 26 01:18 logs
-rw-r-----. 1 autosys_prd autosys_prd 1723 Nov 27 08:33 NOTICE
-r-xr-xr-x. 1 autosys_prd autosys_prd 9465 Mar 2 05:35 prewebremove.sh
-rw-r-----. 1 autosys_prd autosys_prd 7138 Nov 27 08:33 RELEASE-NOTES
-rw-r-----. 1 autosys_prd autosys_prd 16246 Nov 27 08:33 RUNNING.txt
drwxr-x---. 2 autosys_prd autosys_prd 30 Feb 26 01:18 temp
drwxr-x---. 2 autosys_prd autosys_prd 6 Feb 26 01:18 webapps
drwxr-x---. 2 autosys_prd autosys_prd 6 Feb 26 01:18 work
#
# cd /opt/CA/WorkloadAutomationAE/webserver/bin/
# grep ^RUN_AS_USER waae_webserver.ACE
RUN_AS_USER=autosys
For example:
The Webserver directory is owned by user "autosys_prd", however the RUN_AS_USER parameter in the /opt/CA/WorkloadAutomationAE/webserver/bin/waae_webserver.$AUTOSERV is set to "autosys"
# ls -ld /opt/CA/WorkloadAutomationAE/webserver/
drwxr-x---. 9 autosys_prd autosys_prd 183 Feb 26 01:18 /opt/CA/WorkloadAutomationAE/webserver/
#
# ls -l /opt/CA/WorkloadAutomationAE/webserver/
total 108
drwxr-x---. 3 autosys_prd autosys_prd 4096 Apr 16 00:36 bin
drwx------. 2 autosys_prd autosys_prd 4096 Feb 26 01:18 conf
drwxr-x---. 2 autosys_prd autosys_prd 4096 Mar 6 03:33 lib
-rw-r-----. 1 autosys_prd autosys_prd 57092 Nov 27 08:33 LICENSE
drwxr-x---. 2 autosys_prd autosys_prd 6 Feb 26 01:18 logs
-rw-r-----. 1 autosys_prd autosys_prd 1723 Nov 27 08:33 NOTICE
-r-xr-xr-x. 1 autosys_prd autosys_prd 9465 Mar 2 05:35 prewebremove.sh
-rw-r-----. 1 autosys_prd autosys_prd 7138 Nov 27 08:33 RELEASE-NOTES
-rw-r-----. 1 autosys_prd autosys_prd 16246 Nov 27 08:33 RUNNING.txt
drwxr-x---. 2 autosys_prd autosys_prd 30 Feb 26 01:18 temp
drwxr-x---. 2 autosys_prd autosys_prd 6 Feb 26 01:18 webapps
drwxr-x---. 2 autosys_prd autosys_prd 6 Feb 26 01:18 work
#
# cd /opt/CA/WorkloadAutomationAE/webserver/bin/
# grep ^RUN_AS_USER waae_webserver.ACE
RUN_AS_USER=autosys
Resolution
Edit the Web server start up script - /opt/CA/WorkloadAutomationAE/webserver/bin/waae_webserver.$AUTOSERV - and set the RUN_AS_USER parameter to the same user who owns the /opt/CA/WorkloadAutomationAE/webserver/ directory.
In the aforementioned example, we set the RUN_AS_USER parameter, like so:
RUN_AS_USER=autosys_prd
In the aforementioned example, we set the RUN_AS_USER parameter, like so:
RUN_AS_USER=autosys_prd
Additional Information
Excerpt from the /opt/CA/WorkloadAutomationAE/webserver/bin/waae_webserver.$AUTOSERV fie:
# If specified, the Wrapper will be run as the specified user.
# IMPORTANT - Make sure that the user has the required privileges to write
# the PID file and wrapper.log files. Failure to be able to write the log
# file will cause the Wrapper to exit without any way to write out an error
# message.
# NOTE - This will set the user which is used to run the Wrapper as well as
# the JVM and is not useful in situations where a privileged resource or
# port needs to be allocated prior to the user being changed.
#RUN_AS_USER=
# If specified, the Wrapper will be run as the specified user.
# IMPORTANT - Make sure that the user has the required privileges to write
# the PID file and wrapper.log files. Failure to be able to write the log
# file will cause the Wrapper to exit without any way to write out an error
# message.
# NOTE - This will set the user which is used to run the Wrapper as well as
# the JVM and is not useful in situations where a privileged resource or
# port needs to be allocated prior to the user being changed.
#RUN_AS_USER=
Feedback
Yes
No
Powered by
