Question5Replies1002Views ANU_V Member since 2006 8 posts Virtusa Corp. Posted: 9 months agoLast activity: 6 months 1 week ago Error: Stream service is not running in the clusterApplication got upgraded from 7.1.8 to 8.2.3. we have 2 nodes. Admin studio shows system & nodes landing page shows Error: Stream service is not running in the cluster.Also when check the Stream status it says Unreachable and Joining_Fail for the nodesNodes list has stream node, but still getting stream not found issue. Any idea how to solve the issue System Administration Low-Code App Development Installation and Deployment Low-Code App Development Upgrades ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Posted: 9 months agogundk PEGA replied to ANU_VHi Please check the logs. Looks like binding issue. Add below DSS setting in prconfig.xml file. Each node should have different open port. <env name="dsm/services/stream/pyBrokerPort" value="xxxx" /> (default 9092) <env name="dsm/services/stream/pyKeeperPort" value="xxxx" /> (default 2181) <env name="dsm/services/stream/pyJmxPort" value="xxxx" /> ( default 9999) <env name="dsm/services/stream/pyPort" value="xxxx" /> (default 7003) Posted: 9 months agoANU_V Virtusa Corp. replied to gundkI have these settings in place. not sure how this can be given in each node level. we are using only DSS and no prconfig.xml Posted: 9 months agonayar2 PEGA replied to ANU_VFor the Stream node type, each JVM requires its own port for the Stream services. The Startup logs display port conflict messages. Can you share the start up logs to check the error. Posted: 9 months agoANU_V Virtusa Corp. replied to nayar2I have attached the logs. seems it is trying to access node 81b5db219df0289efcfce317d799e321 which not explicitly defined. not sure why it is trying to access 81b5db219df0289efcfce317d799e321 node. I have already given the all DSS given in the above reply. Please let me know how this issue can be fixed. currently search is also unable to enable due to this failure Posted: 6 months agochoky PEGA replied to ANU_VHi, As you have shown the nodes and status in the Decisioning > Infrastructure > Service > Stream path. Some of them has JOINING_FAILED and some are UNREACHABLE status. I think the desired node may be the one with status UNREACHABLE. So, Please decommission the unwanted nodes and start the desired node using the Actions button. You can also decommission all nodes and adding the required nodes using Add node button. If the Add node and Actions buttons are disabled then you may have to private edit the pyDeployment section to remove the disable conditions. Hope this helps.