Re: Issue with Alpha 1.0 r 4 on Debian

2009-03-06 Thread Jamie Whitehouse

If it was as Bill said, the default Apache site was in use.  You can
disable it with a2dissite : sudo a2dissite 000-default (or whatever
the name of the default site's file is in sites-enabled).

On Mar 5, 12:49 pm, tadow tadow...@gmail.com wrote:
 Bill,

 Can you provide any details on what you did to fix this?  I have the
 exact same issue and same situation (Debian).

 On Feb 19, 4:54 pm, Bill DeVoe bill.de...@maptek.com wrote:

  Hi Christian,

  Thank you for the very speedy response. There was a default configuration 
  that I needed to alter, but it's all happy now.

  Thanks again!

                                                                  --- Bill.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To post to this group, send email to reviewboard@googlegroups.com
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: Issue with Alpha 1.0 r 4 on Debian

2009-03-05 Thread tadow

Bill,

Can you provide any details on what you did to fix this?  I have the
exact same issue and same situation (Debian).

On Feb 19, 4:54 pm, Bill DeVoe bill.de...@maptek.com wrote:
 Hi Christian,

 Thank you for the very speedy response. There was a default configuration 
 that I needed to alter, but it's all happy now.

 Thanks again!

                                                                 --- Bill.


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
reviewboard group.
To post to this group, send email to reviewboard@googlegroups.com
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: Issue with Alpha 1.0 r 4 on Debian

2009-02-19 Thread Bill DeVoe
Hi Christian,

Thank you for the very speedy response. There was a default configuration that 
I needed to alter, but it's all happy now.

Thanks again!

 

--- Bill.

 

From: reviewboard@googlegroups.com [mailto:reviewbo...@googlegroups.com] On 
Behalf Of Christian Hammond
Sent: Thursday, February 19, 2009 4:30 PM
To: reviewboard@googlegroups.com
Subject: Re: Issue with Alpha 1.0 r 4 on Debian

 

You may have a default.conf or something in your sites-enabled directory 
that's creating a site for /var/www and taking precedence over the Review Board 
one. If so, delete that file and see if it works.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.review-board.org
VMware, Inc. - http://www.vmware.com



On Thu, Feb 19, 2009 at 3:20 PM, Bill DeVoe bill.de...@maptek.com wrote:

Hello all,

This got accidentally posted to the reviewboard-issues list, so I apologize to 
those getting it twice.

I've been trying to get ReviewBoard working on a Debian 5 installation. I've 
got apache2 and the required utilities installed (I believe), but when I go to 
the directory where ReviewBoard should be accessed I only see a directory list. 
I've looked through the mailing list archive but the info there hasn't seemed 
to pinpoint the problem. I've looked through the httpd.conf and the 
apache2.conf files (which are below) but I'm not seeing any issues and hope 
someone out there can help.

I installed ReviewBoard to /var/www/reviews. I'm not using a fully qualified 
domain name (it's all internal), so the domain was just 'xyzzy'. I upgraded to 
Alpha 1.0 release 4 just today, but now I just see an additional tmp/ 
directory in the list - the directory list is still the only thing visible. 

The reported configuration is: Apache/2.2.9 (Debian) mod_ssl/2.2.9 
OpenSSL/0.9.8g mod_python/3.3.1 Python/2.5.2 Server at xyzzy Port 443

 

Here's my httpd.conf:

# This is here for backwards compatability reasons and to support

#  installing 3rd party modules directly via apxs2, rather than

#  through the /etc/apache2/mods-{available,enabled} mechanism.

#

#LoadModule mod_placeholder /usr/lib/apache2/modules/mod_placeholder.so

LoadModule python_module /usr/lib/apache2/modules/mod_python.so

# End of httpd.conf --

 

Here's the apache2.conf:

#

# Based upon the NCSA server configuration files originally by Rob McCool.

#

# This is the main Apache server configuration file.  It contains the

# configuration directives that give the server its instructions.

# See http://httpd.apache.org/docs/2.2/ for detailed information about

# the directives.

#

# Do NOT simply read the instructions in here without understanding

# what they do.  They're here only as hints or reminders.  If you are unsure

# consult the online docs. You have been warned.  

#

# The configuration directives are grouped into three basic sections:

#  1. Directives that control the operation of the Apache server process as a

# whole (the 'global environment').

#  2. Directives that define the parameters of the 'main' or 'default' server,

# which responds to requests that aren't handled by a virtual host.

# These directives also provide default values for the settings

# of all virtual hosts.

#  3. Settings for virtual hosts, which allow Web requests to be sent to

# different IP addresses or hostnames and have them handled by the

# same Apache server process.

#

# Configuration and logfile names: If the filenames you specify for many

# of the server's control files begin with / (or drive:/ for Win32), the

# server will use that explicit path.  If the filenames do *not* begin

# with /, the value of ServerRoot is prepended -- so 
/var/log/apache2/foo.log

# with ServerRoot set to  will be interpreted by the

# server as //var/log/apache2/foo.log.

#

 

### Section 1: Global Environment

#

# The directives in this section affect the overall operation of Apache,

# such as the number of concurrent requests it can handle or where it

# can find its configuration files.

#

 

#

# ServerRoot: The top of the directory tree under which the server's

# configuration, error, and log files are kept.

#

# NOTE!  If you intend to place this on an NFS (or otherwise network)

# mounted filesystem then please read the LockFile documentation (available

# at URL:http://httpd.apache.org/docs-2.1/mod/mpm_common.html#lockfile);

# you will save yourself a lot of trouble.

#

# Do NOT add a slash at the end of the directory path.

#

ServerRoot /etc/apache2

 

#

# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.

#

#IfModule !mpm_winnt.c

#IfModule !mpm_netware.c

LockFile /var/lock/apache2/accept.lock

#/IfModule

#/IfModule

 

#

# PidFile: The file in which the server should record its process

# identification number when it starts.

# This needs to be set in /etc/apache2/envvars

#

PidFile