wildfly won't start after clearing up drive space issue
search cancel

wildfly won't start after clearing up drive space issue

book

Article ID: 242182

calendar_today

Updated On:

Products

Virtual Network Assurance

Issue/Introduction

After resolving a drive space issue on the VNA server wildfly will not stops

The following messages are seen in the server.log

2022-05-19 10:51:18,205 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) xxx: Operation ("add") failed - address: ([("deployment" => "oc-21.2.9-RELEASE.ear")]) - failure description: "xxx: No deployment content with hash 28caffe00e398617b9bd446e88abcf3adebd2ac3 is available in the deployment content repository for deployment 'oc-21.2.9-RELEASE.ear'. This is a fatal boot error. To correct the problem, either restart with the --admin-only switch set and use the CLI to install the missing content or remove it from the configuration, or remove the deployment from the xml configuration file and restart."
2022-05-19 10:51:18,214 FATAL [org.jboss.as.server] (Controller Boot Thread) xxx: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
2022-05-19 10:51:18,231 INFO  [org.jboss.as] (MSC service thread 1-2) xxx: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) stopped in 13ms
2022-05-19 11:03:26,106 INFO  [org.jboss.modules] (main) JBoss Modules version 1.10.0.Final
2022-05-19 11:03:26,557 INFO  [org.jboss.msc] (main) JBoss MSC version 1.4.11.Final
2022-05-19 11:03:26,566 INFO  [org.jboss.threads] (main) JBoss Threads version 2.3.3.Final
2022-05-19 11:03:26,703 INFO  [org.jboss.as] (MSC service thread 1-3) xxx: WildFly Full 19.1.0.Final (WildFly Core 11.1.1.Final) starting
2022-05-19 11:03:26,706 DEBUG [org.jboss.as.config] (MSC service thread 1-3) Configured system properties:

Environment

Dx NetOps Virtual Network Assurance any version 

Cause

unknown

Resolution

Ultimately an over install of the VNA software resolved this issue.  This will lay down wildfly files and allow it to start back up

Before doing this the database should be collected to validate it is not corrupt.