You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-user@hadoop.apache.org by Lewis John Mcgibbney <le...@gmail.com> on 2013/01/09 04:37:48 UTC
UnknownHostException after upgrade from 1.0.3 > 1.1.1
Hi All,
Over @Nutch, we are experiencing failed builds on our nightly CI builds
after the above upgrade.
This happens on the Jenkins (Solaris and Ubuntu) builds but NOT on local
operating systems. This has been verified by numerous members of the
community.
The stack we get is appended below.
So far we've located some threads [0][1][2] which display 'similar'
behaviour, however no solution is jumping out as obvious at this point in
time.
Any help would be greatly appreciated, we would like to get stable builds
back online.
Thank you very much in advance.
Lewis
[0] : http://lucene.472066.n3.nabble.com/Nutch-Crawling-error-td612107.html
[1] : http://www.thegeekstuff.com/2012/02/hadoop-standalone-installation/
[2] : http://www.mail-archive.com/user@cassandra.apache.org/msg16668.html
java.net.UnknownHostException: -s: -s
at java.net.InetAddress.getLocalHost(InetAddress.java:1354)
at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:936)
at org.apache.hadoop.mapred.JobClient$2.run(JobClient.java:912)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1136)
at org.apache.hadoop.mapred.JobClient.submitJobInternal(JobClient.java:912)
at org.apache.hadoop.mapred.JobClient.submitJob(JobClient.java:886)
at org.apache.hadoop.mapred.JobClient.runJob(JobClient.java:1323)
at org.apache.nutch.crawl.Generator.generate(Generator.java:551)
at org.apache.nutch.crawl.Generator.generate(Generator.java:465)
at org.apache.nutch.crawl.TestGenerator.generateFetchlist(TestGenerator.java:313)
at org.apache.nutch.crawl.TestGenerator.testFilter(TestGenerator.java:259)
--
*Lewis*
Re: UnknownHostException after upgrade from 1.0.3 > 1.1.1
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi Andy,
This is perfect.
Thanks for the heads up.
Lewis
On Wed, Jan 9, 2013 at 12:56 PM, Andy Isaacson <ad...@cloudera.com> wrote:
> On Tue, Jan 8, 2013 at 7:37 PM, Lewis John Mcgibbney
> <le...@gmail.com> wrote:
> > Over @Nutch, we are experiencing failed builds on our nightly CI builds
> > after the above upgrade.
> > This happens on the Jenkins (Solaris and Ubuntu) builds but NOT on local
> > operating systems. This has been verified by numerous members of the
> > community.
> > The stack we get is appended below.
> [snip]
> > java.net.UnknownHostException: -s: -s
>
> I guess this is an error from the Solaris build, and that the Linux
> one is slightly different, with a different string in place of the
> "-s"? The "-s" output implies that some Linux-specific script was run
> as root on your Solaris machine and did a "hostname -s", which on
> Linux prints the short hostname, but on Solaris sets the current
> hostname of the machine to "-s". A reboot will clear up that problem,
> or you can manually fix the hostname with "hostname
> whatever-the-hostname-is". If you're doing your Jenkins builds as
> root, I highly recommend that you stop doing that.
>
> In both cases you can fix the build failure by ensuring that the build
> machine's hostname (run the "hostname" command) is present in the
> /etc/hosts file, per
>
> http://www.thegeekstuff.com/2012/02/hadoop-standalone-installation/
>
> There are "better" ways to fix the problem by ensuring that your
> network's DHCP and DNS configuration is correct, but /etc/hosts is the
> quick and easy way.
>
> -andy
>
--
*Lewis*
Re: UnknownHostException after upgrade from 1.0.3 > 1.1.1
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi Andy,
This is perfect.
Thanks for the heads up.
Lewis
On Wed, Jan 9, 2013 at 12:56 PM, Andy Isaacson <ad...@cloudera.com> wrote:
> On Tue, Jan 8, 2013 at 7:37 PM, Lewis John Mcgibbney
> <le...@gmail.com> wrote:
> > Over @Nutch, we are experiencing failed builds on our nightly CI builds
> > after the above upgrade.
> > This happens on the Jenkins (Solaris and Ubuntu) builds but NOT on local
> > operating systems. This has been verified by numerous members of the
> > community.
> > The stack we get is appended below.
> [snip]
> > java.net.UnknownHostException: -s: -s
>
> I guess this is an error from the Solaris build, and that the Linux
> one is slightly different, with a different string in place of the
> "-s"? The "-s" output implies that some Linux-specific script was run
> as root on your Solaris machine and did a "hostname -s", which on
> Linux prints the short hostname, but on Solaris sets the current
> hostname of the machine to "-s". A reboot will clear up that problem,
> or you can manually fix the hostname with "hostname
> whatever-the-hostname-is". If you're doing your Jenkins builds as
> root, I highly recommend that you stop doing that.
>
> In both cases you can fix the build failure by ensuring that the build
> machine's hostname (run the "hostname" command) is present in the
> /etc/hosts file, per
>
> http://www.thegeekstuff.com/2012/02/hadoop-standalone-installation/
>
> There are "better" ways to fix the problem by ensuring that your
> network's DHCP and DNS configuration is correct, but /etc/hosts is the
> quick and easy way.
>
> -andy
>
--
*Lewis*
Re: UnknownHostException after upgrade from 1.0.3 > 1.1.1
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi Andy,
This is perfect.
Thanks for the heads up.
Lewis
On Wed, Jan 9, 2013 at 12:56 PM, Andy Isaacson <ad...@cloudera.com> wrote:
> On Tue, Jan 8, 2013 at 7:37 PM, Lewis John Mcgibbney
> <le...@gmail.com> wrote:
> > Over @Nutch, we are experiencing failed builds on our nightly CI builds
> > after the above upgrade.
> > This happens on the Jenkins (Solaris and Ubuntu) builds but NOT on local
> > operating systems. This has been verified by numerous members of the
> > community.
> > The stack we get is appended below.
> [snip]
> > java.net.UnknownHostException: -s: -s
>
> I guess this is an error from the Solaris build, and that the Linux
> one is slightly different, with a different string in place of the
> "-s"? The "-s" output implies that some Linux-specific script was run
> as root on your Solaris machine and did a "hostname -s", which on
> Linux prints the short hostname, but on Solaris sets the current
> hostname of the machine to "-s". A reboot will clear up that problem,
> or you can manually fix the hostname with "hostname
> whatever-the-hostname-is". If you're doing your Jenkins builds as
> root, I highly recommend that you stop doing that.
>
> In both cases you can fix the build failure by ensuring that the build
> machine's hostname (run the "hostname" command) is present in the
> /etc/hosts file, per
>
> http://www.thegeekstuff.com/2012/02/hadoop-standalone-installation/
>
> There are "better" ways to fix the problem by ensuring that your
> network's DHCP and DNS configuration is correct, but /etc/hosts is the
> quick and easy way.
>
> -andy
>
--
*Lewis*
RE: UnknownHostException after upgrade from 1.0.3 > 1.1.1
Posted by Markus Jelsma <ma...@openindex.io>.
Cool, thanks for tracking it down Lewis!! :)
-----Original message-----
> From:Lewis John Mcgibbney <le...@gmail.com>
> Sent: Wed 09-Jan-2013 23:29
> To: dev@nutch.apache.org
> Subject: Fwd: UnknownHostException after upgrade from 1.0.3 > 1.1.1
>
> Hi All,
>
> OK please see below for some progress on this one. We most certainly need to configure the slave node to build Nutch before we can get the nightly builds back online.
>
> In the meantime, AFAIK the patches pending for commit have been tested and no objections have been raised.
>
> I'll keep working on this.
>
> Best
>
> Lewis
>
> ---------- Forwarded message ----------
> From: Andy Isaacson <adi@cloudera.com <ma...@cloudera.com> >
> Date: Wed, Jan 9, 2013 at 12:56 PM
> Subject: Re: UnknownHostException after upgrade from 1.0.3 > 1.1.1
> To: user@hadoop.apache.org <ma...@hadoop.apache.org>
>
>
> On Tue, Jan 8, 2013 at 7:37 PM, Lewis John Mcgibbney
> <lewis.mcgibbney@gmail.com <ma...@gmail.com> > wrote:
> > Over @Nutch, we are experiencing failed builds on our nightly CI builds
> > after the above upgrade.
> > This happens on the Jenkins (Solaris and Ubuntu) builds but NOT on local
> > operating systems. This has been verified by numerous members of the
> > community.
> > The stack we get is appended below.
> [snip]
> > java.net.UnknownHostException: -s: -s
>
> I guess this is an error from the Solaris build, and that the Linux
> one is slightly different, with a different string in place of the
> "-s"? The "-s" output implies that some Linux-specific script was run
> as root on your Solaris machine and did a "hostname -s", which on
> Linux prints the short hostname, but on Solaris sets the current
> hostname of the machine to "-s". A reboot will clear up that problem,
> or you can manually fix the hostname with "hostname
> whatever-the-hostname-is". If you're doing your Jenkins builds as
> root, I highly recommend that you stop doing that.
>
> In both cases you can fix the build failure by ensuring that the build
> machine's hostname (run the "hostname" command) is present in the
> /etc/hosts file, per
>
> http://www.thegeekstuff.com/2012/02/hadoop-standalone-installation/ <http://www.thegeekstuff.com/2012/02/hadoop-standalone-installation/>
>
> There are "better" ways to fix the problem by ensuring that your
> network's DHCP and DNS configuration is correct, but /etc/hosts is the
> quick and easy way.
>
> -andy
>
>
>
> --
> Lewis
>
Fwd: UnknownHostException after upgrade from 1.0.3 > 1.1.1
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi All,
OK please see below for some progress on this one. We most certainly need
to configure the slave node to build Nutch before we can get the nightly
builds back online.
In the meantime, AFAIK the patches pending for commit have been tested and
no objections have been raised.
I'll keep working on this.
Best
Lewis
---------- Forwarded message ----------
From: Andy Isaacson <ad...@cloudera.com>
Date: Wed, Jan 9, 2013 at 12:56 PM
Subject: Re: UnknownHostException after upgrade from 1.0.3 > 1.1.1
To: user@hadoop.apache.org
On Tue, Jan 8, 2013 at 7:37 PM, Lewis John Mcgibbney
<le...@gmail.com> wrote:
> Over @Nutch, we are experiencing failed builds on our nightly CI builds
> after the above upgrade.
> This happens on the Jenkins (Solaris and Ubuntu) builds but NOT on local
> operating systems. This has been verified by numerous members of the
> community.
> The stack we get is appended below.
[snip]
> java.net.UnknownHostException: -s: -s
I guess this is an error from the Solaris build, and that the Linux
one is slightly different, with a different string in place of the
"-s"? The "-s" output implies that some Linux-specific script was run
as root on your Solaris machine and did a "hostname -s", which on
Linux prints the short hostname, but on Solaris sets the current
hostname of the machine to "-s". A reboot will clear up that problem,
or you can manually fix the hostname with "hostname
whatever-the-hostname-is". If you're doing your Jenkins builds as
root, I highly recommend that you stop doing that.
In both cases you can fix the build failure by ensuring that the build
machine's hostname (run the "hostname" command) is present in the
/etc/hosts file, per
http://www.thegeekstuff.com/2012/02/hadoop-standalone-installation/
There are "better" ways to fix the problem by ensuring that your
network's DHCP and DNS configuration is correct, but /etc/hosts is the
quick and easy way.
-andy
--
*Lewis*
Re: UnknownHostException after upgrade from 1.0.3 > 1.1.1
Posted by Lewis John Mcgibbney <le...@gmail.com>.
Hi Andy,
This is perfect.
Thanks for the heads up.
Lewis
On Wed, Jan 9, 2013 at 12:56 PM, Andy Isaacson <ad...@cloudera.com> wrote:
> On Tue, Jan 8, 2013 at 7:37 PM, Lewis John Mcgibbney
> <le...@gmail.com> wrote:
> > Over @Nutch, we are experiencing failed builds on our nightly CI builds
> > after the above upgrade.
> > This happens on the Jenkins (Solaris and Ubuntu) builds but NOT on local
> > operating systems. This has been verified by numerous members of the
> > community.
> > The stack we get is appended below.
> [snip]
> > java.net.UnknownHostException: -s: -s
>
> I guess this is an error from the Solaris build, and that the Linux
> one is slightly different, with a different string in place of the
> "-s"? The "-s" output implies that some Linux-specific script was run
> as root on your Solaris machine and did a "hostname -s", which on
> Linux prints the short hostname, but on Solaris sets the current
> hostname of the machine to "-s". A reboot will clear up that problem,
> or you can manually fix the hostname with "hostname
> whatever-the-hostname-is". If you're doing your Jenkins builds as
> root, I highly recommend that you stop doing that.
>
> In both cases you can fix the build failure by ensuring that the build
> machine's hostname (run the "hostname" command) is present in the
> /etc/hosts file, per
>
> http://www.thegeekstuff.com/2012/02/hadoop-standalone-installation/
>
> There are "better" ways to fix the problem by ensuring that your
> network's DHCP and DNS configuration is correct, but /etc/hosts is the
> quick and easy way.
>
> -andy
>
--
*Lewis*
Re: UnknownHostException after upgrade from 1.0.3 > 1.1.1
Posted by Andy Isaacson <ad...@cloudera.com>.
On Tue, Jan 8, 2013 at 7:37 PM, Lewis John Mcgibbney
<le...@gmail.com> wrote:
> Over @Nutch, we are experiencing failed builds on our nightly CI builds
> after the above upgrade.
> This happens on the Jenkins (Solaris and Ubuntu) builds but NOT on local
> operating systems. This has been verified by numerous members of the
> community.
> The stack we get is appended below.
[snip]
> java.net.UnknownHostException: -s: -s
I guess this is an error from the Solaris build, and that the Linux
one is slightly different, with a different string in place of the
"-s"? The "-s" output implies that some Linux-specific script was run
as root on your Solaris machine and did a "hostname -s", which on
Linux prints the short hostname, but on Solaris sets the current
hostname of the machine to "-s". A reboot will clear up that problem,
or you can manually fix the hostname with "hostname
whatever-the-hostname-is". If you're doing your Jenkins builds as
root, I highly recommend that you stop doing that.
In both cases you can fix the build failure by ensuring that the build
machine's hostname (run the "hostname" command) is present in the
/etc/hosts file, per
http://www.thegeekstuff.com/2012/02/hadoop-standalone-installation/
There are "better" ways to fix the problem by ensuring that your
network's DHCP and DNS configuration is correct, but /etc/hosts is the
quick and easy way.
-andy
Re: UnknownHostException after upgrade from 1.0.3 > 1.1.1
Posted by Andy Isaacson <ad...@cloudera.com>.
On Tue, Jan 8, 2013 at 7:37 PM, Lewis John Mcgibbney
<le...@gmail.com> wrote:
> Over @Nutch, we are experiencing failed builds on our nightly CI builds
> after the above upgrade.
> This happens on the Jenkins (Solaris and Ubuntu) builds but NOT on local
> operating systems. This has been verified by numerous members of the
> community.
> The stack we get is appended below.
[snip]
> java.net.UnknownHostException: -s: -s
I guess this is an error from the Solaris build, and that the Linux
one is slightly different, with a different string in place of the
"-s"? The "-s" output implies that some Linux-specific script was run
as root on your Solaris machine and did a "hostname -s", which on
Linux prints the short hostname, but on Solaris sets the current
hostname of the machine to "-s". A reboot will clear up that problem,
or you can manually fix the hostname with "hostname
whatever-the-hostname-is". If you're doing your Jenkins builds as
root, I highly recommend that you stop doing that.
In both cases you can fix the build failure by ensuring that the build
machine's hostname (run the "hostname" command) is present in the
/etc/hosts file, per
http://www.thegeekstuff.com/2012/02/hadoop-standalone-installation/
There are "better" ways to fix the problem by ensuring that your
network's DHCP and DNS configuration is correct, but /etc/hosts is the
quick and easy way.
-andy
Re: UnknownHostException after upgrade from 1.0.3 > 1.1.1
Posted by Andy Isaacson <ad...@cloudera.com>.
On Tue, Jan 8, 2013 at 7:37 PM, Lewis John Mcgibbney
<le...@gmail.com> wrote:
> Over @Nutch, we are experiencing failed builds on our nightly CI builds
> after the above upgrade.
> This happens on the Jenkins (Solaris and Ubuntu) builds but NOT on local
> operating systems. This has been verified by numerous members of the
> community.
> The stack we get is appended below.
[snip]
> java.net.UnknownHostException: -s: -s
I guess this is an error from the Solaris build, and that the Linux
one is slightly different, with a different string in place of the
"-s"? The "-s" output implies that some Linux-specific script was run
as root on your Solaris machine and did a "hostname -s", which on
Linux prints the short hostname, but on Solaris sets the current
hostname of the machine to "-s". A reboot will clear up that problem,
or you can manually fix the hostname with "hostname
whatever-the-hostname-is". If you're doing your Jenkins builds as
root, I highly recommend that you stop doing that.
In both cases you can fix the build failure by ensuring that the build
machine's hostname (run the "hostname" command) is present in the
/etc/hosts file, per
http://www.thegeekstuff.com/2012/02/hadoop-standalone-installation/
There are "better" ways to fix the problem by ensuring that your
network's DHCP and DNS configuration is correct, but /etc/hosts is the
quick and easy way.
-andy
Re: UnknownHostException after upgrade from 1.0.3 > 1.1.1
Posted by Andy Isaacson <ad...@cloudera.com>.
On Tue, Jan 8, 2013 at 7:37 PM, Lewis John Mcgibbney
<le...@gmail.com> wrote:
> Over @Nutch, we are experiencing failed builds on our nightly CI builds
> after the above upgrade.
> This happens on the Jenkins (Solaris and Ubuntu) builds but NOT on local
> operating systems. This has been verified by numerous members of the
> community.
> The stack we get is appended below.
[snip]
> java.net.UnknownHostException: -s: -s
I guess this is an error from the Solaris build, and that the Linux
one is slightly different, with a different string in place of the
"-s"? The "-s" output implies that some Linux-specific script was run
as root on your Solaris machine and did a "hostname -s", which on
Linux prints the short hostname, but on Solaris sets the current
hostname of the machine to "-s". A reboot will clear up that problem,
or you can manually fix the hostname with "hostname
whatever-the-hostname-is". If you're doing your Jenkins builds as
root, I highly recommend that you stop doing that.
In both cases you can fix the build failure by ensuring that the build
machine's hostname (run the "hostname" command) is present in the
/etc/hosts file, per
http://www.thegeekstuff.com/2012/02/hadoop-standalone-installation/
There are "better" ways to fix the problem by ensuring that your
network's DHCP and DNS configuration is correct, but /etc/hosts is the
quick and easy way.
-andy