Frank Liu
June 21, 2018 06:52PM
The issue is with this:

<mailproxy-lb-01.peak.org> [150] # service nginx restart
Stopping nginx: [FAILED]

Since stopping FAILED, the IP/port still in use. That's why start failed
with "binding" error.

You can try "service nginx stop" along and check error log to see why it
failed to stop.




On Thu, Jun 21, 2018 at 3:12 PM, abatie <nginx-forum@forum.nginx.org> wrote:

> I believe this is related to blocking neighbor discovery on the address for
> the purposes of doing direct server return load balancing, and not nginx
> related, thanks!
>
> Posted at Nginx Forum: https://forum.nginx.org/read.
> php?2,280234,280239#msg-280239
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

dual stack binding

abatie June 21, 2018 04:37PM

Re: dual stack binding

Steve Wilson June 21, 2018 05:38PM

Re: dual stack binding

abatie June 21, 2018 05:43PM

Re: dual stack binding

abatie June 21, 2018 05:45PM

Re: dual stack binding

abatie June 21, 2018 06:12PM

Re: dual stack binding

Frank Liu June 21, 2018 06:52PM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 78
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready