Author: Jason Ritz
Date: December 8th, 2023
Audience: Everyone
Environmental details: Self-hosted
Summary:
After restarting the application server, Replicated and Jama Connect® will not start even though no changes were made to the server.
Solution:
- Check if SELinux is running
sestatus
- If SELinux is running temporarily disable it
setenforce 0
- Check if Firewalld is running
systemctl status firewalld
- If Firewalld is running temporarily disable it
systemctl stop firewalld
- Restart Docker
systemctl restart docker
Cause:
SELinux and Firewalld are set to run on system startup by default, so a server reboot can restart them, causing the issue.
Prevention:
You can permanently disable SELinux by editing the following file:
/etc/sysconfig/selinux
Update the line SELinux=enforcing to be SELinux=disabled
Feedback: Please leave feedback in the comments below.
Related to
- Self-Hosted
- Authentication
- Relationships
- Administration
- Testing
- REST API and extensibility
- Reports
- Microsoft Word
- Microsoft Excel
- Installation
- Migration
- Coverage and traceability
- Traditional
- Jama Connect Interchange™
- Customer-Validated Cloud
- Replicated
- Security
- Diagram/Graph Editor
- Jama Software® Subscriptions Maintenance and Support Service Agreement
- Jama Connect®
- Supported
- Application Server
- Item Configuration
- Deployment Migration
- Integrations
Comments
0 comments
Please sign in to leave a comment.