Unfortunately, you’ve migrated from an unsupported operating system (CentOS 7) to another unsupported operating system (Amazon Linux 2). Amazon Linux 2 is unsupported by the Jenkins project. We don’t test it.
We announced in a May 2023 blog that support would end in November 2023.
Present jenkins server is installed on Centos7. Centos7 End of life is 30th June2024 so we are migrating this present server to Amazon Linux 2.
Amazon Linux 2 is also a derivative of Red Hat Enterprise Linux 7 but it will be supported up to June 30, 2025.
We have also tried to migrate present jenkins server running on Centos7 to Amazon Linux 2023.
Showing below error.
An ExecStart= process belonging to unit jenkins.service has exited.
░░
░░ The process’ exit code is ‘exited’ and its exit status is 255.
systemd[1]: jenkins.service: Failed with result ‘exit-code’.
░░ Subject: Unit failed
░░ Defined-By: systemd
systemctl start jenkins
Job for jenkins.service failed because the control process exited with error code.
See “systemctl status jenkins.service” and “journalctl -xeu jenkins.service” for details.
jenkins]# systemctl status jenkins.service
● jenkins.service - Jenkins Continuous Integration Server
Loaded: loaded (/etc/systemd/system/jenkins.service; enabled; preset: disabled)
Active: activating (start) since Fri 2024-06-28 02:31:55 UTC; 5s ago
Main PID: 507080 (java)
Tasks: 67 (limit: 38478)
Memory: 777.7M
CPU: 17.292s
CGroup: /system.slice/jenkins.service
└─507080 /usr/lib/jvm/java-11-amazon-corretto.x86_64/bin/java -Djava.awt.headless=true -jar /usr/share/java/jenkins.war --webroot=/var/cache/je>
Amazon has chosen to support Amazon Linux 2 until June 30, 2025. The Jenkins project stopped supporting Amazon Linux 2 in November 2023.
The detailed output from the two commands systemctl status jenkins.service and from journalctl -xeu jenkins.service usually provide enough information for you to diagnose the issue, though you’re running on a systemd configuration that the Jenkins project no longer tests.
