VCRM crash during catalog validation

[Lackner Thomas]

After synchronizing dir VCRM (2.2.1.830) repository with HP, the VCRM service crash during the Catalog validation. Windows restarts the service and the catalog will be validated again. So this is an infinite loop. I tried to delete all packages in the repository and uploaded some PSPs. After the upload VCRM was able to validate the catalog. After sync with the HP website the problem occurs again. I can’t see in the log file which update causes the crash.

[Maxim Revutskiy]

Same issue :( Seems like a global bug

[Manuel Dobrounig]

Same issue in our environment! Since we updated HP SIM to version 5.3 SP1 and VCRM to 2.2.1.830 the service crashes a few times during one day.

Should we downgrade to previous VCRM version till the problem is solved?

br

[Oertli]

same issue here. HP-SIM is still V5.2. Problem started after upgrade to VCRM 2.2.1.830

[Lackner Thomas]

I found a temporary solution that works in my environment.
1.Disable the automatic update with hp.com
2.Delete the following files from the repository directory:
- hpdiags-7.5.0-14.linux.i386.rpm
- hpdiags-7.5.5-1.linux.i386.rpm
- hpdiags-7.6.0-23.linux.i386.rpm
- hponcfg-1.4.0-2.linux.rpm
- hponcfg-1.5.0-1.linux.rpm
- hppyd-1.0.1-18.linux.rpm
- hppyd-1.0.2-3.linux.rpm
- hpsmh-2.0.2-109.linux.i386.rpm
- hpsmh-2.1.5-146.linux.i386.rpm
3. restart the service and recreate the softwarecatalog

[Maxim Revutskiy]

Disabling automatic updates making VCRM no sense to use

[Jens Ey]

Same problem here.

I even set up a new server with VCRM and populated it freshly through the internet but that one crashes, too.

It's a bug in 2.2.1.830. I also tried to delete the files where the VCRM crashes but on the second server that where different files :-(

I deinstalled the 2.2.1.830 und installed the 2.2.0.820. Seems stable at the moment.

Jens

[Manfred Schilling]

works in my environment: delete all *.scexe (Linux?)-files from repository and rescan...
(also after new update)

[Jens Ey]

A few days have been passed since my downgrade to the previous VCRM version.
My VCRM now work without any problem! So, if you still have the problem just dump the new version.

Jens

[dl585]

Thomas,

Instead of disabling automatic update, it might help to create a dummy file with same name as the files mentioned in your earlier post.

If those files are indeed the problem, you may mislead the VCRM by creating a dummy file with same name, thereby causing it not to attempt the download again , and thus avoiding a crash.
Seems like VCRM is not handling some of the meta data information contained those RPMs files.