You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Thomas Andrews (Created) (JIRA)" <ji...@apache.org> on 2012/03/19 21:15:38 UTC
[jira] [Created] (FLUME-1039) Vlingo physical node name not the
same as hostname output (extra . in name) which makes it hard to
auto-install
Vlingo physical node name not the same as hostname output (extra . in name) which makes it hard to auto-install
---------------------------------------------------------------------------------------------------------------
Key: FLUME-1039
URL: https://issues.apache.org/jira/browse/FLUME-1039
Project: Flume
Issue Type: Bug
Components: Docs, Node
Affects Versions: v0.9.4
Environment: CentOS Linux
Reporter: Thomas Andrews
When we installed a node on a host name app16-perf.qa.ourcompany.com, Flume decided the node name was "app16-perf.qa..ourcompany.com". Note the extra period. We are completely unclear why this happened.
Even worse, however, is that it is unclear in the documentation how to override the default physical node name in the configuration. Where does that go, exactly?
Without either a fix to this (so that the default physical node name is precisely as the documentation says it is, the output of the "hostname" command) or a way to configure this parameter in the flume-site.xml file, we are kind of hosed with auto-deploying flume agents on our servers.
It's possible I missed something in the documentation - I looked for the word "hostname" and did not find anything covering this in the User Guide.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (FLUME-1039) Vlingo physical node name not the
same as hostname output (extra . in name) which makes it hard to
auto-install
Posted by "Thomas Andrews (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13234768#comment-13234768 ]
Thomas Andrews commented on FLUME-1039:
---------------------------------------
The cause of this problem was a bad entry in "/etc/hosts".
However, the docs say that the default physical node name is the same as the output of "hostname," and "hostname" was not returning the broken host name.
> Vlingo physical node name not the same as hostname output (extra . in name) which makes it hard to auto-install
> ---------------------------------------------------------------------------------------------------------------
>
> Key: FLUME-1039
> URL: https://issues.apache.org/jira/browse/FLUME-1039
> Project: Flume
> Issue Type: Bug
> Components: Docs, Node
> Affects Versions: v0.9.4
> Environment: CentOS Linux
> Reporter: Thomas Andrews
>
> When we installed a node on a host named {{app16-perf.qa.ourcompany.com}}, Flume decided the node name was {{app16-perf.qa..ourcompany.com}}. Note the extra period. We are completely unclear why this happened.
> Even worse, however, is that it is unclear in the documentation how to override the default physical node name in the configuration. Where does that go, exactly?
> Without either a fix to this (so that the default physical node name is precisely as the documentation says it is, the output of the "hostname" command) or a way to configure this parameter in the flume-site.xml file, we are kind of hosed with auto-deploying flume agents on our servers.
> It's possible I missed something in the documentation - I looked for the word "hostname" and did not find anything covering this in the User Guide.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLUME-1039) Vlingo physical node name not the
same as hostname output (extra . in name) which makes it hard to
auto-install
Posted by "Thomas Andrews (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Andrews updated FLUME-1039:
----------------------------------
Description:
When we installed a node on a host named {{app16-perf.qa.ourcompany.com}}, Flume decided the node name was {{app16-perf.qa..ourcompany.com}}. Note the extra period. We are completely unclear why this happened.
Even worse, however, is that it is unclear in the documentation how to override the default physical node name in the configuration. Where does that go, exactly?
Without either a fix to this (so that the default physical node name is precisely as the documentation says it is, the output of the "hostname" command) or a way to configure this parameter in the flume-site.xml file, we are kind of hosed with auto-deploying flume agents on our servers.
It's possible I missed something in the documentation - I looked for the word "hostname" and did not find anything covering this in the User Guide.
was:
When we installed a node on a host named app16-perf.qa.ourcompany.c{{om}}, Flume decided the node name was {{app16-perf.qa..ourcompany.com}}. Note the extra period. We are completely unclear why this happened.
Even worse, however, is that it is unclear in the documentation how to override the default physical node name in the configuration. Where does that go, exactly?
Without either a fix to this (so that the default physical node name is precisely as the documentation says it is, the output of the "hostname" command) or a way to configure this parameter in the flume-site.xml file, we are kind of hosed with auto-deploying flume agents on our servers.
It's possible I missed something in the documentation - I looked for the word "hostname" and did not find anything covering this in the User Guide.
> Vlingo physical node name not the same as hostname output (extra . in name) which makes it hard to auto-install
> ---------------------------------------------------------------------------------------------------------------
>
> Key: FLUME-1039
> URL: https://issues.apache.org/jira/browse/FLUME-1039
> Project: Flume
> Issue Type: Bug
> Components: Docs, Node
> Affects Versions: v0.9.4
> Environment: CentOS Linux
> Reporter: Thomas Andrews
>
> When we installed a node on a host named {{app16-perf.qa.ourcompany.com}}, Flume decided the node name was {{app16-perf.qa..ourcompany.com}}. Note the extra period. We are completely unclear why this happened.
> Even worse, however, is that it is unclear in the documentation how to override the default physical node name in the configuration. Where does that go, exactly?
> Without either a fix to this (so that the default physical node name is precisely as the documentation says it is, the output of the "hostname" command) or a way to configure this parameter in the flume-site.xml file, we are kind of hosed with auto-deploying flume agents on our servers.
> It's possible I missed something in the documentation - I looked for the word "hostname" and did not find anything covering this in the User Guide.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FLUME-1039) Vlingo physical node name not the
same as hostname output (extra . in name) which makes it hard to
auto-install
Posted by "Thomas Andrews (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FLUME-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Andrews updated FLUME-1039:
----------------------------------
Description:
When we installed a node on a host named app16-perf.qa.ourcompany.c{{om}}, Flume decided the node name was {{app16-perf.qa..ourcompany.com}}. Note the extra period. We are completely unclear why this happened.
Even worse, however, is that it is unclear in the documentation how to override the default physical node name in the configuration. Where does that go, exactly?
Without either a fix to this (so that the default physical node name is precisely as the documentation says it is, the output of the "hostname" command) or a way to configure this parameter in the flume-site.xml file, we are kind of hosed with auto-deploying flume agents on our servers.
It's possible I missed something in the documentation - I looked for the word "hostname" and did not find anything covering this in the User Guide.
was:
When we installed a node on a host name app16-perf.qa.ourcompany.com, Flume decided the node name was "app16-perf.qa..ourcompany.com". Note the extra period. We are completely unclear why this happened.
Even worse, however, is that it is unclear in the documentation how to override the default physical node name in the configuration. Where does that go, exactly?
Without either a fix to this (so that the default physical node name is precisely as the documentation says it is, the output of the "hostname" command) or a way to configure this parameter in the flume-site.xml file, we are kind of hosed with auto-deploying flume agents on our servers.
It's possible I missed something in the documentation - I looked for the word "hostname" and did not find anything covering this in the User Guide.
> Vlingo physical node name not the same as hostname output (extra . in name) which makes it hard to auto-install
> ---------------------------------------------------------------------------------------------------------------
>
> Key: FLUME-1039
> URL: https://issues.apache.org/jira/browse/FLUME-1039
> Project: Flume
> Issue Type: Bug
> Components: Docs, Node
> Affects Versions: v0.9.4
> Environment: CentOS Linux
> Reporter: Thomas Andrews
>
> When we installed a node on a host named app16-perf.qa.ourcompany.c{{om}}, Flume decided the node name was {{app16-perf.qa..ourcompany.com}}. Note the extra period. We are completely unclear why this happened.
> Even worse, however, is that it is unclear in the documentation how to override the default physical node name in the configuration. Where does that go, exactly?
> Without either a fix to this (so that the default physical node name is precisely as the documentation says it is, the output of the "hostname" command) or a way to configure this parameter in the flume-site.xml file, we are kind of hosed with auto-deploying flume agents on our servers.
> It's possible I missed something in the documentation - I looked for the word "hostname" and did not find anything covering this in the User Guide.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira