mad jenkins on hpi:run

[Emanuele Zattin]

Hello there!

While developing a plugin I got the weird behavior shown in the
picture. Please note the null instead of job and the dead executors.
In the stdout/err, before even opening the browser to visit the
webpage, I can see that subversion, maven and the other plugins have
been stopped, but no exception is shown and no stacktrace.

As soon as I open the webpage the console goes crazy with exceptions.
The whole log is attached as well.

At the moment I cannot try on another machine, but starting jenkins
with java -jar jenkins.war works fine, even with my plugin.

I have the feeling there might be some conflict going on with a
jenkins.pkg installation i did some months ago. I think I removed
everything installed by the pkg file, but maybe something is still
there.

Any hint?

BR,

Emanuele Zattin
---------------------------------------------------
-I don't have to know an answer. I don't feel frightened by not
knowing things; by being lost in a mysterious universe without any
purpose — which is the way it really is, as far as I can tell,
possibly. It doesn't frighten me.- Richard Feynman

[Jesse Farinacci]

Greetings,

Try wiping out work/ directory and then restart hpi:run.

-Jesse

On Feb 22, 2012 4:38 AM, "Emanuele Zattin" <[hidden email]> wrote:

Hello there!

While developing a plugin I got the weird behavior shown in the
picture. Please note the null instead of job and the dead executors.
In the stdout/err, before even opening the browser to visit the
webpage, I can see that subversion, maven and the other plugins have
been stopped, but no exception is shown and no stacktrace.

As soon as I open the webpage the console goes crazy with exceptions.
The whole log is attached as well.

At the moment I cannot try on another machine, but starting jenkins
with java -jar jenkins.war works fine, even with my plugin.

I have the feeling there might be some conflict going on with a
jenkins.pkg installation i did some months ago. I think I removed
everything installed by the pkg file, but maybe something is still
there.

Any hint?

BR,

Emanuele Zattin
---------------------------------------------------
-I don't have to know an answer. I don't feel frightened by not
knowing things; by being lost in a mysterious universe without any
purpose — which is the way it really is, as far as I can tell,
possibly. It doesn't frighten me.- Richard Feynman

[Emanuele Zattin]

Tried that... didn't work :(

Emanuele Zattin
---------------------------------------------------
-I don't have to know an answer. I don't feel frightened by not
knowing things; by being lost in a mysterious universe without any
purpose — which is the way it really is, as far as I can tell,
possibly. It doesn't frighten me.- Richard Feynman



On Wed, Feb 22, 2012 at 3:05 PM, Jesse Farinacci <[hidden email]> wrote:

> Greetings,
>
> Try wiping out work/ directory and then restart hpi:run.
>
> -Jesse
>
> On Feb 22, 2012 4:38 AM, "Emanuele Zattin" <[hidden email]> wrote:
>>
>> Hello there!
>>
>> While developing a plugin I got the weird behavior shown in the
>> picture. Please note the null instead of job and the dead executors.
>> In the stdout/err, before even opening the browser to visit the
>> webpage, I can see that subversion, maven and the other plugins have
>> been stopped, but no exception is shown and no stacktrace.
>>
>> As soon as I open the webpage the console goes crazy with exceptions.
>> The whole log is attached as well.
>>
>> At the moment I cannot try on another machine, but starting jenkins
>> with java -jar jenkins.war works fine, even with my plugin.
>>
>> I have the feeling there might be some conflict going on with a
>> jenkins.pkg installation i did some months ago. I think I removed
>> everything installed by the pkg file, but maybe something is still
>> there.
>>
>> Any hint?
>>
>> BR,
>>
>> Emanuele Zattin
>> ---------------------------------------------------
>> -I don't have to know an answer. I don't feel frightened by not
>> knowing things; by being lost in a mysterious universe without any
>> purpose — which is the way it really is, as far as I can tell,
>> possibly. It doesn't frighten me.- Richard Feynman

[dharmsheta]

This is also seen by me sometime however not reproducible all the time ...
however it has been quite known...https://wiki.jenkins-ci.org/display/JENKINS/Dead+Executor  and corresponding JIRA ticket https://issues.jenkins-ci.org/browse/JENKINS-7807 

[dharmsheta]

This is also seen by me sometime however not reproducible all the time ...
however it has been quite known...https://wiki.jenkins-ci.org/display/JENKINS/Dead+Executor  and corresponding JIRA ticket https://issues.jenkins-ci.org/browse/JENKINS-7807 

[dharmesh sheta]

This is also seen by me sometime however not reproducible all the
time

Seems also that it has been quite known...https://wiki.jenkins-ci.org/
display/JENKINS/Dead+Executor  and corresponding JIRA ticket
https://issues.jenkins-ci.org/browse/JENKINS-7807

On Feb 22, 3:08 pm, Emanuele Zattin <[hidden email]> wrote:

> Tried that... didn't work :(
>
> Emanuele Zattin
> ---------------------------------------------------
> -I don't have to know an answer. I don't feel frightened by not
> knowing things; by being lost in a mysterious universe without any
> purpose — which is the way it really is, as far as I can tell,
> possibly. It doesn't frighten me.- Richard Feynman
>
>
>
>
>
>
>
> On Wed, Feb 22, 2012 at 3:05 PM, Jesse Farinacci <[hidden email]> wrote:
> > Greetings,
>
> > Try wiping out work/ directory and then restart hpi:run.
>
> > -Jesse
>
> > On Feb 22, 2012 4:38 AM, "Emanuele Zattin" <[hidden email]> wrote:
>
> >> Hello there!
>
> >> While developing a plugin I got the weird behavior shown in the
> >> picture. Please note the null instead of job and the dead executors.
> >> In the stdout/err, before even opening the browser to visit the
> >> webpage, I can see that subversion, maven and the other plugins have
> >> been stopped, but no exception is shown and no stacktrace.
>
> >> As soon as I open the webpage the console goes crazy with exceptions.
> >> The whole log is attached as well.
>
> >> At the moment I cannot try on another machine, but starting jenkins
> >> with java -jar jenkins.war works fine, even with my plugin.
>
> >> I have the feeling there might be some conflict going on with a
> >> jenkins.pkg installation i did some months ago. I think I removed
> >> everything installed by the pkg file, but maybe something is still
> >> there.
>
> >> Any hint?
>
> >> BR,
>
> >> Emanuele Zattin
> >> ---------------------------------------------------
> >> -I don't have to know an answer. I don't feel frightened by not
> >> knowing things; by being lost in a mysterious universe without any
> >> purpose — which is the way it really is, as far as I can tell,
> >> possibly. It doesn't frighten me.- Richard Feynman