Announcements

SecurID® Discussions

Browse the SecurID discussion board to get product help and collaborate with other SecurID users.
SpencerMay
Beginner
Beginner

Web Tier - Get a open files limit error when checking web tier server or bootstrapper status

Jump to solution

I get the following error when checking status of web tier server or bootstrapper.  The status is returned but it also returns this message.  Any thoughts?  I verified the open files had limit is set above 4096.

 

line 20: ulimit: open files: cannot modify limit: Operation not permitted

Labels (1)
0 Likes
1 Solution

Accepted Solutions
EdwardDavis
Employee
Employee

Try this increase, 65536 should cause no issues.

 

 

 set the ulimit of the install user(username) to 65536 in /etc/security/limits.conf

 

username hard nofile 65536
username soft nofile 65536

View solution in original post

4 Replies
EdwardDavis
Employee
Employee

Try this increase, 65536 should cause no issues.

 

 

 set the ulimit of the install user(username) to 65536 in /etc/security/limits.conf

 

username hard nofile 65536
username soft nofile 65536

I'm seeing this at a customer too.  if you run ulimit on the command line, it returns "unlimited," but when used by rsaserv (8.4 p1 webtier) it generates the ulimit not permitted message mentioned above. It doesn't stop anything from running, but it's annoying.

 

-bash-4.1$ cd server

-bash-4.1$ ls

apps           bin        edit.lok              lib          orchestration  servers

autodeploy     config     fileRealm.properties  logs         rsaserv        startWebLogic.sh

backup_config  downloads  init-info             nodemanager  security       wrapper

-bash-4.1$ ./rsaserv status

./rsaserv: line 20: ulimit: open files: cannot modify limit: Operation not permitted

RSA Webtier Server                                         [RUNNING]

 

-bash-4.1$ ulimit

unlimited

-bash-4.1$

Thanks.  I've requested the ulimit set to 65536 as mentioned.  Once set by our *nix team I'll check for resolution.

0 Likes

That's the behavior we are experiencing.  If I use the ulimit command we have unlimited as well.  If I do ulimit -Hn or ulimit -Sn we currently have 8192 set.  Hopefully Edwards suggestion will resolve it.

0 Likes