Hi Steve, That error is, indeed, old and wrong. We've fixed this in 1.6, and it's much more clear now.
What probably happened is that, for some reason, there was a temporary communication problem or something with your database. Perhaps it couldn't talk to it, or it reached a max number of connections, or it had some other error. Either way, our checks saw "We failed to get this table we were checking for!" and made an assumption. A bad assumption. One that 1.6 doesn't make anymore. So you did the right thing with rb-site upgrade. No, those commands it lists shouldn't be used. The assumption in the past is that you'd only see that in development installs, hence the lack of rb-site, and that you'd never see them anymore because the table we try to fetch is from pre-1.0 days. If you upgrade to 1.6, you'll start seeing actual error messages telling you exactly what went wrong. Hopefully you never see them again, but if you do, it'll at least give you an idea what to look for. Christian -- Christian Hammond - [email protected] Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Tue, Oct 4, 2011 at 12:43 PM, Steve <[email protected]> wrote: > I upgraded our RB site 2 weeks ago from 1.0.9 to 1.5.5. As part of > the upgrade, I ran > > $ rb-site upgrade /var/www/reviewboard > > Everything went smoothly and RB has been running fine for over a week. > Then today, several users reported being unable to access RB. They > were getting a message saying: > > """ > The Review Board database schema has changed since your last upgrade. > To update your schema, run: > $ ./manage.py syncdb > """ > > That seemed odd because I'm pretty sure 'rb-site upgrade' updated the > database schema. If it hadn't, RB would have been pretty non- > functional and that wasn't the case. So I searched here and found a > message from 2009 where the OP was getting the same message: > > """ > "Database changes > The Review Board database schema has changed since your last upgrade. > To update your schema, run: > > $ ./manage.py syncdb > Follow any additional instructions it may give you. If, for example, > it tells you to perform a schema evolution, run: > > $ ./manage.py evolve --execute" > """ > > The reply to that was > > """ > Those instructions should be changed. You need to follow the > instructions in > the admin guide on upgrading sites using 'rb-site upgrade /path/to/ > site' > """ > > Based on that, I decided to restart RB and that made the problem go > away. Or at least it made RB functional again, but I have a nagging > feeling the problem could return. To add to my confusion, I see a > recent discussion here where 'manage.py syncdb' was the correct action > to take, for something called a django evolution. > > So, > > 1. If I ran 'rb-site upgrade', do I still need to run 'manage.py > syncdb'? > 2. Is that still an outdated message that should be changed? > 3. Can anyone think of why the site would be running fine for over a > week (it gets pretty high traffic) and then suddenly behave in this > way? > > Thanks! > > -- > -- Steve > > -- > 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
