<html><body><div style="font-family: Arial, Helvetica, sans-serif; font-size: 12pt; color: #000000"><div>This is a very busy server and tried to push our programming department to move to persistent connections, they feel that it could be a security issue if dealing with sensitive information since that connection could be hijacked. We do not have an issue on the mysql server side with <span style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;" data-mce-style="color: #000000; font-family: Arial, Helvetica, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">Port Exhaustion, just on the "Frontend webserver". We have made a lot of changes, and are currently managing but I fear that we will reach the 65k limit again. If I could get something to load balance LAN interfaces I could double the port limitation. I see that haproxy has an article on this, I love nginx and use it for other applications but maybe its the wrong product for this senerio. I was thinking there might be a way using proxy_bind. </span><!--EndFragment--><div style="clear: both;" data-mce-style="clear: both;"><br data-mce-bogus="1"></div></div><div data-marker="__SIG_PRE__"><div><a href="https://www.haproxy.com/blog/haproxy-high-mysql-request-rate-and-tcp-source-port-exhaustion/" data-mce-href="https://www.haproxy.com/blog/haproxy-high-mysql-request-rate-and-tcp-source-port-exhaustion/">https://www.haproxy.com/blog/haproxy-high-mysql-request-rate-and-tcp-source-port-exhaustion/</a></div><div><span></span><div><span style="font-size: medium;"><strong><br data-mce-bogus="1"></strong></span></div><div><span style="font-size: medium;"><strong><br data-mce-bogus="1"></strong></span></div><div><span style="font-size: medium;"><strong><br data-mce-bogus="1"></strong></span></div><div><span style="font-size: medium;"><strong>Best Regards,</strong> <br>
</span> <span style="color: #666666;"><b><span style="font-family: arial, helvetica, sans-serif;">
Brandon Mallory</span><br>
Network & Systems Engineer<br>
<span style="color: #339999;"><b>MEDENT EMR/EHR</b><br>
</span> <span style="color: #666666;"><b>
15 Hulbert Street<br>
Auburn, NY 13021<br>
Phone: <span class="Object" id="OBJ_PREFIX _DWT174_com_zimbra_phone"><a href="callto:(315)-255-0900" target="_blank">(315)-255-0900</a></span><br>
Fax: <span class="Object" id="OBJ_PREFIX_DWT175_com_zimbra_phone"><a href="callto:(315)-255-3539" target="_blank">(315)-255-3539</a></span><a><br>
Web: <span class="Object" id="OBJ_PREFIX_DWT177_com_zimbra_url"></span></a><a target="_blank" href="http://www.medent.com">www.medent.com</a></b></span></b></span><b><b><br><br>
<img src="https://webmail.medent.com/zimbra/sigs/defmailsig_nocchit.jpg" style="border: 0pt none;"><br><br>
This message and any attachments may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail or the information contained herein is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by e-mail, and permanently delete this e-mail.<br></b></b></div><div><b><b><br><span></span><br></b></b></div></div></div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Reinis Rozitis" <r@roze.lv><br><b>To: </b>"nginx" <nginx@nginx.org><br><b>Sent: </b>Thursday, May 16, 2019 9:35:18 AM<br><b>Subject: </b>RE: Port Exhaustion - SQL<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">> Yes all of those changes you have mentioned have been made. <br><br>Well imo there is nothing else besides to even more decrease the FIN timeout (in a LAN that shouldn't be an issue (no slow clients)) so the lingering sockets are closed faster.<br><br>Also instead of adding the network adapter(s) on the webserver you should add the interfaces on the mysql server and then either via loadbalancer or on application level use a round robin fashion (as binding to a specific local interface is harder than just connect to a different remote ip).<br><br><br>Other than that depending on the application you might want to consider using persistent connections to MySQL or use some kind of mysql proxy between which could pool the connections to the mysql server.<br><br>rr<br><br>_______________________________________________<br>nginx mailing list<br>nginx@nginx.org<br>http://mailman.nginx.org/mailman/listinfo/nginx<br></div></div></body></html>