A QcnProcessRunner temporary file is preventing the FMS from starting up.
Example: FMS log entries:
<external process launcher> WARN [main] Launcher/src/process_runner - stderr: 2012-01-23 14:47:56.000 ERROR [native] (internal error) Could not bind socket to path /tmp/QcnProcessRunner-cbd49855edd4f01390663508b047d615.msg to listen for messages: Address already in use
<external process launcher> WARN [main] Launcher/src/process_runner - stderr: 2012-01-23 14:47:56.000 FATAL [native] Could not Quest Process Runner communications channel
ERROR [main] QcnUtil/src/unix/qcn_message_unix - Could not transmit the inter-launcher communications message as you are not the owner of the process the message is destined for. Local 15100, Remote 0.
ERROR [main] com.quest.nitro.db.EmbeddedDatabaseManager - Cant run command: {0}
java.io.IOException: Could not transmit inter-launcher communications message. Check the logs for more information.
An FMS crash or former service temporary files in the sytem /tmp folder is bound as root or another user preventing the foglight service account to overwrite and start.
Workaround 1
