Error starting mwa services
---------
Starting MWA Wrapper script. Checking if all ports are free to start the servers and dispatcher...
PortNumber: 10356 is not free to start the server. Please specify a different port in the configuration file (or) end the process using this port
PortNumber: 10358 is not free to start the server. Please specify a different port in the configuration file (or) end the process using this port
PortNumber: 10360 is not free to start the server. Please specify a different port in the configuration file (or) end the process using this port
PortNumber: 10878 is not free to start the dispatcher. Please specify a different port in the configuration file (or) end the process using this port
----------
Solution :
Use higher range of ports for the same.
found lots of FNDLIBR processess being used by the ports and conflicting it with the ports defined in $INST_TOP/admin/install/mwa.cfg
Updated below ports range and started the services and all working fine now.
Define in $INST_TOP/admin/install/mwa.cfg and also change in $CONTEXT_FILE
mwa.TelnetPortNumber=32503,32565,32635
mwa.Dispatcher=evtdev08.danahertm.com:32500
mwa.TelnetServer
References:
Importance of TCP/UDP Parameters in 11gR2 (Doc ID 1307804.1)
Port Conflicts In EBS - Address already in use (Doc ID 1940314.1)
How to find out the processess being used by port.
netstat -nape |grep 10358
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 129.196.132.233:24438 129.196.132.232:1550 ESTABLISHED 3737 911035884 19876/FNDLIBR
tcp 0 0 129.196.132.233:24436 129.196.132.232:1550 ESTABLISHED 3737 911035871 19874/FNDLIBR
tcp 0 0 129.196.132.233:24437 129.196.132.232:1550 ESTABLISHED 3737 911035878 19875/FNDLIBR
tcp 0 0 129.196.132.233:24434 129.196.132.232:1550 ESTABLISHED 3737 911035857 19869/FNDLIBR
tcp 0 0 129.196.132.233:24435 129.196.132.232:1550 ESTABLISHED 3737 911035865 19873/FNDLIBR
tcp 0 0 129.196.132.233:24432 129.196.132.232:1550 ESTABLISHED 3737 911035845 19867/FNDLIBR
tcp 0 0 129.196.132.233:24440 129.196.132.232:1550 ESTABLISHED 3737 911035897 19879/FNDLIBR
tcp 0 0 129.196.132.233:24430 129.196.132.232:1550 ESTABLISHED 3737 911035833 19865/FNDLIBR
tcp 0 0 129.196.132.233:24431 129.196.132.232:1550 ESTABLISHED 3737 911035839 19866/FNDLIBR
tcp 0 0 129.196.132.233:24429 129.196.132.232:1550 ESTABLISHED 3737 911035827 19864/FNDLIBR
udp 0 0 127.0.0.1:11790 0.0.0.0:* 3737 911035894 19879/FNDLIBR
udp 0 0 127.0.0.1:62999 0.0.0.0:* 3737 911035842 19867/FNDLIBR
udp 0 0 127.0.0.1:10649 0.0.0.0:* 3737 911035824 19864/FNDLIBR
udp 0 0 127.0.0.1:54051 0.0.0.0:* 3737 911035881 19876/FNDLIBR
Thanks
Vijay
---------
Starting MWA Wrapper script. Checking if all ports are free to start the servers and dispatcher...
PortNumber: 10356 is not free to start the server. Please specify a different port in the configuration file (or) end the process using this port
PortNumber: 10358 is not free to start the server. Please specify a different port in the configuration file (or) end the process using this port
PortNumber: 10360 is not free to start the server. Please specify a different port in the configuration file (or) end the process using this port
PortNumber: 10878 is not free to start the dispatcher. Please specify a different port in the configuration file (or) end the process using this port
----------
Solution :
Use higher range of ports for the same.
found lots of FNDLIBR processess being used by the ports and conflicting it with the ports defined in $INST_TOP/admin/install/mwa.cfg
Updated below ports range and started the services and all working fine now.
Define in $INST_TOP/admin/install/mwa.cfg and also change in $CONTEXT_FILE
mwa.TelnetPortNumber=32503,32565,32635
mwa.Dispatcher=evtdev08.danahertm.com:32500
mwa.TelnetServer
References:
Importance of TCP/UDP Parameters in 11gR2 (Doc ID 1307804.1)
Port Conflicts In EBS - Address already in use (Doc ID 1940314.1)
How to find out the processess being used by port.
netstat -nape |grep 10358
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 129.196.132.233:24438 129.196.132.232:1550 ESTABLISHED 3737 911035884 19876/FNDLIBR
tcp 0 0 129.196.132.233:24436 129.196.132.232:1550 ESTABLISHED 3737 911035871 19874/FNDLIBR
tcp 0 0 129.196.132.233:24437 129.196.132.232:1550 ESTABLISHED 3737 911035878 19875/FNDLIBR
tcp 0 0 129.196.132.233:24434 129.196.132.232:1550 ESTABLISHED 3737 911035857 19869/FNDLIBR
tcp 0 0 129.196.132.233:24435 129.196.132.232:1550 ESTABLISHED 3737 911035865 19873/FNDLIBR
tcp 0 0 129.196.132.233:24432 129.196.132.232:1550 ESTABLISHED 3737 911035845 19867/FNDLIBR
tcp 0 0 129.196.132.233:24440 129.196.132.232:1550 ESTABLISHED 3737 911035897 19879/FNDLIBR
tcp 0 0 129.196.132.233:24430 129.196.132.232:1550 ESTABLISHED 3737 911035833 19865/FNDLIBR
tcp 0 0 129.196.132.233:24431 129.196.132.232:1550 ESTABLISHED 3737 911035839 19866/FNDLIBR
tcp 0 0 129.196.132.233:24429 129.196.132.232:1550 ESTABLISHED 3737 911035827 19864/FNDLIBR
udp 0 0 127.0.0.1:11790 0.0.0.0:* 3737 911035894 19879/FNDLIBR
udp 0 0 127.0.0.1:62999 0.0.0.0:* 3737 911035842 19867/FNDLIBR
udp 0 0 127.0.0.1:10649 0.0.0.0:* 3737 911035824 19864/FNDLIBR
udp 0 0 127.0.0.1:54051 0.0.0.0:* 3737 911035881 19876/FNDLIBR
Thanks
Vijay