It seems like a lot of the recent hbase apache jenkins builds have been
failing with this message:
FATAL: hudson.remoting.RequestAbortedException: java.io.IOException:
Unexpected termination of the
channelhudson.remoting.RequestAbortedException
<http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>:
hudson.remoting.RequestAbortedException: java.io.IOException:
Unexpected termination of the channel
at hudson.remoting.Request.call(Request.java:174)
<http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Request.call&entity=method>
at hudson.remoting.Channel.call(Channel.java:663)
<http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Channel.call&entity=method>
at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158)
<http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.RemoteInvocationHandler.invoke&entity=method>
at $Proxy38.join(Unknown Source)
This says it may be due to environmental issues.
http://stackoverflow.com/questions/9998298/jenkins-slave-jobs-failing-on-unexpected-termination-of-channel

I'm looking into this.

Jon.
--
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// [EMAIL PROTECTED]

On Tue, Sep 4, 2012 at 7:07 PM, Jonathan Hsieh <[EMAIL PROTECTED]> wrote:
> It seems like a lot of the recent hbase apache jenkins builds have been
> failing with this message:
>
>
> FATAL: hudson.remoting.RequestAbortedException: java.io.IOException:
> Unexpected termination of the
> channelhudson.remoting.RequestAbortedException
> <http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException>:
> hudson.remoting.RequestAbortedException: java.io.IOException:
> Unexpected termination of the channel
>         at hudson.remoting.Request.call(Request.java:174)
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Request.call&entity=method>
>         at hudson.remoting.Channel.call(Channel.java:663)
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Channel.call&entity=method>
>         at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158)
> <http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.RemoteInvocationHandler.invoke&entity=method>
>         at $Proxy38.join(Unknown Source)
>
>
> This says it may be due to environmental issues.
> http://stackoverflow.com/questions/9998298/jenkins-slave-jobs-failing-on-unexpected-termination-of-channel
>
Thanks Jon.
St.Ack

I'm pretty convinced this was an environmental issue -- things seem well
enough on some our internal builds of apache branches.

Jon.

On Tue, Sep 4, 2012 at 7:56 PM, Stack <[EMAIL PROTECTED]> wrote:

> On Tue, Sep 4, 2012 at 7:07 PM, Jonathan Hsieh <[EMAIL PROTECTED]> wrote:
> > It seems like a lot of the recent hbase apache jenkins builds have been
> > failing with this message:
> >
> >
> > FATAL: hudson.remoting.RequestAbortedException: java.io.IOException:
> > Unexpected termination of the
> > channelhudson.remoting.RequestAbortedException
> > <
> http://stacktrace.jenkins-ci.org/search?query=hudson.remoting.RequestAbortedException
> >:
> > hudson.remoting.RequestAbortedException: java.io.IOException:
> > Unexpected termination of the channel
> >         at hudson.remoting.Request.call(Request.java:174)
> > <
> http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Request.call&entity=method
> >
> >         at hudson.remoting.Channel.call(Channel.java:663)
> > <
> http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.Channel.call&entity=method
> >
> >         at
> hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158)
> > <
> http://stacktrace.jenkins-ci.org/search/?query=hudson.remoting.RemoteInvocationHandler.invoke&entity=method
> >
> >         at $Proxy38.join(Unknown Source)
> >
> >
> > This says it may be due to environmental issues.
> >
> http://stackoverflow.com/questions/9998298/jenkins-slave-jobs-failing-on-unexpected-termination-of-channel
> >
> Thanks Jon.
> St.Ack
>

--
// Jonathan Hsieh (shay)
// Software Engineer, Cloudera
// [EMAIL PROTECTED]

On Wed, Sep 5, 2012 at 5:28 PM, Jonathan Hsieh <[EMAIL PROTECTED]> wrote:
> I'm pretty convinced this was an environmental issue -- things seem well
> enough on some our internal builds of apache branches.
>

You think we should file an INFRA issue on it to see if we get any
clue as to what its about?
St.Ack

To me, the issue is on hadoop6, while hadoop1, hadoop2 seem to be ok?

On Thu, Sep 6, 2012 at 7:27 AM, Stack <[EMAIL PROTECTED]> wrote:

> On Wed, Sep 5, 2012 at 5:28 PM, Jonathan Hsieh <[EMAIL PROTECTED]> wrote:
> > I'm pretty convinced this was an environmental issue -- things seem well
> > enough on some our internal builds of apache branches.
> >
>
> You think we should file an INFRA issue on it to see if we get any
> clue as to what its about?
> St.Ack
>