topic Re: Version control agent needs to be restarted after reboot in Server Management - Systems Insight Manager

Version control agent needs to be restarted after reboot

harry white_2 — Tue, 15 May 2007 04:12:04 GMT

I am running Windows 2000 on a DL360 G5. I have set up SNMP and the VCA correctly and I am using certificate authentication. Everything works apart from I have restart VCA after a reboot. I have tried upgrading to the latest version of VCA and the PSP, but to no avail. Has anyone else seen this problem?

Re: Version control agent needs to be restarted after reboot

Rob Buxton — Tue, 15 May 2007 15:32:00 GMT

What error?
What versions of agents?
Did you install the entire PSP or just the agents?

Re: Version control agent needs to be restarted after reboot

harry white_2 — Wed, 16 May 2007 02:43:47 GMT

I have installed PSP 7.60A and also upgraded the Version Control Agent to 2.1.8.780.

After the server has been rebooted, all services appeared to be started (I checked in the services MMC). However when you try to open the VCA the page times out. If I restart the the VCA service, the page opens as normal.

Re: Version control agent needs to be restarted after reboot

Rancher — Wed, 16 May 2007 07:31:03 GMT

We are having the same trouble but we are running version 7.70. It does not happen on all of our servers however. We are also having trouble with the System Management Homepage as well. When you try to access it, it says that there isn't one. I restart that service, restart the VCA, run an identify system, and then run a software poll. After that, they both respond until the next time the server is rebooted.
Our servers are ML370 G4's running 2003.

Re: Version control agent needs to be restarted after reboot

Gladiator — Fri, 18 May 2007 07:34:20 GMT

Hi,
Can you Check the VCA service properties is set to automatic. If it is manual, Set it to Automatic.

If VCRM repository contains more than 1000 Components it may get timed out.

Re: Version control agent needs to be restarted after reboot

harry white_2 — Fri, 18 May 2007 08:08:05 GMT

Yes, the service is set to automatic :-)

How would I go about checking the number of items in the VCRM?

Re: Version control agent needs to be restarted after reboot

Rancher — Fri, 18 May 2007 08:10:35 GMT

All of my services are also set to automatic. The services do start, so that is not a problem, they just don't work properly and need a little effort to get them going correctly.

Re: Version control agent needs to be restarted after reboot

harry white_2 — Mon, 21 May 2007 03:32:11 GMT

I have managed to find a work around for this. If I make the VCA service dependent on the HP Insight Foundation Agents service then VCA works properly first time after a reboot.

Has anyone else had a problem similar to this?

Re: Version control agent needs to be restarted after reboot

TechGuru — Thu, 07 Jun 2007 05:06:16 GMT

As "Gladiator" told above, It must be the VCRM load issue.

VCA use VCRM to calculate status & to get available updates.

Every time VCRM server or VCRM service is restarted, it will scan the complete repository folder for consistency. this might make VCRM busy & not respond to VCA query.

Re: Version control agent needs to be restarted after reboot

harry white_2 — Thu, 07 Jun 2007 05:17:43 GMT

VCRM is running on a different server though it is not being restarted. Maybe the VCA service is starting up too soon and cannot contact the VCRM. Would the service fail to start if it could not contact the VCRM?

Re: Version control agent needs to be restarted after reboot

TechGuru — Thu, 07 Jun 2007 05:27:35 GMT

if VCA is not able to connect to VCRM, service will not fail, but status will be unknown.

VCA also depends on Insight Foundation agants & SNMP for inventory collection.

how long dose it take for VCA to work properly?

Re: Version control agent needs to be restarted after reboot

harry white_2 — Thu, 07 Jun 2007 05:32:30 GMT

Thanks for getting back to me so quickly! The original problem was that VCA service did not start after a reboot even though it was set to automatic. However if you logged in after the reboot you could manually start the service.

To get round it I changed the VCA service to be dependent on the HP Insight Foundation Agents service. After this change, VCA always starts after a reboot. Maybe HP need to add this dependency to the service?

Re: Version control agent needs to be restarted after reboot

Rancher — Fri, 15 Jun 2007 07:44:34 GMT

How did you make the VCA dependent on the Foundation Agent service?