1. Forum
  2. Usenet
  3. COMP.DATABASES.INGRES

  • File descriptor soft limit for the NET Server

    From Steve@21:1/5 to All on Fri Aug 28 02:30:59 2020
    Ingres reported the following warning on startup:

    WARNING!!! The recommended file descriptor soft limit for the NET Server to service 64 inbound, and 64 outbound connections is 261. The current file descriptor soft limit is set to 256.

    syscheck:
    Checking host "myhost" for system resources required to run
    Ingres...

    614 file descriptors per-process required.
    256 is the current system soft limit.

    Your system has sufficient resources to run
    Ingres.

    ulimit -a
    time(seconds) unlimited
    file(blocks) unlimited
    data(kbytes) unlimited
    stack(kbytes) 8192
    coredump(blocks) unlimited
    nofiles(descriptors) 256
    vmemory(kbytes) unlimited

    ulimit -aH
    time(seconds) unlimited
    file(blocks) unlimited
    data(kbytes) unlimited
    stack(kbytes) unlimited
    coredump(blocks) unlimited
    nofiles(descriptors) 65536
    vmemory(kbytes) unlimited

    Don't know why there is such a big difference between the soft and hard limits?

    Trying to understand what might have changed to cause this warning.

    Thanks
    Steve

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Karl Schendel@21:1/5 to Steve on Sat Aug 29 20:25:56 2020
    Copy: info-ingres@lists.planetingres.org

    On Aug 28, 2020, at 5:30 AM, Steve <s.anderson.au@gmail.com> wrote:

    Ingres reported the following warning on startup:

    WARNING!!! The recommended file descriptor soft limit for the NET Server to service 64 inbound, and 64 outbound connections is 261. The current file descriptor soft limit is set to 256.
    ...
    ulimit -a
    nofiles(descriptors) 256

    ulimit -aH
    nofiles(descriptors) 65536

    Don't know why there is such a big difference between the soft and hard limits?

    This is generally set by some sort of system configuration file; what
    OS are you running? Any change was likely caused either by an OS upgrade
    or some sort of system admin action; Ingres has little or no say in it.

    Karl

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Steve@21:1/5 to Karl Schendel on Mon Aug 31 19:04:10 2020
    On Sunday, August 30, 2020 at 10:26:04 AM UTC+10, Karl Schendel wrote:
    On Aug 28, 2020, at 5:30 AM, Steve <s.ande...@gmail.com> wrote:

    Ingres reported the following warning on startup:

    WARNING!!! The recommended file descriptor soft limit for the NET Server to service 64 inbound, and 64 outbound connections is 261. The current file descriptor soft limit is set to 256.
    ...
    ulimit -a
    nofiles(descriptors) 256

    ulimit -aH
    nofiles(descriptors) 65536

    Don't know why there is such a big difference between the soft and hard limits?
    This is generally set by some sort of system configuration file; what
    OS are you running? Any change was likely caused either by an OS upgrade
    or some sort of system admin action; Ingres has little or no say in it.

    Karl

    Running Solaris 10.

    I presume increasing the soft limit does not affect Ingres, in terms of its configuration, memory allocation, etc.

    Will highlight the soft limit with the administrator, God willing.

    Thanks
    Steve

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Steve@21:1/5 to All on Mon Nov 9 20:04:22 2020
    It seems the default soft and hard limits on 64-bit Solaris 10 are 256 and 65536 respectively.

    The soft limit can be set by any user and thus can be different across users. The soft limit change is lost upon logging out, if not added to the user's profile, for example.

    To check file limits:
    ulimit -Sn
    ulimit -Hn

    To change the soft limit:
    ulimit -Sn 2000

    Ingres indicated it needed 614 file descriptors per-process, so I set the soft limit to 2000.

    Steve

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)