Re: restoring to 2.0.18 from 2.0.15 SQL backup
I'll keep the support contract in mind. For now, I think we can muddle along without it. Thanks again for all your help. David On Friday, July 31, 2015 at 5:17:49 PM UTC-4, Christian Hammond wrote: Glad it works, David! Sorry for the Power Pack issue. I'll see if we can bullet-proof that a bit more. If it helps down the road, we've been providing support contracts to customers and working with them closely when major issues like this come up, to help them get up and running quickly as soon as there's a problem. I'd be happy to talk to you more about this if it'd be useful. Christian -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: restoring to 2.0.18 from 2.0.15 SQL backup
Excellent. The DEBUG = True was just the ticket. The problem was that we had installed the PowerPack extension for the trial period on the old server. We never used it after that, so I completely forgot about it. But, its presence was known to the backup, so whenever I clicked on a repository link, it was trying to import some power pack stuff and barfed. By the way, I chose to debug this on a separate debug install that I did this morning on a VM. I did not want to disrupt the masses until I was sure I had a solution. Took a few whacks, but mostly worked well. All I had to do was install the PowerPack via easy_install. I did not bother to enable it, since we don't plan to use it. But my VM will now happily load the admin repository pages. And, I'm about to disrupt the masses for a moment while I restart httpd on the production server. Thank you for all your *excellent* help. We love the tool. David On Thursday, July 30, 2015 at 6:06:14 PM UTC-4, Christian Hammond wrote: Hi David, Been in meetings. Sorry for not getting back to you sooner. That's odd. If you get a 500, it should definitely appear in the log. What you can try doing if that's not happening is *temporarily* setting this in your $sitedir/conf/settings_local.py: DEBUG = True (This *will* change behavior of the site, so remove it when done with this test.) Reload the web server and go back to that repository. You should get a detailed traceback now, along with all the variables at each point in the trace. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: restoring to 2.0.18 from 2.0.15 SQL backup
Glad it works, David! Sorry for the Power Pack issue. I'll see if we can bullet-proof that a bit more. If it helps down the road, we've been providing support contracts to customers and working with them closely when major issues like this come up, to help them get up and running quickly as soon as there's a problem. I'd be happy to talk to you more about this if it'd be useful. Christian -- Christian Hammond - christ...@beanbaginc.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com On Fri, Jul 31, 2015 at 12:59 PM, David Carson dccar...@gmail.com wrote: Excellent. The DEBUG = True was just the ticket. The problem was that we had installed the PowerPack extension for the trial period on the old server. We never used it after that, so I completely forgot about it. But, its presence was known to the backup, so whenever I clicked on a repository link, it was trying to import some power pack stuff and barfed. By the way, I chose to debug this on a separate debug install that I did this morning on a VM. I did not want to disrupt the masses until I was sure I had a solution. Took a few whacks, but mostly worked well. All I had to do was install the PowerPack via easy_install. I did not bother to enable it, since we don't plan to use it. But my VM will now happily load the admin repository pages. And, I'm about to disrupt the masses for a moment while I restart httpd on the production server. Thank you for all your *excellent* help. We love the tool. David On Thursday, July 30, 2015 at 6:06:14 PM UTC-4, Christian Hammond wrote: Hi David, Been in meetings. Sorry for not getting back to you sooner. That's odd. If you get a 500, it should definitely appear in the log. What you can try doing if that's not happening is *temporarily* setting this in your $sitedir/conf/settings_local.py: DEBUG = True (This *will* change behavior of the site, so remove it when done with this test.) Reload the web server and go back to that repository. You should get a detailed traceback now, along with all the variables at each point in the trace. Christian -- Christian Hammond - chi...@chipx86.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: restoring to 2.0.18 from 2.0.15 SQL backup
Hi David, First, to cover the PySVN vs. Subvertpy question, Subvertpy was only the default for the first release or two of 2.0.x. It had a lot of compatibility problems and broke in far too many situations, so we flipped the defaults. If it was working for you and you want to go back to it, you can set the following in settings_local.py: SVNTOOL_BACKENDS = [ 'reviewboard.scmtools.svn.subvertpy', 'reviewboard.scmtools.svn.pysvn', ] Alright, on to the problem at hand. Passwords for repositories are stored encrypted. Perhaps something went wrong between the dump and restore that broke this. Can you check your dump file and the contents in the database for the repository (scmtools_repository table) to see if it's the expected password in plain text, or if it's something encrypted that starts with a tab character? If it's neither, that's the problem. You can, in this case, change the stored password in the repository to your plain text password. The next time Review Board reads the password in for the repository, it will re-encrypt it. One more thing: Did you copy over the old site directory, or create a new one from scratch? Christian -- Christian Hammond - chip...@chipx86.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com On Thu, Jul 30, 2015 at 11:18 AM, David Carson dccar...@gmail.com wrote: I'm trying to restore a ReviewBoard server after a hardware system failure. This is a live system and I'm under pressure to get it back up. I'm very close to having it working, but I'm hitting a UnicodeDecodeError. (Yes, I know there are other topics on this forum regarding UnicodeDecodeError, but none of them seem quite the same as mine.) The new server is running 2.0.18. The old server was running 2.0.15. I think this may be part of the problem. I installed 2.0.18 using yum on CentOS 7.0. I then created the reviewboard database in mariadb (aka MySQL) and proceeded to restore the SQL backup from my old system. This went without any problems, to my great relief. I was expecting problems, since the backup is from an older version of RB. Then I ran `rb-site upgrade /path/to/rbsite`, also without any errors. The site displays fine. I can do various admin functions fine, including displaying the latest activity that was backed up. However, when I try to open any review, I get the UnicodeDecodeError: 2015-07-30 17:50:35,484 - ERROR - - Exception thrown for user dcarson at http://reviewboard.mycompany.com/r/3254/ 'ascii' codec can't decode byte 0xf8 in position 0: ordinal not in range(128) Traceback (most recent call last): File /usr/lib/python2.7/site-packages/django/core/handlers/base.py, line 112, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.7/site-packages/reviewboard/accounts/decorators.py, line 23, in _check return view_func(*args, **kwargs) File /usr/lib/python2.7/site-packages/reviewboard/site/decorators.py, line 35, in _check return view_func(request, local_site=local_site, *args, **kwargs) File /usr/lib/python2.7/site-packages/reviewboard/reviews/views.py, line 717, in review_detail 'screenshots': screenshots, File /usr/lib/python2.7/site-packages/reviewboard/reviews/context.py, line 95, in make_review_request_context upload_diff_form = UploadDiffForm(review_request, request=request) File /usr/lib/python2.7/site-packages/reviewboard/reviews/forms.py, line 95, in __init__ data, *args, **kwargs) File /usr/lib/python2.7/site-packages/reviewboard/diffviewer/forms.py, line 41, in __init__ if self.repository.get_scmtool().get_diffs_use_absolute_paths(): File /usr/lib/python2.7/site-packages/reviewboard/scmtools/models.py, line 231, in get_scmtool return cls(self) File /usr/lib/python2.7/site-packages/reviewboard/scmtools/svn/__init__.py, line 74, in __init__ local_site_name) File /usr/lib/python2.7/site-packages/reviewboard/scmtools/svn/__init__.py, line 441, in build_client client = Client(config_dir, repopath, username, password) File /usr/lib/python2.7/site-packages/reviewboard/scmtools/svn */pysvn.py*, line 41, in __init__ self.client.set_default_password(six.text_type(password)) UnicodeDecodeError: 'ascii' codec can't decode byte 0xf8 in position 0: ordinal not in range(128) One thing I'm wondering is why pysvn is being used, instead of subvertpy. I thought I read that the new default was subvertpy. It does not seem to matter which review request I try to open. They all give me this error. This leads me to believe that it is not a case of some weird character in an individual request. Any help would be most appreciated. Thanks. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to
Re: restoring to 2.0.18 from 2.0.15 SQL backup
Christian, Thanks for the quick response. 1. I don't need or want subvertpy. I just noticed that the error was in pysvn. I'll stick with what you guys have determined works best; i.e., pysvn. 2. I don't remember ever setting passwords for the repositories. I see what I guess is encrypted passwords in the scmtools_repository table. They are encrypted and do *not* start with a tab, so I guess that is the problem. How do I change them again? If I go into Repositories as the admin and click on a repository, I get the same error. Can I change them directly in the database (as plain text)? On Thursday, July 30, 2015 at 3:25:33 PM UTC-4, Christian Hammond wrote: Hi David, First, to cover the PySVN vs. Subvertpy question, Subvertpy was only the default for the first release or two of 2.0.x. It had a lot of compatibility problems and broke in far too many situations, so we flipped the defaults. If it was working for you and you want to go back to it, you can set the following in settings_local.py: SVNTOOL_BACKENDS = [ 'reviewboard.scmtools.svn.subvertpy', 'reviewboard.scmtools.svn.pysvn', ] Alright, on to the problem at hand. Passwords for repositories are stored encrypted. Perhaps something went wrong between the dump and restore that broke this. Can you check your dump file and the contents in the database for the repository (scmtools_repository table) to see if it's the expected password in plain text, or if it's something encrypted that starts with a tab character? If it's neither, that's the problem. You can, in this case, change the stored password in the repository to your plain text password. The next time Review Board reads the password in for the repository, it will re-encrypt it. One more thing: Did you copy over the old site directory, or create a new one from scratch? Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com On Thu, Jul 30, 2015 at 11:18 AM, David Carson dcca...@gmail.com javascript: wrote: I'm trying to restore a ReviewBoard server after a hardware system failure. This is a live system and I'm under pressure to get it back up. I'm very close to having it working, but I'm hitting a UnicodeDecodeError. (Yes, I know there are other topics on this forum regarding UnicodeDecodeError, but none of them seem quite the same as mine.) The new server is running 2.0.18. The old server was running 2.0.15. I think this may be part of the problem. I installed 2.0.18 using yum on CentOS 7.0. I then created the reviewboard database in mariadb (aka MySQL) and proceeded to restore the SQL backup from my old system. This went without any problems, to my great relief. I was expecting problems, since the backup is from an older version of RB. Then I ran `rb-site upgrade /path/to/rbsite`, also without any errors. The site displays fine. I can do various admin functions fine, including displaying the latest activity that was backed up. However, when I try to open any review, I get the UnicodeDecodeError: 2015-07-30 17:50:35,484 - ERROR - - Exception thrown for user dcarson at http://reviewboard.mycompany.com/r/3254/ 'ascii' codec can't decode byte 0xf8 in position 0: ordinal not in range(128) Traceback (most recent call last): File /usr/lib/python2.7/site-packages/django/core/handlers/base.py, line 112, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.7/site-packages/reviewboard/accounts/decorators.py, line 23, in _check return view_func(*args, **kwargs) File /usr/lib/python2.7/site-packages/reviewboard/site/decorators.py, line 35, in _check return view_func(request, local_site=local_site, *args, **kwargs) File /usr/lib/python2.7/site-packages/reviewboard/reviews/views.py, line 717, in review_detail 'screenshots': screenshots, File /usr/lib/python2.7/site-packages/reviewboard/reviews/context.py, line 95, in make_review_request_context upload_diff_form = UploadDiffForm(review_request, request=request) File /usr/lib/python2.7/site-packages/reviewboard/reviews/forms.py, line 95, in __init__ data, *args, **kwargs) File /usr/lib/python2.7/site-packages/reviewboard/diffviewer/forms.py, line 41, in __init__ if self.repository.get_scmtool().get_diffs_use_absolute_paths(): File /usr/lib/python2.7/site-packages/reviewboard/scmtools/models.py, line 231, in get_scmtool return cls(self) File /usr/lib/python2.7/site-packages/reviewboard/scmtools/svn/__init__.py, line 74, in __init__ local_site_name) File /usr/lib/python2.7/site-packages/reviewboard/scmtools/svn/__init__.py, line 441, in build_client client = Client(config_dir,
Re: restoring to 2.0.18 from 2.0.15 SQL backup
Christian, Thanks for the quick response. 1. I don't need or want subvertpy. I just noticed that the error was in pysvn. I'll stick with what you guys have determined works best; i.e., pysvn. 2. I created the site directory from scratch, but then tried to find stuff from the backup site directory to tweak. The only thing that looked interesting was the uploaded/files content, which I ended up copying to the new server. 3. I don't remember ever setting passwords for the repositories. I see what I guess is encrypted passwords in the scmtools_repository table. They are encrypted and do *not* start with a tab, so I guess that is the problem. How do I change them again? If I go into Repositories as the admin and click on a repository, I get the same error. Can I change them directly in the database (as plain text)? On Thursday, July 30, 2015 at 3:25:33 PM UTC-4, Christian Hammond wrote: Hi David, First, to cover the PySVN vs. Subvertpy question, Subvertpy was only the default for the first release or two of 2.0.x. It had a lot of compatibility problems and broke in far too many situations, so we flipped the defaults. If it was working for you and you want to go back to it, you can set the following in settings_local.py: SVNTOOL_BACKENDS = [ 'reviewboard.scmtools.svn.subvertpy', 'reviewboard.scmtools.svn.pysvn', ] Alright, on to the problem at hand. Passwords for repositories are stored encrypted. Perhaps something went wrong between the dump and restore that broke this. Can you check your dump file and the contents in the database for the repository (scmtools_repository table) to see if it's the expected password in plain text, or if it's something encrypted that starts with a tab character? If it's neither, that's the problem. You can, in this case, change the stored password in the repository to your plain text password. The next time Review Board reads the password in for the repository, it will re-encrypt it. One more thing: Did you copy over the old site directory, or create a new one from scratch? Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com On Thu, Jul 30, 2015 at 11:18 AM, David Carson dcca...@gmail.com javascript: wrote: I'm trying to restore a ReviewBoard server after a hardware system failure. This is a live system and I'm under pressure to get it back up. I'm very close to having it working, but I'm hitting a UnicodeDecodeError. (Yes, I know there are other topics on this forum regarding UnicodeDecodeError, but none of them seem quite the same as mine.) The new server is running 2.0.18. The old server was running 2.0.15. I think this may be part of the problem. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: restoring to 2.0.18 from 2.0.15 SQL backup
OK, progress. I edited my SQL dump file, replacing the tab-initial-character-encrypted passwords with plain-text passwords. Not sure what they used to be, so I just put something simple. Then I dropped the reviewboard database and recreated it as utf8, and loaded the edited dump file. Now I can successfully navigate to review requests. Have not tried anything more complicated on the user side yet. I also tried to click on a repository as the admin user ( http://reviewboard.mycompany.com/admin/db/scmtools/repository/) and I get the '500' error. However, I am not getting anything in the log this time. So, based on this, I'm not quite sure what else might be broken. I'm a bit hesitant to advertise that the server is online again (already did that once), until I'm more confident that users won't be hitting more problems. For now, I'd like to understand why I get no log output and what the error actually is for the repository links. Thanks. On Thursday, July 30, 2015 at 4:01:31 PM UTC-4, David Carson wrote: Sorry, I was wrong. All repository passwords do start with 0x09. I was not looking at them correctly. On Thursday, July 30, 2015 at 3:58:09 PM UTC-4, David Carson wrote: 3. I don't remember ever setting passwords for the repositories. I see what I guess is encrypted passwords in the scmtools_repository table. They are encrypted and do *not* start with a tab, so I guess that is the problem. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: restoring to 2.0.18 from 2.0.15 SQL backup
Hi David, Been in meetings. Sorry for not getting back to you sooner. That's odd. If you get a 500, it should definitely appear in the log. What you can try doing if that's not happening is *temporarily* setting this in your $sitedir/conf/settings_local.py: DEBUG = True (This *will* change behavior of the site, so remove it when done with this test.) Reload the web server and go back to that repository. You should get a detailed traceback now, along with all the variables at each point in the trace. Christian -- Christian Hammond - chip...@chipx86.com Review Board - https://www.reviewboard.org Beanbag, Inc. - https://www.beanbaginc.com On Thu, Jul 30, 2015 at 1:46 PM, David Carson dccar...@gmail.com wrote: OK, progress. I edited my SQL dump file, replacing the tab-initial-character-encrypted passwords with plain-text passwords. Not sure what they used to be, so I just put something simple. Then I dropped the reviewboard database and recreated it as utf8, and loaded the edited dump file. Now I can successfully navigate to review requests. Have not tried anything more complicated on the user side yet. I also tried to click on a repository as the admin user ( http://reviewboard.mycompany.com/admin/db/scmtools/repository/) and I get the '500' error. However, I am not getting anything in the log this time. So, based on this, I'm not quite sure what else might be broken. I'm a bit hesitant to advertise that the server is online again (already did that once), until I'm more confident that users won't be hitting more problems. For now, I'd like to understand why I get no log output and what the error actually is for the repository links. Thanks. On Thursday, July 30, 2015 at 4:01:31 PM UTC-4, David Carson wrote: Sorry, I was wrong. All repository passwords do start with 0x09. I was not looking at them correctly. On Thursday, July 30, 2015 at 3:58:09 PM UTC-4, David Carson wrote: 3. I don't remember ever setting passwords for the repositories. I see what I guess is encrypted passwords in the scmtools_repository table. They are encrypted and do *not* start with a tab, so I guess that is the problem. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
restoring to 2.0.18 from 2.0.15 SQL backup
I'm trying to restore a ReviewBoard server after a hardware system failure. This is a live system and I'm under pressure to get it back up. I'm very close to having it working, but I'm hitting a UnicodeDecodeError. (Yes, I know there are other topics on this forum regarding UnicodeDecodeError, but none of them seem quite the same as mine.) The new server is running 2.0.18. The old server was running 2.0.15. I think this may be part of the problem. I installed 2.0.18 using yum on CentOS 7.0. I then created the reviewboard database in mariadb (aka MySQL) and proceeded to restore the SQL backup from my old system. This went without any problems, to my great relief. I was expecting problems, since the backup is from an older version of RB. Then I ran `rb-site upgrade /path/to/rbsite`, also without any errors. The site displays fine. I can do various admin functions fine, including displaying the latest activity that was backed up. However, when I try to open any review, I get the UnicodeDecodeError: 2015-07-30 17:50:35,484 - ERROR - - Exception thrown for user dcarson at http://reviewboard.mycompany.com/r/3254/ 'ascii' codec can't decode byte 0xf8 in position 0: ordinal not in range(128) Traceback (most recent call last): File /usr/lib/python2.7/site-packages/django/core/handlers/base.py, line 112, in get_response response = wrapped_callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.7/site-packages/reviewboard/accounts/decorators.py, line 23, in _check return view_func(*args, **kwargs) File /usr/lib/python2.7/site-packages/reviewboard/site/decorators.py, line 35, in _check return view_func(request, local_site=local_site, *args, **kwargs) File /usr/lib/python2.7/site-packages/reviewboard/reviews/views.py, line 717, in review_detail 'screenshots': screenshots, File /usr/lib/python2.7/site-packages/reviewboard/reviews/context.py, line 95, in make_review_request_context upload_diff_form = UploadDiffForm(review_request, request=request) File /usr/lib/python2.7/site-packages/reviewboard/reviews/forms.py, line 95, in __init__ data, *args, **kwargs) File /usr/lib/python2.7/site-packages/reviewboard/diffviewer/forms.py, line 41, in __init__ if self.repository.get_scmtool().get_diffs_use_absolute_paths(): File /usr/lib/python2.7/site-packages/reviewboard/scmtools/models.py, line 231, in get_scmtool return cls(self) File /usr/lib/python2.7/site-packages/reviewboard/scmtools/svn/__init__.py, line 74, in __init__ local_site_name) File /usr/lib/python2.7/site-packages/reviewboard/scmtools/svn/__init__.py, line 441, in build_client client = Client(config_dir, repopath, username, password) File /usr/lib/python2.7/site-packages/reviewboard/scmtools/svn */pysvn.py*, line 41, in __init__ self.client.set_default_password(six.text_type(password)) UnicodeDecodeError: 'ascii' codec can't decode byte 0xf8 in position 0: ordinal not in range(128) One thing I'm wondering is why pysvn is being used, instead of subvertpy. I thought I read that the new default was subvertpy. It does not seem to matter which review request I try to open. They all give me this error. This leads me to believe that it is not a case of some weird character in an individual request. Any help would be most appreciated. Thanks. -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
