On Friday, June 10, 2022 at 7:12:40 AM UTC-6 fcenedese wrote: > At 08:16 10.06.2022, you wrote: > > >Hi, > > > >I upgraded Jenkins (running as a service) from version 2.235.5 to 2.303.2 > (by just replacing .war file and restarting the service), which seemed to > work pretty stable. Before doing it, I upgraded Java from OpenJDK 8 to > OpenJDK 11, which was the prerequisite for Jenkins upgrade. I tried to > upgrade even to 2.319.3 or to 2.332.3 and I was able to log in to GUI with > my AD credentials after upgrade, however there are some issues which cause > Jenkins to restart by itself from time to time when using these 2 releases, > so for now I downgraded it back to 2.303.2. >
One issue might be related to the technique you used to perform the upgrade to Jenkins 2.332.3. Unfortunately, you haven't provided enough information for others to know if you made that mistake or not. If the original installation used a Linux package (deb or rpm), then you failed to upgrade correctly when you upgraded by replacing the war file. Please use the Linux package manager to upgrade if you used the Linux package manager for the initial installation. Please review the changelog and the upgrade guide for the releases. Specifically note in the Jenkins 2.332.1 changelog <https://www.jenkins.io/changelog-stable/#v2.332.1> that the Jenkins Linux installers switched from System V init to systemd. Note in the Jenkins 2.332.1 upgrade guide <https://www.jenkins.io/changelog-stable/#v2.332.1> that the Jenkins Linux installers switched from System V init to systemd. There is also a blog post <https://www.jenkins.io/blog/2022/03/25/systemd-migration/> that describes the details needed for an issue report <https://www.jenkins.io/blog/2022/03/25/systemd-migration/#reporting-issues> that will allow others to help with the issue. Note that the Linux installer change did not affect Jenkins 2.319.3, so if you were seeing restarts in Jenkins 2.319.3, then it was not related to the change from System V init to systemd. If the original installation used the Windows installer, then you are making a large enough jump in versions that you should probably install with the latest Windows installer rather than replacing the war file. Another issue might be related to possible bug in Jenkins that is reported as Java 11 requiring more memory that Java 8 for a similar configuration. Unfortunately, you haven't provided enough information for others to know if that is the issue or not. One confirmed instance of that report is the metaspace memory leak report <https://issues.jenkins.io/browse/JENKINS-63766> in JENKINS-63766 <https://issues.jenkins.io/browse/JENKINS-63766>. If that is the specific issue, then updating plugins to most recent versions should resolve it. If it is none of those things, then you'll need to provide more details that help isolate the cause of the issue. > >The question is why is this happening ? > > I can't offer an explanation or even a solution but we too had that > problem of Jenkins restarting. As consequence I downgraded from > Jenkins 2.332.3. It may have been rather a problem with Java 11 > but I don't remember exactly. Currently we're using Jenkins > version 2.319.3 (on Ubuntu) with openJDK 8 and that is stable. > Of course we'd welcome a solution to this problem as well. > > Since Jenkins weekly will end support of Java 8 in June 2022 and Jenkins LTS will end support of Java 8 in September 2022, it is in your best interest to provide enough information so that others can understand and assist with the issue you're seeing. Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/877d8fb6-20f4-4125-aca0-85380ac1a14en%40googlegroups.com.
