BladeSystem Server Blades
cancel
Showing results for 
Search instead for 
Did you mean: 

HP SUM error : Timeout waiting for service to launch

 
SOLVED
Go to solution
Prak
Occasional Advisor

HP SUM error : Timeout waiting for service to launch

Hi, I am trying to run HP SUM version 8.1 and it failed with Timeout waiting for service to launch

I am running this on a BL460C server running Windows Server 2008 R2.

When looking at the logs I can see the following errors:

[DEBUG] :: Jan-11-2018 10:47:39:669 am :: [httpconnection.cpp:201] ::
request:
[WARN] :: Jan-11-2018 10:47:40:867 am :: [httpconnection.cpp:150] :: Warning: HTTPConnectionError: WriteHttpData: Communication finished with error 7 : Couldn't connect to server. Extended error 0
Please check whether the server is running or specified ports are blocked..
[DEBUG] :: Jan-11-2018 10:47:40:867 am :: [httpconnection.cpp:286] ::
response:

 

4 REPLIES

Re: HP SUM error : Timeout waiting for service to launch

Hi @Prak, how are you doing ?

Do you tested with another version ?
Exemple...8.0:

https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_7edb0427d9734f509c7379cf86

Regards

 

denis_b
HPE Pro

Re: HP SUM error : Timeout waiting for service to launch

I saw same when required port was busy by another process.

Please, check ports requirements in the article http://downloads.linux.hpe.com/repo/spp/2013.02.0_supspp_rhel6.4_x86_64/v16689560.htm and verify that there's no conflict.

I am HPE Employee
Best regards,
Denis
SrikanthB
HPE Pro

Re: HP SUM error : Timeout waiting for service to launch

Hi, It looks like the SUM service didn't start or sum_binary was unable to communicate to the sum_service listening on 63001/63002 port. 

Can we try launching SUM with /open_firewall switch?

Try running gatherlogs.bat and attach the logs to this post, if the above method didn't work for you.

 

I am an HPE Employee
Prak
Occasional Advisor
Solution

Re: HP SUM error : Timeout waiting for service to launch

What worked for me was using HP SUM 8.1 on a Windows 2012 server and then connecting to the blade server as a remote node.