I suspect the last thing in the Jenkins log is much less helpful for diagnosis than the early contents of the Jenkins log. Somewhere in the early portions of the Jenkins log I would expect to find a good hint that something is unable to start.
On Sun, May 20, 2018 at 4:24 PM Kernel Panic <netwarrior...@gmail.com> wrote: > Thank you very much for the explanation, I will try to restore the old > plugin version, and by the way this is the last thing on jenkins log > > Caused by: java.lang.NullPointerException > > at > org.jenkinsci.plugins.github.config.GitHubPluginConfig.constructDefaultUrl(GitHubPluginConfig.java:228) > > at > org.jenkinsci.plugins.github.config.GitHubPluginConfig.getHookUrl(GitHubPluginConfig.java:116) > > ... 341 more > > > May 20, 2018 9:00:55 PM hudson.ExpressionFactory2$JexlExpression evaluate > > WARNING: Caught exception evaluating: descriptor.helpFile in > /job/project-name/configure. Reason: > java.lang.reflect.InvocationTargetException > > java.lang.reflect.InvocationTargetException > at sun.reflect.GeneratedMethodAccessor298.invoke(Unknown Source)Caused > by: java.lang.NoClassDefFoundError: org/eclipse/jgit/transport/RemoteConfig > > at java.lang.Class.getDeclaredMethods0(Native Method) > > at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) > > at java.lang.Class.getDeclaredMethods(Class.java:1975) > > at > org.kohsuke.stapler.ClassDescriptor.findMethods(ClassDescriptor.java:149) > > at org.kohsuke.stapler.ClassDescriptor.<init>(ClassDescriptor.java:85) > > at > org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:216) > > at > org.kohsuke.stapler.lang.KlassNavigator$1.getFunctions(KlassNavigator.java:141) > > at org.kohsuke.stapler.lang.Klass.getFunctions(Klass.java:98) > > at org.kohsuke.stapler.KlassDescriptor.<init>(KlassDescriptor.java:27) > > at org.kohsuke.stapler.MetaClass.buildDispatchers(MetaClass.java:105) > > at org.kohsuke.stapler.MetaClass.<init>(MetaClass.java:93) > > at org.kohsuke.stapler.WebApp.getMetaClass(WebApp.java:204) > > at > org.kohsuke.stapler.jelly.groovy.GroovyFacet.createRequestDispatcher(GroovyFacet.java:109) > > at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:257) > > at org.kohsuke.stapler.RequestImpl.getView(RequestImpl.java:252) > > at hudson.model.Descriptor.getHelpFile(Descriptor.java:750) > > at hudson.model.Descriptor.getHelpFile(Descriptor.java:732) > > at hudson.model.Descriptor.getHelpFile(Descriptor.java:721) > > ... 160 more > > Caused by: java.lang.ClassNotFoundException: > org.eclipse.jgit.transport.RemoteConfig > > at > jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) > > at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) > > at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) > > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > El domingo, 20 de mayo de 2018, 19:00:03 (UTC-3), Mark Waite escribió: > >> On Sun, May 20, 2018 at 2:32 PM Kernel Panic wrote: >> >>> If there was a manual update, ( I can see some some git-client git and >>> git hub hpi/jpi files under plugin directory ) how can I revert it back? >>> >>> Thanks you very much! >>> >>> >> If one or more plugins were upgraded from a prior version to the current >> version, then there would be a "<plugin-name>.bak" file in the /plugins/ >> subdirectory of the Jenkins home directory. For example, I recently >> upgraded the docker-commons plugin and there is now a "docker-commons.bak" >> file (previous docker-commons plugin version) and a "docker-commons.jpi" >> file (currentl version of the docker-commons plugin). >> >> Plugins which have not been upgraded (at least on my installation) appear >> as "<plugin-name>.jpi" without a matching "<plugin-name>.bak". >> >> If you want to replace an existing plugin at the file system level with a >> different version, it may be enough to stop Jenkins, perform a backup, then >> repalce the "<plugin-name>.jpi" (or "<plugin-name>.hpi" if it exists >> instead) with the replacement version. >> >> You might also read the Jenkins log file to see if there are hints in the >> log file that might give an indication why the plugin is unable to start. >> >> Mark Waite >> >> > >>> El domingo, 20 de mayo de 2018, 16:54:48 (UTC-3), Mark Waite escribió: >>>> >>>> Have you checked in the "Plugin Manager" section of "Manage Jenkins" to >>>> confirm that there are no warnings about unsatisfied dependencies? >>>> >>>> I think that type of message might appear if a new git plugin were >>>> manually uploaded to a system that hadn't yet updated the git client plugin >>>> to the latest version. >>>> >>>> On Sun, May 20, 2018 at 1:50 PM Kernel Panic <netwar...@gmail.com> >>>> wrote: >>>> >>>>> Hello >>>>> I inherited a server with git 2.107.3 installed, it seems the previous >>>>> admin upgraded it, now when I got to project config I get this error: >>>>> >>>>> org.apache.commons.jelly.JellyTagException: >>>>> jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.107.3.jar!/lib/hudson/project/config-scm.jelly:36:91: >>>>> <st:include> Type org.eclipse.jgit.transport.RemoteConfig not present >>>>> >>>>> If I scroll down to Source Management I do not see the git option, >>>>> only None, CVS, and CVS Project set. >>>>> If I got to Manage Jenkins / Configure System I get the same java >>>>> error. >>>>> >>>>> The git plugin version is 3.9.0 and I do no see an option to >>>>> downgrade, so Im lost in here, any idea how can I troubleshoot this >>>>> issue? >>>>> The servert is Debian 8.2 >>>>> >>>>> Thanks in advance >>>>> Regards >>>>> >>>>> -- >>>>> 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 jenkinsci-use...@googlegroups.com. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/jenkinsci-users/44b9093d-75d9-4f3f-9a01-39d953c3a64c%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- >>> 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 jenkinsci-use...@googlegroups.com. >>> >> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-users/1b980dec-bbb8-4c5c-889b-9ca1b1890355%40googlegroups.com >>> <https://groups.google.com/d/msgid/jenkinsci-users/1b980dec-bbb8-4c5c-889b-9ca1b1890355%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- > 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 jenkinsci-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/dc913356-fab7-48c1-88b5-9328b5500816%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/dc913356-fab7-48c1-88b5-9328b5500816%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtF0kMBbmVFiEg-ewB8MsJmP5FyszFERYyL9xaspA_xnyg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
