error Couldn't calc cores number [error 'open /proc/stat: too many open files']

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

error Couldn't calc cores number [error 'open /proc/stat: too many open files']

L2 Linker

Recently had some performance problems reported from my xsoar users.

Found a tenant crashing.  Upon investigating I found the following error in the logs:

App03 host:

error Couldn't calc cores number [error 'open /proc/stat: too many open files']error Couldn't calc cores number [error 'open /proc/stat: too many open files'] 

 

I set this on APP03 last night as a temporary band-aid until I could better understand:
https://docs.paloaltonetworks.com/cortex/cortex-xsoar/6-2/cortex-xsoar-multi-tenant-guide/manage-con...

 

 

Review other host nodes that I didn't touch I see the following:

ulimit -a for root shows:

open files                      (-n) 1024

 

DockerHardeningCheck shows:

jboyd98_0-1646331590341.png

Additionally:

jboyd98_1-1646331827555.png

 

This key does NOT exist under  Advanced /Troubleshooting:

jboyd98_2-1646331889270.png

 

Where is it pulling 1048576 from; where would this be set and whats the difference between that and my ulimit -a for root (there is no special config in /etc/security/limits.conf)

Any feedback is appreciated,

 

Boyd

 

1 REPLY 1

L3 Networker

Hi @jboyd98 , is this still an issue for you? Please open a support case with logs and screenshots. 

  • 1610 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!