RE: /bloodhound/[^/]+/login
Hi, Gary.
Thanks for getting back to me.
Yes, I tried /bloodhound/login, and that works for me.
/bloodhound/([^/]+/)?login works for me too.
Thanks!
-Chris Harris
From: Gary Martin [mailto:gary.mar...@wandisco.com]
Sent: Monday, March 16, 2015 6:25 PM
To: user@bloodhound.apache.org
Subject: Re: /bloodhound/[^/]+/login
Hi Chris,
Sorry about the delay. I should probably take some time to look into what the
exact issue is but here are my initial thoughts.
If you are just after a regex that will match /bloodhound/login you could
experiment with just using /bloodhound/login in that location. If it turns out
it is better to keep some of the flavour of what the original LocationMatch is
attempting, the next obvious thing would be to try /bloodhound/([^/]+/)?login
or something that allows for 0 or 1 matches of the whole section.
It is quite possible that this is a mistake in our documentation and the
intention of the match is so that you can serve a set of trac projects such
that the [^/]+ is matching the trac project while we are only really intending
there to be a single trac project (with one or more bloodhound products).
I'll have to investigate a bit further but I hope that is of some use.
Cheers,
Gary
On 10 March 2015 at 23:01, Harris, Christopher P
chris_har...@baxter.commailto:chris_har...@baxter.com wrote:
After some Googling, I read the following:
([^/]+)
Which means match text of 1 or more characters until a forward slash is found.
So, that would match a URL such as:
http://localhost/bloodhound/blah/login
So, I tried the following:
/bloodhound/[^/]*/login
…but that didn’t work either. Basic auth is effectively disabled, and I’m not
greeted with a Basic auth dialog box by the browser.
Do I really need “/bloodhound/[^/]+/login” as my RegEx pattern to catch
whatever it is that the Trac/Bloodhound authors intend for me to catch?
-Chris Harris
From: Harris, Christopher P
Sent: Tuesday, March 10, 2015 5:42 PM
To: 'user@bloodhound.apache.orgmailto:user@bloodhound.apache.org'
Subject: /bloodhound/[^/]+/login
Hi.
Since I started using Bloodhound, around v0.4, I’ve had issues with the RegEx
pattern /bloodhound/[^/]+/login that’s defined in my Apache HTTPd web
server’s virtual hosts config.
Specifically, my issue is that it never works!
If I click on the Login link on the Bloodhound home page, I’m redirected to the
login page, but I’m not greeted with a basic auth dialog box by the browser.
Yes, my basic auth creds from previous sessions are being cleared…in case
that’s what you’re thinking. Ironically, I’ve had much success with IE 8 in
regard to clearing my basic auth credentials.
I’ve only had success with the following RegEx patterns:
/bloodhound/login -- this pattern being the most ideal out of these 2
patterns
/bloodhound
Still, I can circumvent the basic auth dialog box if I type in more than 1
forward slash in between bloodhound and before login. That’s not ideal.
I think I understand that the pattern in question means to catch URL’s that
have any number of forward slashes after bloodhound and before login.
Ex – http://localhost/bloodhound//loginhttp://localhost/bloodhound/login
Is my understanding correct?
I know…this is not exactly Bloodhound-specific. It’s more Apache
HTTPd-specific or RegEx-specific.
In any case, can someone please explain to me why /bloodhound/[^/]+/login is
not working?
Here’s my httpd-vhosts.conf (and, in any case, I can at least share my working
config that auths with Active Director groups in Apache 2.4 ☺ ):
WSGIPythonHome C:/apache/bloodhound/installer/bloodhound
WSGIPythonPath
C:/apache/bloodhound/installer/bloodhound/site;C:/apache/bloodhound/installer/bloodhound/Lib/site-packages
#NOTEThe following virtual host uses mod_authz_ldap.so to handle auth
access to Bloodhound.
# Go to http://httpd.apache.org/docs/2.4/mod/mod_authnz_ldap.html for
documentation.
VirtualHost *:80
WSGIScriptAlias /bloodhound
C:/apache/bloodhound/installer/bloodhound/site/cgi-bin/trac.wsgi
Directory
C:/apache/bloodhound/installer/bloodhound/site/cgi-bin
WSGIApplicationGroup %{GLOBAL}
Require all granted
Files trac.wsgi
Require all granted
/Files
/Directory
LogLevel debug
LocationMatch /bloodhound/[^/]+/login
AuthLDAPURL
ldap://the_host:3268/the_search_base?the_attribute?sub?(objectClass=the_object_class)
AuthLDAPBindDN the_bind_dn”
AuthLDAPBindPassword the_password
LDAPReferrals Off
AuthType Basic
AuthName Bloodhound - Please Provide Your
Credentials
Re: /bloodhound/[^/]+/login
Chris,
That is great to hear! I'll still need to look into this further of course
to see if there is an appropriate fix for our documentation. It might also
be nice for us to add specific notes for installing with LDAP but I'll need
to get a test setup for that. Thanks for prompting all this!
Cheers,
Gary
On 17 March 2015 at 06:33, Harris, Christopher P chris_har...@baxter.com
wrote:
Hi, Gary.
Thanks for getting back to me.
Yes, I tried /bloodhound/login, and that works for me.
/bloodhound/([^/]+/)?login works for me too.
Thanks!
-Chris Harris
*From:* Gary Martin [mailto:gary.mar...@wandisco.com]
*Sent:* Monday, March 16, 2015 6:25 PM
*To:* user@bloodhound.apache.org
*Subject:* Re: /bloodhound/[^/]+/login
Hi Chris,
Sorry about the delay. I should probably take some time to look into what
the exact issue is but here are my initial thoughts.
If you are just after a regex that will match /bloodhound/login you could
experiment with just using /bloodhound/login in that location. If it turns
out it is better to keep some of the flavour of what the original
LocationMatch is attempting, the next obvious thing would be to try
/bloodhound/([^/]+/)?login or something that allows for 0 or 1 matches of
the whole section.
It is quite possible that this is a mistake in our documentation and the
intention of the match is so that you can serve a set of trac projects such
that the [^/]+ is matching the trac project while we are only really
intending there to be a single trac project (with one or more bloodhound
products).
I'll have to investigate a bit further but I hope that is of some use.
Cheers,
Gary
On 10 March 2015 at 23:01, Harris, Christopher P chris_har...@baxter.com
wrote:
After some Googling, I read the following:
([^/]+)
Which means match text of 1 or more characters until a forward slash is
found.
So, that would match a URL such as:
http://localhost/bloodhound/blah/login
So, I tried the following:
/bloodhound/[^/]*/login
…but that didn’t work either. Basic auth is effectively disabled, and I’m
not greeted with a Basic auth dialog box by the browser.
Do I really need “/bloodhound/[^/]+/login” as my RegEx pattern to catch
whatever it is that the Trac/Bloodhound authors intend for me to catch?
-Chris Harris
*From:* Harris, Christopher P
*Sent:* Tuesday, March 10, 2015 5:42 PM
*To:* 'user@bloodhound.apache.org'
*Subject:* /bloodhound/[^/]+/login
Hi.
Since I started using Bloodhound, around v0.4, I’ve had issues with the
RegEx pattern /bloodhound/[^/]+/login that’s defined in my Apache HTTPd
web server’s virtual hosts config.
Specifically, my issue is that it never works!
If I click on the Login link on the Bloodhound home page, I’m redirected
to the login page, but I’m not greeted with a basic auth dialog box by the
browser. Yes, my basic auth creds from previous sessions are being
cleared…in case that’s what you’re thinking. Ironically, I’ve had much
success with IE 8 in regard to clearing my basic auth credentials.
I’ve only had success with the following RegEx patterns:
/bloodhound/login ß this pattern being the most ideal out of these 2
patterns
/bloodhound
Still, I can circumvent the basic auth dialog box if I type in more than 1
forward slash in between bloodhound and before login. That’s not ideal.
I think I understand that the pattern in question means to catch URL’s
that have any number of forward slashes after bloodhound and before login.
Ex – http://localhost/bloodhound//login
http://localhost/bloodhound/login
Is my understanding correct?
I know…this is not exactly Bloodhound-specific. It’s more Apache
HTTPd-specific or RegEx-specific.
In any case, can someone please explain to me why
/bloodhound/[^/]+/login is not working?
Here’s my httpd-vhosts.conf (and, in any case, I can at least share my
working config that auths with Active Director groups in Apache 2.4 J ):
WSGIPythonHome C:/apache/bloodhound/installer/bloodhound
WSGIPythonPath
C:/apache/bloodhound/installer/bloodhound/site;C:/apache/bloodhound/installer/bloodhound/Lib/site-packages
#NOTEThe following virtual host uses mod_authz_ldap.so to handle
auth access to Bloodhound.
# Go to http://httpd.apache.org/docs/2.4/mod/mod_authnz_ldap.html for
documentation.
VirtualHost *:80
WSGIScriptAlias /bloodhound
C:/apache/bloodhound/installer/bloodhound/site/cgi-bin/trac.wsgi
Directory
C:/apache/bloodhound/installer/bloodhound/site/cgi-bin
WSGIApplicationGroup %{GLOBAL}
Require all granted
Files trac.wsgi
Require all granted
/Files
/Directory
LogLevel debug
LocationMatch
Re: Bloodhound Login Error
On 31/07/13 12:48, Matevž Bradač wrote: On 31. Jul, 2013, at 10:54, Pedro Estrela wrote: I did that command: tracd -p 8000 /var/www/bloodhound/installer/bloodhound/environments/main and i get this errors on localhost:8000/main : Warning: Unknown theme bloodhound configured. Please check your trac.ini. You may need to enable the theme's plugin. and Trac detected an internal error: DataError: invalid input syntax for integer: trac.wiki.api.WikiSystem.pages LINE 1: SELECT generation FROM cache WHERE id=E'trac.wiki.api.WikiSy... ^ From the looks of it, it seems like you have a corrupt virtual environment or something in that direction. I would suggest recreating the environment from scratch, under the same user account that will be used for running Apache. Note that you may have to manually remove Babel and replace it with an older version (use Babel==0.9.6 with pip), as the newer versions may not work. After the new environment has been set up, running a standalone tracd should work properly. Once this is fixed we can continue debugging the Apache issues. This seems sensible. It might also be worth removing the system installed versions of the packages though if we can work out which they are. I may not have been exhaustive in this list and it may be that some of these are installed from the CentOS repositories so you may need to be careful in case other programs need some of these.. however unless you expect to have Trac itself installed alongside, the following will hopefully be safe enough (deactivate included in case you are starting from an activated virtualenv): deactivate pip uninstall Babel pip uninstall BloodhoundDashboardPlugin pip uninstall BloodhoundMultiProduct pip uninstall BloodhoundRelationsPlugin pip uninstall BloodhoundSearchPlugin pip uninstall BloodhoundTheme pip uninstall Genshi pip uninstall Pygments pip uninstall Trac pip uninstall TracAccountManager pip uninstall TracPermRedirect pip uninstall TracThemeEngine pip uninstall Whoosh pip uninstall sqlparse Cheers, Gary
Re: Bloodhound Login Error
I'm running as root.
Here is the result of pip freeze:
Warning: cannot find svn location for
BloodhoundMultiProduct==0.7.0dev-r1506070
Warning: cannot find svn location for
BloodhoundRelationsPlugin==0.7.0dev-r1503571
Warning: cannot find svn location for BloodhoundTheme==0.7.0dev-r1506038
Warning: cannot find svn location for
BloodhoundSearchPlugin==0.7.0dev-r1503560
Warning: cannot find svn location for
BloodhoundDashboardPlugin==0.7.0dev-r1505871
Warning: cannot find svn location for PEAK-Rules==0.5a1.dev-r2582
AddOns==0.6
Babel==0.9.4
Beaker==1.3.1
## FIXME: could not find svn URL in dependency_links for this package:
BloodhoundDashboardPlugin==0.7.0dev-r1505871
## FIXME: could not find svn URL in dependency_links for this package:
BloodhoundMultiProduct==0.7.0dev-r1506070
## FIXME: could not find svn URL in dependency_links for this package:
BloodhoundRelationsPlugin==0.7.0dev-r1503571
## FIXME: could not find svn URL in dependency_links for this package:
BloodhoundSearchPlugin==0.7.0dev-r1503560
## FIXME: could not find svn URL in dependency_links for this package:
BloodhoundTheme==0.7.0dev-r1506038
BytecodeAssembler==0.5.1
Cheetah==2.4.1
DecoratorTools==1.7
Extremes==1.1
FormEncode==1.2.2
Genshi==0.6
Magic-file-extensions==0.1
Mako==0.3.4
Markdown==2.0.1
MarkupSafe==0.9.2
MySQL-python==1.2.3c1
Myghty==1.1
## FIXME: could not find svn URL in dependency_links for this package:
PEAK-Rules==0.5a1.dev-r2582
Paste==1.7.4
PasteDeploy==1.3.3
PasteScript==1.7.3
PyGreSQL==3.8.1
Pygments==1.1.1
Pylons==0.9.7
Routes==1.10.3
SQLAlchemy==0.5.5
SSSDConfig==1.9.2
SetupDocs==1.0.5
SymbolType==1.0
Tempita==0.4
ToscaWidgets==0.9.8
Trac==1.0.1
TracAccountManager==0.4.3
TracPermRedirect==3.0
TracThemeEngine==2.2.0
TurboGears2==2.0.3
TurboJson==1.2.1
WebError==0.10.2
WebFlash==0.1a9
WebHelpers==0.6.4
WebOb==0.9.6.1
WebTest==1.2
Whoosh==2.4.1
cas==0.15
cups==1.0
cupshelpers==1.0
decorator==3.0.1
distribute==0.6.10
ethtool==0.6
firstboot==1.110
freeipa==2.0.0.alpha.0
iniparse==0.3.1
iotop==0.3.2
ipapython==3.0.0
iwlib==1.0
kerberos==1.0
luci==0.26.0
lxml==2.2.3
matplotlib==0.99.1.1
netaddr==0.7.5
nose==0.10.4
numpy==1.4.1
paramiko==1.7.5
pexpect==2.3
policycoreutils-default-encoding==0.1
prioritized-methods==0.2.1
psycopg2==2.0.14
pyOpenSSL==0.10
pyasn1==0.0.12a
pycrypto==2.0.1
pycurl==7.19.0
pygpgme==0.1
python-dateutil==1.4.1
python-default-encoding==0.1
python-ldap==2.3.10
python-meh==0.11
python-memcached==1.43
python-nss==0.13
pytz==2010h
pyxdg==0.18
qpid-python==0.14
qpid-tools==0.14
repoze.tm2==1.0a4
repoze.what==1.0.8
repoze.what-pylons==1.0
repoze.who==1.0.18
repoze.who-friendlyform==1.0.8
repoze.who-testutil==1.0rc1
scdate==1.9.60
sckdump==2.0.5
scservices==0.99.45
scservices.dbus==0.99.45
setools==1.0
simplejson==2.0.9
slip==0.2.20
slip.dbus==0.2.20
slip.gtk==0.2.20
smbc==1.0
sqlparse==0.1.7
suds==0.4.1
transaction==1.0.1
urlgrabber==3.9.1
virtualenv==1.9.1
yum-metadata-parser==1.1.2
zope.interface==3.5.2
zope.sqlalchemy==0.4
2013/7/30 Matevž Bradač mat...@digiverse.si
On 30. Jul, 2013, at 10:20, Pedro Estrela wrote:
import acct_mgr.web_ui
Traceback (most recent call last):
File stdin, line 1, in module
ImportError: No module named acct_mgr.web_ui
I guess is missing something
Most likely it's not installed. Could you please provide the output of
pip freeze
command so that we can determine which modules have been installed in
the environment?
Also, how are you running your web server - as admin/root, or as a
separate user?
2013/7/30 Olemis Lang ole...@gmail.com
On 7/29/13, Pedro Estrela p.estr...@campus.fct.unl.pt wrote:
Hi,
:)
[...]
Can you please tell me what i did wrong? This is the error that i get:
Error: Not Found
No handler matched request to /login
This is an indication of the fact that account manager plugin has not
been ( detected / loaded / enabled ). Could you please launch your
python interpreter, execute the following code and tell us what's the
result ? Is it even close to what you see below?
{{{#!py
from trac.env import open_environment as oe
env = oe('/path/to/bh/env')
import acct_mgr.web_ui
env[web_ui.LoginModule]
acct_mgr.web_ui.LoginModule object at 0x38a9710
}}}
--
Regards,
Olemis - @olemislc
Apache(tm) Bloodhound contributor
http://issues.apache.org/bloodhound
http://blood-hound.net
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: Bloodhound Login Error
On 30. Jul, 2013, at 10:45, Pedro Estrela wrote:
I'm running as root.
Here is the result of pip freeze:
Warning: cannot find svn location for
BloodhoundMultiProduct==0.7.0dev-r1506070
Warning: cannot find svn location for
BloodhoundRelationsPlugin==0.7.0dev-r1503571
Warning: cannot find svn location for BloodhoundTheme==0.7.0dev-r1506038
Warning: cannot find svn location for
BloodhoundSearchPlugin==0.7.0dev-r1503560
Warning: cannot find svn location for
BloodhoundDashboardPlugin==0.7.0dev-r1505871
Warning: cannot find svn location for PEAK-Rules==0.5a1.dev-r2582
AddOns==0.6
Babel==0.9.4
Beaker==1.3.1
## FIXME: could not find svn URL in dependency_links for this package:
BloodhoundDashboardPlugin==0.7.0dev-r1505871
## FIXME: could not find svn URL in dependency_links for this package:
BloodhoundMultiProduct==0.7.0dev-r1506070
## FIXME: could not find svn URL in dependency_links for this package:
BloodhoundRelationsPlugin==0.7.0dev-r1503571
## FIXME: could not find svn URL in dependency_links for this package:
BloodhoundSearchPlugin==0.7.0dev-r1503560
## FIXME: could not find svn URL in dependency_links for this package:
BloodhoundTheme==0.7.0dev-r1506038
BytecodeAssembler==0.5.1
Cheetah==2.4.1
DecoratorTools==1.7
Extremes==1.1
FormEncode==1.2.2
Genshi==0.6
Magic-file-extensions==0.1
Mako==0.3.4
Markdown==2.0.1
MarkupSafe==0.9.2
MySQL-python==1.2.3c1
Myghty==1.1
## FIXME: could not find svn URL in dependency_links for this package:
PEAK-Rules==0.5a1.dev-r2582
Paste==1.7.4
PasteDeploy==1.3.3
PasteScript==1.7.3
PyGreSQL==3.8.1
Pygments==1.1.1
Pylons==0.9.7
Routes==1.10.3
SQLAlchemy==0.5.5
SSSDConfig==1.9.2
SetupDocs==1.0.5
SymbolType==1.0
Tempita==0.4
ToscaWidgets==0.9.8
Trac==1.0.1
TracAccountManager==0.4.3
TracPermRedirect==3.0
TracThemeEngine==2.2.0
TurboGears2==2.0.3
TurboJson==1.2.1
WebError==0.10.2
WebFlash==0.1a9
WebHelpers==0.6.4
WebOb==0.9.6.1
WebTest==1.2
Whoosh==2.4.1
cas==0.15
cups==1.0
cupshelpers==1.0
decorator==3.0.1
distribute==0.6.10
ethtool==0.6
firstboot==1.110
freeipa==2.0.0.alpha.0
iniparse==0.3.1
iotop==0.3.2
ipapython==3.0.0
iwlib==1.0
kerberos==1.0
luci==0.26.0
lxml==2.2.3
matplotlib==0.99.1.1
netaddr==0.7.5
nose==0.10.4
numpy==1.4.1
paramiko==1.7.5
pexpect==2.3
policycoreutils-default-encoding==0.1
prioritized-methods==0.2.1
psycopg2==2.0.14
pyOpenSSL==0.10
pyasn1==0.0.12a
pycrypto==2.0.1
pycurl==7.19.0
pygpgme==0.1
python-dateutil==1.4.1
python-default-encoding==0.1
python-ldap==2.3.10
python-meh==0.11
python-memcached==1.43
python-nss==0.13
pytz==2010h
pyxdg==0.18
qpid-python==0.14
qpid-tools==0.14
repoze.tm2==1.0a4
repoze.what==1.0.8
repoze.what-pylons==1.0
repoze.who==1.0.18
repoze.who-friendlyform==1.0.8
repoze.who-testutil==1.0rc1
scdate==1.9.60
sckdump==2.0.5
scservices==0.99.45
scservices.dbus==0.99.45
setools==1.0
simplejson==2.0.9
slip==0.2.20
slip.dbus==0.2.20
slip.gtk==0.2.20
smbc==1.0
sqlparse==0.1.7
suds==0.4.1
transaction==1.0.1
urlgrabber==3.9.1
virtualenv==1.9.1
yum-metadata-parser==1.1.2
zope.interface==3.5.2
zope.sqlalchemy==0.4
Hmm, it does seem to be installed.
Are you also running Olemis' tests as root?
Could you also check that the top level BH/Trac modules can be imported
properly by the python interpreter, e.g.:
{{{#!py
import genshi
import babel
import themeengine
import acct_mgr
import bhtheme
import bhdashboard
import bhsearch
import multiproduct
import bhrelations
}}}
2013/7/30 Matevž Bradač mat...@digiverse.si
On 30. Jul, 2013, at 10:20, Pedro Estrela wrote:
import acct_mgr.web_ui
Traceback (most recent call last):
File stdin, line 1, in module
ImportError: No module named acct_mgr.web_ui
I guess is missing something
Most likely it's not installed. Could you please provide the output of
pip freeze
command so that we can determine which modules have been installed in
the environment?
Also, how are you running your web server - as admin/root, or as a
separate user?
2013/7/30 Olemis Lang ole...@gmail.com
On 7/29/13, Pedro Estrela p.estr...@campus.fct.unl.pt wrote:
Hi,
:)
[...]
Can you please tell me what i did wrong? This is the error that i get:
Error: Not Found
No handler matched request to /login
This is an indication of the fact that account manager plugin has not
been ( detected / loaded / enabled ). Could you please launch your
python interpreter, execute the following code and tell us what's the
result ? Is it even close to what you see below?
{{{#!py
from trac.env import open_environment as oe
env = oe('/path/to/bh/env')
import acct_mgr.web_ui
env[web_ui.LoginModule]
acct_mgr.web_ui.LoginModule object at 0x38a9710
}}}
--
Regards,
Olemis - @olemislc
Apache™ Bloodhound contributor
http://issues.apache.org/bloodhound
http://blood-hound.net
Blog ES:
Re: Bloodhound Login Error
Can we be careful to distinguish which environments you are trying this
in. Is this in the activated bloodhound virtualenv?
Cheers,
Gary
On 30/07/13 10:17, Pedro Estrela wrote:
Yes i did all as root.
[root@lbtvmcentosbug Desktop]# python
Python 2.6.6 (r266:84292, Feb 22 2013, 00:00:18)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-3)] on linux2
Type help, copyright, credits or license for more information.
import genshi
import babel
import themeengine
import acct_mgr
Traceback (most recent call last):
File stdin, line 1, in module
ImportError: No module named acct_mgr
import bhtheme
import bhdashboard
import bhsearch
import multiproduct
import bhrelations
this is my output, i guess i'm having some troubles with acct_mgr
2013/7/30 Matevž Bradač mat...@digiverse.si mailto:mat...@digiverse.si
On 30. Jul, 2013, at 10:45, Pedro Estrela wrote:
I'm running as root.
Here is the result of pip freeze:
Warning: cannot find svn location for
BloodhoundMultiProduct==0.7.0dev-r1506070
Warning: cannot find svn location for
BloodhoundRelationsPlugin==0.7.0dev-r1503571
Warning: cannot find svn location for
BloodhoundTheme==0.7.0dev-r1506038
Warning: cannot find svn location for
BloodhoundSearchPlugin==0.7.0dev-r1503560
Warning: cannot find svn location for
BloodhoundDashboardPlugin==0.7.0dev-r1505871
Warning: cannot find svn location for PEAK-Rules==0.5a1.dev-r2582
AddOns==0.6
Babel==0.9.4
Beaker==1.3.1
## FIXME: could not find svn URL in dependency_links for this
package:
BloodhoundDashboardPlugin==0.7.0dev-r1505871
## FIXME: could not find svn URL in dependency_links for this
package:
BloodhoundMultiProduct==0.7.0dev-r1506070
## FIXME: could not find svn URL in dependency_links for this
package:
BloodhoundRelationsPlugin==0.7.0dev-r1503571
## FIXME: could not find svn URL in dependency_links for this
package:
BloodhoundSearchPlugin==0.7.0dev-r1503560
## FIXME: could not find svn URL in dependency_links for this
package:
BloodhoundTheme==0.7.0dev-r1506038
BytecodeAssembler==0.5.1
Cheetah==2.4.1
DecoratorTools==1.7
Extremes==1.1
FormEncode==1.2.2
Genshi==0.6
Magic-file-extensions==0.1
Mako==0.3.4
Markdown==2.0.1
MarkupSafe==0.9.2
MySQL-python==1.2.3c1
Myghty==1.1
## FIXME: could not find svn URL in dependency_links for this
package:
PEAK-Rules==0.5a1.dev-r2582
Paste==1.7.4
PasteDeploy==1.3.3
PasteScript==1.7.3
PyGreSQL==3.8.1
Pygments==1.1.1
Pylons==0.9.7
Routes==1.10.3
SQLAlchemy==0.5.5
SSSDConfig==1.9.2
SetupDocs==1.0.5
SymbolType==1.0
Tempita==0.4
ToscaWidgets==0.9.8
Trac==1.0.1
TracAccountManager==0.4.3
TracPermRedirect==3.0
TracThemeEngine==2.2.0
TurboGears2==2.0.3
TurboJson==1.2.1
WebError==0.10.2
WebFlash==0.1a9
WebHelpers==0.6.4
WebOb==0.9.6.1
WebTest==1.2
Whoosh==2.4.1
cas==0.15
cups==1.0
cupshelpers==1.0
decorator==3.0.1
distribute==0.6.10
ethtool==0.6
firstboot==1.110
freeipa==2.0.0.alpha.0
iniparse==0.3.1
iotop==0.3.2
ipapython==3.0.0
iwlib==1.0
kerberos==1.0
luci==0.26.0
lxml==2.2.3
matplotlib==0.99.1.1
netaddr==0.7.5
nose==0.10.4
numpy==1.4.1
paramiko==1.7.5
pexpect==2.3
policycoreutils-default-encoding==0.1
prioritized-methods==0.2.1
psycopg2==2.0.14
pyOpenSSL==0.10
pyasn1==0.0.12a
pycrypto==2.0.1
pycurl==7.19.0
pygpgme==0.1
python-dateutil==1.4.1
python-default-encoding==0.1
python-ldap==2.3.10
python-meh==0.11
python-memcached==1.43
python-nss==0.13
pytz==2010h
pyxdg==0.18
qpid-python==0.14
qpid-tools==0.14
repoze.tm2==1.0a4
repoze.what==1.0.8
repoze.what-pylons==1.0
repoze.who==1.0.18
repoze.who-friendlyform==1.0.8
repoze.who-testutil==1.0rc1
scdate==1.9.60
sckdump==2.0.5
scservices==0.99.45
scservices.dbus==0.99.45
setools==1.0
simplejson==2.0.9
slip==0.2.20
slip.dbus==0.2.20
slip.gtk==0.2.20
smbc==1.0
sqlparse==0.1.7
suds==0.4.1
transaction==1.0.1
urlgrabber==3.9.1
virtualenv==1.9.1
yum-metadata-parser==1.1.2
zope.interface==3.5.2
zope.sqlalchemy==0.4
Hmm, it does seem to be installed.
Are you also running Olemis' tests as root?
Could you also check that the top level BH/Trac modules can be
imported
properly by the python interpreter, e.g.:
{{{#!py
import genshi
import babel
import themeengine
import acct_mgr
import bhtheme
import bhdashboard
import bhsearch
import multiproduct
import bhrelations
}}}
2013/7/30
Re: Bloodhound Login Error
No it wasn't. Sorry about that.
Here it is now:
[root@lbtvmcentosbug /]# cd var
[root@lbtvmcentosbug var]# cd www
[root@lbtvmcentosbug www]# cd bloodhound/
[root@lbtvmcentosbug bloodhound]# cd installer/
[root@lbtvmcentosbug installer]# ls
bloodhound createdigest.pycrequirements-dev.txt
bloodhound_setup.py pgrequirements.txt requirements.txt
createdigest.py README.rst tests.py
[root@lbtvmcentosbug installer]# cd bloodhound
[root@lbtvmcentosbug bloodhound]# dir
bin bloodhound environments include lib lib64 site
[root@lbtvmcentosbug bloodhound]# source ./bin/activate
(bloodhound)[root@lbtvmcentosbug bloodhound]# python
Python 2.6.6 (r266:84292, Feb 22 2013, 00:00:18)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-3)] on linux2
Type help, copyright, credits or license for more information.
import genshi
import babel
import themeengine
import acct_mgr
import bhtheme
import bhdashboard
import bhsearch
import multiproduct
import bhrelations
exit()
(bloodhound)[root@lbtvmcentosbug bloodhound]# python
Python 2.6.6 (r266:84292, Feb 22 2013, 00:00:18)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-3)] on linux2
Type help, copyright, credits or license for more information.
from trac.env import open_environment as oe
env = oe('/var/www/bloodhound/installer/bloodhound/environments/main')
import acct_mgr.web_ui
env[web_ui.LoginModule]
Traceback (most recent call last):
File stdin, line 1, in module
NameError: name 'web_ui' is not defined
2013/7/30 Gary Martin gary.mar...@wandisco.com
Can we be careful to distinguish which environments you are trying this
in. Is this in the activated bloodhound virtualenv?
Cheers,
Gary
On 30/07/13 10:17, Pedro Estrela wrote:
Yes i did all as root.
[root@lbtvmcentosbug Desktop]# python
Python 2.6.6 (r266:84292, Feb 22 2013, 00:00:18)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-3)] on linux2
Type help, copyright, credits or license for more information.
import genshi
import babel
import themeengine
import acct_mgr
Traceback (most recent call last):
File stdin, line 1, in module
ImportError: No module named acct_mgr
import bhtheme
import bhdashboard
import bhsearch
import multiproduct
import bhrelations
this is my output, i guess i'm having some troubles with acct_mgr
2013/7/30 Matevž Bradač mat...@digiverse.si mailto:mat...@digiverse.si
On 30. Jul, 2013, at 10:45, Pedro Estrela wrote:
I'm running as root.
Here is the result of pip freeze:
Warning: cannot find svn location for
BloodhoundMultiProduct==0.7.**0dev-r1506070
Warning: cannot find svn location for
BloodhoundRelationsPlugin==0.**7.0dev-r1503571
Warning: cannot find svn location for
BloodhoundTheme==0.7.0dev-**r1506038
Warning: cannot find svn location for
BloodhoundSearchPlugin==0.7.**0dev-r1503560
Warning: cannot find svn location for
BloodhoundDashboardPlugin==0.**7.0dev-r1505871
Warning: cannot find svn location for PEAK-Rules==0.5a1.dev-r2582
AddOns==0.6
Babel==0.9.4
Beaker==1.3.1
## FIXME: could not find svn URL in dependency_links for this
package:
BloodhoundDashboardPlugin==0.**7.0dev-r1505871
## FIXME: could not find svn URL in dependency_links for this
package:
BloodhoundMultiProduct==0.7.**0dev-r1506070
## FIXME: could not find svn URL in dependency_links for this
package:
BloodhoundRelationsPlugin==0.**7.0dev-r1503571
## FIXME: could not find svn URL in dependency_links for this
package:
BloodhoundSearchPlugin==0.7.**0dev-r1503560
## FIXME: could not find svn URL in dependency_links for this
package:
BloodhoundTheme==0.7.0dev-**r1506038
BytecodeAssembler==0.5.1
Cheetah==2.4.1
DecoratorTools==1.7
Extremes==1.1
FormEncode==1.2.2
Genshi==0.6
Magic-file-extensions==0.1
Mako==0.3.4
Markdown==2.0.1
MarkupSafe==0.9.2
MySQL-python==1.2.3c1
Myghty==1.1
## FIXME: could not find svn URL in dependency_links for this
package:
PEAK-Rules==0.5a1.dev-r2582
Paste==1.7.4
PasteDeploy==1.3.3
PasteScript==1.7.3
PyGreSQL==3.8.1
Pygments==1.1.1
Pylons==0.9.7
Routes==1.10.3
SQLAlchemy==0.5.5
SSSDConfig==1.9.2
SetupDocs==1.0.5
SymbolType==1.0
Tempita==0.4
ToscaWidgets==0.9.8
Trac==1.0.1
TracAccountManager==0.4.3
TracPermRedirect==3.0
TracThemeEngine==2.2.0
TurboGears2==2.0.3
TurboJson==1.2.1
WebError==0.10.2
WebFlash==0.1a9
WebHelpers==0.6.4
WebOb==0.9.6.1
WebTest==1.2
Whoosh==2.4.1
cas==0.15
cups==1.0
cupshelpers==1.0
decorator==3.0.1
distribute==0.6.10
ethtool==0.6
firstboot==1.110
freeipa==2.0.0.alpha.0
iniparse==0.3.1
iotop==0.3.2
ipapython==3.0.0
Re: Bloodhound Login Error
On 30. Jul, 2013, at 12:50, Pedro Estrela wrote:
Those acct_mgr entries are all enable.
Those are the files @
/var/www/bloodhound/installer/bloodhound/lib/python2.6/site-packages/acct_mgr
:
(bloodhound)[root@lbtvmcentosbug acct_mgr]# ls -l
total 412
-rw-r--r-- 1 root root 29414 Jul 24 11:30 admin.py
-rw-r--r-- 1 root root 21742 Jul 24 11:30 admin.pyc
-rw-r--r-- 1 root root 16703 Jul 24 11:30 api.py
-rw-r--r-- 1 root root 20038 Jul 24 11:30 api.pyc
-rw-r--r-- 1 root root 4653 Jul 24 11:30 db.py
-rw-r--r-- 1 root root 5220 Jul 24 11:30 db.pyc
-rw-r--r-- 1 root root 10221 Jul 24 11:30 guard.py
-rw-r--r-- 1 root root 8868 Jul 24 11:30 guard.pyc
-rw-r--r-- 1 root root 404 Jul 24 11:30 hashlib_compat.py
-rw-r--r-- 1 root root 357 Jul 24 11:30 hashlib_compat.pyc
drwxr-xr-x 2 root root 4096 Jul 24 11:30 htdocs
-rw-r--r-- 1 root root 10261 Jul 24 11:30 htfile.py
-rw-r--r-- 1 root root 9907 Jul 24 11:30 htfile.pyc
-rw-r--r-- 1 root root 2838 Jul 24 11:30 http.py
-rw-r--r-- 1 root root 2936 Jul 24 11:30 http.pyc
-rw-r--r-- 1 root root 0 Jul 24 11:30 __init__.py
-rw-r--r-- 1 root root 168 Jul 24 11:30 __init__.pyc
drwxr-xr-x 22 root root 4096 Jul 24 11:30 locale
-rw-r--r-- 1 root root 6451 Jul 24 11:30 macros.py
-rw-r--r-- 1 root root 6216 Jul 24 11:30 macros.pyc
-rw-r--r-- 1 root root 2782 Jul 24 11:30 md5crypt.py
-rw-r--r-- 1 root root 2901 Jul 24 11:30 md5crypt.pyc
-rw-r--r-- 1 root root 9429 Jul 24 11:30 model.py
-rw-r--r-- 1 root root 8418 Jul 24 11:30 model.pyc
-rw-r--r-- 1 root root 6737 Jul 24 11:30 notification.py
-rw-r--r-- 1 root root 8604 Jul 24 11:30 notification.pyc
-rw-r--r-- 1 root root 4918 Jul 24 11:30 pwhash.py
-rw-r--r-- 1 root root 6322 Jul 24 11:30 pwhash.pyc
-rw-r--r-- 1 root root 25360 Jul 24 11:30 register.py
-rw-r--r-- 1 root root 21636 Jul 24 11:30 register.pyc
-rw-r--r-- 1 root root 2406 Jul 24 11:30 svnserve.py
-rw-r--r-- 1 root root 3420 Jul 24 11:30 svnserve.pyc
drwxr-xr-x 2 root root 4096 Jul 24 11:30 templates
-rw-r--r-- 1 root root 4234 Jul 24 11:30 util.py
-rw-r--r-- 1 root root 4864 Jul 24 11:30 util.pyc
-rw-r--r-- 1 root root 32613 Jul 24 11:30 web_ui.py
-rw-r--r-- 1 root root 25674 Jul 24 11:30 web_ui.pyc
Ah, I can see that acct_mgr.web_ui was imported properly below,
it's just that the next line contains a bug. This
env[web_ui.LoginModule]
should actually be
env[acct_mgr.web_ui.LoginModule]
Please check that this works, as we then know that the virtualenv
is properly set up.
2013/7/30 Matevž Bradač mat...@digiverse.si
On 30. Jul, 2013, at 11:57, Pedro Estrela wrote:
No it wasn't. Sorry about that.
Here it is now:
[root@lbtvmcentosbug /]# cd var
[root@lbtvmcentosbug var]# cd www
[root@lbtvmcentosbug www]# cd bloodhound/
[root@lbtvmcentosbug bloodhound]# cd installer/
[root@lbtvmcentosbug installer]# ls
bloodhound createdigest.pycrequirements-dev.txt
bloodhound_setup.py pgrequirements.txt requirements.txt
createdigest.py README.rst tests.py
[root@lbtvmcentosbug installer]# cd bloodhound
[root@lbtvmcentosbug bloodhound]# dir
bin bloodhound environments includelib lib64 site
[root@lbtvmcentosbug bloodhound]# source ./bin/activate
(bloodhound)[root@lbtvmcentosbug bloodhound]# python
Python 2.6.6 (r266:84292, Feb 22 2013, 00:00:18)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-3)] on linux2
Type help, copyright, credits or license for more information.
import genshi
import babel
import themeengine
import acct_mgr
import bhtheme
import bhdashboard
import bhsearch
import multiproduct
import bhrelations
exit()
(bloodhound)[root@lbtvmcentosbug bloodhound]# python
Python 2.6.6 (r266:84292, Feb 22 2013, 00:00:18)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-3)] on linux2
Type help, copyright, credits or license for more information.
from trac.env import open_environment as oe
env = oe('/var/www/bloodhound/installer/bloodhound/environments/main')
import acct_mgr.web_ui
env[web_ui.LoginModule]
Traceback (most recent call last):
File stdin, line 1, in module
NameError: name 'web_ui' is not defined
Ok that seems better, could you look at the file
/var/www/bloodhound/installer/bloodhound/environments/main/conf/base.ini
there should be the following acct_mgr entries under [components]:
acct_mgr.admin.* = enabled
acct_mgr.api.accountmanager = enabled
acct_mgr.guard.accountguard = enabled
acct_mgr.htfile.htdigeststore = enabled
acct_mgr.web_ui.accountmodule = enabled
acct_mgr.web_ui.loginmodule = enabled
Then also please check which acct_mgr .py files were installed for the
virtual env, they should be in the
/var/www/bloodhound/installer/bloodhound/lib/pythonversion/site-packages/acct_mgr
2013/7/30 Gary Martin gary.mar...@wandisco.com
Can we be careful to distinguish which
Re: Bloodhound Login Error
On 30/07/13 12:13, Pedro Estrela wrote:
Here is the result:
(bloodhound)[root@lbtvmcentosbug bloodhound]# python
Python 2.6.6 (r266:84292, Feb 22 2013, 00:00:18)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-3)] on linux2
Type help, copyright, credits or license for more information.
from trac.env import open_environment as oe
env = oe('/var/www/bloodhound/installer/bloodhound/environments/main')
import acct_mgr.web_ui
env[acct_mgr.web_ui.LoginModule]
acct_mgr.web_ui.LoginModule object at 0x3c9f510
Sorry to intervene again but to try to keep this discussion on track, I
gather that when you run the code through tracd in the activated
environment you are not seeing this error but the problem manifests
itself when running through the webserver. Is this still the case?
Cheers,
Gary
Re: Bloodhound Login Error
On 7/30/13, Matevž Bradač mat...@digiverse.si wrote: [...] Ah, I can see that acct_mgr.web_ui was imported properly below, it's just that the next line contains a bug. This env[web_ui.LoginModule] should actually be env[acct_mgr.web_ui.LoginModule] My misake , sorry ... [...] -- Regards, Olemis - @olemislc
Re: Bloodhound Login Error
On 7/30/13, Pedro Estrela p.estr...@campus.fct.unl.pt wrote: this is what happen when I run tracd: (bloodhound)[root@lbtvmcentosbug bloodhound]# dir bin bloodhound environments include lib lib64 site (bloodhound)[root@lbtvmcentosbug bloodhound]# cd environments/ (bloodhound)[root@lbtvmcentosbug environments]# dir main (bloodhound)[root@lbtvmcentosbug environments]# tracd --port=8000 /main Server starting in PID 46169. Serving on 0.0.0.0:8000 view at http://127.0.0.1:8000/ Using HTTP/1.1 protocol version 127.0.0.1 - - [30/Jul/2013 12:25:53] GET /main HTTP/1.1 500 - 127.0.0.1 - - [30/Jul/2013 12:25:53] GET /main/chrome/site/your_project_logo.png HTTP/1.1 404 - 127.0.0.1 - - [30/Jul/2013 12:26:00] GET /main/login HTTP/1.1 500 - 127.0.0.1 - - [30/Jul/2013 12:26:00] GET /main/chrome/site/your_project_logo.png HTTP/1.1 404 - 127.0.0.1 - - [30/Jul/2013 12:26:07] GET /main HTTP/1.1 500 - 127.0.0.1 - - [30/Jul/2013 12:26:08] GET /main/chrome/site/your_project_logo.png HTTP/1.1 404 - and here is a screen of localhost:8000/main I had never seen that error before . It is bizarre . What DB backend have you deployed ? SQLite ? PostgreSQL ? MySQL ? -- Regards, Olemis - @olemislc Apache™ Bloodhound contributor http://issues.apache.org/bloodhound http://blood-hound.net Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article:
Re: Bloodhound Login Error
On Jul 29, 2013 10:04 AM, Pedro Estrela p.estr...@campus.fct.unl.pt wrote: Hi, I'm having some troubles with my instalation of apache bloodhound. I already did all the steps @ https://issues.apache.org/bloodhound/wiki/BloodhoundInstall and @ https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation . Unfortunatly, after I completed all the steps, i couldn't login in order to create a ticket. I have to tell that I did all my instalation as root. Can you please tell me what i did wrong? This is the error that i get: Error: Not Found No handler matched request to /login Thanks, Pedro If you installed to the global Python packages directory, you probably want to delete those eggs and start the installation steps again. You should remove any globally installed eggs because we use specify the --system-site-packages option with virtualenv, which will make the global installed packages available to the virtualenv. You probably want to first confirm that you've installed the packages in the global directory though. Which OS are you on?
Re: Bloodhound Login Error
I already follow all instructions and I'm still waiting for his answer. I'm running Bloodhound in CentOS 2013/7/29 Ryan Ollos ryan.ol...@wandisco.com On Jul 29, 2013 10:52 AM, Ryan Ollos ryan.ol...@wandisco.com wrote: On Jul 29, 2013 10:04 AM, Pedro Estrela p.estr...@campus.fct.unl.pt wrote: Hi, I'm having some troubles with my instalation of apache bloodhound. I already did all the steps @ https://issues.apache.org/bloodhound/wiki/BloodhoundInstall and @ https://issues.apache.org/bloodhound/wiki/BloodhoundDetailedInstallation . Unfortunatly, after I completed all the steps, i couldn't login in order to create a ticket. I have to tell that I did all my instalation as root. Can you please tell me what i did wrong? This is the error that i get: Error: Not Found No handler matched request to /login Thanks, Pedro If you installed to the global Python packages directory, you probably want to delete those eggs and start the installation steps again. You should remove any globally installed eggs because we use specify the --system-site-packages option with virtualenv, which will make the global installed packages available to the virtualenv. You probably want to first confirm that you've installed the packages in the global directory though. Which OS are you on? Please ignore my comment and instead follow up in the thread where you had a lengthy discussion with Gary.
