PegaRULES initialization failed - server won't start
One particular Pega JVM is experiencing problems with starting up. This is a multi-node environment and other nodes are up and running.
[7/25/17 18:14:52:234 EDT] 000000a6 SystemOut O 2017-07-25 18:14:52,233 [your_host] [ STANDARD] [ ] [ ] ( internal.mgmt.PRNodeImpl) ERROR - Another node is using the same explicit temp directory on this system as this node (same SysNodeID Hash is being generated). Please change the temp directory on this node and restart
[7/25/17 18:14:52:247 EDT] 000000a6 SystemOut O 2017-07-25 18:14:52,241 [your_host] [ STANDARD] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: your_host
Steps to ReproduceNot Applicable
Root CauseA defect or configuration issue in the operating environment.
Another node is using the same explicit temp directory on this system as this node (same SysNodeID Hash is being generated) . Systemout.log from this Websphere instance shows the location of the
PegaRULES effective temp path.
[7/25/17 18:13:59:615 EDT] 000000a6 SystemOut O 2017-07-25 18:13:59,614 [your_host] [ ] [ ] [ ] (rnal.mgmt.InitialConfiguration) INFO - PegaRULES effective temp path: /your_usr/your_webspheres855/AppServer/profiles/Applications/temp/your_pega/your_PegaServer/your_prpcear/prweb.war
ResolutionThere are a few different ways to solve this:
- Add JVM argument -Dpega.tmpdir=<PegaRULES effective temp path> and restart.
- Add JVM argument -Didentification.nodeid=<your_uniqueNODE_ID> and restart.
Published August 26, 2017 - Updated October 8, 2020