Red Hat JBoss Enterprise Application Platform (EAP) is a Java EE-based cross-application platform built around deploying and managing Java applications and services. This hands-on lab explores troubleshooting common things that can go wrong during the installation of JBoss EAP on Red Hat Enterprise Linux 8.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Install JBoss
Run the installer located in the
cloud_user‘s home directory:sudo java -jar jboss-eap-7.2.0-installer.jar -console
Review installer:
- Set the language.
- Accept terms.
- Set path (use
/opt/jboss-eapto match default configuration). - Install all packages.
- Set admin name (
admin). - Set admin password.
- Use the default configuration.
- Choose whether to save an automatic installation script based on this install.
Create the service user:
sudo useradd --no-create-home --shell /bin/false/ jboss-eapOpen the configuration file and uncomment the
JBOSS_HOMEandJBOSS_USERsettings; save and exit.cd /opt/jboss-eap sudo vim bin/init.d/jboss-eap.confCopy service files to the appropriate locations:
sudo cp bin/init.d/jboss-eap.conf /etc/default/ sudo cp bin/init.d/jboss-eap-rhel.sh /etc/init.d/Set script as an executable:
sudo chmod +x /etc/init.d/jboss-eap-rhel.shSet the service to start automatically:
sudo chkconfig --add jboss-eap-rhel.sh sudo chkconfig jboss-eap-rhel.sh onAttempt to start JBoss EAP:
sudo systemctl start jboss-eap-rhelThe service start should fail.
- Determine Cause of Failure (SELinux)
Begin troubleshooting by viewing the
journalctllog, as suggested in the output:journalctl -xe | less
Scroll towards the bottom of the logs. Look for a line stating:
SELinux is preventing jboss-eap-rhel. from create access on the file console.log.We’ll need to update SELinux to allow JBoss. Luckily, instructions for this are included in the log itself. Note that we’ll have to adjust the commands to use
sudo:sudo ausearch -c 'jboss-eap-rhel.' --raw | sudo audit2allow -M jboss-eap-rhel sudo semodule -X 300 -i jboss-eap-rhel.ppAttempt to start JBoss once more:
sudo systemctl start jboss-eap-rhelOnce more, it will fail.
- Determine Cause of Failure (Permissions)
Rerun the
journalctlcommand:journalctl -xe | less
Once more, scroll towards the bottom. Here we can see a permissions error:
Starting jboss-eap: chown: missing operand after ‘/var/run/jboss-eap’We’ll need to ensure our
jboss-eapuser can access the/var/run/jboss-eapdirectory:sudo chown -R jboss-eap:jboss-eap /var/run/jboss-eapAttempt another service start:
sudo systemctl start jboss-eap-rhelYet again, it fails.
- Determine Cause of Failure (JBoss Logs)
Should we check the logs this time, what we’re given is not very helpful. Instead, we want to look at JBoss’s logs themselves, found at
/var/log/jboss-eap:cat /var/log/jboss-eap/console.logNote that not all log content will be here. This is because our
jboss-eapuser doesn’t have permissions for this directory:ls -al /var/log/jboss-eap/Change the ownership for this directory:
sudo chown -R jboss-eap:jboss-eap /var/log/jboss-eapRerun the
startcommand:sudo systemctl start jboss-eap-rhelNow we can review our logs:
less /var/log/jboss-eap/console.logNotice that we cannot create a directory in
/opt/jboss-eap— this also needs to have its ownership updated:sudo chown -R jboss-eap:jboss-eap /opt/jboss-eapStart the service:
sudo systemctl start jboss-eap-rhel
