database revision control problem

[melipla]

Originally Posted by Papinko

Thank you for the hint, melipla. You should have posted that 2 days earlier ;-)

Sorry I've known since Oct :( I tried to warn people here. It took about a month before Check Point finally acknowledged that it was an issue and there's still no fix for it. Its been a really frustrating experience.

[Monkey D.]

I have the same problem.
How did you replace the old gtar package ?
What is the good version (rpmfind.net) of the package for a Secure Platform (NGX R65) ?
Thanks a lot for the reply.

[rokudan]

Download from here:
http://web.sitepros.net/stuff/gtar.1.15.zip

Download will be slow, my server is getting hammered... But that is the one that worked for me...

Then below to 'install' it...

cd /opt/CPshrd-R62/util/
mv gtar gtar.orig
cp /tmp/gtar.1.15.90 gtar
chmod 755 gtar

[DrkNite]

Any updates on this one
I've just got this problem after 9 months of version control working just fine
went to push a new config and by company policy create a database revison only to the the error "failed to create a version" I've replaced gtar with gtar.1.15.90 and also renamed my orginal db_versions folder, i've rebooted several times and still nothing
anyone have any other ideas?
BTW i'm runnning R65

[Thorpuse]

this is going to sound really silly.... try using a short name and comment (less than 8 characters in both, with only alpha characters). I have one site where the name of the revision determines whether it will save or not, could be a similar issue.

[DrkNite]

Thanks for the suggestion Thorpuse but it didn't work for me tried test and test for the name and comment and got the same error

[Thorpuse]

DO a cpstop and cpstart on the SC Server and test again. There's something weird going on here - I've also had issues where the first DB revision would work, but subsequent revisions wouldn't....

[DrkNite]

I've rebooted smartcenter a number of times after making the above changes, i've also tried doing cpstop and cpstart with no luck
I'm going to be putting a ticket in with support later today i think there is something else wrong here.

[BarryStiefel]

Originally Posted by DrkNite

I've rebooted smartcenter a number of times after making the above changes, i've also tried doing cpstop and cpstart with no luck
I'm going to be putting a ticket in with support later today i think there is something else wrong here.

I've heard several rumors that Database Version Control isn't "fully cooked" yet. We may have to wait for another version before it gets mature and stable.

[dantro]

Had a similar issue. Check Point provided an updated Gtar package (gtar.1.15.zip) which solved all our DB Revision Control issues.

[DrkNite]

Well I got my problem fixed after calling support

did some debugging with support using these commands in expert mode

fw debug fwm on TDERROR_ALL_ALL=5
fwm load -d Yourpolicyname yourfirewall_object 2> policypush.txt
fw debug fwm on TDERROR_ALL_ALL=0

Yourpolicyname and yourfirewall_object are the policy name and the firewall name you are pushing too (note they are case sensity)

then we looked over that txt file and $FWDIR/log/fwm.elg where we noticed

CCreateVersionHandler::Init: Failed to IArchiverConfDocument::Load ('/opt/CPsuite-R65/fw1/conf/mv_doc.C') with err 0x80004005 ('Unspecified error')

CCreateVersionHandler::CreateVersionMain: Failed to Initialize

upon checking mv_doc.C we discovered it had a file size of 0
we replaced the mv_doc.C with a known good one and dropped it on the box

check the version control and bingo its working again.

[Thorpuse]

Originally Posted by DrkNite

upon checking mv_doc.C we discovered it had a file size of 0
we replaced the mv_doc.C with a known good one and dropped it on the box

check the version control and bingo its working again.

This sounds like a workaround, not a fix. Does CP know what causes the mv_doc.C to corrupt? Otherwise, you'll need to keep on fixing this file every time a DB fails...

[DrkNite]

nope they dont know what corrupted it, i asked them flat out
but the time stamp on the file points to the exact time on monday morning when I when to do a revison before I did deployed an update to the rules.

[dietDrThunder]

Ok, so I'm jumping on the bandwagon too...just did an upgrade from R55 to R65 HFA02, and I"m having the same problem. I see the stuff about replacing that one file, but I saw a post about replacing it w. the original before applying any hot fixes. So, I have already applied the hot fix...does that mean I shouldn't replace the file? If I should, which should I use?

Thanks!

[melipla]

Originally Posted by dietDrThunder

So, I have already applied the hot fix...does that mean I shouldn't replace the file? If I should, which should I use?

You can replace the file now that you've applied the hotfixes. Use gtar 1.15.90 which rokudan linked and replace the gtar you have in /opt/CPshrd-R65/util/.

Keep a backup copy of the original gtar file--if you need to apply a hotfix in the future you MUST use the backup copy of gtar (so swap them around, apply the hotfix and swap back).

My SR is still open with Check Point, they haven't officially resolved this issue and it sounds like they won't for a while....