Skip to main content
NetApp Knowledge Base

WFA install or upgrade fails with message that server service could not be started

  1. Last updated
  2. Save as PDF
Views:
692
Visibility:
Public
Votes:
0
Category:
oncommand-workflow-automation-wfa
Specialty:
legacy
Last Updated:

Applies to

OnCommand Workflow Automation (WFA) 5.x
RHEL 7.x
CentOS 7.x

Issue

WFA install or upgrade to 5.x fails with an error that the WFA server service could not start. The console log from the install shows that pinging localhost  was unsuccessful.
 
The install logs are located in /var/log/wfa.
 
install.log
Apr 10 15:38:43:  Finished installing rpm package.
Apr 10 15:38:43:  Starting WFA services ...
Apr 10 15:38:43:  Starting WFA server service. This may take few minutes ...
Apr 10 15:38:56:  Could not start WFA server service successfully.
Apr 10 15:38:56:  Exiting installation...
 
console.log
Total number of wars : 4
Parameters of pingng jboss are host=localhost, port=443 and timeout=50.
Could not ping host machine on wfa port 443. JBOSS startup failed during wfa-server service startup.

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.