Wily not starting, Port already in use

[Former Member]

Hi All !!!!

When i am trying to start the wily using the command

/usr/sap/ccms/wilyintroscope/Introscope_Enterprise_Manager,

i am getting an error as follows Port already in use: 8081 To change the Web Server port, modify the EM property: introscope.enterprisemanager.webserver.port

if I change the Enterprise manager port number and trying to start, it remains in the initial screen itself and not getting executed.

Log file details as follows

12/09/08 06:35:24 PM IST [INFO] [Manager.SmartStor] Shutting down data persistence subsystem

12/09/08 06:35:24 PM IST [INFO] [Manager.Scheduler] Shutting down scheduler

12/09/08 06:35:24 PM IST [INFO] [Manager] Beginning orderly shutdown...

12/09/08 06:35:24 PM IST [INFO] [Manager.EMWebServer] Shutting down EM Web Server...

12/09/08 06:35:24 PM IST [INFO] [Manager.EMWebServer] EM Web Server shutdown complete.

12/09/08 06:35:24 PM IST [INFO] [Manager.SmartStor] Shutting down data persistence subsystem

12/09/08 06:35:24 PM IST [INFO] [Manager] Orderly shutdown complete.

Kindly provid your valuable suggestions

Please also tell me the how to search the processes that belong to Wily Enterprise Manager.

Edited by: Naveen kumar Palanichamy on Dec 9, 2008 3:27 PM

[Former Member]

Thanks for your replies, the issue is resolved. Issue was with the hosts file of the server. Now wily is running.

[markus_doehr2]

> Thanks for your replies, the issue is resolved. Issue was with the hosts file of the server. Now wily is running.

That was what I was initially assuming in the other post )

Markus

[markus_doehr2]

It seems that some other program is running on the same port.

Check

netstat -an | grep -i listen | grep 80

This will list all open ports.

Markus

[Former Member]

Hi Experts,,,

I am still facing that error, I have found the similar issue in the thread

Link:[] unfortunatly reply is not so clear.

Kindly advice

[Former Member]

Naveen,

This SDN blog can help you ti get rid of the issue.

We had the same problem and followed the steps as mentioned in the blog and we are able to start.

Regards,

Sanjai