Re: post-reviews: The requested URL could not be retrieved
Looking at my %appdata% folder... Does .reviewboardrc get automatically installed? I don't see it in my %appdata% folder. Thanks! Peter On Jun 21, 12:42 pm, Leonel Togniolli wrote: > http://www.reviewboard.org/docs/manual/dev/users/tools/post-review/#r... > > On windows, I have it on each user's "%appdata%" folder. > > On Tue, Jun 21, 2011 at 4:20 PM, ptrchen wrote: > > Hi Leonel, > > > Thanks for the reply, but where may I find .reviewboardrc? > > > Thanks! > > > Peter > > > On Jun 20, 4:42 am, Leonel Togniolli wrote: > >> Hi ptrchen, > > >> I worked around this issue by adding two lines to .reviewboardrc > > >> import os > >> os.environ["no_proxy"] = "*" > > >> On Fri, Jun 17, 2011 at 7:48 PM, ptrchen wrote: > >> > Hi Christian, > > >> > I think this page suggestions that should address my issues, correct? > >> >http://groups.google.com/group/reviewboard/browse_thread/thread/69e33... > > >> > On Jun 10, 4:54 pm, ptrchen wrote: > >> >> Sorry Chrisitan, never mind, I misread your post. I'll do some more > >> >> digging for overriding the proxy configuration > > >> >> On Jun 10, 4:51 pm,ptrchen wrote: > > >> >> > Ah, so would setting the environment variable in the command prompt > >> >> > window do the trick? > > >> >> > On Jun 10, 4:32 pm, Christian Hammond wrote: > > >> >> > > We've seen people run into this sort of error with proxy servers. > >> >> > > Regardless > >> >> > > of your client-side proxy server configuration (say, in your > >> >> > > Internet > >> >> > > settings, on Windows), it may still use the proxy server on > >> >> > > post-review. > > >> >> > > The error output looks very much like it came from a proxy server, > >> >> > > meaning > >> >> > > that the request is going out to the proxy, and the proxy can't > >> >> > > find the > >> >> > > domain. You'll need to blacklist it. I don't recall if it will at > >> >> > > all > >> >> > > respect this black list with Python running on Windows. If it's > >> >> > > Linux, then > >> >> > > you want to be sure your http_proxy environment variable isn't set. > > >> >> > > This has come up a couple of times, and it's clear we need a > >> >> > > setting in > >> >> > > post-review itself to just override the proxy configuration. > > >> >> > > If you search on this mailing list, you'll probably find a couple > >> >> > > other > >> >> > > solutions. > > >> >> > > Christian > > >> >> > > -- > >> >> > > Christian Hammond - chip...@chipx86.com > >> >> > > Review Board -http://www.reviewboard.org > >> >> > > VMware, Inc. -http://www.vmware.com > > >> >> > > On Fri, Jun 10, 2011 at 3:55 PM,ptrchen wrote: > >> >> > > > Sorry for not listing all the output, but company policy > >> >> > > > prohibits me > >> >> > > > from doing that. > > >> >> > > > Yes, the error lists the hostname and FQDN > > >> >> > > > Also, we do give it the FQDN following the --server option > > >> >> > > > On Jun 10, 2:56 pm, Tucker wrote: > >> >> > > > > Does the error actually only list the hostname and not the fully > >> >> > > > > qualified name? If so, that may be part of your problem > >> >> > > > > (throwing out > >> >> > > > > guesses). Have you tried using the fully qualified name? > > >> >> > > > > On Fri, Jun 10, 2011 at 11:22 AM,ptrchen > >> >> > > > > wrote: > >> >> > > > > > Hi Tucker, > > >> >> > > > > > Thanks for the reply. > > >> >> > > > > > I ran "nslookup " from both (XP > >> >> > > > > > server) and > >> >> > > > > > from a sparc-solaris2.10 machine. > > >> >> > > > > > Both return > > >> >> > > > > > Name: . > >> >> > > > > > Address: > > >> >> > > > > > On Jun 10, 11:15 am, Tucker wrote: > >> >> > > > > >> You appear to have a DNS problem: > > >> >> > > > > >> "Unable to determine IP address from host name for > >> >> > > > > >> ." > > >> >> > > > > >> What does "nslookup " say? > > >> >> > > > > >> On Thu, Jun 9, 2011 at 7:12 PM,ptrchen > >> >> > > > > >> wrote: > >> >> > > > > >> > Hi, > > >> >> > > > > >> > We've been trying to run post-review but have been running > >> >> > > > > >> > into a > >> >> > > > > >> > "requested URL could not be retrieved" error > > >> >> > > > > >> > We're running: > > >> >> > > > > >> > ReviewBoard 1.5.5 on Windows XP > >> >> > > > > >> > Python 2.5.x > >> >> > > > > >> > Apache 2.2.x > > >> >> > > > > >> > Subversion 1.6.16, running on a sparc-solaris2.10 > > >> >> > > > > >> > Here is the output after adding the --debug option: > > >> >> > > > -- > >> >> > > > > >> > post-review --server=/ > >> >> > > > > >> > --username= -- > >> >> > > > > >> > password= --revision-range=8325 --debug > >> >> > > > > >> RBTools 0.3.2 > >> >> > > > > >> Home = C:\Documents and Settings\\Application Data > >> >> > > > > >> svn info > >> >> > > > > >> diff --version > >> >> > > > > >> repository info: Path: > >> >> > > > > >> //, Base >
Re: 403 forbidden in Apache
On Tue, Jun 21, 2011 at 3:11 AM, Krles wrote: > # Direct all other requests to the fastcgi server Unless you have a specific reason for using fastcgi, I recommend using wsgi. mod_fcgid has a bunch of timeouts that make it hard to tune for an application that may take a while to run. I would redo 'rb-site install' and use mod_wsgi. Thanks, Anton -- 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: post-reviews: The requested URL could not be retrieved
http://www.reviewboard.org/docs/manual/dev/users/tools/post-review/#reviewboardrc On windows, I have it on each user's "%appdata%" folder. On Tue, Jun 21, 2011 at 4:20 PM, ptrchen wrote: > Hi Leonel, > > Thanks for the reply, but where may I find .reviewboardrc? > > Thanks! > > Peter > > On Jun 20, 4:42 am, Leonel Togniolli wrote: >> Hi ptrchen, >> >> I worked around this issue by adding two lines to .reviewboardrc >> >> import os >> os.environ["no_proxy"] = "*" >> >> On Fri, Jun 17, 2011 at 7:48 PM, ptrchen wrote: >> > Hi Christian, >> >> > I think this page suggestions that should address my issues, correct? >> >http://groups.google.com/group/reviewboard/browse_thread/thread/69e33... >> >> > On Jun 10, 4:54 pm, ptrchen wrote: >> >> Sorry Chrisitan, never mind, I misread your post. I'll do some more >> >> digging for overriding the proxy configuration >> >> >> On Jun 10, 4:51 pm,ptrchen wrote: >> >> >> > Ah, so would setting the environment variable in the command prompt >> >> > window do the trick? >> >> >> > On Jun 10, 4:32 pm, Christian Hammond wrote: >> >> >> > > We've seen people run into this sort of error with proxy servers. >> >> > > Regardless >> >> > > of your client-side proxy server configuration (say, in your Internet >> >> > > settings, on Windows), it may still use the proxy server on >> >> > > post-review. >> >> >> > > The error output looks very much like it came from a proxy server, >> >> > > meaning >> >> > > that the request is going out to the proxy, and the proxy can't find >> >> > > the >> >> > > domain. You'll need to blacklist it. I don't recall if it will at all >> >> > > respect this black list with Python running on Windows. If it's >> >> > > Linux, then >> >> > > you want to be sure your http_proxy environment variable isn't set. >> >> >> > > This has come up a couple of times, and it's clear we need a setting >> >> > > in >> >> > > post-review itself to just override the proxy configuration. >> >> >> > > If you search on this mailing list, you'll probably find a couple >> >> > > other >> >> > > solutions. >> >> >> > > Christian >> >> >> > > -- >> >> > > Christian Hammond - chip...@chipx86.com >> >> > > Review Board -http://www.reviewboard.org >> >> > > VMware, Inc. -http://www.vmware.com >> >> >> > > On Fri, Jun 10, 2011 at 3:55 PM,ptrchen wrote: >> >> > > > Sorry for not listing all the output, but company policy prohibits >> >> > > > me >> >> > > > from doing that. >> >> >> > > > Yes, the error lists the hostname and FQDN >> >> >> > > > Also, we do give it the FQDN following the --server option >> >> >> > > > On Jun 10, 2:56 pm, Tucker wrote: >> >> > > > > Does the error actually only list the hostname and not the fully >> >> > > > > qualified name? If so, that may be part of your problem >> >> > > > > (throwing out >> >> > > > > guesses). Have you tried using the fully qualified name? >> >> >> > > > > On Fri, Jun 10, 2011 at 11:22 AM,ptrchen wrote: >> >> > > > > > Hi Tucker, >> >> >> > > > > > Thanks for the reply. >> >> >> > > > > > I ran "nslookup " from both (XP >> >> > > > > > server) and >> >> > > > > > from a sparc-solaris2.10 machine. >> >> >> > > > > > Both return >> >> >> > > > > > Name: . >> >> > > > > > Address: >> >> >> > > > > > On Jun 10, 11:15 am, Tucker wrote: >> >> > > > > >> You appear to have a DNS problem: >> >> >> > > > > >> "Unable to determine IP address from host name for >> >> > > > > >> ." >> >> >> > > > > >> What does "nslookup " say? >> >> >> > > > > >> On Thu, Jun 9, 2011 at 7:12 PM,ptrchen >> >> > > > > >> wrote: >> >> > > > > >> > Hi, >> >> >> > > > > >> > We've been trying to run post-review but have been running >> >> > > > > >> > into a >> >> > > > > >> > "requested URL could not be retrieved" error >> >> >> > > > > >> > We're running: >> >> >> > > > > >> > ReviewBoard 1.5.5 on Windows XP >> >> > > > > >> > Python 2.5.x >> >> > > > > >> > Apache 2.2.x >> >> >> > > > > >> > Subversion 1.6.16, running on a sparc-solaris2.10 >> >> >> > > > > >> > Here is the output after adding the --debug option: >> >> >> > > > -- >> >> > > > > >> > post-review --server=/ --username= >> >> > > > > >> > -- >> >> > > > > >> > password= --revision-range=8325 --debug >> >> > > > > >> RBTools 0.3.2 >> >> > > > > >> Home = C:\Documents and Settings\\Application Data >> >> > > > > >> svn info >> >> > > > > >> diff --version >> >> > > > > >> repository info: Path: >> >> > > > > >> //, Base >> >> > > > pa >> >> > > > > >> > th: /trunk, Supports changesets: False >> >> > > > > >> HTTP GETting api/ >> >> > > > > >> Got HTTP error: 503: > >> > > > > >> HTML 4.01 >> >> > > > Transition >> >> > > > > >> > al//EN" "http://www.w3.org/TR/html4/loose.dtd";> >> >> > > > > >> > > >> > > > > >> > CONTENT="text/html; >> >> > > > > >> > charset=iso-8859 >> >> >
RBTools Windows installation
Hi, So I used easy_install for installing RBTools (ran "easy_install -U RBTools") It installed "C:\Python25\Scripts\post-review.exe \post- review.exe.manifest \post-review-script.py and "C:\Python25\Lib\site-packages\RBTools-0.3.2-py2.5.egg" Was the RBTools egg file supposed to install as a directory? Thanks! Peter -- 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: post-reviews: The requested URL could not be retrieved
Hi Leonel, Thanks for the reply, but where may I find .reviewboardrc? Thanks! Peter On Jun 20, 4:42 am, Leonel Togniolli wrote: > Hi ptrchen, > > I worked around this issue by adding two lines to .reviewboardrc > > import os > os.environ["no_proxy"] = "*" > > On Fri, Jun 17, 2011 at 7:48 PM, ptrchen wrote: > > Hi Christian, > > > I think this page suggestions that should address my issues, correct? > >http://groups.google.com/group/reviewboard/browse_thread/thread/69e33... > > > On Jun 10, 4:54 pm, ptrchen wrote: > >> Sorry Chrisitan, never mind, I misread your post. I'll do some more > >> digging for overriding the proxy configuration > > >> On Jun 10, 4:51 pm,ptrchen wrote: > > >> > Ah, so would setting the environment variable in the command prompt > >> > window do the trick? > > >> > On Jun 10, 4:32 pm, Christian Hammond wrote: > > >> > > We've seen people run into this sort of error with proxy servers. > >> > > Regardless > >> > > of your client-side proxy server configuration (say, in your Internet > >> > > settings, on Windows), it may still use the proxy server on > >> > > post-review. > > >> > > The error output looks very much like it came from a proxy server, > >> > > meaning > >> > > that the request is going out to the proxy, and the proxy can't find > >> > > the > >> > > domain. You'll need to blacklist it. I don't recall if it will at all > >> > > respect this black list with Python running on Windows. If it's Linux, > >> > > then > >> > > you want to be sure your http_proxy environment variable isn't set. > > >> > > This has come up a couple of times, and it's clear we need a setting in > >> > > post-review itself to just override the proxy configuration. > > >> > > If you search on this mailing list, you'll probably find a couple other > >> > > solutions. > > >> > > Christian > > >> > > -- > >> > > Christian Hammond - chip...@chipx86.com > >> > > Review Board -http://www.reviewboard.org > >> > > VMware, Inc. -http://www.vmware.com > > >> > > On Fri, Jun 10, 2011 at 3:55 PM,ptrchen wrote: > >> > > > Sorry for not listing all the output, but company policy prohibits me > >> > > > from doing that. > > >> > > > Yes, the error lists the hostname and FQDN > > >> > > > Also, we do give it the FQDN following the --server option > > >> > > > On Jun 10, 2:56 pm, Tucker wrote: > >> > > > > Does the error actually only list the hostname and not the fully > >> > > > > qualified name? If so, that may be part of your problem (throwing > >> > > > > out > >> > > > > guesses). Have you tried using the fully qualified name? > > >> > > > > On Fri, Jun 10, 2011 at 11:22 AM,ptrchen wrote: > >> > > > > > Hi Tucker, > > >> > > > > > Thanks for the reply. > > >> > > > > > I ran "nslookup " from both (XP > >> > > > > > server) and > >> > > > > > from a sparc-solaris2.10 machine. > > >> > > > > > Both return > > >> > > > > > Name: . > >> > > > > > Address: > > >> > > > > > On Jun 10, 11:15 am, Tucker wrote: > >> > > > > >> You appear to have a DNS problem: > > >> > > > > >> "Unable to determine IP address from host name for > >> > > > > >> ." > > >> > > > > >> What does "nslookup " say? > > >> > > > > >> On Thu, Jun 9, 2011 at 7:12 PM,ptrchen wrote: > >> > > > > >> > Hi, > > >> > > > > >> > We've been trying to run post-review but have been running > >> > > > > >> > into a > >> > > > > >> > "requested URL could not be retrieved" error > > >> > > > > >> > We're running: > > >> > > > > >> > ReviewBoard 1.5.5 on Windows XP > >> > > > > >> > Python 2.5.x > >> > > > > >> > Apache 2.2.x > > >> > > > > >> > Subversion 1.6.16, running on a sparc-solaris2.10 > > >> > > > > >> > Here is the output after adding the --debug option: > > >> > > > -- > >> > > > > >> > post-review --server=/ --username= > >> > > > > >> > -- > >> > > > > >> > password= --revision-range=8325 --debug > >> > > > > >> RBTools 0.3.2 > >> > > > > >> Home = C:\Documents and Settings\\Application Data > >> > > > > >> svn info > >> > > > > >> diff --version > >> > > > > >> repository info: Path: > >> > > > > >> //, Base > >> > > > pa > >> > > > > >> > th: /trunk, Supports changesets: False > >> > > > > >> HTTP GETting api/ > >> > > > > >> Got HTTP error: 503: >> > > > > >> HTML 4.01 > >> > > > Transition > >> > > > > >> > al//EN" "http://www.w3.org/TR/html4/loose.dtd";> > >> > > > > >> > >> > > > > >> > CONTENT="text/html; > >> > > > > >> > charset=iso-8859 > >> > > > > >> > -1"> > >> > > > > >> > ERROR: The requested URL could not be retrieved > >> > > > > >> > > >> > > > > >> > > >> > > > > >> > The requested URL could not be retrieved > >> > > > > >> > > >> > > > > >> > > >> > > > > >> > While trying to
403 forbidden in Apache
Hello,
I have successfully installed all the pre-reqs on RedHat server and
Reviewboard.
I configured apache using the example http.conf entry as follows:
IfModule mod_fcgid.c>
AddHandler fcgid-script .fcgi
AddHandler fastcgi-script .fcgi
FastCGIServer "/var/www/reviewboard/htdocs/reviewboard.fcgi" -
socket "/var/www/reviewboard/tmp/fastcgi.sock"
ServerName global-ad.net
DocumentRoot "/var/www/reviewboard/htdocs"
# Alias static media requests to filesystem
Alias /media "/var/www/reviewboard/htdocs/media"
Alias /errordocs "/var/www/reviewboard/htdocs/errordocs"
# Error handlers
ErrorDocument 500 /errordocs/500.html
Options +Includes -Indexes
AllowOverride All
Order allow,deny
Allow from all
# Direct all other requests to the fastcgi server
RewriteEngine on
RewriteRule ^/(media.*)$ /$1 [QSA,L,PT]
RewriteRule ^/(errordocs.*)$ /$1 [QSA,L,PT]
RewriteRule ^/(media.*)$ /$1 [QSA,L,PT]
RewriteRule ^/(errordocs.*)$ /$1 [QSA,L,PT]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ /reviewboard.fcgi/$1 [QSA,L]
When I start Apache I get a message
Forbidden
You don't have permission to access /reviewboard/ on this server.
Error.log
Directory index forbidden by Options directive: /var/www/html/
reviewboard/
I try add Options -Indexes but log is still same.
Am I doing something wrong?
--
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
RevewBoard 1.5.2 + RBTools-0.3.2-py2.6 + Perforce + Pre-commit Review - '500 Error' when CLN changed after p4 submit
Hi everyone, We have RevewBoard 1.5.2 working with Perforce. On client side we use RBTools-0.3.2-py2.6 to do pre-commit review. We can post review request and all comments/updates on RB portal works just fineuntil the changelist was submitted to P4. The problem is that when we submit the changelist to p4 the changelist number altered at P4 (e.g. from 703920 to 797978); that means the original changelist number listed on the review request of ReviewBoard (e.g. 703920) was no longer exist on P4 server. We then have problem viewing the review request - "Something broke! (Error 500)" was showed when we tried to browse the review request link. After searching on server log we found below exception: - P4Exception: [P4#run] Warnings during command execution( "p4 describe - s 703920" ) [Warning]: 703920 - no such changelist - This wasn't happening before we updated the version from 1.0.5.1 to 1.5.2 and add our LDAP to RB server. Did anyone have similar problem before? Thanks in advance. -- 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
Found blog post: Using Reviewboard with Git
Hi, I have just come across this blog post: http://ericholscher.com/blog/2011/jan/24/using-reviewboard-git/ Thought that you may like to add it to the list of posts on you homepage... Cheers, elf Pavlik http://wwelves.org/perpetual-tripper -- 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
