Unable to start as-agent - "error none of the listen URL is available"
Article ID: KB0077132
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveSpaces | 2.x |
Description
On startup below error reported:
INVALID_ARG (command_line_arg_invalid - -listen argument tcp://<host>:<port>, none of the listen URL is available [interface=<host>])
<Exception>
1) MemberManager.cpp: 184: MemberManager::init: command_line_arg_invalid - -listen argument tcp://<host>:<port>, none of the listen URL is available [interface=<host>]
2) Gmp.cpp: 50: Gmp::initialize
3) Metaspace.cpp: 108: Metaspace::initialize
4) MetaspaceManager.cpp: 211: MetaspaceManager::createMetaspace
</Exception>
INVALID_ARG (command_line_arg_invalid - -listen argument tcp://<host>:<port>, none of the listen URL is available [interface=<host>])
<Exception>
1) MemberManager.cpp: 184: MemberManager::init: command_line_arg_invalid - -listen argument tcp://<host>:<port>, none of the listen URL is available [interface=<host>]
2) Gmp.cpp: 50: Gmp::initialize
3) Metaspace.cpp: 108: Metaspace::initialize
4) MetaspaceManager.cpp: 211: MetaspaceManager::createMetaspace
</Exception>
Issue/Introduction
Unable to start as-agent - "error none of the listen URL is available"
Environment
All Operating Systems
Resolution
This is an configuration issue. The error could caused by:
1.)
Invalid hostname/IP address defined as the listen URL (parameter -listen). The IP-address (nslookup <hostname>) must available on the local machine (validate with ipconfig/ifconfig).
2.)
The configured port used by another application. To avoid the error stop that application or configure a different port that is available on the machine.
To validate if configured port is available or used by another application:
Windows (last column -> processID):
netstat -ano|findstr "<portnumber>"
Linux (last column <processID>/<application name>)
netstat -nlp|grep <portnumber>
3.)
Secure cluster.
The format of the discoveryURL in configured policy file is incorrect (all members in discoveryURL start with "tcp://").
Correct format in policy file:
metaspace_access=metaspace=<metaspacename>;discovery=tcp://<host>:<port>;<host>:<port>;<host>:<port>;...
eg:
metaspace_access=metaspace=testsupport;discovery=tcp://localhost:50000;localhost:50001
1.)
Invalid hostname/IP address defined as the listen URL (parameter -listen). The IP-address (nslookup <hostname>) must available on the local machine (validate with ipconfig/ifconfig).
2.)
The configured port used by another application. To avoid the error stop that application or configure a different port that is available on the machine.
To validate if configured port is available or used by another application:
Windows (last column -> processID):
netstat -ano|findstr "<portnumber>"
Linux (last column <processID>/<application name>)
netstat -nlp|grep <portnumber>
3.)
Secure cluster.
The format of the discoveryURL in configured policy file is incorrect (all members in discoveryURL start with "tcp://").
Correct format in policy file:
metaspace_access=metaspace=<metaspacename>;discovery=tcp://<host>:<port>;<host>:<port>;<host>:<port>;...
eg:
metaspace_access=metaspace=testsupport;discovery=tcp://localhost:50000;localhost:50001
Additional Information
configuration, listenURL
Feedback
Yes
No
Powered by
