additional info: nsslapd-maxdescriptors: invalid value "65536", maximum file descriptors must range from 1 to 8192 (the current process limit). Server will use a setting of 8192.
my freeipa 4.3 May I ask, this parameter cannot be increased, this limit refers to where the limit?Can the system see if it can reach 262140, or is there another configuration limit in the service? apt list | grep 389-ds 389-ds/xenial,xenial 1.3.4.9-1 all ....
ldapmodify -x -H "ldaps://xx.com:636" -D "cn=directory manager" -w xxx dn: cn=config changetype: modify replace: nsslapd-maxdescriptors nsslapd-maxdescriptors: 65536
modifying entry "cn=config" ldap_modify: Server is unwilling to perform (53) additional info: nsslapd-maxdescriptors: invalid value "65536", maximum file descriptors must range from 1 to 8192 (the current process limit). Server will use a setting of 8192.
----- ulimit -aH core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 512646 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 262140 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) 512646 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
ulimit -Hn 262140
roy liang via FreeIPA-devel wrote:
my freeipa 4.3 May I ask, this parameter cannot be increased, this limit refers to where the limit?Can the system see if it can reach 262140, or is there another configuration limit in the service? apt list | grep 389-ds 389-ds/xenial,xenial 1.3.4.9-1 all ....
ldapmodify -x -H "ldaps://xx.com:636" -D "cn=directory manager" -w xxx dn: cn=config changetype: modify replace: nsslapd-maxdescriptors nsslapd-maxdescriptors: 65536
modifying entry "cn=config" ldap_modify: Server is unwilling to perform (53) additional info: nsslapd-maxdescriptors: invalid value "65536", maximum file descriptors must range from 1 to 8192 (the current process limit). Server will use a setting of 8192.
ulimit -aH core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 512646 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 262140 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) 512646 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
ulimit -Hn 262140
I guess you have a per-user or per-service limit set. The max value is determined using:
getrlimit(RLIMIT_NOFILE, &rlp)
Do you have a LimitNOFILE set in the dirsrv systemd configuration perhaps? Maybe setting it there would help.
rob
dirsrv systemd configuration LimitNOFILE =8192
And sure enough, that's the configuration that limits it. It says, well, just increase the value thanks again
Hi,
On Wed, Dec 14, 2022 at 10:35 AM roy liang via FreeIPA-devel < freeipa-devel@lists.fedorahosted.org> wrote:
my freeipa 4.3 May I ask, this parameter cannot be increased, this limit refers to where the limit?Can the system see if it can reach 262140, or is there another configuration limit in the service? apt list | grep 389-ds 389-ds/xenial,xenial 1.3.4.9-1 all ....
ldapmodify -x -H "ldaps://xx.com:636" -D "cn=directory manager" -w xxx dn: cn=config changetype: modify replace: nsslapd-maxdescriptors nsslapd-maxdescriptors: 65536
modifying entry "cn=config" ldap_modify: Server is unwilling to perform (53) additional info: nsslapd-maxdescriptors: invalid value "65536", maximum file descriptors must range from 1 to 8192 (the current process limit). Server will use a setting of 8192.
According to nsslapd-maxdescriptors [1] description in RHDS Configuration
and schema reference: ----- 8< ----- The number given here should not be greater than the total number of file descriptors that the operating system allows the ns-slapd process to use. This number differs depending on the operating system. ----- >8 -----
On RHEL or fedora, the directory server is started through systemd and you can change the value LimitNOFILE=<val> as described in /usr/lib/systemd/system/dirsrv@.service.d/custom.conf: # To change any of the below values, please use a drop-in file in which # you can declare overrides according to systemd.unit(5), either of: # - applying to all instances: # /etc/systemd/system/dirsrv@.service.d/custom.conf # - applying to a single instance (overriding the above): # /etc/systemd/system/dirsrv@<instance>.service.d/custom.conf
HTH, flo
[1] https://access.redhat.com/documentation/en-us/red_hat_directory_server/12/ht...
ulimit -aH core file size (blocks, -c) unlimited data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 512646 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 262140 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) unlimited cpu time (seconds, -t) unlimited max user processes (-u) 512646 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited
ulimit -Hn 262140
FreeIPA-devel mailing list -- freeipa-devel@lists.fedorahosted.org To unsubscribe send an email to freeipa-devel-leave@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/freeipa-devel@lists.fedorahoste... Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
thank
freeipa-devel@lists.fedorahosted.org
-
Florence Blanc-Renaud -
Rob Crittenden -
roy liang