Re: Logging is not working When failure happens?
Hi, Are there any logs at all other than the rotation information in that file? Are you certain logging is turned on in settings? Is the log file's ownership set to allow the Apache server to write to it? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Jan 2, 2013 at 7:19 AM, Thangappan M thangappan...@gmail.comwrote: Hi Team, Installed reviewboard 1.7.1 in my centos 5 machine with Python version 2.7.2 and Django version 1.4.3 Configured the authentication method as LDAP Tried log in to the page, it says invalid user name and password ( though I am giving correct user name and password ) To check what goes wrong enabled Logging facility in reviewboard ( also profiling ) Restarted httpd ( apache) server. Tried giving logging credentials. It says Failure again. Entered into my review site directory and checked the log file /var/www/reviewboard/logs/reviewboard.log It has nothing about the ldap failure or success. The log file content looks like Rotating logging configurations Please anyone help me where can I see the error logs whenever any failure/success occurs? -- 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 reviewboard+unsubscr...@googlegroups.com 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: negative outgoing review
Hi David, Its causing a problem, the diff is not getting uploaded after this change through GUI, have any idea on this. On Tuesday, 18 December 2012 16:39:18 UTC+5:30, satish singh wrote: Thanks a lot David, it worked. -Satish On Monday, 17 December 2012 11:07:57 UTC+5:30, David Trowbridge wrote: Satish, If you'd like to backport it, https://github.com/reviewboard/reviewboard/commit/84c42014dafd8be04a2dc34bc0fea56663777176was my change to fix the last issue. That said, I think there are other related issues in 1.6.3. We highly recommend just upgrading to the new 1.6.15, which has this fix and others. -David -David On Sun, Dec 16, 2012 at 10:34 PM, satish singh triv...@gmail.com wrote: Hi David, I have seen the module 'reviewboard.reviews.models' , I put some debug statements and found that the save method is not called with update_counts=True, when we discarded a unpublished review and again publish a review with same change no. It calls the save method but the update_counts is false. def save(self, update_counts=False, **kwargs): self.bugs_closed = self.bugs_closed.strip() self.summary = truncate(self.summary, MAX_SUMMARY_LENGTH) if update_counts or self.id is None: self._update_counts() if self.status != self.PENDING_REVIEW: # If this is not a pending review request now, delete any # and all ReviewRequestVisit objects. self.visits.all().delete() super(ReviewRequest, self).save(**kwargs) Please give me some pointer on how to fix this issue. On Thursday, 13 December 2012 11:03:38 UTC+5:30, David Trowbridge wrote: I think we still have a lingering bug when reopening existing review requests. I'll look into it. In the meantime, you can run the fixreviewcounts management command to fix these. -David -David On Wed, Dec 12, 2012 at 9:30 PM, satish singh triv...@gmail.comwrote: can any one give me a pointer on this pls. On Wednesday, 12 December 2012 15:49:51 UTC+5:30, satish singh wrote: I am running on Review Board 1.6.3. Say the outgoing review count is 10. When i post a review through GUI with a change no, the outgoing review count is increased by 1 that is 11, and then i discard it before publishing. The outgoing review count is decreased by 1, that is 10. Now again publish a review with same change no. the outgoing review count is not increased this time. and remain 10. if i repeat this 10 more time, the outgoing review count becomes negative. -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/**donate/http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/**users/http://www.reviewboard.org/users/ -~--~~~~--**~~--~--~--- To unsubscribe from this group, send email to reviewboard...@** googlegroups.com For more options, visit this group at http://groups.google.com/** group/reviewboard?hl=enhttp://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 reviewboard...@googlegroups.com 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Logging is not working When failure happens?
I missed to enable debug in settings_local.py file. Now the logging is happening for the repository creation, and raising review request. but not for the LDAP authentication. LDAP log in is not working and no error or debug statement is printing in the log file. Also checked in the httpd ( error_log, access_log ). There also not finding any debug statements. Is there way to know about what is happening behind the screen for ldap authentication method? On Thursday, January 3, 2013 2:24:19 PM UTC+5:30, Christian Hammond wrote: Hi, Are there any logs at all other than the rotation information in that file? Are you certain logging is turned on in settings? Is the log file's ownership set to allow the Apache server to write to it? Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Wed, Jan 2, 2013 at 7:19 AM, Thangappan M thanga...@gmail.comjavascript: wrote: Hi Team, Installed reviewboard 1.7.1 in my centos 5 machine with Python version 2.7.2 and Django version 1.4.3 Configured the authentication method as LDAP Tried log in to the page, it says invalid user name and password ( though I am giving correct user name and password ) To check what goes wrong enabled Logging facility in reviewboard ( also profiling ) Restarted httpd ( apache) server. Tried giving logging credentials. It says Failure again. Entered into my review site directory and checked the log file /var/www/reviewboard/logs/reviewboard.log It has nothing about the ldap failure or success. The log file content looks like Rotating logging configurations Please anyone help me where can I see the error logs whenever any failure/success occurs? -- 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 reviewboard...@googlegroups.com javascript: 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
1.6.13 to 1.7.1 upgrade issues: ERROR (EXTERNAL IP): Internal Server Error: /r/213/
Since upgrading to 1.7.1 all new reviews have been running into this issue (backtrace below). I did some digging into the traceback that was generated and found the following: reviewboard/scmtools/hg.py line 215, the version variable being passed to parse_version is None. This is coming from line 213 from mercurial.__version__ import version When I run the line above from the command line I get back 1.9, but for some reason it is not working from the web server. I have not changed any set up with the web server since upgrading from 1.6.13 to 1.7.1, but this wasn't an issue before. I have verified the rb-site was properly upgraded. Is there something I missed somewhere? To get it to work in the mean time I hardcoded the version number for mercurial, which seems to have mitigated the issue (and made me feel really dirty), but I'm still not sure why it thinks it should break itself. Traceback (most recent call last): File /usr/lib/python2.6/site-packages/Django-1.4.3-py2.6.egg/django/core/handlers/base.py, line 111, in get_response response = callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/accounts/decorators.py, line 20, in _check return login_required(view_func)(*args, **kwargs) File /usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg/djblets/auth/util.py, line 47, in _checklogin return view_func(request, *args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/views.py, line 728, in review_detail 'screenshots': screenshots, File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/views.py, line 124, in _make_review_request_context upload_diff_form = UploadDiffForm(review_request) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/forms.py, line 276, in __init__ data, *args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/diffviewer/forms.py, line 51, in __init__ if self.repository.get_scmtool().get_diffs_use_absolute_paths(): File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/models.py, line 134, in get_scmtool return cls(self) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/hg.py, line 31, in __init__ self.client = HgClient(repository.path, repository.local_site) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/hg.py, line 215, in __init__ if parse_version(version) = parse_version(1.2): File /usr/lib/python2.6/site-packages/distribute-0.6.30-py2.6.egg/pkg_resources.py, line 1984, in parse_version for part in _parse_version_parts(s.lower()): TypeError: 'NoneType' object is not callable -- 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Testing 1.7.1 on Fedora 18
Hi Stephen, After running rb-site install and visiting the website, I get errors about a couple of directories not being writeable. The web page helpfully suggests a couple of chmod -R commands. However on Fedora the SELinux profile for the httpd process prevents writing regardless of unix permissions. I'm not sure if there's anything Fedora can do to make that easier for users, perhaps it's just something to document. The SELinux Troubleshooter correctly indicates how to workaround this issue. Hi Christian, With my test site up and running, I had a brief look around. Here are a few issues I noticed on the admin pages: On the Admin dashboard, System Information section on left hand side 1) Both Review Emails and Email TLS Authentication are hyperlinks to the same page. Should they be different links or would one link would be sufficient? 2) Indexed Search links to /admin/settings/general, which is the same as the General link at the system settings section. Perhaps this is influence by my install not having PyLucene. Should Indexed Search link to a different page? 3) General Settings admin page mentions PyLucene (with JCC) is required to enable search. See the documentation for instructions.. The documentation link points to http://www.reviewboard.org/docs/manual/dev/admin/sites/enabling-search/ however that serves up a 404 Not Found page. 4) Review Board Activity: Clicking on the four toggle buttons (Reviews, Comments, Review Requests, Changes) affects how much data is plotted. The graph goes from four datasets down to one. Deactivating the last toggle greys out the last button, but doesn't remove the last dataset from the graph (tested on Firefox 17, Fedora 17). Hope that feedback's useful, Paul From: Christian Hammond chip...@gmail.com To: reviewboard@googlegroups.com reviewboard@googlegroups.com Cc: reviewboard@googlegroups.com reviewboard@googlegroups.com; pfee p...@talk21.com; chip...@chipx86.com chip...@chipx86.com Sent: Friday, 21 December 2012, 21:24 Subject: Re: Review Board 1.7.1 released Hmm, first time anybody has reported this, and that line has been there for years. I'll make sure to fix it, but it'll only affect new installs. Christian On Dec 21, 2012, at 5:37, pfee p...@talk21.com wrote: Hi Christian, I think my next issue is with ReviewBoard rather than Fedora. The Apache configuration generated by rb-site includes this line: Options -Indexes FollowSymLinks This mixes options starting with +/- with those without a prefix. The documentation for httpd 2.2 warns this can lead to unexpected results (https://httpd.apache.org/docs/2.2/mod/core.html#options). However httpd 2.4 is stricter, causing the server to abort (https://httpd.apache.org/docs/2.4/mod/core.html#options). Fedora 18 uses Apache httpd 2.4.3, hence the httpd config generated by rb-site will not work. I adjusted the line as follows, though I'm not sure if that's appropriate. Options -Indexes +FollowSymLinks Thanks, Paul On Friday, 21 December 2012 13:14:48 UTC, pfee wrote: Hi Stephen, Installing python-docutils got past those popup errors, only to reveal similar errors about the lack of markdown. Installing python-markdown fixed this second set of popup errors. rb-site now proceeds to create the DB tables and then runs successfully to completion. Hence that's two dependencies you need, python-docutils and python-markdown. Thanks for your help, Paul On Friday, 21 December 2012 12:49:11 UTC, Stephen Gallagher wrote: On 12/21/2012 06:18 AM, pfee wrote: Hi Stephen and Christian, Excellent - thanks for your work. I tried this out on F18 beta, yum install worked without issue. I then issued rb-site install /var/www/reviewboard. I had adjusted unix permissions so that rb-site could create /var/www/reviewboard. I had setup mysql authorisation, such that the mysql user had all privileges within the reviewboard database. However I get a couple of popup dialogs: 1) Unable to execute the manager command evolve: No module named docutils.core 2) Unable to execute the manager command registerscmtools: No module named docutils.core This one is a packaging issue. I forgot to add a dependency on python-docutils. I'll fix that up in the next version. In the meantime, if you 'yum install python-docutils' you should be able to get past this. Probably more importantly, I get this error on the console django.db.utils.DatabaseError: (1146, Table 'reviewboard.auth_user' doesn't exist) It looks as though rb-site is connecting to mysql, but is not creating any tables. Is yum install ReviewBoard, followed by rb-site install the correct procedure? Is there a Django step such as manage.py syncdb require in between? I'm not sure if this is a Fedora packaging issue or a general reviewboard problem. Can you try with python-docutils installed first? It may be that it just
Upgaded from 1.6.3 to 1.7.1 - Styles missing
Hello, I upgraded from v1.6.3 to v1.7.1 this morning using the following steps: easy_install -U ReviewBoard rb-site upgrade /var/www/reviewboard /etc/init.d/memcached restart service apache2 restart then found that I had to do: chown -R www-data /var/www/reviewboard/htdocs/media/ext service apache2 restart The upgrade seemed to go ok except the styles are missing when I look at our site, I just see text. I found here (https://groups.google.com/forum/?fromgroups=#!topic/reviewboard/PRKV4CPZoZY) that I apparently missed something in the rb-site upgrade so I added Alias /static /var/www/reviewboard/htdoc/static to my Apache config and restarted Apache again. But I'm still not seeing the styles. Any ideas? Thanks, Brian -- 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Upgaded from 1.6.3 to 1.7.1 - Styles missing
I believe it is htdocs with an S on the end. Alias /static /var/www/reviewboard/htdocs/static I ran into the same problem. On Thursday, January 3, 2013 10:15:13 AM UTC-7, Brian wrote: Hello, I upgraded from v1.6.3 to v1.7.1 this morning using the following steps: easy_install -U ReviewBoard rb-site upgrade /var/www/reviewboard /etc/init.d/memcached restart service apache2 restart then found that I had to do: chown -R www-data /var/www/reviewboard/htdocs/media/ext service apache2 restart The upgrade seemed to go ok except the styles are missing when I look at our site, I just see text. I found here ( https://groups.google.com/forum/?fromgroups=#!topic/reviewboard/PRKV4CPZoZY) that I apparently missed something in the rb-site upgrade so I added Alias /static /var/www/reviewboard/htdoc/static to my Apache config and restarted Apache again. But I'm still not seeing the styles. Any ideas? Thanks, Brian -- 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Upgaded from 1.6.3 to 1.7.1 - Styles missing
You were absolutely correct. Man, what a dumb mistake. :D Thanks for catching that! On Thursday, January 3, 2013 10:26:19 AM UTC-7, Brian Armstrong wrote: I believe it is htdocs with an S on the end. Alias /static /var/www/reviewboard/htdocs/static I ran into the same problem. On Thursday, January 3, 2013 10:15:13 AM UTC-7, Brian wrote: Hello, I upgraded from v1.6.3 to v1.7.1 this morning using the following steps: easy_install -U ReviewBoard rb-site upgrade /var/www/reviewboard /etc/init.d/memcached restart service apache2 restart then found that I had to do: chown -R www-data /var/www/reviewboard/htdocs/media/ext service apache2 restart The upgrade seemed to go ok except the styles are missing when I look at our site, I just see text. I found here ( https://groups.google.com/forum/?fromgroups=#!topic/reviewboard/PRKV4CPZoZY) that I apparently missed something in the rb-site upgrade so I added Alias /static /var/www/reviewboard/htdoc/static to my Apache config and restarted Apache again. But I'm still not seeing the styles. Any ideas? Thanks, Brian -- 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Problems accessing Bazaar repository after upgrading to v1.7.1.
Hopefully this question isn't as dumb as my last one! After upgrading from v1.6.3 where we were successfully using Bazaar and ReviewBoard together, it seems we can no longer connect to Bazaar through ReviewBoard. I first noticed this when trying to create a new review and I got this error: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist. I went into the Repositories page in the Admin Dashboard and verified that all the data was still there after the upgrade. The the type, path, and ssh key still all look correct. I tried giving the username/password and again got the Connection closed error. I haven't changed anything with Bazaar, so is there something I need to do with the permissions within ReviewBoard to access our repository? Thanks, Brian -- 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Testing 1.7.1 on Fedora 18
On Thu 03 Jan 2013 11:47:06 AM EST, p...@talk21.com wrote: Hi Stephen, After running rb-site install and visiting the website, I get errors about a couple of directories not being writeable. The web page helpfully suggests a couple of chmod -R commands. However on Fedora the SELinux profile for the httpd process prevents writing regardless of unix permissions. I'm not sure if there's anything Fedora can do to make that easier for users, perhaps it's just something to document. The SELinux Troubleshooter correctly indicates how to workaround this issue. We can't really make this easier because we don't have advance knowledge of where you're installing the Review Board site. I *think* what you need to do is set the following SELinux contexts (with 'chcon -t context file' or 'chcon -R -r context directory'): 1) apache-wsgi.conf needs to be httpd_config_t 2) $SITE_DIR/htdocs and $SITE_DIR/data (if using an SQLITE DB) need to be httpd_sys_content_t What else did the Troubleshooter say? I'm naming those from memory. -- 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Problems accessing Bazaar repository after upgrading to v1.7.1.
Update: I found this in my apache2 error.log. A lot of warnings, but since it has to do with ssh, I thought it might be relevant. [Thu Jan 03 18:56:51 2013] [error] /usr/local/lib/python2.6/dist-packages/Djblets-0.7.8-py2.6.egg/djblets/extensions/base.py:467: UserWarning: Module _mysql was already imported from /usr/lib/pymodules/python2.6/_mysql.so, but /usr/lib/pymodules/python2.6 is being added to sys.path [Thu Jan 03 18:56:51 2013] [error] import pkg_resources [Thu Jan 03 18:56:51 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. [Thu Jan 03 18:56:51 2013] [error] DeprecationWarning [Thu Jan 03 18:56:51 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/conf/__init__.py:75: DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead. [Thu Jan 03 18:56:51 2013] [error] use STATIC_URL instead., DeprecationWarning) [Thu Jan 03 18:56:51 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/contrib/auth/__init__.py:26: DeprecationWarning: Authentication backends without a `supports_inactive_user` attribute are deprecated. Please define it in class 'reviewboard.accounts.backends.ActiveDirectoryBackend'. [Thu Jan 03 18:56:51 2013] [error] DeprecationWarning) [Thu Jan 03 11:56:52 2013] [warn] mod_wsgi (pid=7839): Callback registration for signal 2 ignored. [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/core/handlers/wsgi.py, line 241, in __call__ [Thu Jan 03 11:56:52 2013] [warn] response = self.get_response(request) [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/core/handlers/base.py, line 111, in get_response [Thu Jan 03 11:56:52 2013] [warn] response = callback(request, *callback_args, **callback_kwargs) [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/contrib/admin/options.py, line 366, in wrapper [Thu Jan 03 11:56:52 2013] [warn] return self.admin_site.admin_view(view)(*args, **kwargs) [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/utils/decorators.py, line 91, in _wrapped_view [Thu Jan 03 11:56:52 2013] [warn] response = view_func(request, *args, **kwargs) [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/decorators/cache.py, line 89, in _wrapped_view_func [Thu Jan 03 11:56:52 2013] [warn] response = view_func(request, *args, **kwargs) [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/contrib/admin/sites.py, line 196, in inner [Thu Jan 03 11:56:52 2013] [warn] return view(request, *args, **kwargs) [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/utils/decorators.py, line 25, in _wrapper [Thu Jan 03 11:56:52 2013] [warn] return bound_func(*args, **kwargs) [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/utils/decorators.py, line 91, in _wrapped_view [Thu Jan 03 11:56:52 2013] [warn] response = view_func(request, *args, **kwargs) [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/utils/decorators.py, line 21, in bound_func [Thu Jan 03 11:56:52 2013] [warn] return func(self, *args2, **kwargs2) [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/db/transaction.py, line 209, in inner [Thu Jan 03 11:56:52 2013] [warn] return func(*args, **kwargs) [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/contrib/admin/options.py, line 1035, in change_view [Thu Jan 03 11:56:52 2013] [warn] if form.is_valid(): [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/forms.py, line 871, in is_valid [Thu Jan 03 11:56:52 2013] [warn] if not super(RepositoryForm, self).is_valid(): [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/forms/forms.py, line 124, in is_valid [Thu Jan 03 11:56:52 2013] [warn] return self.is_bound and not bool(self.errors) [Thu Jan 03 11:56:52 2013] [warn] File /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/forms/forms.py, line 115, in _get_errors [Thu Jan 03 11:56:52 2013] [warn]
Re: Problems accessing Bazaar repository after upgrading to v1.7.1.
And one more update. I set DEBUG=True in settings_local.py and saw this in reviewboard.log 2013-01-03 13:23:02,184 - DEBUG - Logging to /var/www/reviewboard/logs/reviewboard.log with a minimum level of DEBUG 2013-01-03 13:23:07,617 - DEBUG - BZRTool: Attempting ssh connection with host: gdb.corp.celestech.com, username: bazaar 2013-01-03 13:23:07,622 - DEBUG - starting thread (client mode): 0x7b399250L 2013-01-03 13:23:07,623 - INFO - Connected (version 2.0, client OpenSSH_5.3p1) 2013-01-03 13:23:07,624 - DEBUG - kex algos:['diffie-hellman-group-exchange-sha256', 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 'diffie-hellman-group1-sha1'] server key:['ssh-rsa', 'ssh-dss'] client encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-...@lysator.liu.se'] server encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-...@lysator.liu.se'] client mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] server mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] client compress:['none', 'z...@openssh.com'] server compress:['none', 'z...@openssh.com'] client lang:[''] server lang:[''] kex follows?False 2013-01-03 13:23:07,624 - DEBUG - Ciphers agreed: local=aes128-ctr, remote=aes128-ctr 2013-01-03 13:23:07,624 - DEBUG - using kex diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local hmac-sha1, remote hmac-sha1; compression: local none, remote none 2013-01-03 13:23:07,686 - DEBUG - Switch to new keys ... 2013-01-03 13:23:07,701 - DEBUG - Trying SSH key 194c0f8ceb972b4798af50bb90eee8ec 2013-01-03 13:23:07,719 - DEBUG - userauth is OK 2013-01-03 13:23:08,120 - INFO - Authentication (publickey) successful! 2013-01-03 13:23:08,221 - DEBUG - EOF in transport thread and looking again at the Apache error log: [Thu Jan 03 13:22:58 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/db/models/fields/__init__.py:761: RuntimeWarning: DateTimeField received a naive datetime (2012-12-04 00:00:00) while time zone support is active. [Thu Jan 03 13:22:58 2013] [error] RuntimeWarning) [Thu Jan 03 13:22:58 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/db/models/fields/__init__.py:761: RuntimeWarning: DateTimeField received a naive datetime (2013-01-03 00:00:00) while time zone support is active. [Thu Jan 03 13:22:58 2013] [error] RuntimeWarning) [Thu Jan 03 13:23:01 2013] [error] /usr/local/lib/python2.6/dist-packages/Djblets-0.7.8-py2.6.egg/djblets/extensions/base.py:467: UserWarning: Module _mysql was already imported from /usr/lib/pymodules/python2.6/_mysql.so, but /usr/lib/pymodules/python2.6 is being added to sys.path [Thu Jan 03 13:23:01 2013] [error] import pkg_resources [Thu Jan 03 13:23:01 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. [Thu Jan 03 13:23:01 2013] [error] DeprecationWarning [Thu Jan 03 13:23:02 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/conf/__init__.py:75: DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead. [Thu Jan 03 13:23:02 2013] [error] use STATIC_URL instead., DeprecationWarning) [Thu Jan 03 13:23:02 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/contrib/auth/__init__.py:26: DeprecationWarning: Authentication backends without a `supports_inactive_user` attribute are deprecated. Please define it in class 'reviewboard.accounts.backends.ActiveDirectoryBackend'. [Thu Jan 03 13:23:02 2013] [error] DeprecationWarning) [Thu Jan 03 13:23:02 2013] [error] DEBUG:root:Logging to /var/www/reviewboard/logs/reviewboard.log with a minimum level of DEBUG [Thu Jan 03 13:23:02 2013] [error] 2013-01-03 13:23:02,184 - DEBUG - Logging to /var/www/reviewboard/logs/reviewboard.log with a minimum level of DEBUG [Thu Jan 03 13:23:07 2013] [error] DEBUG:root:BZRTool: Attempting ssh connection with host: gdb.corp.celestech.com, username: bazaar [Thu Jan 03 13:23:07 2013] [error] 2013-01-03 13:23:07,617 - DEBUG - BZRTool: Attempting ssh connection with host: gdb.corp.celestech.com, username: bazaar [Thu Jan 03 13:23:07 2013] [error] DEBUG:paramiko.transport:starting thread (client mode): 0x7b399250L [Thu Jan 03 13:23:07 2013] [error]
Re: Problems accessing Bazaar repository after upgrading to v1.7.1.
Hi Brian, We thunk out to rbssh for all our SSH communication. It acts as a wrapper. Somehow, the Python path is ending up all wrong when it gets there, preventing settings from being imported correctly. What version of bzr is this? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 12:27 PM, Brian phxgat...@gmail.com wrote: And one more update. I set DEBUG=True in settings_local.py and saw this in reviewboard.log 2013-01-03 13:23:02,184 - DEBUG - Logging to /var/www/reviewboard/logs/reviewboard.log with a minimum level of DEBUG 2013-01-03 13:23:07,617 - DEBUG - BZRTool: Attempting ssh connection with host: gdb.corp.celestech.com, username: bazaar 2013-01-03 13:23:07,622 - DEBUG - starting thread (client mode): 0x7b399250L 2013-01-03 13:23:07,623 - INFO - Connected (version 2.0, client OpenSSH_5.3p1) 2013-01-03 13:23:07,624 - DEBUG - kex algos:['diffie-hellman-group-exchange-sha256', 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 'diffie-hellman-group1-sha1'] server key:['ssh-rsa', 'ssh-dss'] client encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-...@lysator.liu.se'] server encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijndael-...@lysator.liu.se'] client mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] server mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] client compress:['none', 'z...@openssh.com'] server compress:['none', 'z...@openssh.com'] client lang:[''] server lang:[''] kex follows?False 2013-01-03 13:23:07,624 - DEBUG - Ciphers agreed: local=aes128-ctr, remote=aes128-ctr 2013-01-03 13:23:07,624 - DEBUG - using kex diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local hmac-sha1, remote hmac-sha1; compression: local none, remote none 2013-01-03 13:23:07,686 - DEBUG - Switch to new keys ... 2013-01-03 13:23:07,701 - DEBUG - Trying SSH key 194c0f8ceb972b4798af50bb90eee8ec 2013-01-03 13:23:07,719 - DEBUG - userauth is OK 2013-01-03 13:23:08,120 - INFO - Authentication (publickey) successful! 2013-01-03 13:23:08,221 - DEBUG - EOF in transport thread and looking again at the Apache error log: [Thu Jan 03 13:22:58 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/db/models/fields/__init__.py:761: RuntimeWarning: DateTimeField received a naive datetime (2012-12-04 00:00:00) while time zone support is active. [Thu Jan 03 13:22:58 2013] [error] RuntimeWarning) [Thu Jan 03 13:22:58 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/db/models/fields/__init__.py:761: RuntimeWarning: DateTimeField received a naive datetime (2013-01-03 00:00:00) while time zone support is active. [Thu Jan 03 13:22:58 2013] [error] RuntimeWarning) [Thu Jan 03 13:23:01 2013] [error] /usr/local/lib/python2.6/dist-packages/Djblets-0.7.8-py2.6.egg/djblets/extensions/base.py:467: UserWarning: Module _mysql was already imported from /usr/lib/pymodules/python2.6/_mysql.so, but /usr/lib/pymodules/python2.6 is being added to sys.path [Thu Jan 03 13:23:01 2013] [error] import pkg_resources [Thu Jan 03 13:23:01 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. [Thu Jan 03 13:23:01 2013] [error] DeprecationWarning [Thu Jan 03 13:23:02 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/conf/__init__.py:75: DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead. [Thu Jan 03 13:23:02 2013] [error] use STATIC_URL instead., DeprecationWarning) [Thu Jan 03 13:23:02 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/contrib/auth/__init__.py:26: DeprecationWarning: Authentication backends without a `supports_inactive_user` attribute are deprecated. Please define it in class 'reviewboard.accounts.backends.ActiveDirectoryBackend'. [Thu Jan 03 13:23:02 2013] [error] DeprecationWarning) [Thu Jan 03 13:23:02 2013] [error] DEBUG:root:Logging to /var/www/reviewboard/logs/reviewboard.log with a minimum level of DEBUG [Thu Jan 03 13:23:02 2013] [error] 2013-01-03 13:23:02,184 - DEBUG - Logging to /var/www/reviewboard/logs/reviewboard.log with a minimum level of DEBUG [Thu Jan 03 13:23:07 2013] [error] DEBUG:root:BZRTool:
Re: 1.6.13 to 1.7.1 upgrade issues: ERROR (EXTERNAL IP): Internal Server Error: /r/213/
Hi Brian, Just to sanity check, when you run that manually, is it also using Python 2.6? It seems weird that we'd be able to import that file but not get the version. In my copy here, it's nothing but a straight-forward variable assignment in a file called __version__.py. It'd be interesting to add some logging there to print mercurial.__version__.__file__ and then look in there to see what it says. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 7:55 AM, Brian Armstrong kf7...@gmail.com wrote: Since upgrading to 1.7.1 all new reviews have been running into this issue (backtrace below). I did some digging into the traceback that was generated and found the following: reviewboard/scmtools/hg.py line 215, the version variable being passed to parse_version is None. This is coming from line 213 from mercurial.__version__ import version When I run the line above from the command line I get back 1.9, but for some reason it is not working from the web server. I have not changed any set up with the web server since upgrading from 1.6.13 to 1.7.1, but this wasn't an issue before. I have verified the rb-site was properly upgraded. Is there something I missed somewhere? To get it to work in the mean time I hardcoded the version number for mercurial, which seems to have mitigated the issue (and made me feel really dirty), but I'm still not sure why it thinks it should break itself. Traceback (most recent call last): File /usr/lib/python2.6/site-packages/Django-1.4.3-py2.6.egg/django/core/handlers/base.py, line 111, in get_response response = callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/accounts/decorators.py, line 20, in _check return login_required(view_func)(*args, **kwargs) File /usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg/djblets/auth/util.py, line 47, in _checklogin return view_func(request, *args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/views.py, line 728, in review_detail 'screenshots': screenshots, File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/views.py, line 124, in _make_review_request_context upload_diff_form = UploadDiffForm(review_request) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/forms.py, line 276, in __init__ data, *args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/diffviewer/forms.py, line 51, in __init__ if self.repository.get_scmtool().get_diffs_use_absolute_paths(): File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/models.py, line 134, in get_scmtool return cls(self) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/hg.py, line 31, in __init__ self.client = HgClient(repository.path, repository.local_site) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/hg.py, line 215, in __init__ if parse_version(version) = parse_version(1.2): File /usr/lib/python2.6/site-packages/distribute-0.6.30-py2.6.egg/pkg_resources.py, line 1984, in parse_version for part in _parse_version_parts(s.lower()): TypeError: 'NoneType' object is not callable -- 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 reviewboard+unsubscr...@googlegroups.com 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Problems accessing Bazaar repository after upgrading to v1.7.1.
We're (for now) using 2.1.4. My plan was to update that this week also, I just happened to start my list of upgrades with ReviewBoard. Thanks, Brian On Thursday, January 3, 2013 2:37:14 PM UTC-7, Christian Hammond wrote: Hi Brian, We thunk out to rbssh for all our SSH communication. It acts as a wrapper. Somehow, the Python path is ending up all wrong when it gets there, preventing settings from being imported correctly. What version of bzr is this? Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 12:27 PM, Brian phxg...@gmail.com javascript:wrote: And one more update. I set DEBUG=True in settings_local.py and saw this in reviewboard.log 2013-01-03 13:23:02,184 - DEBUG - Logging to /var/www/reviewboard/logs/reviewboard.log with a minimum level of DEBUG 2013-01-03 13:23:07,617 - DEBUG - BZRTool: Attempting ssh connection with host: gdb.corp.celestech.com, username: bazaar 2013-01-03 13:23:07,622 - DEBUG - starting thread (client mode): 0x7b399250L 2013-01-03 13:23:07,623 - INFO - Connected (version 2.0, client OpenSSH_5.3p1) 2013-01-03 13:23:07,624 - DEBUG - kex algos:['diffie-hellman-group-exchange-sha256', 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 'diffie-hellman-group1-sha1'] server key:['ssh-rsa', 'ssh-dss'] client encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijnda...@lysator.liu.sejavascript:'] server encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfour', 'rijnda...@lysator.liu.sejavascript:'] client mac:['hmac-md5', 'hmac-sha1', 'uma...@openssh.com javascript:', 'hmac-ripemd160', 'hmac-ri...@openssh.com javascript:', 'hmac-sha1-96', 'hmac-md5-96'] server mac:['hmac-md5', 'hmac-sha1', ' uma...@openssh.com javascript:', 'hmac-ripemd160', ' hmac-ri...@openssh.com javascript:', 'hmac-sha1-96', 'hmac-md5-96'] client compress:['none', 'zl...@openssh.com javascript:'] server compress:['none', 'zl...@openssh.com javascript:'] client lang:[''] server lang:[''] kex follows?False 2013-01-03 13:23:07,624 - DEBUG - Ciphers agreed: local=aes128-ctr, remote=aes128-ctr 2013-01-03 13:23:07,624 - DEBUG - using kex diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local hmac-sha1, remote hmac-sha1; compression: local none, remote none 2013-01-03 13:23:07,686 - DEBUG - Switch to new keys ... 2013-01-03 13:23:07,701 - DEBUG - Trying SSH key 194c0f8ceb972b4798af50bb90eee8ec 2013-01-03 13:23:07,719 - DEBUG - userauth is OK 2013-01-03 13:23:08,120 - INFO - Authentication (publickey) successful! 2013-01-03 13:23:08,221 - DEBUG - EOF in transport thread and looking again at the Apache error log: [Thu Jan 03 13:22:58 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/db/models/fields/__init__.py:761: RuntimeWarning: DateTimeField received a naive datetime (2012-12-04 00:00:00) while time zone support is active. [Thu Jan 03 13:22:58 2013] [error] RuntimeWarning) [Thu Jan 03 13:22:58 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/db/models/fields/__init__.py:761: RuntimeWarning: DateTimeField received a naive datetime (2013-01-03 00:00:00) while time zone support is active. [Thu Jan 03 13:22:58 2013] [error] RuntimeWarning) [Thu Jan 03 13:23:01 2013] [error] /usr/local/lib/python2.6/dist-packages/Djblets-0.7.8-py2.6.egg/djblets/extensions/base.py:467: UserWarning: Module _mysql was already imported from /usr/lib/pymodules/python2.6/_mysql.so, but /usr/lib/pymodules/python2.6 is being added to sys.path [Thu Jan 03 13:23:01 2013] [error] import pkg_resources [Thu Jan 03 13:23:01 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/views/generic/list_detail.py:10: DeprecationWarning: Function-based generic views have been deprecated; use class-based views instead. [Thu Jan 03 13:23:01 2013] [error] DeprecationWarning [Thu Jan 03 13:23:02 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/conf/__init__.py:75: DeprecationWarning: The ADMIN_MEDIA_PREFIX setting has been removed; use STATIC_URL instead. [Thu Jan 03 13:23:02 2013] [error] use STATIC_URL instead., DeprecationWarning) [Thu Jan 03 13:23:02 2013] [error] /usr/local/lib/python2.6/dist-packages/Django-1.4.3-py2.6.egg/django/contrib/auth/__init__.py:26: DeprecationWarning: Authentication backends without a `supports_inactive_user` attribute are deprecated. Please define it in class 'reviewboard.accounts.backends.ActiveDirectoryBackend'.
Re: Logging is not working When failure happens?
Hi,
If logging is now working, and you're not seeing any logging failures, then
we're not hitting any error cases in the logging module. To get more
information, you'd have to add your own logging statements, in order to
trace where things go wrong. If you feel comfortable at all doing this, you
can edit reviewboard/accounts/backends.py, find the appropriate class, and
sprinkle logging.info('...') statements in places to try to track it down.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Thu, Jan 3, 2013 at 6:30 AM, Thangappan M thangappan...@gmail.comwrote:
I missed to enable debug in settings_local.py file.
Now the logging is happening for the repository creation, and raising
review request. but not for the LDAP authentication.
LDAP log in is not working and no error or debug statement is printing
in the log file.
Also checked in the httpd ( error_log, access_log ). There also not
finding any debug statements.
Is there way to know about what is happening behind the screen for
ldap authentication method?
On Thursday, January 3, 2013 2:24:19 PM UTC+5:30, Christian Hammond wrote:
Hi,
Are there any logs at all other than the rotation information in that
file? Are you certain logging is turned on in settings? Is the log file's
ownership set to allow the Apache server to write to it?
Christian
--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Wed, Jan 2, 2013 at 7:19 AM, Thangappan M thanga...@gmail.com wrote:
Hi Team,
Installed reviewboard 1.7.1 in my centos 5 machine with Python version
2.7.2 and Django version 1.4.3
Configured the authentication method as LDAP
Tried log in to the page, it says invalid user name and password (
though I am giving correct user name and password )
To check what goes wrong enabled Logging facility in reviewboard ( also
profiling )
Restarted httpd ( apache) server.
Tried giving logging credentials. It says Failure again.
Entered into my review site directory and checked the log
file /var/www/reviewboard/**logs/reviewboard.log
It has nothing about the ldap failure or success.
The log file content looks like Rotating logging configurations
Please anyone help me where can I see the error logs whenever any
failure/success occurs?
--
Want to help the Review Board project? Donate today at
http://www.reviewboard.org/**donate/http://www.reviewboard.org/donate/
Happy user? Let us know at
http://www.reviewboard.org/**users/http://www.reviewboard.org/users/
-~--~~~~--**~~--~--~---
To unsubscribe from this group, send email to reviewboard...@**
googlegroups.com
For more options, visit this group at http://groups.google.com/**
group/reviewboard?hl=enhttp://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
reviewboard+unsubscr...@googlegroups.com
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
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
RE: a couple of issues post 1.7.1 upgrade
Hey Christian, This is on lighttpd. Here's the output; 01-03 13:45 root DEBUG['/usr/bin/rbssh', 'svnpoller@svn', 'svnserve', '-t'] 01-03 13:45 root DEBUGPID 28511 01-03 13:45 root DEBUG!!! svn, svnpoller, ['svnserve', '-t'] 01-03 13:45 root DEBUG['/usr/bin/rbssh', 'svnpoller@svn', 'svnserve', '-t'] 01-03 13:45 root DEBUGPID 28512 01-03 13:45 root DEBUG!!! svn, svnpoller, ['svnserve', '-t'] 01-03 13:45 root DEBUG['/usr/bin/rbssh', 'svnpoller@svn', 'svnserve', '-t'] 01-03 13:45 root DEBUGPID 28513 01-03 13:45 root DEBUG!!! svn, svnpoller, ['svnserve', '-t'] -Original Message- From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On Behalf Of Christian Hammond Sent: Thursday, January 03, 2013 1:31 PM To: reviewboard@googlegroups.com Subject: Re: a couple of issues post 1.7.1 upgrade Hi Dave, Usually there's a more detailed error for such failures. We'll have to dig more. First step would be to turn on rbssh logging. I'm assuming you're using mod_wsgi. If so, add the following to your sitedir/htdocs/reviewboard.wsgi file: os.environ['DEBUG_RBSSH'] = '1' os.environ['RBSSH_LOG_DIR'] = '/path/to/a/log/dir' # -- make sure you create this and make it writable by Apache If you're using mod_python, add equivalent SetEnv calls. Then reload Apache and repeat the operation. You *should* see some rbssh log files in that directory. See if any of them are indicating errors of any kind, and attach those. Hoping that will help with additional information. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 7:34 AM, Dave Preston d.pres...@complianceease.com wrote: We see this; Diff currently unavailable. Error: Network connection closed unexpectedly Details https://reviewboard.logiceasedev.com/r/542/diff/ Traceback (most recent call last): File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1- py2.6.egg/reviewboard/diffviewer/views.py, line 383, in view_diff_fragment file = get_requested_diff_file() File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1- py2.6.egg/reviewboard/diffviewer/views.py, line 309, in get_requested_diff_file populate_diff_chunks(files, highlighting) File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1- py2.6.egg/reviewboard/diffviewer/diffutils.py, line 1197, in populate_diff_chunks large_data=True) File /usr/local/lib/python2.6/dist-packages/Djblets-0.7.8- py2.6.egg/djblets/util/misc.py, line 156, in cache_memoize data = lookup_callable() File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1- py2.6.egg/reviewboard/diffviewer/diffutils.py, line 1196, in lambda enable_syntax_highlighting)), File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1- py2.6.egg/reviewboard/diffviewer/diffutils.py, line 598, in get_chunks old = get_original_file(filediff) File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1- py2.6.egg/reviewboard/diffviewer/diffutils.py, line 379, in get_original_file large_data=True)[0] File /usr/local/lib/python2.6/dist-packages/Djblets-0.7.8- py2.6.egg/djblets/util/misc.py, line 156, in cache_memoize data = lookup_callable() File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1- py2.6.egg/reviewboard/diffviewer/diffutils.py, line 378, in lambda data = cache_memoize(key, lambda: [fetch_file(file, revision)], File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1- py2.6.egg/reviewboard/diffviewer/diffutils.py, line 358, in fetch_file data = repository.get_file(file, revision) File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1- py2.6.egg/reviewboard/scmtools/models.py, line 155, in get_file return self.get_scmtool().get_file(path, revision) File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1- py2.6.egg/reviewboard/scmtools/svn.py, line 173, in get_file return self._do_on_path(get_file_data, path, revision) File /usr/local/lib/python2.6/dist-packages/ReviewBoard-1.7.1- py2.6.egg/reviewboard/scmtools/svn.py, line 157, in _do_on_path raise SCMError(e) SCMError: Network connection closed unexpectedly Could this maybe be a permissions issue on the filesystem itself? I feel like this is something obvious that I am missing. As for the ssh part, I am able to reproduce it with 1.7 1.7.1 on Ubuntu 10.04 12.04. Thanks, Dave -Original Message- From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On Behalf Of Christian Hammond Sent: Thursday, January 03, 2013 12:58 AM To:
Re: 1.6.13 to 1.7.1 upgrade issues: ERROR (EXTERNAL IP): Internal Server Error: /r/213/
Correct, Python 2.6.6. Everything else works, is also the weird thing. I hardcoded a version number if it came back as None (I guess I could add some logging to that if statement too) and it just keeps going. It generates the diffs fine, all the other integration options seem to work. So I have no idea what it could be. I'll add your logging and see if it comes back with anything interesting. On Thursday, January 3, 2013 2:40:03 PM UTC-7, Christian Hammond wrote: Hi Brian, Just to sanity check, when you run that manually, is it also using Python 2.6? It seems weird that we'd be able to import that file but not get the version. In my copy here, it's nothing but a straight-forward variable assignment in a file called __version__.py. It'd be interesting to add some logging there to print mercurial.__version__.__file__ and then look in there to see what it says. Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 7:55 AM, Brian Armstrong kf7...@gmail.comjavascript: wrote: Since upgrading to 1.7.1 all new reviews have been running into this issue (backtrace below). I did some digging into the traceback that was generated and found the following: reviewboard/scmtools/hg.py line 215, the version variable being passed to parse_version is None. This is coming from line 213 from mercurial.__version__ import version When I run the line above from the command line I get back 1.9, but for some reason it is not working from the web server. I have not changed any set up with the web server since upgrading from 1.6.13 to 1.7.1, but this wasn't an issue before. I have verified the rb-site was properly upgraded. Is there something I missed somewhere? To get it to work in the mean time I hardcoded the version number for mercurial, which seems to have mitigated the issue (and made me feel really dirty), but I'm still not sure why it thinks it should break itself. Traceback (most recent call last): File /usr/lib/python2.6/site-packages/Django-1.4.3-py2.6.egg/django/core/handlers/base.py, line 111, in get_response response = callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/accounts/decorators.py, line 20, in _check return login_required(view_func)(*args, **kwargs) File /usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg/djblets/auth/util.py, line 47, in _checklogin return view_func(request, *args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/views.py, line 728, in review_detail 'screenshots': screenshots, File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/views.py, line 124, in _make_review_request_context upload_diff_form = UploadDiffForm(review_request) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/reviews/forms.py, line 276, in __init__ data, *args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/diffviewer/forms.py, line 51, in __init__ if self.repository.get_scmtool().get_diffs_use_absolute_paths(): File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/models.py, line 134, in get_scmtool return cls(self) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/hg.py, line 31, in __init__ self.client = HgClient(repository.path, repository.local_site) File /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/scmtools/hg.py, line 215, in __init__ if parse_version(version) = parse_version(1.2): File /usr/lib/python2.6/site-packages/distribute-0.6.30-py2.6.egg/pkg_resources.py, line 1984, in parse_version for part in _parse_version_parts(s.lower()): TypeError: 'NoneType' object is not callable -- 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 reviewboard...@googlegroups.com javascript: 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Problems accessing Bazaar repository after upgrading to v1.7.1.
I have now upgraded to Bazaar 2.5.1 in case it helped, but it looks like I still have the same behavior. Thanks, Brian -- 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Problems accessing Bazaar repository after upgrading to v1.7.1.
I'll play with it some here. I don't suppose your bzr repo is public, so I can test against it? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 2:14 PM, Brian phxgat...@gmail.com wrote: I have now upgraded to Bazaar 2.5.1 in case it helped, but it looks like I still have the same behavior. Thanks, Brian -- 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Problems accessing Bazaar repository after upgrading to v1.7.1.
No, it's not, sorry. If there's anything I can do to help your testing, I'd be happy to do what I can. Thanks, Brian On Thursday, January 3, 2013 3:44:17 PM UTC-7, Christian Hammond wrote: I'll play with it some here. I don't suppose your bzr repo is public, so I can test against it? Christian -- Christian Hammond - chi...@chipx86.com javascript: Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 2:14 PM, Brian phxg...@gmail.com javascript:wrote: I have now upgraded to Bazaar 2.5.1 in case it helped, but it looks like I still have the same behavior. Thanks, Brian -- 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Reviewboard with Perforce repository that uses an SSL connection
I've installed ReviewBoard 1.6.13 with Perforce 2012.2 and it contains about 50 review requests that use the Perforce repository. Now, the Perforce(P4) administrator has introduced SSL encryption for P4 connection. P4 connection string has the prefix of *ssl:* After the introduction of *ssl* switch to the connection string, there are issues viewing existing review requests within ReviewBoard. The error is in the attached file: *errorWhenViewingExistingReviewRequests.txt* * * Please suggest how I can use P4 repository which now uses a SSL connection within ReviewBoard. I tried creating a new repository providing the Path of my P4 server with the ssl: prefix. However, this results in error that a reporitory was not found at the specified path -- 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en Traceback (most recent call last): File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/core/handlers/base.py, line 111, in get_response response = callback(request, *callback_args, **callback_kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.6.13-py2.6.egg/reviewboard/accounts/decorators.py, line 22, in _check return view_func(*args, **kwargs) File /usr/lib/python2.6/site-packages/ReviewBoard-1.6.13-py2.6.egg/reviewboard/reviews/views.py, line 682, in review_detail 'screenshots': screenshots, File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/shortcuts/__init__.py, line 20, in render_to_response return HttpResponse(loader.render_to_string(*args, **kwargs), **httpresponse_kwargs) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/loader.py, line 183, in render_to_string return t.render(Context(dictionary)) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 123, in render return self._render(context) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 117, in _render return self.nodelist.render(context) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 744, in render bits.append(self.render_node(node, context)) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 757, in render_node return node.render(context) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/loader_tags.py, line 127, in render return compiled_parent._render(context) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 117, in _render return self.nodelist.render(context) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 744, in render bits.append(self.render_node(node, context)) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 757, in render_node return node.render(context) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/loader_tags.py, line 127, in render return compiled_parent._render(context) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 117, in _render return self.nodelist.render(context) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 744, in render bits.append(self.render_node(node, context)) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 757, in render_node return node.render(context) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/loader_tags.py, line 64, in render result = block.nodelist.render(context) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 744, in render bits.append(self.render_node(node, context)) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 757, in render_node return node.render(context) File /usr/lib/python2.6/site-packages/Djblets-0.6.23-py2.6.egg/djblets/util/decorators.py, line 186, in render return self.tag_func(context, self.nodelist, *args) File /usr/lib/python2.6/site-packages/Djblets-0.6.23-py2.6.egg/djblets/util/templatetags/djblets_deco.py, line 44, in box 'content': nodelist.render(context) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line 744, in render bits.append(self.render_node(node, context)) File /usr/lib/python2.6/site-packages/Django-1.3.3-py2.6.egg/django/template/base.py, line
Re: Problems accessing Bazaar repository after upgrading to v1.7.1.
Hi Brian, What kind of Python loader are you using? mod_wsgi, mod_python, fastcgi? What happens when you run rbssh from the command line on that server? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 2:45 PM, Brian phxgat...@gmail.com wrote: No, it's not, sorry. If there's anything I can do to help your testing, I'd be happy to do what I can. Thanks, Brian On Thursday, January 3, 2013 3:44:17 PM UTC-7, Christian Hammond wrote: I'll play with it some here. I don't suppose your bzr repo is public, so I can test against it? Christian -- Christian Hammond - chi...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 2:14 PM, Brian phxg...@gmail.com wrote: I have now upgraded to Bazaar 2.5.1 in case it helped, but it looks like I still have the same behavior. Thanks, Brian -- 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 reviewboard+unsubscr...@googlegroups.com 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Problems accessing Bazaar repository after upgrading to v1.7.1.
Hello again, I'm using mod_wsgi. And when I do rbssh bazaar@servername I get access with no errors. Thanks, Brian -- 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Problems accessing Bazaar repository after upgrading to v1.7.1.
Hi Brian, One more thing to confirm. Hopefully I can get you some commands to run soon that will provide more useful info. What distro are you using, and is SELinux enabled? Trying to determine what's preventing the resulting process from getting the PYTHONPATH environment... Can you also share with me your $sitedir/htdocs/settings_local.py file? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 3:49 PM, Brian phxgat...@gmail.com wrote: Hello again, I'm using mod_wsgi. And when I do rbssh bazaar@servername I get access with no errors. Thanks, Brian -- 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 reviewboard+unsubscr...@googlegroups.com 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Testing 1.7.1 on Fedora 18
Hi, On Thu, Jan 3, 2013 at 8:47 AM, p...@talk21.com wrote: Hi Stephen, After running rb-site install and visiting the website, I get errors about a couple of directories not being writeable. The web page helpfully suggests a couple of chmod -R commands. However on Fedora the SELinux profile for the httpd process prevents writing regardless of unix permissions. I'm not sure if there's anything Fedora can do to make that easier for users, perhaps it's just something to document. The SELinux Troubleshooter correctly indicates how to workaround this issue. Hi Christian, With my test site up and running, I had a brief look around. Here are a few issues I noticed on the admin pages: On the Admin dashboard, System Information section on left hand side 1) Both Review Emails and Email TLS Authentication are hyperlinks to the same page. Should they be different links or would one link would be sufficient? Yeah, they're just all quick ways of jumping to the setting for the page. The sidebar is meant to be a quick at-a-glance of certain setting values, and clicking on them takes you to the page containing that setting. There's going to be some overlap. 2) Indexed Search links to /admin/settings/general, which is the same as the General link at the system settings section. Perhaps this is influence by my install not having PyLucene. Should Indexed Search link to a different page? Nope, same as above. 3) General Settings admin page mentions PyLucene (with JCC) is required to enable search. See the documentationhttp://www.reviewboard.org/docs/manual/dev/admin/sites/enabling-search/for instructions.. The documentation link points to http://www.reviewboard.org/docs/manual/dev/admin/sites/enabling-search/however that serves up a 404 Not Found page. I'll make sure to fix the link for the next release. 4) Review Board Activity: Clicking on the four toggle buttons (Reviews, Comments, Review Requests, Changes) affects how much data is plotted. The graph goes from four datasets down to one. Deactivating the last toggle greys out the last button, but doesn't remove the last dataset from the graph (tested on Firefox 17, Fedora 17). Would you mind filing a bug on this one? I'll see what we can do about it. Hoping to get some unit tests in place for these widgets in time. Thanks! Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com -- 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Problems accessing Bazaar repository after upgrading to v1.7.1.
I think it's on Ubuntu 10.04 and I don't think SELinux is enabled, but I will confirm later this evening or tomorrow when I'm back in the office. I'll also get the contents of settings_local.py for you then. Thanks, Brian On Jan 3, 2013 5:20 PM, Christian Hammond chip...@chipx86.com wrote: Hi Brian, One more thing to confirm. Hopefully I can get you some commands to run soon that will provide more useful info. What distro are you using, and is SELinux enabled? Trying to determine what's preventing the resulting process from getting the PYTHONPATH environment... Can you also share with me your $sitedir/htdocs/settings_local.py file? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 3:49 PM, Brian phxgat...@gmail.com wrote: Hello again, I'm using mod_wsgi. And when I do rbssh bazaar@servername I get access with no errors. Thanks, Brian -- 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 reviewboard+unsubscr...@googlegroups.com 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: a couple of issues post 1.7.1 upgrade
At what point during the log is it asking for the password? It looks like it's connected. Maybe it's svnserve asking for the password? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 5:32 PM, Dave Preston d.pres...@complianceease.comwrote: You are correct, I've gotten a bit sloppy as the day has gone on. So now when I execute svn cat it just keeps prompting me for a password even though the key exists on the other side. The log shows that pubkey is successful and then falls back to password. USER=www-data DEBUG_RBSSH=1 DJANGO_SETTINGS_MODULE=reviewboard.settings HOME=/var/www/reviewboard.logiceasedev.com/data PYTHONPATH=/var/www/reviewboard.logiceasedev.com/conf 01-03 17:29 root DEBUG['/tmp/rbssh', 'svnpoller@svn', 'svnserve', '-t'] 01-03 17:29 root DEBUGPID 30058 01-03 17:29 root DEBUG!!! svn, svnpoller, ['svnserve', '-t'] 01-04 01:29 paramiko.transport DEBUGstarting thread (client mode): 0x1144450L 01-04 01:29 paramiko.transport INFO Connected (version 2.0, client OpenSSH_5.3p1) 01-04 01:29 paramiko.transport DEBUGkex algos:['diffie-hellman-group-exchange-sha256', 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 'diffie-hellman-group1-sha1'] server key: ['ssh-rsa', 'ssh-dss'] client encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfou r', 'rijndael-...@lysator.liu.se'] server encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-c bc', 'arcfour', 'rijndael-...@lysator.liu.se'] client mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] server mac:['hm ac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] client compress:['none', 'z...@openssh.com'] server compress:['none', 'zlib@o penssh.com'] client lang:[''] server lang:[''] kex follows?False 01-04 01:29 paramiko.transport DEBUGCiphers agreed: local=aes128-ctr, remote=aes128-ctr 01-04 01:29 paramiko.transport DEBUGusing kex diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local hmac-sha1, remote hmac-sha1; compression: local none, remote none 01-04 01:29 paramiko.transport DEBUGSwitch to new keys ... 01-04 01:29 paramiko.transport DEBUGTrying SSH key f3a2e6c6b62eba6b6519578ce97e57cd 01-04 01:29 paramiko.transport DEBUGuserauth is OK 01-04 01:29 paramiko.transport INFO Authentication (publickey) successful! 01-04 01:29 paramiko.transport DEBUG[chan 1] Max packet in: 34816 bytes 01-04 01:29 paramiko.transport DEBUG[chan 1] Max packet out: 32768 bytes 01-04 01:29 paramiko.transport INFO Secsh channel 1 opened. 01-04 01:29 root DEBUG!!! Using PosixHandler 01-04 01:29 root DEBUG!!! Sending command ['svnserve', '-t'] 01-04 01:29 paramiko.transport DEBUG[chan 1] Sesch channel 1 request ok 01-04 01:29 root DEBUG!! process_channel 01-04 01:29 root DEBUG!! process_stdin 01-04 01:29 root DEBUG!! process_stdin 01-04 01:29 root DEBUG!! process_stdin .. cut ... 01-04 01:29 paramiko.transport DEBUG[chan 1] EOF received (1) 01-04 01:29 paramiko.transport DEBUG[chan 1] EOF sent (1) 01-04 01:29 root DEBUG!! process_channel -Original Message- From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On Behalf Of Christian Hammond Sent: Thursday, January 03, 2013 4:17 PM To: reviewboard@googlegroups.com Subject: Re: a couple of issues post 1.7.1 upgrade I just noticed that the username it's trying to use when connecting to the remote host is www-data. That's probably not what you're wanting. I know we have the username field, but it doesn't seem that Subversion provides the configured username to the SSH client. So, try changing your Path to be something more like: svn+ssh://yourusername@host:/path. Then change Mirror Path to be the previous version of the path without the username. That should ensure that rbssh will get some information on the correct username to use. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 4:09 PM, Dave Preston d.pres...@complianceease.com wrote: Nope, I had su'd as root. su - www-data Not a problem and I do appreciate your time on this. Dave
Re: Problems accessing Bazaar repository after upgrading to v1.7.1.
Confirming - I'm on Ubuntu 10.04.3 LTS, no SELinux appears to be installed.
the contents of the /conf/settings_local.py file are:
# Site-specific configuration settings for Review Board
# Definitions of these settings can be found at
# http://docs.djangoproject.com/en/dev/ref/settings/
# Database configuration
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
'NAME': 'reviewboard',
'USER': 'reviewboard',
'PASSWORD': 'rvb',
'HOST': 'localhost',
'PORT': '',
},
}
# Unique secret key. Don't share this with anybody.
SECRET_KEY = 'zf)wa6kg7wh48$=gq#!ouw#-_548$ex-6i=wii+6bhm2w6d!'
# Cache backend settings.
CACHES = {
'default': {
'BACKEND': 'django.core.cache.backends.memcached.MemcachedCache',
'LOCATION': 'localhost:11211',
},
}
# Extra site information.
SITE_ID = 1
SITE_ROOT = '/'
FORCE_SCRIPT_NAME = ''
DEBUG = True
Thanks again for the help.
Brian
On Thursday, January 3, 2013 5:19:42 PM UTC-7, Christian Hammond wrote:
Hi Brian,
One more thing to confirm. Hopefully I can get you some commands to run
soon that will provide more useful info.
What distro are you using, and is SELinux enabled?
Trying to determine what's preventing the resulting process from getting
the PYTHONPATH environment...
Can you also share with me your $sitedir/htdocs/settings_local.py file?
Christian
--
Christian Hammond - chi...@chipx86.com javascript:
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Thu, Jan 3, 2013 at 3:49 PM, Brian phxg...@gmail.com javascript:wrote:
Hello again,
I'm using mod_wsgi.
And when I do
rbssh bazaar@servername
I get access with no errors.
Thanks,
Brian
--
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
reviewboard...@googlegroups.com javascript:
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
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/reviewboard?hl=en
Re: Reviewboard with Perforce repository that uses an SSL connection
Hi David, I'm facing the same issue - However I'm using Perforce 2012.1. Please address the following queries: 1. Does ReviewBoard support SSL connections to Perforce 2012.1? 2. Do let me know when to expect ReviewBoard v1.7.2 release? Are release dates for 1.7.2 (and later) published on a wiki? 3. Will you confirm whether the fix is included in 1.7.2, via its release notes? Please share the link once it is released Thanks, Gayle On Friday, January 4, 2013 5:16:58 AM UTC+5:30, David Trowbridge wrote: I'm afraid that we currently don't support the 2012.2 SSL setup. I'll look into fixing this for 1.7.2. -David -David On Thu, Jan 3, 2013 at 5:26 AM, ralleye red ralle...@gmail.comjavascript: wrote: I've installed ReviewBoard 1.6.13 with Perforce 2012.2 and it contains about 50 review requests that use the Perforce repository. Now, the Perforce(P4) administrator has introduced SSL encryption for P4 connection. P4 connection string has the prefix of *ssl:* After the introduction of *ssl* switch to the connection string, there are issues viewing existing review requests within ReviewBoard. The error is in the attached file: * errorWhenViewingExistingReviewRequests.txt* * * Please suggest how I can use P4 repository which now uses a SSL connection within ReviewBoard. I tried creating a new repository providing the Path of my P4 server with the ssl: prefix. However, this results in error that a reporitory was not found at the specified path -- 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 reviewboard...@googlegroups.com javascript: 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
RE: a couple of issues post 1.7.1 upgrade
All those process_stdin is where it prompts for the password. I don't get why it seems to connect with the key ok and then fall back to password, if that's what is actually happening. -Original Message- From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On Behalf Of Christian Hammond Sent: Thursday, January 03, 2013 5:45 PM To: reviewboard@googlegroups.com Subject: Re: a couple of issues post 1.7.1 upgrade At what point during the log is it asking for the password? It looks like it's connected. Maybe it's svnserve asking for the password? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 5:32 PM, Dave Preston d.pres...@complianceease.com wrote: You are correct, I've gotten a bit sloppy as the day has gone on. So now when I execute svn cat it just keeps prompting me for a password even though the key exists on the other side. The log shows that pubkey is successful and then falls back to password. USER=www-data DEBUG_RBSSH=1 DJANGO_SETTINGS_MODULE=reviewboard.settings HOME=/var/www/reviewboard.logiceasedev.com/data PYTHONPATH=/var/www/reviewboard.logiceasedev.com/conf 01-03 17:29 root DEBUG['/tmp/rbssh', 'svnpoller@svn', 'svnserve', '-t'] 01-03 17:29 root DEBUGPID 30058 01-03 17:29 root DEBUG!!! svn, svnpoller, ['svnserve', '-t'] 01-04 01:29 paramiko.transport DEBUGstarting thread (client mode): 0x1144450L 01-04 01:29 paramiko.transport INFO Connected (version 2.0, client OpenSSH_5.3p1) 01-04 01:29 paramiko.transport DEBUGkex algos:['diffie-hellman-group-exchange-sha256', 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 'diffie-hellman-group1-sha1'] server key: ['ssh-rsa', 'ssh-dss'] client encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfou r', 'rijndael-...@lysator.liu.se'] server encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-c bc', 'arcfour', 'rijndael-...@lysator.liu.se'] client mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] server mac:['hm ac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] client compress:['none', 'z...@openssh.com'] server compress:['none', 'zlib@o penssh.com'] client lang:[''] server lang:[''] kex follows?False 01-04 01:29 paramiko.transport DEBUGCiphers agreed: local=aes128-ctr, remote=aes128-ctr 01-04 01:29 paramiko.transport DEBUGusing kex diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local hmac-sha1, remote hmac- sha1; compression: local none, remote none 01-04 01:29 paramiko.transport DEBUGSwitch to new keys ... 01-04 01:29 paramiko.transport DEBUGTrying SSH key f3a2e6c6b62eba6b6519578ce97e57cd 01-04 01:29 paramiko.transport DEBUGuserauth is OK 01-04 01:29 paramiko.transport INFO Authentication (publickey) successful! 01-04 01:29 paramiko.transport DEBUG[chan 1] Max packet in: 34816 bytes 01-04 01:29 paramiko.transport DEBUG[chan 1] Max packet out: 32768 bytes 01-04 01:29 paramiko.transport INFO Secsh channel 1 opened. 01-04 01:29 root DEBUG!!! Using PosixHandler 01-04 01:29 root DEBUG!!! Sending command ['svnserve', '-t'] 01-04 01:29 paramiko.transport DEBUG[chan 1] Sesch channel 1 request ok 01-04 01:29 root DEBUG!! process_channel 01-04 01:29 root DEBUG!! process_stdin 01-04 01:29 root DEBUG!! process_stdin 01-04 01:29 root DEBUG!! process_stdin .. cut ... 01-04 01:29 paramiko.transport DEBUG[chan 1] EOF received (1) 01-04 01:29 paramiko.transport DEBUG[chan 1] EOF sent (1) 01-04 01:29 root DEBUG!! process_channel -Original Message- From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On Behalf Of Christian Hammond Sent: Thursday, January 03, 2013 4:17 PM To: reviewboard@googlegroups.com Subject: Re: a couple of issues post 1.7.1 upgrade I
Re: Reviewboard with Perforce repository that uses an SSL connection
The ssl: syntax is currently not supported for any perforce release. I think it will be doable but it will probably require manually installing p4python in order to enable SSL support in the library. We don't have a firm schedule for 1.7.2 but it shouldn't be too long. The release notes will definitely list the change if we get it in. -David On Thu, Jan 3, 2013 at 6:46 PM, Gayle Ribeiro sa.ribeiro.ga...@gmail.comwrote: Hi David, I'm facing the same issue - However I'm using Perforce 2012.1. Please address the following queries: 1. Does ReviewBoard support SSL connections to Perforce 2012.1? 2. Do let me know when to expect ReviewBoard v1.7.2 release? Are release dates for 1.7.2 (and later) published on a wiki? 3. Will you confirm whether the fix is included in 1.7.2, via its release notes? Please share the link once it is released Thanks, Gayle On Friday, January 4, 2013 5:16:58 AM UTC+5:30, David Trowbridge wrote: I'm afraid that we currently don't support the 2012.2 SSL setup. I'll look into fixing this for 1.7.2. -David -David On Thu, Jan 3, 2013 at 5:26 AM, ralleye red ralle...@gmail.com wrote: I've installed ReviewBoard 1.6.13 with Perforce 2012.2 and it contains about 50 review requests that use the Perforce repository. Now, the Perforce(P4) administrator has introduced SSL encryption for P4 connection. P4 connection string has the prefix of *ssl:* After the introduction of *ssl* switch to the connection string, there are issues viewing existing review requests within ReviewBoard. The error is in the attached file: *errorWhenViewingExisting ReviewRequests.txt* * * Please suggest how I can use P4 repository which now uses a SSL connection within ReviewBoard. I tried creating a new repository providing the Path of my P4 server with the ssl: prefix. However, this results in error that a reporitory was not found at the specified path -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/**donate/http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/**users/http://www.reviewboard.org/users/ -~--~~~~--**~~--~--~--- To unsubscribe from this group, send email to reviewboard...@** googlegroups.com For more options, visit this group at http://groups.google.com/** group/reviewboard?hl=enhttp://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 reviewboard+unsubscr...@googlegroups.com 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 reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: a couple of issues post 1.7.1 upgrade
If it's process_stdin, it sounds like it's svnserve asking for the password, meaning the SSH authentication was successful. I assume it's doing this in the original log you showed as well, and the lack of stdin was causing the connection to be closed unexpectedly. I don't know why it'd be different from when you were using 1.6.9 (nor do I know what would have changed to break this in this way). Sounds like something changed, though. Were any other things upgraded along with Review Board? The SVN server, or pysvn/libsvn? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 7:59 PM, Dave Preston d.pres...@complianceease.comwrote: All those process_stdin is where it prompts for the password. I don't get why it seems to connect with the key ok and then fall back to password, if that's what is actually happening. -Original Message- From: reviewboard@googlegroups.com [mailto:reviewboard@googlegroups.com] On Behalf Of Christian Hammond Sent: Thursday, January 03, 2013 5:45 PM To: reviewboard@googlegroups.com Subject: Re: a couple of issues post 1.7.1 upgrade At what point during the log is it asking for the password? It looks like it's connected. Maybe it's svnserve asking for the password? Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org VMware, Inc. - http://www.vmware.com On Thu, Jan 3, 2013 at 5:32 PM, Dave Preston d.pres...@complianceease.com wrote: You are correct, I've gotten a bit sloppy as the day has gone on. So now when I execute svn cat it just keeps prompting me for a password even though the key exists on the other side. The log shows that pubkey is successful and then falls back to password. USER=www-data DEBUG_RBSSH=1 DJANGO_SETTINGS_MODULE=reviewboard.settings HOME=/var/www/reviewboard.logiceasedev.com/data PYTHONPATH=/var/www/reviewboard.logiceasedev.com/conf 01-03 17:29 root DEBUG['/tmp/rbssh', 'svnpoller@svn', 'svnserve', '-t'] 01-03 17:29 root DEBUGPID 30058 01-03 17:29 root DEBUG!!! svn, svnpoller, ['svnserve', '-t'] 01-04 01:29 paramiko.transport DEBUGstarting thread (client mode): 0x1144450L 01-04 01:29 paramiko.transport INFO Connected (version 2.0, client OpenSSH_5.3p1) 01-04 01:29 paramiko.transport DEBUGkex algos:['diffie-hellman-group-exchange-sha256', 'diffie-hellman-group-exchange-sha1', 'diffie-hellman-group14-sha1', 'diffie-hellman-group1-sha1'] server key: ['ssh-rsa', 'ssh-dss'] client encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-cbc', 'arcfou r', 'rijndael-...@lysator.liu.se'] server encrypt:['aes128-ctr', 'aes192-ctr', 'aes256-ctr', 'arcfour256', 'arcfour128', 'aes128-cbc', '3des-cbc', 'blowfish-cbc', 'cast128-cbc', 'aes192-cbc', 'aes256-c bc', 'arcfour', 'rijndael-...@lysator.liu.se'] client mac:['hmac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] server mac:['hm ac-md5', 'hmac-sha1', 'umac...@openssh.com', 'hmac-ripemd160', 'hmac-ripemd...@openssh.com', 'hmac-sha1-96', 'hmac-md5-96'] client compress:['none', 'z...@openssh.com'] server compress:['none', 'zlib@o penssh.com'] client lang:[''] server lang:[''] kex follows?False 01-04 01:29 paramiko.transport DEBUGCiphers agreed: local=aes128-ctr, remote=aes128-ctr 01-04 01:29 paramiko.transport DEBUGusing kex diffie-hellman-group1-sha1; server key type ssh-rsa; cipher: local aes128-ctr, remote aes128-ctr; mac: local hmac-sha1, remote hmac- sha1; compression: local none, remote none 01-04 01:29 paramiko.transport DEBUGSwitch to new keys ... 01-04 01:29 paramiko.transport DEBUGTrying SSH key f3a2e6c6b62eba6b6519578ce97e57cd 01-04 01:29 paramiko.transport DEBUGuserauth is OK 01-04 01:29 paramiko.transport INFO Authentication (publickey) successful! 01-04 01:29 paramiko.transport DEBUG[chan 1] Max packet in: 34816 bytes 01-04 01:29 paramiko.transport DEBUG[chan 1] Max packet out: 32768 bytes 01-04 01:29 paramiko.transport INFO Secsh channel 1 opened. 01-04 01:29 root DEBUG!!! Using PosixHandler 01-04 01:29 root DEBUG!!! Sending command ['svnserve', '-t'] 01-04 01:29 paramiko.transport DEBUG[chan 1]
Issue 2844 in reviewboard: Admin templates are broken
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2844 by pmi...@gmail.com: Admin templates are broken http://code.google.com/p/reviewboard/issues/detail?id=2844 * NOTE: For customer support, please post to * * reviewbo...@googlegroups.com * ** * Do not post confidential information in this bug report. * * If you need immediate support, please contact* * reviewbo...@googlegroups.com * What version are you running? 1.7.1 What's the URL of the page containing the problem? http://*/admin/db/auth/user/ What steps will reproduce the problem? 1. Go to Admin 2. Click on Users or Add User What is the expected output? What do you see instead? I expect to see users page but I see an error that template is missing: Request Method: GET Request URL:http://*/admin/db/auth/user/ Django Version: 1.4.3 Exception Type: TemplateDoesNotExist Exception Value: admin/auth/user/change_list.html, admin/auth/change_list.html, admin/change_list.html Exception Location: /usr/lib/python2.6/site-packages/django/template/loader.py in select_template, line 193 Python Executable: /usr/bin/python Python Version: 2.6.6 Python Path: ['/var/www/reviewboard/conf', '/usr/lib/python2.6/site-packages/python_memcached-1.48-py2.6.egg', '/usr/lib/python2.6/site-packages/recaptcha_client-1.0.6-py2.6.egg', '/usr/lib/python2.6/site-packages/pytz-2011n-py2.6.egg', '/usr/lib/python2.6/site-packages/python_dateutil-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/flup-1.0.3.dev_20110405-py2.6.egg', '/usr/lib/python2.6/site-packages/pycrypto-2.4.1-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/PIL-1.1.7-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/MySQL_python-1.2.3-py2.6-linux-x86_64.egg', '/usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg', '/usr/lib/python2.6/site-packages/Pygments-1.5-py2.6.egg', '/usr/lib/python2.6/site-packages/paramiko-1.9.0-py2.6.egg', '/usr/lib/python2.6/site-packages/mimeparse-0.1.3-py2.6.egg', '/usr/lib/python2.6/site-packages/Markdown-2.2.1-py2.6.egg', '/usr/lib/python2.6/site-packages/docutils-0.10-py2.6.egg', '/usr/lib/python2.6/site-packages/django_pipeline-1.2.23-py2.6.egg', '/usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg', '/usr/lib/python2.6/site-packages/django_evolution-0.6.7-py2.6.egg', '/usr/lib/python2.6/site-packages/feedparser-5.1.3-py2.6.egg', '/usr/lib64/python26.zip', '/usr/lib64/python2.6', '/usr/lib64/python2.6/plat-linux2', '/usr/lib64/python2.6/lib-tk', '/usr/lib64/python2.6/lib-old', '/usr/lib64/python2.6/lib-dynload', '/usr/lib64/python2.6/site-packages', '/usr/lib64/python2.6/site-packages/gtk-2.0', '/usr/lib/python2.6/site-packages'] Server time:Thu, 3 Jan 2013 04:28:55 -0800 Template-loader postmortem Django tried loading these templates, in this order: Using loader django.template.loaders.filesystem.Loader: /usr/lib/python2.6/site-packages/ReviewBoard-1.7.1-py2.6.egg/reviewboard/templates/admin/auth/user/change_list.html, admin/auth/change_list.html, admin/change_list.html (File does not exist) Using loader django.template.loaders.app_directories.Loader: /usr/lib/python2.6/site-packages/django/contrib/admin/templates/admin/auth/user/change_list.html, admin/auth/change_list.html, admin/change_list.html (File does not exist) /usr/lib/python2.6/site-packages/django/contrib/auth/templates/admin/auth/user/change_list.html, admin/auth/change_list.html, admin/change_list.html (File does not exist) /usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg/djblets/datagrid/templates/admin/auth/user/change_list.html, admin/auth/change_list.html, admin/change_list.html (File does not exist) /usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg/djblets/extensions/templates/admin/auth/user/change_list.html, admin/auth/change_list.html, admin/change_list.html (File does not exist) /usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg/djblets/feedview/templates/admin/auth/user/change_list.html, admin/auth/change_list.html, admin/change_list.html (File does not exist) /usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg/djblets/log/templates/admin/auth/user/change_list.html, admin/auth/change_list.html, admin/change_list.html (File does not exist) /usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg/djblets/pipeline/templates/admin/auth/user/change_list.html, admin/auth/change_list.html, admin/change_list.html (File does not exist) /usr/lib/python2.6/site-packages/Djblets-0.7.8-py2.6.egg/djblets/siteconfig/templates/admin/auth/user/change_list.html, admin/auth/change_list.html, admin/change_list.html (File does not exist)
Issue 2845 in reviewboard: Reviewers marked as required, even if Groups are used
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2845 by adam.col...@gmail.com: Reviewers marked as required, even if Groups are used http://code.google.com/p/reviewboard/issues/detail?id=2845 What version are you running? 1.7.1 What's the URL of the page containing the problem? http://reviewboard.company.com/r/5000 What steps will reproduce the problem? 1. Use post-review to create a review request with review groups (e.g. --target-groups=my_group) 2. View review request in browser What is the expected output? What do you see instead? Expected: * No red asterisk noting that Reviewers is a required field Actual: * A red asterisk implying that Reviewers should be filled in What operating system are you using? What browser? * Hosted on Ubuntu 12.04, viewed in Firefox 17.0.1 on Ubuntu 12.04 workstation. Please provide any additional information below. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2841 in reviewboard: Using non-standard ssh port (!=22) for connecting to git repository
Comment #1 on issue 2841 by mario.zi...@gmail.com: Using non-standard ssh port (!=22) for connecting to git repository http://code.google.com/p/reviewboard/issues/detail?id=2841 After some more digging, I actually found that the problem is not with schemeless_url_re. Problem seams to be usage of urlparse.urlparse which doesn't differentiate hostname and port in netloc: Parse a URL into 6 components: scheme://netloc/path;params?query#fragment Return a 6-tuple: (scheme, netloc, path, params, query, fragment). Note that we don't break the components up in smaller bits (e.g. netloc is a single string) and we don't expand % escapes. Easy workaround could be to modify check_host method in ssh/utils.py to split netloc in hostname and port as in attached patch created against release-1.7.x branch. When I tried this change, I noticed that connection has been successfully established to my git server but something else went wrong that I don't understand (attached screenshot and logfile). Any help would be appreciated. Regards, Mario Attachments: Enabling-ports-other-than-22-for-SSH-access-to-repos.patch 1.3 KB Screenshoot.png 108 KB error.log 5.2 KB -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2841 in reviewboard: Using non-standard ssh port (!=22) for connecting to git repository
Comment #2 on issue 2841 by mario.zi...@gmail.com: Using non-standard ssh port (!=22) for connecting to git repository http://code.google.com/p/reviewboard/issues/detail?id=2841 Patch submitted for review: http://reviews.reviewboard.org/r/3712/ -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2841 in reviewboard: Using non-standard ssh port (!=22) for connecting to git repository
Updates: Status: PendingReview Labels: Component-SSH Comment #3 on issue 2841 by trowb...@gmail.com: Using non-standard ssh port (!=22) for connecting to git repository http://code.google.com/p/reviewboard/issues/detail?id=2841 (No comment was entered for this change.) -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2842 in reviewboard: Jump to search box does not work in 1.7
Updates: Labels: Component-Search Comment #1 on issue 2842 by trowb...@gmail.com: Jump to search box does not work in 1.7 http://code.google.com/p/reviewboard/issues/detail?id=2842 (No comment was entered for this change.) -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2843 in reviewboard: Extensions' 'config/' and 'db/' admin links don't work when SITE_ROOT isn't '/'
Updates: Labels: Component-Extensions Comment #1 on issue 2843 by trowb...@gmail.com: Extensions' 'config/' and 'db/' admin links don't work when SITE_ROOT isn't '/' http://code.google.com/p/reviewboard/issues/detail?id=2843 (No comment was entered for this change.) -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2845 in reviewboard: Reviewers marked as required, even if Groups are used
Updates: Status: NotABug Comment #1 on issue 2845 by chip...@gmail.com: Reviewers marked as required, even if Groups are used http://code.google.com/p/reviewboard/issues/detail?id=2845 The Reviewers is a heading, of which Groups and People fall under. The asterisk means that there must be reviewers, whether groups or people. They aren't based on whether or not there's already fields filled in. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2844 in reviewboard: Admin templates are broken
Updates: Status: NeedInfo Comment #1 on issue 2844 by chip...@gmail.com: Admin templates are broken http://code.google.com/p/reviewboard/issues/detail?id=2844 The template it's trying to reach is part of Django. Sounds like something is still busted with your Django install. If Django couldn't install, there's something wrong on your system. What problem did you hit? -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
