You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Tim Robertson (Created) (JIRA)" <ji...@apache.org> on 2012/01/30 11:05:10 UTC

[jira] [Created] (WHIRR-491) Improve logging when network firewalls are blocking access

Improve logging when network firewalls are blocking access
----------------------------------------------------------

                 Key: WHIRR-491
                 URL: https://issues.apache.org/jira/browse/WHIRR-491
             Project: Whirr
          Issue Type: Improvement
    Affects Versions: 0.7.0
            Reporter: Tim Robertson
            Priority: Trivial


I am a newbie who was standing up an HBase on EC2.
In my instance it partially worked - the VHs came up, the data nodes had all their services started, but the master did not.  The logs did not provide any pointers to the cause of the problem - my network admins had blocked certain ports on the firewall and hence the bootstrapping failed.

The improvement I propose would be as soon as the VHs come up, it does some diagnostic checking and reports clearly if there are connection issues.  I presume this is quite tricky as different modules will require different ports / protocols, but a diagnostic stage on launch might help debug issues for newbies like me.  Alternatively the HBase module logging might benefit from some diagnostic stage, or report that it failed to copy the config up.

--
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