Jump to content
Sign in to follow this  
davidduff

retrospect10: retroengine assertion failure at grx.cpp-1098

Recommended Posts

i'm seeing assertion failures from retrospect engine.

 

oddly, they are happening at 5 minute intervals.

 

they seem to be related to an instability i observed with client communications (reported under a separate thread).

 

"Assertion failure at "grx.cpp-1089", on threadID <hexID>"

Share this post


Link to post
Share on other sites

it appears to me that my retroengine process is dying each time the above message is written to the logs.

 

i didn't realize it at first, because one of the running activities (a groom operation) seems to survive the engine crashes.

 

so this is a more serious problem than i originally thought.

Share this post


Link to post
Share on other sites

The GRX assert is caused by a catalog file that is corrupt due to a prior failed grooming operation. If you perform a catalog rebuild on the bad catalog file, the crash will no longer happen.

Share this post


Link to post
Share on other sites

ok - thanks. i eventually reached that conclusion myself "the hard way" - i.e., everything else i tried failed badly.

 

fyi, i tried doing a repair on the media set a couple of times and it crashed the engine and the console. not good.

 

also, for my own understanding, in the case where a catalog is corrupt, shouldn't repair do essentially the same as rebuild? if not, why not? and why should repair crash both engine and console?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×