Juniper NETWORK AND SECURITY MANAGER 2010.4 - REV1, Installation Manual, Page: 236 / 244

The defaults mentioned here are configured by NSM during initial installation. In some
cases, the actual PostgreSQL default values are not indicated.
Shared Memory
When you configure the PostgreSQL server to perform better with more shared memory,
the devSvrDbSvr (postmaster) process may not come up if the system does not support
it. In such cases, after a failed run of devSvrDbSvr, you can identify the actual memory
requirement from the following file:
$NSROOT/DevSvr/var/pgsql/data/psql.log file
The error appears as follows:
"Failed system call was shmget(key=5432001, size=145408000, 03600)"
Note that size specifies the required shared memory. You can then update the shared
memory requirement.
On Solaris systems, add/update the following line in
/etc/system
:
set shmsys:shminfo_shmmax=<required shared mem>'
set shmsys:shminfo_shmmin=1
set shmsys:shminfo_shmmni=256
set shmsys:shminfo_shmseg=256
set semsys:seminfo_semmap=256
set semsys:seminfo_semmni=512
set semsys:seminfo_semmns=512
set semsys:seminfo_semmsl=32
On Linux systems, add/update the following line in
/etc/sysctl.conf
:
kernel.shmmax=<required shared mem>'
After updating the shared memory requirements, you must restart the system.
Device Server
You can also configure settings on the Device Server to improve the performance of the
Profiler DB. Table 38 on page 214 describes parameters in the Device Server configuration
file (devSvr.cfg) that affect performance.
Table 38: Device Server Settings
Default
Value
Description Parameter
Notice For debugging, info is most useful, but
will potentially generate lots of logs. profilerMgr.printLevel
300
seconds A profiler session times out of time
exceeds this configured value. profilerMgr.receiver.pktIntTimeoutInSec
Copyright © 2010, Juniper Networks, Inc. 214
Network and Security Manager Installation Guide