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

HAProxy can't start #3541

Closed
josephapg opened this issue Sep 14, 2018 · 2 comments
Closed

HAProxy can't start #3541

josephapg opened this issue Sep 14, 2018 · 2 comments

Comments

@josephapg
Copy link

josephapg commented Sep 14, 2018

Windows build number: 10.0.17134.285
Distro: Ubuntu 18.04.1 LTS

Installed HAProxy 1.8.13 from vbernat's ppa and here's what happened when I tried to start it:

[WARNING]: Failed to get the default value of TCP_MAXSEG
[WARNING]: Failed to get the default value of TCP_MAXSEG for IPv6
[ALERT]: Starting frontend http: cannot bind socket [0.0.0.0:80]
[ALERT]: Starting frontend https: cannot bind socket [0.0.0.0:443]

netstat -anp shows no processes listening on port 80 and 443.

@therealkenc
Copy link
Collaborator

therealkenc commented Sep 14, 2018

You deleted the template. Note second sentence.

cannot bind socket [0.0.0.0:443]

That port is open in in Windows and thus can't be bound. I assume port 80 is too ~!, but there is no (straightforward) way to not bind 443 in windows.~~

[WARNING]: Failed to get the default value of TCP_MAXSEG

An strace would show the setsockopt(2) failing, but it it looks like a soft fail. Hasn't been reported before AFAIK. Suppose this issue can be the landing zone for that.

netstat -anp shows no processes listening on port 80 and 443.

#2249. From the CMD prompt do netstat.exe -an | find.exe "443"

[ed] Guh I mixed up port 443 and 445 in my head. Close/disable/dontrun whatever is consuming 80/443 and see if it fares any better. It might; it might fail for other reasons. The TCP_MAXSEG warning can probably be ignored.

@josephapg
Copy link
Author

Hi, @therealkenc!

Somehow it works after I did a reset from apps & features.

The TCP_MAXSEG warning can probably be ignored.

Yes, you're correct. Now it works even with that warning.

Thanks for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants