[p4dti-discussion] Perforce\Bugzilla out of sync
Dan Carreira
dcarreira at monteris.com
Tue Dec 4 21:44:43 GMT 2007
My bugzilla server went down a couple of days ago; and wouldn't you know
that after 3 years of rock solid operation the system goes down the week
before a deadline.
Anyways, I have the system back up now; and the Perforce server
continued to operate while Bugzilla was down.
No changes were made to perforce as far as jobs go since the bugzilla
server went down, because I told people to stop making changes thinking
that if I could get the server back up I wouldn't have any sync
issues...
Wasn't the case; now whenever I go back in to Perforce to look at the
jobs I get an "Out of Memory" error that repeats continuously until I
kill Perforce via task manager.
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.
I got the following e-mail when I powered the bugzilla server back up:
Subject: (P4DTI-8636) The replicator failed to poll successfully.
(P4DTI-8658) This is an automatically generated e-mail from the
Perforce Defect Tracking Integration replicator 'replicator0'.
(P4DTI-8647) The replicator failed to poll successfully, because of the
following problem:
(P4DTI-891X) Error (_mysql_exceptions.OperationalError): (1034,
"Incorrect key file for table: 'p4dti_replications'. Try to repair it")
(P4DTI-8523) Here's a full Python traceback:
Exception:
OperationalError: (1034, "Incorrect key file for table:
'p4dti_replications'. Try to repair it") Traceback (innermost last):
File "replicator.py", line 857, in carefully_poll_databases
self.poll_databases()
locals:
self: <replicator.replicator instance at 8198700>
File "replicator.py", line 1220, in poll_databases
self.dt.mark_changes_done(dt_marker)
locals:
_: {}
self: <replicator.replicator instance at 8198700>
changed_issues: <replicator.list_cursor instance at 8223948>
changelists: [...deleted, contains company confidential info...]}
p4_marker: 56742
File "dt_bugzilla.py", line 615, in mark_changes_done
self.bugzilla.end_replication()
locals:
self: <dt_bugzilla.dt_bugzilla instance at 8194930>
replication: '2007-11-29 16:46:30'
File "bugzilla.py", line 1915, in end_replication
'end != 0 and '
locals:
self: <bugzilla.bugzilla instance at 81810e8>
File "bugzilla.py", line 618, in delete_rows_rid_sid
self.delete_rows(table, where +
locals:
self: <bugzilla.bugzilla instance at 81810e8>
table: 'p4dti_replications'
where: 'end != 0 and end < date_sub(now(), INTERVAL 1 HOUR)'
File "bugzilla.py", line 612, in delete_rows
self.execute('delete from %s where %s;' % (table, where))
locals:
self: <bugzilla.bugzilla instance at 81810e8>
table: 'p4dti_replications'
where: "end != 0 and end < date_sub(now(), INTERVAL 1 HOUR) and
rid = 'replicator0' and sid = 'perforce0'"
File "bugzilla.py", line 102, in execute
self.cursor.execute(sql)
locals:
sql: "delete from p4dti_replications where end != 0 and end <
date_sub(now(), INTERVAL 1 HOUR) and rid = 'replicator0' and sid =
'perforce0';"
self: <bugzilla.bugzilla instance at 81810e8>
File "/usr/lib/python1.5/site-packages/MySQLdb/cursors.py", line 95,
in execute
return self._execute(query, args)
locals:
args: None
self: <MySQLdb.cursors.Cursor instance at 818d018>
query: "delete from p4dti_replications where end != 0 and end <
date_sub(now(), INTERVAL 1 HOUR) and rid = 'replicator0' and sid =
'perforce0';"
File "/usr/lib/python1.5/site-packages/MySQLdb/cursors.py", line 114,
in _execute
self.errorhandler(self, exc, value)
locals:
query: "delete from p4dti_replications where end != 0 and end <
date_sub(now(), INTERVAL 1 HOUR) and rid = 'replicator0' and sid =
'perforce0';"
value: <_mysql_exceptions.OperationalError instance at 818ce80>
TupleType: <type 'tuple'>
self: <MySQLdb.cursors.Cursor instance at 818d018>
exc_info: <built-in function exc_info>
ListType: <type 'list'>
args: None
exc: <class _mysql_exceptions.OperationalError at 8178020>
File "/usr/lib/python1.5/site-packages/MySQLdb/connections.py", line
33, in defaulterrorhandler
raise errorclass, errorvalue
locals:
error: (<class _mysql_exceptions.OperationalError at 8178020>,
<_mysql_exceptions.OperationalError instance at 818ce80>)
connection: <MySQLdb.connections.Connection instance at 818b9a8>
errorvalue: <_mysql_exceptions.OperationalError instance at
818ce80>
cursor: <MySQLdb.cursors.Cursor instance at 818d018>
errorclass: <class _mysql_exceptions.OperationalError at 8178020>
Thanks in Advance
Daniel Carreira
Manager of Software Development
dcarreira at monteris.com
Ph: (204) 272-2220 ext. 227
Fax: (204) 272-2219
www.monteris.com <http://www.monteris.com/>
Monteris Medical
100-78 Innovation Dr.
Winnipeg, Manitoba
R3T 6C2
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ravenbrook.com/pipermail/p4dti-discussion/attachments/20071204/ef219e51/attachment-0001.html
More information about the P4DTI-discussion
mailing list