# Jenkins service is failing after migrate jenkins from centos7 to AWS linux2 **URL:** \ **Category:** Using Jenkins\ **Created:** [June 27, 2024, 9:05am UTC](https://community.jenkins.io/t/jenkins-service-is-failing-after-migrate-jenkins-from-centos7-to-aws-linux2/16429 "2024-06-27T09:05:49Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![poorna](https://avatars.discourse-cdn.com/v4/letter/p/a6a055/32.png) [@poorna](https://community.jenkins.io/u/poorna)\ **Post date:** [June 27, 2024, 9:05am UTC](https://community.jenkins.io/t/jenkins-service-is-failing-after-migrate-jenkins-from-centos7-to-aws-linux2/16429/1 "2024-06-27T09:05:49Z")
Jenkins service is failing. It is showing below output. Any idea that how to resolve this ? systemctl status jenkins.service -l ● jenkins.service - Jenkins Continuous Integration Server Loaded: loaded (/etc/systemd/system/jenkins.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Thu 2024-06-27 08:47:48 UTC; 15min ago Process: 12331 ExecStart=/usr/bin/jenkins (code=exited, status=1/FAILURE) Main PID: 12331 (code=exited, status=1/FAILURE) Failed to start Jenkins Continuous Integration Server. Unit jenkins.service entered failed state. jenkins.service failed. jenkins.service holdoff time over, scheduling restart. Stopped Jenkins Continuous Integration Server. start request repeated too quickly for jenkins.service Failed to start Jenkins Continuous Integration Server. Unit jenkins.service entered failed state. systemd[1]: jenkins.service failed. Any suggesstions please ? ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [June 27, 2024, 6:08pm UTC](https://community.jenkins.io/t/jenkins-service-is-failing-after-migrate-jenkins-from-centos7-to-aws-linux2/16429/2 "2024-06-27T18:08:27Z")
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](https://www.jenkins.io/blog/2023/05/30/operating-system-end-of-life/) that support would end in November 2023. ---
**Author:** ![poorna](https://avatars.discourse-cdn.com/v4/letter/p/a6a055/32.png) [@poorna](https://community.jenkins.io/u/poorna)\ **Post date:** [June 28, 2024, 2:36am UTC](https://community.jenkins.io/t/jenkins-service-is-failing-after-migrate-jenkins-from-centos7-to-aws-linux2/16429/3 "2024-06-28T02:36:36Z")
Hi MarkEWaite, Thanks for your reply. 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\> Thanks, Poorna ---
**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\ **Post date:** [June 28, 2024, 1:34pm UTC](https://community.jenkins.io/t/jenkins-service-is-failing-after-migrate-jenkins-from-centos7-to-aws-linux2/16429/4 "2024-06-28T13:34:36Z")
> [@poorna](#): > > Amazon Linux 2 is also a derivative of Red Hat Enterprise Linux 7 but it will be supported up to June 30, 2025. 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. You might also refer to the [managing systemd services documentation](https://www.jenkins.io/doc/book/system-administration/systemd-services/). You might also refer to the Darin Pope video on systemd and CentOS 7.9 (knowing that it is no longer supported): [![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/5/5d731f86134683079a41351908d8832c01e0a6f4.jpeg "🔴 Managing the Jenkins systemd Service on CentOS 7.9") ](https://www.youtube.com/watch?v=MkokjTQ2ngc) You might also refer to the Darin Pope video on system logs [![](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/b/b80836739063ca5e70d23bf44ae20113ccac1b9c.jpeg "Where are the Jenkins System Logs?") ](https://www.youtube.com/watch?v=jocHFn4g3vo&t=2s)