The mcm errors shouldn't actually be related (though it may mean your memcached isn't working properly?).
So it sounds like the database schema is correct and up-to-date. It's probably some double entry in the database then. What repository backing are you using? We need to find out what field the "NULL-1" is in (and what actually generated that). What you can try is to dump your database contents using mysqldump to a text file, then searching it for "NULL-1". It should reveal what field it's in. I can make more educated guesses after I know that. Christian -- Christian Hammond - [email protected] Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jun 9, 2011 at 1:55 PM, Christopher Hahn <[email protected]> wrote: > Hello, > > I did run the 'rb-site upgrade'. > > Can you confirm that I gave it the right path to RB? > > It does seem to have chewed on something, but I get errors, and > you see below. > > I may need to start with a fresh install....but if I cannot migrate > the data, then > I will be in a bad place. > > Thank you all so very much for taking the time. It is heartening to > have company. ;0) > > Chris > > =================================================================== > root@servicemanager:/data2/ReviewBoard# rb-site upgrade /data2/ReviewBoard > Rebuilding directory structure > Updating database. This may take a while. > /var/lib/python-support/python2.6/MySQLdb/__init__.py:34: > DeprecationWarning: the sets module is deprecated > from sets import ImmutableSet > [[email protected]] mcm_server_connect():2302: Software caused > connection abort > [[email protected]] mcm_server_connect():2302: Software caused > connection abort > [[email protected]] mcm_server_connect_next_avail():2333: > Software caused connection abort > [[email protected]] mcm_server_connect_next_avail():2338 > [[email protected]] mcm_server_connect_next_avail():2328 > Upgrading Review Board from 1.5 to 1.5.5 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_atomic_cmd():649 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > [[email protected]] mcm_server_connect_next_avail():2328 > No fixtures found. > > /usr/local/lib/python2.6/dist-packages/pycrypto-2.3-py2.6-linux-x86_64.egg/Crypto/Util/randpool.py:40: > RandomPool_DeprecationWarning: This application uses RandomPool, which > is BROKEN in older releases. See > http://www.pycrypto.org/randpool-broken > No evolution required. > Upgrade complete. > =================================================================== > > On Thu, Jun 9, 2011 at 12:29 PM, Christian Hammond <[email protected]> > wrote: > > After upgrading, did you run 'rb-site upgrade' on the site? > > > > Christian > > > > -- > > Christian Hammond - [email protected] > > Review Board - http://www.reviewboard.org > > VMware, Inc. - http://www.vmware.com > > > > > > On Thu, Jun 9, 2011 at 11:24 AM, Christopher Hahn <[email protected]> > wrote: > >> > >> I wanted to add that an upgrade from 1.5 to 1.5.5 executed without > >> complaint, and > >> the results loads fine in IE: > >> ====================================================== > >> root@servicemanager:/data2/ReviewBoard# easy_install -U ReviewBoard > >> Searching for ReviewBoard > >> Reading http://pypi.python.org/simple/ReviewBoard/ > >> Reading http://www.review-board.org/ > >> Reading http://downloads.review-board.org/releases/ReviewBoard/1.0/ > >> Reading http://downloads.reviewboard.org/releases/ReviewBoard/1.5/ > >> Reading http://downloads.review-board.org/releases/ > >> Best match: ReviewBoard 1.5.5 > >> Downloading > >> > http://downloads.reviewboard.org/releases/ReviewBoard/1.5/ReviewBoard-1.5.5-py2.6.egg > >> <SNIP> > >> Installed > >> /usr/local/lib/python2.6/dist-packages/django_evolution-0.6.3-py2.6.egg > >> Finished processing dependencies for ReviewBoard > >> root@servicemanager:/data2/ReviewBoard# > >> ====================================================== > >> > >> This upgrade had no effect on the problem. I am thinking that this > >> problem > >> is caused by some corruption of the database backend. > >> > >> Any backend trouble-shooting tips will be appreciated, > >> > >> Chris > >> > >> On Thu, Jun 9, 2011 at 10:34 AM, XRZ1138 <[email protected]> wrote: > >> > > >> > Hello all, > >> > > >> > I am very new to RB and am just hoping to get a pointer into the docs. > >> > > >> > I am seeing this error when trying to submit a review: > >> > ========================================= > >> > Django Version: 1.2.3 > >> > Exception Type: IntegrityError > >> > Exception Value: (1062, "Duplicate entry 'NULL-1' for key 2") > >> > Exception Location: /var/lib/python-support/python2.6/MySQLdb/ > >> > connections.py in defaulterrorhandler, line 35 > >> > Python Executable: /usr/bin/python > >> > Python Version: 2.6.2 > >> > ========================================= > >> > > >> > I will continue to look into this but any comments appreciated. > >> > > >> > Chris > >> > >> > >> > >> -- > >> Realisant mon espoir, je me lance vers la gloire. > >> Christopher Hahn == [email protected] > >> > >> -- > >> Want to help the Review Board project? Donate today at > >> http://www.reviewboard.org/donate/ > >> Happy user? Let us know at http://www.reviewboard.org/users/ > >> -~----------~----~----~----~------~----~------~--~--- > >> To unsubscribe from this group, send email to > >> [email protected] > >> For more options, visit this group at > >> http://groups.google.com/group/reviewboard?hl=en > > > > -- > > Want to help the Review Board project? Donate today at > > http://www.reviewboard.org/donate/ > > Happy user? Let us know at http://www.reviewboard.org/users/ > > -~----------~----~----~----~------~----~------~--~--- > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > > http://groups.google.com/group/reviewboard?hl=en > > > > -- > Realisant mon espoir, je me lance vers la gloire. > Christopher Hahn == [email protected] > > -- > Want to help the Review Board project? Donate today at > http://www.reviewboard.org/donate/ > Happy user? Let us know at http://www.reviewboard.org/users/ > -~----------~----~----~----~------~----~------~--~--- > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/reviewboard?hl=en > -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~----------~----~----~----~------~----~------~--~--- To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
