In case anyone is curious, I identified two sources of this issue. 1) JGit is throwing exceptions because nanosecond resolution is set to UNDEFINED and any time you do math (add a value) with that value in Java long, you get an Arithmetic Overflow. This seems to have left some threads in an indeterminate state. 2) More importantly, we had an out of date SSL certificate. There were no exceptions thrown during startup relating to this, but we could not get to the update site or download metadata on startup. I think this was the root of many problems but it would have been nice to get an exception (and one with the URL involved, which Jenkins plugins are notorious for not reporting).
Cheers, Randall On Tuesday, 28 July 2020 10:05:16 UTC-4, Randall Becker wrote: > > This has been going on since 2.233. We are getting pretty consistent > failures of Jenkins right after the "Listed all plugins" message is logged. > This just on the controller (there are no agents), running JRE 1.8.0_45. I > have wiped the configuration three times already. As soon as I add pipeline > jobs and actually do a build, I cannot stop and restart Jenkins. There are > no weird exceptions showing in the log. This has been reported as a defect > to Core, with a thread dump, but I have not had any feedback at all. It's > getting seriously frustrating. Has anyone else seen this or have advice on > tracking down what's going on? > -- 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/e10ae546-1381-47b1-a6b2-36e1bf4a667co%40googlegroups.com.
