Installing Hotfix on R82 ElasticXL

[DominusRex23]

Hi Everyone,

We’ve set up an ElasticXL cluster (R82) and successfully installed the hotfix on Gateway1. However, Gateway2 fails with a “db error” during installation.

What we’ve tried:

• Shut down Gateway1 to access Gateway2’s console
• Uploaded the hotfix .tar manually
• Ran installation via CLI, but it throws a “db error” with no further context

We suspect this might be related to database sync issues or corruption on Gateway2. Has anyone seen this before in ElasticXL setups? Is there a recommended way to reset or reinitialize the local DB without affecting the SMO

Any insights or SKs would be appreciated.

Thanks in advance!

[emmap · Accepted solution]

Just to double check, are you following the documented procedure for installation? 

https://sc1.checkpoint.com/documents/R82/WebAdminGuides/EN/CP_R82_ScalablePlatforms_AdminGuide/Conte...

If so and it's still not working, might need a TAC case raised to investigate deeper.

[the_rock]

Im 100% sure you need to follow exactly what @emmap sent. I had exact same issue with customer recently an that was the solution, disable auto clone feature. 

Andy

[genisis__]

Pretty sure I did this (I was on a zoom with TAC) and issue was replicated, hence they are going to lab this as well.

[the_rock]

What is the output of below in clish?

show smo image auto-clone state

Andy

[genisis__]

I've actually got a TAC running for this - the Engineer is labing this issue.

[the_rock]

When I had case with customer for this exact issue, TAC asked us to do the same thing Emma mentioned and that fixed it.

Andy

[genisis__]

I have a TAC case running for this exact issue!
Also can we get this moved to the thread I created " R82 ElasticXL & VSNext Issues"

[genisis__]

b.t.w - just installed another two Nodes in my lab, this time with JHFA33 and in ClusterXL/VSX mode, so far no issues to report.

[the_rock]

Good news!

[genisis__]

Still early but this suggests to me that R82 using traditional technologies would be a safer deployment for production setups, at this stage.  I do have every confidence in ElasticXL and VSNext as superior replacements at some point in the near future. 

It would certainly be worth Checkpoint investigating the conversion path from VSX to VSNext and ClusterXL to ElasticXL (100% sure this would not be easiest thing).

[Chris_Atkinson]

We typical don't merge threads like you've requested.

@PhoneBoy @_Val_ Might consider creating a specific ElasticXL section so tagging them to review.

[genisis__]

Only reason I suggested that so that issues related to ElasticXL and VSNext could be held under one thread.

[_Val_]

@Chris_Atkinson @genisis__ I confirm that we cannot merge threads. Concerning the tags, one can use any tags on any post.