Resolution:
Description:
============
KTP switch installation fails unexpectedly with a timeout on coordinator startup. A fatal stack trace in the log reports a SMResourceError error.

Environment:
===========
TIBCO® KTP 3.x

Symptoms:
========
Switch installation failure with the following terminal output:

        Installing node mdnode_nss04...

        Starting node mdnode_nss04 ...
                Installing Registry ...
                Updating Registry ...

swsrv: mdnode_nss04: Timeout waiting for coordinator to start

Install switch failed

The following trace should be seen in the coordinator log file:

2011-12-22 16:08:32.247877|SCD|INFO |21536|syscoor.cpp(899)|Start of Coordinator initialization
2011-12-22 16:08:32.247955|SCD|INFO |21536|syscoor.cpp(912)|SW_HOME environment variable is set to /app/local/sawara/PZZ4/opt/kabira
2011-12-22 16:08:32.263669|EXP|WARN |21536|syscoor.cpp(974)|CATCH(DSEException)
2011-12-22 16:08:32.263743|EXP|WARN |21536|dseexcpt.cpp(406)|STACK TRACE:
  +++ START +++
    psmem.cpp (499): THROW SWSMemory::SMResourceError: reason: 'Operating system error: function 'shmget': error code (22): error string 'Invalid argument''
    psmemshm.cpp (185): RETHROW SWSMemory::SMResourceError
    psmem.cpp (222): RETHROW SWSMemory::SMResourceError
    psmem.cpp (260): RETHROW SWSMemory::SMResourceError
    smmgr.cpp (765): RETHROW SWSMemory::SMResourceError
    smmgr.cpp (828): RETHROW SWSMemory::SMResourceError
    osstmgr.cpp (511): RETHROW SWSMemory::SMResourceError
    osstmgr.cpp (655): RETHROW SWSMemory::SMResourceError
    syscoor.cpp (974): DUMP SWSMemory::SMResourceError
  +++ END +++
2011-12-22 16:08:32.263763|SCD|FATAL|21536|syscoor.cpp(980)|createStateManager: Failed to create state manager for node mdnode_nss04
2011-12-22 16:08:32.263782|SCD|FATAL|21536|syscoor.cpp(1309)|SWSysCoord::abort.  Coordinator process 21536 exiting!

Cause:
========
The error occurs because the shared memory segment size (see parameter memorysize) is greater than the max-shm-memory kernel parameter.  

Resolution:
==========
Either increase the max-shm-memory kernel parameter, or use an allowed "memorysize" value.