For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Gal_Ziv_34761's avatar
Gal_Ziv_34761
Icon for Nimbostratus rankNimbostratus
Mar 10, 2010

Failed Management pack install (ver. 1.6.1 and 1.7)

In both versions, the setup fails with the same error:   <03-10-2010 11:53:32> Warning: Installer Stage[ServiceStateChange]: action=Custom Install Action: Install, duration=78.3ms, state=Failure[...
management
microsoft
scom
Gal_Ziv_34761's avatar
Gal_Ziv_34761
Icon for Nimbostratus rankNimbostratus
Aug 09, 2010
Hi Dave,

 

I've sent you a message directly to your email. To repeat for the benefit of this forum:

 

1. The Config service is configured as a cluster resource, and so are the SDK and HealthService.

 

2. It looks to me as if the setup routine is trying to restart the service on the node - which it can't do if it's a cluster resource - and thus times out. Rstarting the Config service manually creates the 1210 event and allows setup to get to the next check - which is the HealthService verification.

 

3. Unfortunately, the same "trick" doesn't work for the HealthService, and the setup now terminates on a time out verifying that service. Not sure what exactly it's looking for, but it seems like it's only waiting for 1 minute for the verification to complete (event 1201?), which may not be enough time.

 

 

Once it times out, it rolls back everything of course.

 

Another issue I noticed, which may deserve its own thread, is that the rollback does not remove the "F5 Connector" that's created by the setup routine.

 

Gal.