Re: LDAP Configuration
Thanks for reply Christian. Here are errors from log when I tried to login post providing LDAP Config: [Tue Jul 16 09:02:10.804190 2019] [:error] [pid 20450] WARNING:root:LDAP error: The specified object does not exist in the Directory or provided invalid credentials: sveerla [Tue Jul 16 09:02:29.222958 2019] [:error] [pid 20136] WARNING:root:LDAP error: The specified object does not exist in the Directory or provided invalid credentials: builder Thanks, Sagar On Wednesday, July 17, 2019 at 1:40:09 AM UTC+5:30, Christian Hammond wrote: > > Hi Sagar, > > When a user with an account on the LDAP server tries to log into Review > Board for the first time, Review Board will ask the LDAP server for details > on that username and create an account locally. The LDAP server will > continue to be used for authentication. > > If this isn't working, then it's possible Review Board isn't configured to > talk to LDAP correctly. We log a number of LDAP-related issues. Can you > check the log file to see if you can see any? > > Christian > > On Tue, Jul 16, 2019 at 7:47 AM Sagar Veerla > wrote: > >> Hi All, >> >> Am using LDAP Authentication for Reviewboard, post adding the >> configuration details and trying to login. It fails to login. >> Do we need to create the users explicitly or do they get populated >> automatically? >> >> Thanks, >> Sagar >> >> -- >> Supercharge your Review Board with Power Pack: >> https://www.reviewboard.org/powerpack/ >> Want us to host Review Board for you? Check out RBCommons: >> https://rbcommons.com/ >> Happy user? Let us know! https://www.reviewboard.org/users/ >> --- >> You received this message because you are subscribed to the Google Groups >> "Review Board Community" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to revie...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/reviewboard/567de255-33d8-4c31-a50b-00116c0827e2%40googlegroups.com >> >> <https://groups.google.com/d/msgid/reviewboard/567de255-33d8-4c31-a50b-00116c0827e2%40googlegroups.com?utm_medium=email_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Christian Hammond > President/CEO of Beanbag <https://www.beanbaginc.com/> > Makers of Review Board <https://www.reviewboard.org/> > -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "Review Board Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/reviewboard/5d6f63e2-f025-4fdf-9e24-505e1cebec2a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
LDAP Configuration
Hi All, Am using LDAP Authentication for Reviewboard, post adding the configuration details and trying to login. It fails to login. Do we need to create the users explicitly or do they get populated automatically? Thanks, Sagar -- Supercharge your Review Board with Power Pack: https://www.reviewboard.org/powerpack/ Want us to host Review Board for you? Check out RBCommons: https://rbcommons.com/ Happy user? Let us know! https://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "Review Board Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/reviewboard/567de255-33d8-4c31-a50b-00116c0827e2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue upgrading from 1.7.14 to 2.0.2
So I changed my.cnf and set the default character set to utf8. the apache log still shows: codereviewtest.nyab-tds:80 127.0.0.1 - - [30/Jun/2014:20:01:32 +] GET /admin/ HTTP/1.1 500 551 - Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0 On Monday, 30 June 2014 14:39:49 UTC-5, sagar wrote: I hadn't change anything in mysql, so that's weird. I'll try this and post in a bit. On Friday, 27 June 2014 15:01:43 UTC-5, David Trowbridge wrote: It looks like your table charsets aren't set properly in MySQL. I'd go in with the MySQL client and set them all to utf-8. -David On Jun 27, 2014, at 12:08 PM, sagar khushala...@gmail.com wrote: There are three log files for apache: *other_vhosts_access.log*: codereview.nyab-tds:80 149.244.179.118 - - [27/Jun/2014:19:03:44 +] - 408 0 - - codereview.nyab-tds:80 149.244.178.251 - - [27/Jun/2014:19:03:54 +] GET /dashboard/ HTTP/1.1 200 4318 http://codereview.nyab-tds/dashboard/; Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 codereview.nyab-tds:80 149.244.179.84 - - [27/Jun/2014:19:04:00 +] - 408 0 - - codereview.nyab-tds:80 149.244.179.96 - - [27/Jun/2014:19:04:10 +] GET /api/review-requests/1280/last-update/?api_format=json HTTP/1.1 304 273 http://dfws0237.corp.knorr-bremse.com/r/1280/; Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.132 Safari/537.36 *access.log* is blank *error.log*: Error opening file for reading: Permission denied [Fri Jun 27 18:07:41 2014] [error] /usr/local/lib/python2.7/dist-packages/Django-1.4.8-py2.7.egg/django/db/backends/mysql/base.py:114: Warning: Incorrect string value: '\\xE2\\x88\\x92 (1...' for column 'description' at row 1 [Fri Jun 27 18:07:41 2014] [error] return self.cursor.execute(query, args) On Friday, 27 June 2014 12:25:08 UTC-5, David Trowbridge wrote: What about the apache error logs? -David On Jun 27, 2014, at 8:24 AM, sagar khushala...@gmail.com wrote: Hi! We are currently on 1.7.14 and I am looking to upgrade us to 2.0.2. I've tried 3 paths to upgrade (all following the RB instructions - upgrade RB, upgrade site, restart apache and memcached): 1.7.14 - 2.0.2 1.7.14 - 1.7.26 - 2.0.2 1.7.14 - 2.0.1 - 2.0.2 *I didn't go from 1.7.14 to 1.7.26 to 2.0.1 because of the schema change issue; figured it was probably not a good idea. * The upgrade seems to be successful each time. However, the moment I try to go to the site, I get the following error: *Something broke! (Error 500)* *It appears something broke when you tried to go to here. This is either a bug in Review Board or a server configuration error. Please report this to your administrator.* I tried looking at the server log but there was nothing there (last entry was review related). I deleted the old log to see if one would get created, but no joy. Not sure how to debug this. Has anyone had this issue, and any ideas what I could to upgrade successfully? The rb-site upgrade output for path 1 (1.7.14 - 2.0.2) is below: - begin log output --- Creating tables ... Upgrading Review Board from 1.7.14 to 2.0.2 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. 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) Evolution successful. - end log output --- Resetting in-database caches Upgrade complete! -- 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 email to reviewboard...@googlegroups.com. For more options, visit https
Issue upgrading from 1.7.14 to 2.0.2
Hi! We are currently on 1.7.14 and I am looking to upgrade us to 2.0.2. I've tried 3 paths to upgrade (all following the RB instructions - upgrade RB, upgrade site, restart apache and memcached): 1.7.14 - 2.0.2 1.7.14 - 1.7.26 - 2.0.2 1.7.14 - 2.0.1 - 2.0.2 *I didn't go from 1.7.14 to 1.7.26 to 2.0.1 because of the schema change issue; figured it was probably not a good idea. * The upgrade seems to be successful each time. However, the moment I try to go to the site, I get the following error: *Something broke! (Error 500)* *It appears something broke when you tried to go to here. This is either a bug in Review Board or a server configuration error. Please report this to your administrator.* I tried looking at the server log but there was nothing there (last entry was review related). I deleted the old log to see if one would get created, but no joy. Not sure how to debug this. Has anyone had this issue, and any ideas what I could to upgrade successfully? The rb-site upgrade output for path 1 (1.7.14 - 2.0.2) is below: - begin log output --- Creating tables ... Upgrading Review Board from 1.7.14 to 2.0.2 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. 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) Evolution successful. - end log output --- Resetting in-database caches Upgrade complete! -- 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: Issue upgrading from 1.7.14 to 2.0.2
There are three log files for apache: *other_vhosts_access.log*: codereview.nyab-tds:80 149.244.179.118 - - [27/Jun/2014:19:03:44 +] - 408 0 - - codereview.nyab-tds:80 149.244.178.251 - - [27/Jun/2014:19:03:54 +] GET /dashboard/ HTTP/1.1 200 4318 http://codereview.nyab-tds/dashboard/; Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 codereview.nyab-tds:80 149.244.179.84 - - [27/Jun/2014:19:04:00 +] - 408 0 - - codereview.nyab-tds:80 149.244.179.96 - - [27/Jun/2014:19:04:10 +] GET /api/review-requests/1280/last-update/?api_format=json HTTP/1.1 304 273 http://dfws0237.corp.knorr-bremse.com/r/1280/; Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.132 Safari/537.36 *access.log* is blank *error.log*: Error opening file for reading: Permission denied [Fri Jun 27 18:07:41 2014] [error] /usr/local/lib/python2.7/dist-packages/Django-1.4.8-py2.7.egg/django/db/backends/mysql/base.py:114: Warning: Incorrect string value: '\\xE2\\x88\\x92 (1...' for column 'description' at row 1 [Fri Jun 27 18:07:41 2014] [error] return self.cursor.execute(query, args) On Friday, 27 June 2014 12:25:08 UTC-5, David Trowbridge wrote: What about the apache error logs? -David On Jun 27, 2014, at 8:24 AM, sagar khushala...@gmail.com javascript: wrote: Hi! We are currently on 1.7.14 and I am looking to upgrade us to 2.0.2. I've tried 3 paths to upgrade (all following the RB instructions - upgrade RB, upgrade site, restart apache and memcached): 1.7.14 - 2.0.2 1.7.14 - 1.7.26 - 2.0.2 1.7.14 - 2.0.1 - 2.0.2 *I didn't go from 1.7.14 to 1.7.26 to 2.0.1 because of the schema change issue; figured it was probably not a good idea. * The upgrade seems to be successful each time. However, the moment I try to go to the site, I get the following error: *Something broke! (Error 500)* *It appears something broke when you tried to go to here. This is either a bug in Review Board or a server configuration error. Please report this to your administrator.* I tried looking at the server log but there was nothing there (last entry was review related). I deleted the old log to see if one would get created, but no joy. Not sure how to debug this. Has anyone had this issue, and any ideas what I could to upgrade successfully? The rb-site upgrade output for path 1 (1.7.14 - 2.0.2) is below: - begin log output --- Creating tables ... Upgrading Review Board from 1.7.14 to 2.0.2 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. 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) Evolution successful. - end log output --- Resetting in-database caches Upgrade complete! -- 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 javascript:. 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.
Importing only users/groups from old installation to new one
Hi, and thanks in advance for any help! I was wondering if it was possible to only import users and review-groups from an old installation to a new one (via a mysqldump of some sort). I thought of doing a full mysql dump, but we're switched servers and are changing our repos (CVS - P4), so don't really want to import review requests that will become obsolete. Thanks! Sagar -- 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/groups/opt_out.
Can't seem to connect to pserver CVS repository
Using ReviewBoard version 1.6.5 I've tried the following: *:pserver:user:pass@repo-url:/path/to/repo* ** *:pserver:user@repo-url:/path/to/repo* ** *:pserver:repo-url:/path/to/repo* all with and without the username/password fields filled in. I always get the error: A repository was not found at the specified path. I'm at a loss. Any ideas on what this could be? I can use the command line on the machine to go to the same repository and checkout stuff, using the same URIs, and username and password. -- 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
