Return-Path: X-Original-To: apmail-bloodhound-user-archive@www.apache.org Delivered-To: apmail-bloodhound-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2AE2ECAB6 for ; Thu, 25 Jul 2013 15:38:18 +0000 (UTC) Received: (qmail 13086 invoked by uid 500); 25 Jul 2013 15:38:18 -0000 Delivered-To: apmail-bloodhound-user-archive@bloodhound.apache.org Received: (qmail 13076 invoked by uid 500); 25 Jul 2013 15:38:17 -0000 Mailing-List: contact user-help@bloodhound.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@bloodhound.apache.org Delivered-To: mailing list user@bloodhound.apache.org Received: (qmail 13068 invoked by uid 99); 25 Jul 2013 15:38:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jul 2013 15:38:17 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW X-Spam-Check-By: apache.org Received-SPF: error (nike.apache.org: local policy) Received: from [74.125.83.48] (HELO mail-ee0-f48.google.com) (74.125.83.48) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Jul 2013 15:38:11 +0000 Received: by mail-ee0-f48.google.com with SMTP id b47so997963eek.21 for ; Thu, 25 Jul 2013 08:37:31 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=v2qwKRAU1E7HATIU9/dXZyUFGhYtJZdoenbXtXSbnPE=; b=e+ugHpboHJaFLL/qIwrNNre7Eez75YXcdQKLKiH8EGU9INy7zrbZX0u5sGLmN2jy63 sMcwN2veLVL9SGA5n3Azz3jRCaeYXXJePpxzSDh+je2lXyRIoBxC1Te6jMmb7BQpEyzr eeoz6Z30fLK2fGYHLw5clkmsdSoYmH9tUk8ORyE0F3jkAdh4QYORMUGjpuhpRBeHhhrR mQVsaEXXXnfse26x9dbC0qwq7DYbHKJpcaA9/3+ganf+7WdLgdzXlqgHt0AwXxF+78fx Rmvm4RGeojqodjtSR60WqNL8uckJxKxw6Srqg+qGOzTYVYD/NvZTZ87lPN9ZQIr2qQbt AiHQ== MIME-Version: 1.0 X-Received: by 10.15.64.68 with SMTP id n44mr43360375eex.73.1374766651401; Thu, 25 Jul 2013 08:37:31 -0700 (PDT) Received: by 10.223.153.198 with HTTP; Thu, 25 Jul 2013 08:37:31 -0700 (PDT) In-Reply-To: <51F14484.3010802@wandisco.com> References: <51F135F8.4050804@wandisco.com> <51F14484.3010802@wandisco.com> Date: Thu, 25 Jul 2013 16:37:31 +0100 Message-ID: Subject: Re: Bloodhond Instalation and Configuration CentOS 6.4 From: Pedro Estrela To: user@bloodhound.apache.org Content-Type: multipart/alternative; boundary=001a1132ea38e81c9604e257cd29 X-Gm-Message-State: ALoCoQmw0TZvv36XHuFBSPqzci0oAYidceb1YXv2sgQvnJWRPdyAe46+3DDqBgZzbuQQvduawVk8 X-Virus-Checked: Checked by ClamAV on apache.org --001a1132ea38e81c9604e257cd29 Content-Type: text/plain; charset=ISO-8859-1 You are right. I did all the instalation of bloodhound and trac as admin user and I also didn't know that was as problem. Is there anyway to get over this? The python-path on WSGIDaemonProcess is this /var/www/bloodhound/installer/bloodhound/lib/python2.6/site-packages Thanks, Pedro 2013/7/25 Gary Martin > Obviously it is a solution of sorts but I don't think it can be > recommended so I would quite like to continue investigating how this might > have happened if that is OK. Your setup may become confusing on the > assumption that you wish to upgrade in the future. > > At the moment I suspect that you were attempting to have a virtualenv > setup but at some point you installed packages as the admin user (or with > sudo) by mistake. As the sqlparse package was missing, I think that may > suggest that the python-path specified in the WSGIDaemonProcess is not > correct. > > All suspicions so far of course. > > Cheers, > Gary > > > On 25/07/13 15:44, Pedro Estrela wrote: > >> When i ran the tracd i didn't had any troubles. >> I already fix this problem by manualy copy and past sqlparser to >> /usr/lib/python2.6/site-**packages, although i had this folder on the >> bloodhound project. >> >> >> 2013/7/25 Gary Martin > gary.martin@wandisco.**com >> >> >> >> On 25/07/13 11:47, Pedro Estrela wrote: >> >> Hi, >> >> I'm new with Apache Web Server. I was told to install >> Bloodhound on CentOS, I did all steps in >> https://issues.apache.org/**bloodhound/wiki/**BloodhoundInstall >> and also did the steps at >> https://issues.apache.org/**bloodhound/wiki/** >> BloodhoundDetailedInstallation >> . I have some troubles at the >> https://issues.apache.org/**bloodhound/wiki/** >> BloodhoundInstall#WebServer >> . >> After the configuration of the Virtual Host and restart of >> apache i get this unhelpful error: >> >> "TracError: ImportError: No module named sqlparse" >> The weird part is that i have sqlparse module on the project. >> I already have search a lot on the web but i can't get any >> help to my problem. Can you help me or give me some guidelines? >> >> Thanks. >> >> >> It looks like sqlparse is one of the modules that is installed >> with the pip install -r requirements.txt command so I would >> expect you to have seen errors much earlier if it was missing. I >> would normally suspect that you are using the virtualenv as we >> suggest in the instructions but the webserver is not using the >> correct python environment as I expect that to be a relatively >> common issue. >> >> We could attempt to fix that but at this point I am not yet sure >> if that is the route of your problem. >> >> I don't suppose you could confirm that you do not see this problem >> when you run the tracd standalone server? >> >> Cheers, >> Gary >> >> >> > --001a1132ea38e81c9604e257cd29 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
You are right. I did all the instalation of bloodhound and= trac as admin user and I also didn't know that was as problem. Is ther= e anyway to get over this? The python-path on=A0WSGIDaemonProcess is this=A0/var/www/bloodhound/installer/bloodhound/lib/pyth= on2.6/site-packages

