You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ambari.apache.org by "Waldyn Benbenek (JIRA)" <ji...@apache.org> on 2014/04/04 18:35:14 UTC

[jira] [Updated] (AMBARI-5351) Ganglia connection truncates name of network device and fails

     [ https://issues.apache.org/jira/browse/AMBARI-5351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Waldyn Benbenek updated AMBARI-5351:
------------------------------------

    Description: 
I am doing a manual agent setup on a SLES 11 SP3 system.  The network setup is unique.  Ambari server will be communicating with its agents on an infiniband network.  One of the devices configurations required by our network is eth-unused.  This appears to be too long a name for the ganlia and Nagios to handle as it gives an error saying that the device:  eth-unuse is not found.

I will send the log via the user ls email.
    Environment: SLES 11 Sp3

> Ganglia connection truncates name of network device and fails
> -------------------------------------------------------------
>
>                 Key: AMBARI-5351
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5351
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.4.4
>         Environment: SLES 11 Sp3
>            Reporter: Waldyn Benbenek
>
> I am doing a manual agent setup on a SLES 11 SP3 system.  The network setup is unique.  Ambari server will be communicating with its agents on an infiniband network.  One of the devices configurations required by our network is eth-unused.  This appears to be too long a name for the ganlia and Nagios to handle as it gives an error saying that the device:  eth-unuse is not found.
> I will send the log via the user ls email.



--
This message was sent by Atlassian JIRA
(v6.2#6252)