• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Nginx: [error] accept4() failed Software caused connection abort

Scheduled Pinned Locked Moved Captive Portal
2 Posts 1 Posters 3.3k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • I
    idobudo
    last edited by Jan 3, 2017, 2:20 PM

    I get a lot of log entries like below, when a lot of users attemmpts to login captive portal et the same time:
      nginx: 2016/12/30 12:25:00 [error] 68189#102120: accept4() failed (53: Software caused connection abort)

    I tested with changing a lot of parameters like  "kern.ipc.somaxconn, net.inet.ip.intr_queue_maxlen, net.route.netisr_maxqlen, keepalive_timeout, worker_processes ,  worker_connections" but problem not solved.

    When I add the line "multi_accept on;" in the events block in "/etc/inc/system.inc" file, then my problem solved.

    I want to know if this "multi_accept on;" will make some wrong things to my pfsense? Will this make some bad impact? Have i done right?

    My pfsense is:
    Version 2.3.2-RELEASE-p1 (amd64)
    built on Tue Sep 27 12:13:07 CDT 2016
    FreeBSD 10.3-RELEASE-p9

    1 Reply Last reply Reply Quote 0
    • I
      idobudo
      last edited by Jan 4, 2017, 7:56 AM

      in sys file there is a method like below, in it I set.
      That method produces nginx config file.

      function system_generate_nginx_config(…)
      ....
      events {
          worker_connections  1024;
        **  multi_accept on;**
      }
      ….

      When I set "multi_accept on;" will it cause any problem?

      NOTE:
      The web sites about nginx saying like below about "multi_accept on;":

      • We've enabled multi_accept which causes nginx to attempt to immediately accept as many connections as it can.
      • The option multi_accept makes the worker process accept all new connections instead of serving on at a time.
      • If multi_accept is disabled, a worker process will accept one new connection at a time. Otherwise, a worker process will accept all new connections at a time.
      1 Reply Last reply Reply Quote 0
      2 out of 2
      • First post
        2/2
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
        This community forum collects and processes your personal information.
        consent.not_received