Re: [Errno 13] Permission denied error when sending emails
Hello Michaela, Could you please explain more how you fixed this issue? I meet the same problem of sending emails in web2py running on Apache (CentOS). Thanks! On Tuesday, August 20, 2013 7:03:51 PM UTC+2, Michaela Newell wrote: Actually, figured out what the last bits were it was because I had TLS ticked but my server didn't have it. Fixed now :) Thanks very much. Your command audit2allow -a did not work however. On Tuesday, 20 August 2013 17:34:39 UTC+1, Michaela Newell wrote: Hi Stephan, Thanks for reply. It is RHEL/CentOS 6. It did not go away when I tried the command but the error message has changed. Output from log now is: - Error sending e-mail notification with subject 'Review Request 2: gfhgf' on behalf of ' .x...@.com' to ' .x...@.com': STARTTLS extension not supported by server. Traceback (most recent call last): File /usr/lib/python2.6/site-packages/reviewboard/notifications/email.py, line 244, in send_review_mail message.send() File /usr/lib/python2.6/site-packages/django/core/mail/message.py, line 248, in send return self.get_connection(fail_silently).send_messages([self]) File /usr/lib/python2.6/site-packages/django/core/mail/backends/smtp.py, line 85, in send_messages new_conn_created = self.open() File /usr/lib/python2.6/site-packages/django/core/mail/backends/smtp.py, line 51, in open self.connection.starttls() File /usr/lib64/python2.6/smtplib.py, line 611, in starttls raise SMTPException(STARTTLS extension not supported by server.) SMTPException: STARTTLS extension not supported by server. The audit2allow -a command came back with command not found, running as root. Michaela On Tuesday, 20 August 2013 14:48:30 UTC+1, Stephen Gallagher wrote: On 08/20/2013 09:46 AM, Michaela Newell wrote: I am attempting to set-up emails. I have all three options selected and a valid smtp server. When I add a new user the logs show nothing but the email does not get sent. When I add a new review request I get this in the log: - Error sending e-mail notification with subject 'Review Request 1: ...' on behalf of ' .x...@.com' to ' .x...@.com': [Errno 13] Permission denied Traceback (most recent call last): File /usr/lib/python2.6/site-packages/reviewboard/notifications/email.py, line 244, in send_review_mail message.send() File /usr/lib/python2.6/site-packages/django/core/mail/message.py, line 248, in send return self.get_connection(fail_silently).send_messages([self]) File /usr/lib/python2.6/site-packages/django/core/mail/backends/smtp.py, line 85, in send_messages new_conn_created = self.open() File /usr/lib/python2.6/site-packages/django/core/mail/backends/smtp.py, line 48, in open local_hostname=DNS_NAME.get_fqdn()) File /usr/lib64/python2.6/smtplib.py, line 239, in __init__ (code, msg) = self.connect(host, port) File /usr/lib64/python2.6/smtplib.py, line 295, in connect self.sock = self._get_socket(host, port, self.timeout) File /usr/lib64/python2.6/smtplib.py, line 273, in _get_socket return socket.create_connection((port, host), timeout) File /usr/lib64/python2.6/socket.py, line 567, in create_connection raise error, msg error: [Errno 13] Permission denied Does anyone know of any causes? Is this RHEL/CentOS 6? It's possibke that SELinux might be interfering. Does it go away if you do 'setenforce 0' as root? If so, please run the command: audit2allow -a and send me the output. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: RB always assumes requestor closes request?
Hi Stephen, We never intentionally had the behavior of sending e-mails on behalf of the user instead of the owner of the review request. I think we did have a bug for a little while where this was the case, but it was internally tracked as the review request owner. The e-mail code was just using the wrong variable. So technically, what we have now is correct, but there's room for improving this. We've played around in the past with the ability to have more fine-grained user tracking for actions like this. We have nothing close to landing, but we do want to properly differentiate between updates made by the review request owner and updates made by an administrator/another user with permissions to close/edit. This is the master bug for this work: https://code.google.com/p/reviewboard/issues/detail?id=2187 Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Thu, Nov 6, 2014 at 7:51 AM, Stephen Bash scb...@gmail.com wrote: Hi all- I'm curious if this is a bug or a feature: since RB 2.0 I've noticed that RB always assumes the user who created the review request closes it. I liked the pre-2.0 model where RB recorded (and sent notifications from) the actual user who selected Submitted or Discarded. A little background: our small development team uses a mix of pre- and post-commit review. New features are developed on topic branches that are reviewed by the whole team before merging, while bug fixes go directly onto the main branch and are reviewed after the fact (a hook script automatically generates each review). The bug fix reviews are distributed by round robin across the development team, and the standard practice is if nothing is wrong, close the review. With the introduction of the Get e-mail notifications for my own activity setting (thank you!), we're now in a situation where a lot of the development team isn't notified when their bug fixes are approved (review closed without comment). So given our workflow, if the new behavior is a bug I'd like to report it; if it's a feature I'd like to request a setting to change the behavior back :) Thanks, Stephen -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: rb-site upgrade Fails (upgrading from 1.6.16 to 2.0.11
Hi Cory, My apologies for the delay. What likely happened is that you ended up with a mix of MyISAM and InnoDB tables. The new MySQL server is likely defaulting to InnoDB, whereas your dump is likely MyISAM. You'll need to fix up the dump to replace all MyISAM instances with InnoDB. You'd then need to re-import the dump. It should work this time. Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Thu, Nov 6, 2014 at 8:14 AM, Cory Demerau rheib...@gmail.com wrote: I'm migrating a 1.6.16 RB site to a new server that's running RB 2.0.11. I created a dump of the mysql database with --max_allowed_packet=512M to minimize the chance of incomplete data. I modified the dump so that all tables use InnoDB instead of MyISAM, and restored the reviewboard database on the new server using the dump. I have Django_Evolution version 0.7.4, and when I try to do an rb-site upgrade, I get the following output: -- begin log output -- Creating tables ... There are unapplied evolutions for auth. There are unapplied evolutions for contenttypes. There are unapplied evolutions for accounts. There are unapplied evolutions for attachments. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for hostingsvcs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. There are unapplied evolutions for site. Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) CommandError: Error applying evolution: (1005, Can't create table 'reviewboard.#sql-3f22_1e8' (errno: 150)) I have also tried (before running rb-site upgrade, but after restoring the database) rb-site manage /path/to/site syncdb. This gives the following output: Creating tables ... Creating table extensions_registeredextension Creating table diffviewer_filediffdata Upgrading Review Board from 1.6.16 to 2.0.11 There are unapplied evolutions for auth. The following content types are stale and need to be deleted: auth | message Any objects related to these content types by a foreign key will also be deleted. Are you sure you want to delete these content types? If you're unsure, answer 'no'. Type 'yes' to continue, or 'no' to cancel: If I type 'yes': There are unapplied evolutions for contenttypes. There are unapplied evolutions for accounts. There are unapplied evolutions for attachments. There are unapplied evolutions for changedescs. There are unapplied evolutions for diffviewer. There are unapplied evolutions for hostingsvcs. There are unapplied evolutions for reviews. There are unapplied evolutions for scmtools. There are unapplied evolutions for site. Adding baseline version for new models Project signature has changed - an evolution is required Installing custom SQL ... Installing indexes ... Installed 0 object(s) from 0 fixture(s) After completing this, there is still no change in the output from rb-site upgrade. In the meantime, the Reviewboard site allows me to access some pages, but most return a 500 error. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: RB always assumes requestor closes request?
Thanks for the update Christian. That bug is exactly what I'm looking for, I'll keep an eye on it. Stephen On Thu, Nov 13, 2014 at 7:43 PM, Christian Hammond chip...@chipx86.com wrote: Hi Stephen, We never intentionally had the behavior of sending e-mails on behalf of the user instead of the owner of the review request. I think we did have a bug for a little while where this was the case, but it was internally tracked as the review request owner. The e-mail code was just using the wrong variable. So technically, what we have now is correct, but there's room for improving this. We've played around in the past with the ability to have more fine-grained user tracking for actions like this. We have nothing close to landing, but we do want to properly differentiate between updates made by the review request owner and updates made by an administrator/another user with permissions to close/edit. This is the master bug for this work: https://code.google.com/p/reviewboard/issues/detail?id=2187 Christian -- Christian Hammond - chip...@chipx86.com Review Board - http://www.reviewboard.org Beanbag, Inc. - http://www.beanbaginc.com On Thu, Nov 6, 2014 at 7:51 AM, Stephen Bash scb...@gmail.com wrote: Hi all- I'm curious if this is a bug or a feature: since RB 2.0 I've noticed that RB always assumes the user who created the review request closes it. I liked the pre-2.0 model where RB recorded (and sent notifications from) the actual user who selected Submitted or Discarded. A little background: our small development team uses a mix of pre- and post-commit review. New features are developed on topic branches that are reviewed by the whole team before merging, while bug fixes go directly onto the main branch and are reviewed after the fact (a hook script automatically generates each review). The bug fix reviews are distributed by round robin across the development team, and the standard practice is if nothing is wrong, close the review. With the introduction of the Get e-mail notifications for my own activity setting (thank you!), we're now in a situation where a lot of the development team isn't notified when their bug fixes are approved (review closed without comment). So given our workflow, if the new behavior is a bug I'd like to report it; if it's a feature I'd like to request a setting to change the behavior back :) Thanks, Stephen -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to a topic in the Google Groups reviewboard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/reviewboard/pNP6pmilUsw/unsubscribe. To unsubscribe from this group and all its topics, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Gitlab integration problem
Thank you. You can mark this solved! On Thursday, 13 November 2014 02:53:51 UTC+5:30, David Trowbridge wrote: You'll want to back up that directory, as well as your database. Whether or not you back up the other apache configuration is up to you (the important config files live in the site directory). -David On Wed, Nov 12, 2014 at 1:35 AM, Rajasiman Srinivasan raja...@gmail.com javascript: wrote: Thanks for your reply! I had installed git on Windows without adding the location to the PATH environment variable. Therefore rbt post/rbt setup-repo was unable to execute git commands from cmd. After I added it, it started working fine. Also, another question. If I want to do a daily backup of the reviewboard installation, which folders do I include? Would /var/www/reviewboard_installation_folder/ suffice? Lastly, should I also be backing up the apache2 configuration files? Thank you! - Rajasiman On Wednesday, 12 November 2014 12:43:49 UTC+5:30, David Trowbridge wrote: It looks like your repository is configured correctly in the Review Board admin. You won't see branches or commits in the New Review Request page because this feature is currently only available for GitHub and SVN repositories. If you've created the .reviewboardrc file yourself, you don't need to run 'rbt setup-repo' (all that command does is prompt you for some information and creates the file). All 'rbt' commands should be run from within a checkout of your repository. It looks like you're probably not in the right directory in your cmd prompt. If you are, then maybe something is going wrong with the detection--can you re-run 'rbt post' with the --debug flag? -David On Tue, Nov 11, 2014 at 10:20 PM, Rajasiman Srinivasan raja...@gmail.com wrote: Hello all, I'm setting up a Gitlab + ReviewBoard combination for a pilot project at work. I've set up most of the things needed correctly but the Gitlab branches/commits do not show up in the ReviewBoard site that I set up. Here's my setup. - Gitlab: 7.4.3 - ReviewBoard: 2.0.11 Gitlab runs on server with IP address 192.168.0.104, ReviewBoard on server with IP address 192.168.0.127. Both the websites are setup and are working without throwing any errors. I've created a service account(reviewboard_user) on Gitlab with 'Reporter' permissions to the 'group' of projects. Next, I created the SSH key for this account from ReviewBoard and installed it onto the service account on Gitlab. I've added the Gitlab repository in ReviewBoard(Please see attached screenshot: Repository added in Reviewboard.PNG). I then clicked on New Review Request from the homepage and was taken to this screen(Please see attached screenshot: New Review Request.PNG). The branches/commits were not being shown; so I clicked around and found that I need to set up rbtools and should create a file '.reviewboardrc' in the root of my git repository and commit it(Please see attached screenshot: RBTools setup.PNG). I use a Windows PC, so I created the file in my local git repository and committed the file to Gitlab. Then I tried running rbt post via cmd and was given a error. ERROR: The current directory does not contain a checkout from a supported source code repository. After some more googling and reading around, I got to this page https://www.reviewboard.org/docs/rbtools/dev/rbt/configuration/. Tried running rbt setup-repo via cmd inside the root of the git repository and got the same error message again. ERROR: The current directory does not contain a checkout from a supported source code repository. What am I doing wrong here? As per this link https://www.reviewboard.org/docs/manual/dev/admin/configuration/repositories/#git, git needs a local clone; whereas from Reviewboard v1.7.21 Gitlab is natively supported http://feedback.gitlab.com/forums/176466-general/suggestions/4566001-expose-raw-object-search-via-the-gitlab-api. Please help me get this sorted out! Thanks in advance! - Rajasiman -- Get the Review Board Power Pack at http://www.reviewboard.org/ powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups reviewboard group. To unsubscribe from this group and stop receiving emails from it, send an
Re: Issue 3660 in reviewboard: Files randomly get lost from a review request (This is an empty file.)
Comment #6 on issue 3660 by matt...@salsitasoft.com: Files randomly get lost from a review request (This is an empty file.) https://code.google.com/p/reviewboard/issues/detail?id=3660 Note that https://code.google.com/p/reviewboard/issues/detail?id=3601 appears to be the same issue. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3306 in reviewboard: server Erro page when click Ship it! behind proxy reverse
Comment #9 on issue 3306 by f...@esss.com.br: server Erro page when click Ship it! behind proxy reverse https://code.google.com/p/reviewboard/issues/detail?id=3306 Hi, I found the solution, based on a similar problem with tomcat, I discovered that Django have a parameter to use with Proxy Rever/Loadbalancer: the follow line must be inside conf/settings_local.py USE_X_FORWARDED_HOST = True Thanks for you help -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3648 in reviewboard: rbt post of committed code not supported for Perforce
Comment #2 on issue 3648 by gavin.d@gmail.com: rbt post of committed
code not supported for Perforce
https://code.google.com/p/reviewboard/issues/detail?id=3648
Yes I'm using Perforce client Rev. P4/NTX86/2010.1/251161 (2010/06/16).
I understand that the initial call to p4.change will return the status as
pending or submitted, and that when it's submitted there is different
logic. However I don't understand p4.filelog('//...@%s,%s' % (real_base,
tip)) because a revision range syntax cannot be used for a changelist
number.
I think the correct syntax should be something like this which specifies a
changelist number:
p4 filelog -c822657 -m1 //...
Thanks.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
You received this message because you are subscribed to the Google Groups
reviewboard-issues group.
To unsubscribe from this group and stop receiving emails from it, send an email
to reviewboard-issues+unsubscr...@googlegroups.com.
To post to this group, send email to reviewboard-issues@googlegroups.com.
Visit this group at http://groups.google.com/group/reviewboard-issues.
For more options, visit https://groups.google.com/d/optout.
Re: Issue 3659 in reviewboard: RBTools 0.6.2 not able to differentiate the binary content
Comment #10 on issue 3659 by shahgunj...@gmail.com: RBTools 0.6.2 not able to differentiate the binary content https://code.google.com/p/reviewboard/issues/detail?id=3659 Any update on this ? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3659 in reviewboard: RBTools 0.6.2 not able to differentiate the binary content
Updates: Status: Confirmed Labels: -Priority-Medium Priority-Low Component-RBTools Project-RBTools Comment #11 on issue 3659 by trowb...@gmail.com: RBTools 0.6.2 not able to differentiate the binary content https://code.google.com/p/reviewboard/issues/detail?id=3659 This is something that we'll fix eventually, but it's pretty low priority. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
Re: Issue 3561 in reviewboard: New Select Rows and Close Submitted doesn't seem to work
Updates: Status: Confirmed Labels: -Priority-Medium Priority-High RBCommons Component-Dashboard Comment #1 on issue 3561 by chip...@gmail.com: New Select Rows and Close Submitted doesn't seem to work https://code.google.com/p/reviewboard/issues/detail?id=3561 Hi, This unfortunately got buried in our bug queue. As an RBCommons customer, you're welcome at any point to contact our support channel (supp...@beanbaginc.com) and we'll get a reply to you much faster. Thanks for letting us know about this. We'll try to get a fix in shortly. (Just a note for us: This bug exists solely on RBCommons, and is not present in Review Board.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/d/optout.
