Bug 764805 (GLUSTER-3073) - Change documentation for AMI appliance to add port 80 as a requirement [NEEDINFO]
Summary: Change documentation for AMI appliance to add port 80 as a requirement
Alias: GLUSTER-3073
Product: Gluster-Documentation
Classification: Community
Component: Other
Version: unspecified
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Anjana Suparna Sriram
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2011-06-22 20:33 UTC by Eco
Modified: 2022-06-07 18:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
divya: needinfo? (eco)

Attachments (Terms of Use)

Description Eco 2011-06-22 17:41:29 UTC
Per Craig, this only affects AMI instances running in a VPC.  He is following up with Amazon to clarify what we need to document in such cases and will close or update this bug as appropriate.

Comment 1 Eco 2011-06-22 20:33:55 UTC
Please add port 80 to the list of required ports for the Amazon instances.

It was discovered recently on the dl-hacking thread that Amazon requires port 80 to communicate via it's CLI which we utilize.  Excerpts included for reference below.  Changes should be made in the release notes, pdf and online documentation as appropriate.


The Amazon API (ec2-*) works on port 80, that's probably it.

On Jun 22, 2011, at 12:55, "Harshavardhana" <harsha> wrote:
strange why does nmap checks for port 80? and btw who is checking for port 80? 

On Wed, Jun 22, 2011 at 8:39 AM, Anand Avati <avati> wrote:
OK, this looks to be an nmap issue. The exact command we use is

nmap -n -p 24007 HOSTNAME

Looking into tcpdump while running this command results in an attempt
to establish a connection to port 80! Having port 80 filtered is
causing nmap to declare that the node is down altogether. Please
include port 80 in the list of ports.

>> From: Jacob Shucart [jacob]
> Sent: Friday, May 27, 2011 11:21 AM

> I had a user open up the following ports in their Amazon security group:

> TCP: 22
> TCP: 111
> TCP: 3389
> TCP: 24007 - 24099
> UDP: 24007 - 24099
> When they try to use gluster-ami-newinstance, it gets stuck with:
> Waiting for 1 instance(s) to start Gluster services ... (still booting)
> Waiting for 1 instance(s) to start Gluster services ... (still booting)

Comment 2 Divya 2012-03-13 11:02:05 UTC

Could you please confirm if this bug is still valid for RHSSA?


Note You need to log in before you can comment on or make changes to this bug.