The below warning shows up quite frequently in Confluence, and I saw from other questions that this can easily be solved by setting limits.conf. The challenge with this however, is that the Linux distribution that comes with my Linux device does not have such a file. Regardless though, I can normally query user limits using "ulimit -a" , so I'm wondering if there's another fix I can apply to help Confluence determine the configured process limit ?
2020-10-17 19:34:11,282 WARN [HealthCheck:thread-2] [troubleshooting.stp.spi.DefaultFileSystemInfo] lambda$getThreadLimit$0 Failed to determine the configured process limit
Hello @Jaap !
The limitation you presented “my Linux device does not have such a file” is quite interesting. Usually the limits.conf file is located under /etc/security/.
Since you are still able to use ulimit, you could try to temporarily set the limits with ulimit. As described in our documents:
We recommend setting the maximum running user processes and number of opened files permanently, the way you do this is operating system specific. In most Linux distributions this can be set temporarily using ulimit or permanently using limits.conf (e.g. Ubuntu, RedHat) by adding the following:
You can check the whole document and also the Man page for ulimit here:
Further, would you mind sharing what distribution of Linux are you using? This could help us to understand why the file or manual adjustment for the limits is not present in your system.
Let us hear from you!
I'm running a Confluence lab setup on a NAS device (embedded linux), which uses busybox builtin commands by default.
System-wide looking for limits.conf (excluding docker plugin):
$ updatedb && locate limits.conf | grep -v docker_lib | wc -l
Similarly searching for a security folder yields the following folders:
/sys/kernel/security (empty folder)
/usr/lib/security (only has .so libraries)
Even though, the system still outputs these limits:
$ ulimit -a
-f: file size (blocks) unlimited
-t: cpu time (seconds) unlimited
-d: data seg size (kb) unlimited
-s: stack size (kb) 8192
-c: core file size (blocks) 0
-m: resident set size (kb) unlimited
-l: locked memory (kb) 64
-p: processes 31300
-n: file descriptors 1024
-v: address space (kb) unlimited
-w: locks unlimited
-e: scheduling priority 0
-r: real-time priority 0
Interpreting the output, it seems the system has numerical limits in place for the limits described in Health Check: Thread Limit by default. Though not by the same amount.
-p: processes 31300 -> more then the advised amount of 8192
-n: file descriptors 1024 -> less then the advised amount of 8192
The exception however seem to talk about a NumberFormatException, which (I guess) could have to do with "unlimited". However seeing that actual numbers are in place, I feel it's more likely that Confluence is unable to read the limits altogether.
Any advise on what I can do to work around this is appreciated ?
Kind regards, Jaap
Hi, Confluence collaborators! As part of #Confluence-Collaboratory month, we’ve created a very special Mythsbusters segment, where we're dive into an interesting myth and uncover the truth behind i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events