ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Unable to install VNA as wildfly service failing to start

book

Article ID: 210478

calendar_today

Updated On:

Products

CA Virtual Network Assurance DX NetOps

Issue/Introduction

Attempting to install VNA fails during the later stages of installation when Wildfly fails to start as per the following:

...
Installing Wildfly
Setting up standalone.xml
Configuring Wildfly startup
Enable wildfly to run at system startup
Configuring Wildfly
Updated user 'admin' to file '/opt/CA/VNA/wildfly/standalone/configuration/mgmt-users.properties'
Updated user 'admin' to file '/opt/CA/VNA/wildfly/domain/configuration/mgmt-users.properties'
Added user 'app' to file '/opt/CA/VNA/wildfly/standalone/configuration/application-users.properties'
Added user 'app' to file '/opt/CA/VNA/wildfly/domain/configuration/application-users.properties'
Copying APM configuration files
Installing MySQL
Configuring MySQL startup
Note: Forwarding request to 'systemctl enable mysql.service'.
Initializing MySQL
 100
 100
Starting MySQL.Logging to '/opt/CA/MySql/data/GDNB51777020PM1.err'.
. SUCCESS!
Copying Liquibase
Executing Database Update (logLevel = severe)
/opt/CA/VNA/liquibase /data
Starting Liquibase at Fri, 26 Feb 2021 11:50:09 UTC (version 3.8.0 built at 2019-08-19 05:25:46)
Liquibase Community 3.8.0 by Datical
Liquibase: Update has been successful.
/data
ID Cache file (/opt/CA/VNA/data/ID_CACHE.dat) does not exist; skipping migration
Aggregator Cache file (/opt/CA/VNA/data/REMOTE_VNA_CACHE.dat) does not exist; skipping migration
CA_ROOT_DIR: /opt/CA
Starting wildfly (via systemctl):  Job for wildfly.service failed because the control process exited with error code. See "systemctl status wildfly.service" and "journalctl -xe" for details.
                                                           [FAILED]
Unable to start wildfly
A problem occurred during installation (install directory not deleted). Backing up to /data/CA_VNA_Install_bak

Wildfly service status shows:

# systemctl status wildfly.service
‚óŹ wildfly.service - LSB: WildFly Application Server
   Loaded: loaded (/etc/rc.d/init.d/wildfly; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2021-02-26 11:51:05 UTC; 9min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 10944 ExecStart=/etc/rc.d/init.d/wildfly start (code=exited, status=1/FAILURE)

Feb 26 11:50:33 GDNB51777020PM1 systemd[1]: Starting LSB: WildFly Application Server...
Feb 26 11:50:33 GDNB51777020PM1 runuser[10969]: pam_unix(runuser:session): session opened for user wildfly by (uid=0)
Feb 26 11:50:33 GDNB51777020PM1 runuser[10969]: pam_unix(runuser:session): session closed for user wildfly
Feb 26 11:51:05 GDNB51777020PM1 wildfly[10944]: Starting wildfly: [FAILED]
Feb 26 11:51:05 GDNB51777020PM1 wildfly[10944]: wildfly failed to start within the timeout allowed.
Feb 26 11:51:05 GDNB51777020PM1 systemd[1]: wildfly.service: control process exited, code=exited status=1
Feb 26 11:51:05 GDNB51777020PM1 systemd[1]: Failed to start LSB: WildFly Application Server.
Feb 26 11:51:05 GDNB51777020PM1 systemd[1]: Unit wildfly.service entered failed state.
Feb 26 11:51:05 GDNB51777020PM1 systemd[1]: wildfly.service failed.

Cause

Free memory available is less than minimum required

Environment

DX NetOps Virtual Network Assurance 20.2 or later

Resolution

Ensure that a minimum of 12 GB or more free Memory is available on the server

This will help the wildfly.service to start