BES 6.x : How to troubleshoot some common gatekeeper startup errors

Problem:

This article details some common errors when starting up the gatekeeper process, and their resolutions.

Error: Can"t find libjava.sl
The recommended resolution is to check for java path -- ensure the environment is pointing to the correct java launcher.
You can execute the following commands to check:
$ . ./vbroker.sh
$ which java
$ java -version
You cal also use -VBJdebug option to identify java VM, e.g.
$ gatekeeper -VBJdebug
If nothing is obviously wrong, you may want to explicitly state the correct JVM when starting gatekeeper:
$ gatekeeper -VBJjavavm /opt/java1.4/bin/java
Error: org.omg.CORBA.COMM_FAILURE: java.net.BindException: Permission denied
This error typically implies that the user login does NOT have the permission to open up port number smaller than 1024 -- by default gatekeeper uses port 683 for exterior iiop port, you can set a higher number.
So to overcome this error, you can either grant permission for the user to open up port less than 1024 or amend gatekeeper's default iiop port to a large number, e.g.
$ gatekeeper -Dvbroker.se.exterior.scm.ex-iiop.listener.port=11683
Error: java.io.FileNotFoundException: gatekeeper.ior (Permission denied)
This error indicates your user login does not have write permission to the folder where you launch gatekeeper.
Gatekeeper needs to create an IOR in the folder after successful startup.
To overcome this problem, you can either grant the user account write access to the folder or start gatekeeper with another location that you have write access, e.g.
$ gatekeeper -Dvbroker.gatekeeper.referenceStore=/tmp/gatekeeper.ior

Old KB# 26312