Failure to resolve servicename on CentOS
Article ID: KB0081723
Updated On:
| Products | Versions |
|---|---|
| TIBCO Streaming | 10.x |
Description
By default, CentOS enables firewall rules that block UDP port 54321. This port is needed for StreamBase 10 applications. If it is not open, the following error will be seen when attempting to start a node:
$ epadmin install node application=deployApp1/target/deployApp1-0.0.1-SNAPSHOT-ep-application.zip nodename=A.app1 nodedirectory=~/.nodes/app1 [A.app1] Installing node [A.app1] PRODUCTION executables [A.app1] File shared memory [A.app1] 1 concurrent allocation segments [A.app1] Host name centos74vm [A.app1] Container tibco/sb [A.app1] Starting container services [A.app1] Loading node configuration [A.app1] Auditing node security [A.app1] Deploying application [A.app1] Engine default-engine-for-com.example.app1 [A.app1] Application deployed [A.app1] Administration port is 2676 [A.app1] Discovery Service running on port 54321 [A.app1] Service name is A.app1 [A.app1] Node installed $ epadmin servicename=A.app1 start node Failed to resolve servicename "A.app1" : service not found.
Issue/Introduction
Resolving servicename resolution errors on CentOS.
Resolution
To open port 54321, edit the firewall rules as follows:
$ firewall-cmd --get-active-zones public $ firewall-cmd --zone=public --add-port=54321/udp --permanent success $ firewall-cmd --reload success
Feedback
Yes
No
Powered by
