Jenkins burning devil w/Stack trace--how to recover???

[Steve K]

UGH!
I just installed a large number of plugins and something has sent my Jenkins server into HE!!

Any suggestions on how I can become operational again?

I have a fairly recent backup .zip file backup (created by the Backup plugin).  Do you think it would be worth copying the content of that backup onto the "real" directory and see if Jenkins will start?  Or is there a better way?

OMG.  I should know better than to try upgrading anything just before the weekend.

[Steve K]

It looks like Jenkins is working, but attempting to access its pages has gone to the devil.
I can log in and select "My Views" to see the jobs (they are running).
But, if I attempt to go to the main page, I get the devil.

[James Nord]

You may get some pointers on here if you paste the stack trace, otherwise all you can get is generic pointers.

[Steve K]

Since Jenkins was operational--just not usable for most users--I decided to try downgrading the plugins that I upgraded.
The first plugin I downgraded was "Build Pipeline Plugin".  I took that from 1.4.7 back down to 1.4.4

That did the trick!  Can't believe it.  I feel lucky.  I might even go buy a lottery ticket!
Actually, since it was the presentation of the web pages that was most affected, the "Build Pipeline Plugin" seemed to be the most closely associated.

BTW.  The server is Jenkins ver 1.580.1

I'd still be interested in hearing what you would have done if downgrading the plugin had not worked.
If something like this happens again, I'll take James Nord's advice and include the stack trace.

Thanks.

[David Resnick]

It sounds like you're hitting the same problem I have:
https://issues.jenkins-ci.org/browse/JENKINS-27537

- David