|
|
|
When the Policy Server is placed under load, it opens a large number of sockets and files. This can become a problem if the default limit parameters are not appropriate for the load. You modify the default limit parameters to avoid associated problems.
To view the default limit parameters, type ulimit -a. The system displays a message similar to the following:
|
$ ulimit -a |
|
|
time(seconds) |
unlimited |
|
file(blocks) |
unlimited |
|
data(kbytes |
2097148 |
|
stack(kbytes) |
8192 |
|
coredump(blocks) |
unlimited |
|
nofiles(descriptors) |
256 |
|
vmemory(kbytes) |
unlimited |
The nofiles parameter is set to 256 in this example. This is the total number of files (sockets + files descriptors) that this shell and its descendants have been allocated. If this parameter is not set high enough, the Policy Server returns numerous socket errors. The most common socket error is 10024, or too many open files.
You must increase this parameter value for proper Policy Server operation under load. You can change this value by running the ulimit -n command. For example, to set nofiles to 1024, place the ulimit -n 1024 command in the .profile or smprofile.ksh of the smuser account. The Policy Server is bound by the nofiles parameter within smuser's ulimit for the number of connections to it.
Note: On HP-UX systems, prior to the Policy Server installation, check your .profile file for a set +u option. If it has a set -u option, do a set +u to nullify it. A setting of set -u will cause a problem when the installation sets a SHLIB_PATH for smuser.
| Copyright © 2010 CA. All rights reserved. | Email CA about this topic |