Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(ssl/apache2): Port conflict in ports.conf.gen #7225

Merged
merged 1 commit into from
Jul 15, 2019

Conversation

pdelagrave
Copy link

The Deck pod was failing to start after a recent apache2 version bump in the image(2.4.25 to 2.4.38): (98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:9000
Happening only when SSL was enabled.
Starting from apache2 2.4.28, having multiple Listen directive listening to the same socket is forbidden:

In this case, no need for multiple Listen directive as we always listen on one socket whether SSL is enabled or not.

The Deck pod was failing to start after a recent apache2 version bump in the image(2.4.25 to 2.4.38): `(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:9000`
Happening only when SSL was enabled.
Starting from apache2 2.4.28, having multiple `Listen` directive listening to the same socket is forbidden:
- https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/CHANGES
- https://httpd.apache.org/docs/2.4/mod/mpm_common.html#listen

In this case, no need for multiple Listen directive as we always listen on one socket whether SSL is enabled or not.
@Jammy-Louie Jammy-Louie merged commit 13c4b82 into spinnaker:master Jul 15, 2019
@ezimanyi
Copy link
Contributor

@spinnakerbot cherry-pick 1.15

@ezimanyi
Copy link
Contributor

@spinnakerbot cherry-pick 1.14

spinnakerbot pushed a commit that referenced this pull request Jul 16, 2019
The Deck pod was failing to start after a recent apache2 version bump in the image(2.4.25 to 2.4.38): `(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:9000`
Happening only when SSL was enabled.
Starting from apache2 2.4.28, having multiple `Listen` directive listening to the same socket is forbidden:
- https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/CHANGES
- https://httpd.apache.org/docs/2.4/mod/mpm_common.html#listen

In this case, no need for multiple Listen directive as we always listen on one socket whether SSL is enabled or not.
@spinnakerbot
Copy link
Contributor

Cherry pick successful: #7233

spinnakerbot pushed a commit that referenced this pull request Jul 16, 2019
The Deck pod was failing to start after a recent apache2 version bump in the image(2.4.25 to 2.4.38): `(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:9000`
Happening only when SSL was enabled.
Starting from apache2 2.4.28, having multiple `Listen` directive listening to the same socket is forbidden:
- https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/CHANGES
- https://httpd.apache.org/docs/2.4/mod/mpm_common.html#listen

In this case, no need for multiple Listen directive as we always listen on one socket whether SSL is enabled or not.
@spinnakerbot
Copy link
Contributor

Cherry pick successful: #7234

ezimanyi pushed a commit that referenced this pull request Jul 16, 2019
The Deck pod was failing to start after a recent apache2 version bump in the image(2.4.25 to 2.4.38): `(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:9000`
Happening only when SSL was enabled.
Starting from apache2 2.4.28, having multiple `Listen` directive listening to the same socket is forbidden:
- https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/CHANGES
- https://httpd.apache.org/docs/2.4/mod/mpm_common.html#listen

In this case, no need for multiple Listen directive as we always listen on one socket whether SSL is enabled or not.
ezimanyi pushed a commit that referenced this pull request Jul 16, 2019
The Deck pod was failing to start after a recent apache2 version bump in the image(2.4.25 to 2.4.38): `(98)Address already in use: AH00072: make_sock: could not bind to address 0.0.0.0:9000`
Happening only when SSL was enabled.
Starting from apache2 2.4.28, having multiple `Listen` directive listening to the same socket is forbidden:
- https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x/CHANGES
- https://httpd.apache.org/docs/2.4/mod/mpm_common.html#listen

In this case, no need for multiple Listen directive as we always listen on one socket whether SSL is enabled or not.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants