Description:
"SYS_ERROR pgm initialize failure" error thrown when trying to start the Rules Management Server on a Linux VMware image.



Symptoms:
The following error appears when trying to start RMS using the command line in a Linux VMware image.

2014 May 02 07:58:36:936 GMT -5 D1R55O11G2 Warning [main] - [as.runtime.cluster.om.daoprovider] Failed connecting to [Metaspace:RMS_Cache] with error SYS_ERROR (pgm initialize failure - Unknown parameter). Retrying in [10] seconds
2014 May 02 07:58:46:940 GMT -5 D1R55O11G2 Warning [main] - [as.runtime.cluster.om.daoprovider] Failed connecting to [Metaspace:RMS_Cache] with error SYS_ERROR (pgm initialize failure - Unknown parameter). Retrying in [10] seconds

In RMS.cdd the property has been defined:
 <property name="be.engine.cluster.as.discover.url" value="tibpgm://1234/0.0.0.0;1.2.3.4/"/>


Cause:
The cause is not directly related to TIBCO BusinessEvents, rather an error in the customer's environment.

The following checks can be performed:

1). Confirm that the IP Address for the machine matches the "real" IP Address by validating the settings in /etc/hosts file.

 The command to return the IP address: ifconfig

If the property be.engine.cluster.as.discover.url was removed, add it back into the original place in the be-rms.cdd file.  


2). Validate Active Spaces by executing, "as-admin" and create/join the metaspace.

 Open the terminal and move to AS_HOME  ("cd /home/tibco/as/2.0/lib").

 Add <TIBCO_HOME>/as/2.0/lib to LD_LIBRARY_PATH ("export LD_LIBRARY_PATH=/home/tibco/as/2.0/lib:$LD_LIBRARY_PATH").

 Execute the following as admin:

"/home/tibco/tibcojre64/1.6.0/bin/java -jar as-admin.jar"

 join/create the existing cluster with discoveryURL "tibpgm://1234/0.0.0.0;1.2.3.4/" .

"Connect name 'cache' discovery 'tibpgm://1234/0.0.0.0;1.2.3.4/' " .

Restart the RMS server.


3). Install and configure a loopback adapter on the machine.

For a Virtual environment you can refer to the following:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026955

Repeat Step 2 to validate if "as-admin" is able to connect and join the metaspace.