This article describes one the way to fix the issue with JBoss service not coming up with below exception only.

If we start the JBoss service, it shows below error:

May 06 07:49:01 space-000c29556edxx CROND[12847]: (root) CMD (/usr/nma/bin/writeLogCronJob)
May 06 07:49:57 space-000c29556edxx bash[9205]: jboss (error 1) is not running yet ...
May 06 07:49:57 space-000c29556edxx bash[9205]: domain.sh is not up.
May 06 07:49:57 space-000c29556edxx systemd[1]: jboss.service: control process exited, code=exited status=1
May 06 07:49:57 space-000c29556edxx systemd[1]: Failed to start Jboss Service.

In the /var/log/jboss/console file, we could see the below error:

[Host Controller] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_302] [Host Controller] Caused by: org.jboss.security.vault.SecurityVaultException: java.io.EOFException [Host Controller] at org.picketbox.plugins.vault.PicketBoxSecurityVault.readVaultContent(PicketBoxSecurit yVault.java:487) [Host Controller] at org.picketbox.plugins.vault.PicketBoxSecurityVault.init(PicketBoxSecurityVault.java: 214) [Host Controller] at org.jboss.as.server.services.security.VaultReaderImpl.createVault(RuntimeVaultReader .java:157) [wildfly-server-14.0.0.Final.jar:14.0.0.Final] [Host Controller] ... 13 more [Host Controller] Caused by: java.io.EOFException

Check the files in /var/jboss/vault/ directory, if VAULT.dat file is corrupted i.e file size is 0 then replace it from the working Space node and restart JBoss service.
 

[root@space-005056a9979xx]# cd /var/jboss/vault/
[root@space-005056a997xx vault]# ls -ltr
total 8
-rwxr-xr-x. 1 jboss jboss  498 Dec 23  2021 vault.keystore
-rwxr-xr-x. 1 jboss jboss 1301 Apr  8 22:39 VAULT.dat
[root@space-005056a997xx vault]#