Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Hazelcast errors observed in log on server startup



Hazelcast clustering errors are observed during server startup in the PegaRULES logfile.

Error Messages

Interfaces is disabled, trying to pick one address from TCP-IP config addresses: [IP]

...Could not find a match for URL

Steps to Reproduce

This occurs when Pega starts up a single node system. The system is isolated and cannot access the IP address stated in the error message.

Root Cause

An erroneous or stale IP address was in the py_sys_statusnodes database table. It was in py_sys_statusnodes because there had, at one time, been a deployment of this system at this location before being undeployed.

Due to firewall or other network settings, hazelcast could not reach the IP address in the error message to determine that the node is offline and instead throws the observed network error.



TRUNCATE py_sys_statusnodes to resolve this issue. This removes the record of the non-existant node(s) from the database and hazelcast does not search for them during startup.

Pega rebuilds the py_sys_statusnodes automaticall, with the nodes that are in use.


Published January 31, 2016 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us