all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Mark Schouten" <mark@tuxis.nl>
To: "Thomas Lamprecht" <t.lamprecht@proxmox.com>,
	"Proxmox Backup Server development discussion"
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] Too many open files
Date: Fri, 09 Sep 2022 08:31:44 +0000	[thread overview]
Message-ID: <emda8dd7ed-8534-4281-ab2c-89ae1957db0c@3a15c2fd.com> (raw)
In-Reply-To: <87a756b4-ef3a-47c4-2219-df252b7cce9d@proxmox.com>

Hi,



>How many FDs are open for the proxy?
>
>ls -1 /proc/$(pidof proxmox-backup-proxy)/fd | wc -l


This was not that much at this moment, but aroung 0.00 hours, the 
counter increases, I suspect. ;)

>No, but it doesn't increase it's soft limit to the hard limit, something we
>want to do in the future.
>
>As workaround try increasing soft (and possible hard) limit for root and backup
>user, you can do that by editing `/etc/security/limits.conf`, adding lines like:
>
>backup soft nofile 524288
>root soft nofile 524288
>
>(should set soft to current hard limit)

This did not work for me.

>Or alternatively use a systemd service override to make it really process specific:
>
># systemctl edit proxmox-backup-proxy.service
>
>There add a "[Service]" Section, if not already existing and a "LimitNOFILE=X" below,
>e.g.:
>
>[Service]
>LimitNOFILE=524288
>
>Save and close the editor and restart the service, then do the same for the
>proxmox-backup.service
>
>As said, we plan to upper that soft limit too in the future.

This worked like a charm. Let’s see if it helps tonight during peak 
hours.

Thanks!


—
Mark Schouten, CTO
Tuxis B.V.
mark@tuxis.nl




      reply	other threads:[~2022-09-09  8:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 12:02 Mark Schouten
2022-09-08  7:08 ` Thomas Lamprecht
2022-09-09  8:31   ` Mark Schouten [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=emda8dd7ed-8534-4281-ab2c-89ae1957db0c@3a15c2fd.com \
    --to=mark@tuxis.nl \
    --cc=pbs-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal