[p4dti-discussion] Perforce\Bugzilla out of sync

[Dan Carreira]

Hello everyone...

So it appears that it is only my system that is malfunctioning; if I log into perforce from any other machine it is fine. I'm guessing that perforce is retaining some data on my local machine that is causing some issue? If anyone knows off hand where a perforce windows client stores local user data, I appreciate the heads up. 

But it looks like my problems are gone for now.

Thanks for the help

Dan

-----Original Message-----
From: p4dti-discussion-bounces at ravenbrook.com [mailto:p4dti-discussion-bounces at ravenbrook.com] On Behalf Of Dan Carreira
Sent: December 4, 2007 11:11 PM
To: Perforce Defect Tracking Integration discussion
Subject: Re: [p4dti-discussion] Perforce\Bugzilla out of sync

Hi Bill,

I gave what you suggested a try and sure enough there were some problems; but repairing the databases doesn't seem to have fixed my "out of Memory" problem.

The strange thing here is that I can go into Bugzilla and see all the information; I even confirmed that the last known bug fix from the perforce side in fact made it into bugzilla.

Bug when I try to retrieve the bug list that is in perforce it looks like something sends it into some kind of endless loop.

Is there any possibility that I need to do something in perforce to tell it to adopt what's in bugzilla as far as the bugs go? I've tried restarting the service; but it doesn't seem to have an impact.

Again, any help would be appreciated.

Dan


-----Original Message-----
From: p4dti-discussion-bounces at ravenbrook.com [mailto:p4dti-discussion-bounces at ravenbrook.com] On Behalf Of Bill Farrow
Sent: December 4, 2007 5:16 PM
To: Perforce Defect Tracking Integration discussion
Subject: Re: [p4dti-discussion] Perforce\Bugzilla out of sync

> I guess I should mention that we're using very old versions of
> Perforce(2003.2) and p4dti to match; and my skills are somewhat limited
> when it comes to Linux and python.
> 
> Any help would be greatly appreciated.

No guarantees here. I have done some of these steps in the past, but I am no expert in mysql you should double check what I am saying with your own research and man page reading.

> (P4DTI-891X)  Error (_mysql_exceptions.OperationalError): (1034,
> "Incorrect key file for table: 'p4dti_replications'. Try to repair it")

Your mysql database is corrupt or broken, and you will need to repair it.  It probably broke when the server crashed and it was doing a write to the a file.

Backup your mysql database files (*.frm, *.MYD, *.MYI). If you were running debian the commands would be:
  $ /etc/init.d/mysql stop
  $ tar zcf ~/mysql-files-backup-2007-12-04.tgz /var/lib/mysql
  $ /etc/init.d/mysql start

See if you can dump out the database in question as another form of backup:
  $ mysqldump -u root -p your_bugzilla_database_name > ~/mysql-bugzilla-backup-2007-12-04.sql

If you don't know the mysql database name that you are using run:
  $ mysql -u root -p
  mysql> show databases;

Now check the database tables for problems:
  $ cd /var/lib/mysql
  $ myisamchk *.MYI 

Then do the repair action:
  $ myisamchk -r *.MYI  

And then restart the database service:
  $ /etc/init.d/mysql restart



> www.monteris.com
> Monteris Medical

Good to see another interesting company doing in-vivo laser medical devices.
Good luck,

Bill Farrow
www.optiscan.com


_______________________________________________
P4DTI-discussion mailing list
P4DTI-discussion at ravenbrook.com
http://mailman.ravenbrook.com/mailman/listinfo/p4dti-discussion

_______________________________________________
P4DTI-discussion mailing list
P4DTI-discussion at ravenbrook.com
http://mailman.ravenbrook.com/mailman/listinfo/p4dti-discussion