Thanks,

=
Pedro
=


2013/7/25 Gary Martin = <gary.mart= in@wandisco.com>
Obviously it is a solution of sorts but I don't think it can be recomme= nded so I would quite like to continue investigating how this might have ha= ppened if that is OK. Your setup may become confusing on the assumption tha= t you wish to upgrade in the future.

At the moment I suspect that you were attempting to have a virtualenv setup= but at some point you installed packages as the admin user (or with sudo) = by mistake. As the sqlparse package was missing, I think that may suggest t= hat the python-path specified in the WSGIDaemonProcess is not correct.

All suspicions so far of course.

Cheers,
=A0 =A0 Gary


On 25/07/13 15:44, Pedro Estrela wrote:
When i ran the tracd i didn't had any troubles.
I already fix this problem by manualy copy and past sqlparser to /usr/lib/p= ython2.6/site-packages, although i had this folder on the bloodhound= project.


2013/7/25 Gary Martin <gary.martin@wandisco.com <mailto:gary.martin@wandisco.com= >>


=A0 =A0 On 25/07/13 11:47, Pedro Estrela wrote:

=A0 =A0 =A0 =A0 Hi,

=A0 =A0 =A0 =A0 I'm new with Apache Web Server. I was told to install =A0 =A0 =A0 =A0 Bloodhound on CentOS, I did all steps in
=A0 =A0 =A0 =A0 https://issues.apache.org/bloodhound/= wiki/BloodhoundInstall
=A0 =A0 =A0 =A0 and also did the steps at
=A0 =A0 =A0 =A0 https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation
=A0 =A0 =A0 =A0 . I have some troubles at the
=A0 =A0 =A0 =A0 https://issues.apache.org/b= loodhound/wiki/BloodhoundInstall#WebServer.
=A0 =A0 =A0 =A0 After the configuration of the Virtual Host and restart of<= br> =A0 =A0 =A0 =A0 apache i get this unhelpful error:

=A0 =A0 =A0 =A0 "TracError: ImportError: No module named sqlparse"= ;
=A0 =A0 =A0 =A0 The weird part is that i have sqlparse module on the projec= t.
=A0 =A0 =A0 =A0 I already have search a lot on the web but i can't get = any
=A0 =A0 =A0 =A0 help to my problem. Can you help me or give me some guideli= nes?

=A0 =A0 =A0 =A0 Thanks.


=A0 =A0 It looks like sqlparse is one of the modules that is installed
=A0 =A0 with the pip install -r requirements.txt command so I would
=A0 =A0 =A0expect you to have seen errors much earlier if it was missing. I=
=A0 =A0 would normally suspect that you are using the virtualenv as we
=A0 =A0 suggest in the instructions but the webserver is not using the
=A0 =A0 correct python environment as I expect that to be a relatively
=A0 =A0 common issue.

=A0 =A0 We could attempt to fix that but at this point I am not yet sure =A0 =A0 if that is the route of your problem.

=A0 =A0 I don't suppose you could confirm that you do not see this prob= lem
=A0 =A0 when you run the tracd standalone server?

=A0 =A0 Cheers,
=A0 =A0 =A0 =A0 Gary




--001a1132ea38e81c9604e257cd29--