Great point! Forgot about this one. On Windows Server I also had to do change the Apache 2.2 service to run as the same user that did the same install as well otherwise it would not work. This was not needed on Windows 7. Something with the folders of trac needed to be writeable by Apache.
Cheers, Serge ________________________________ From: Steve Gaul <[email protected]> To: "[email protected]" <[email protected]> Sent: Thursday, August 1, 2013 4:22 PM Subject: Re: bloodhound login with PostgreSQL and apache2 On 8/1/13 4:06 PM, "Olemis Lang" <[email protected]> wrote: >On 8/1/13, Steve Gaul <[email protected]> wrote: >> Has anyone seen this yet? >> > >yes ... > >[...] >> >> However, when you go to login with the admin account you used >>previously, >> that worked from tracd it fails with "Invalid username or password" >> >> In fact, you can keep both instances running, meaning tracd on port >>8000 and >> a bloodhound site a different port, say 80 or 8080 and only the tracd >> instance lets the admin or users login. >> > >This seldom happens to me when I add a new user with sudo . In general >, apache2 will issue such errors if the process cannot access the >passwords file , if the realm does not match (case sensitivity matters >;) , etc ... Ok, this makes a bit more sense… I ran the bloodhound setup scripts using sudo, as this is a Virtual Machine (VM) environment and I don't have a root account on this particular system install, only sudo access. > >> Did I miss a step or is there further documentation needed to setup the >> initial admin account when using PostgreSQL and apache? >> > >Maybe you should check file / user permissions . Where does bloodhound store the user account info? I presumed that would be in postgres and not on a flat file in the apache configuration or am I wrong there too? > >> I searched thru the docs and FAQs but didn't see anything perhaps I >>missed >> it or overlooked the obvious. >> > >If you confirm this is the case , these situations are so common but >maybe deserve more visibility in the installation procedure and/or >troubleshooting guide . Ok, I appreciate that and I am trying to confirm this now… once I get past this and have the bloodhound VM fully functioning, I can attempt to install and/or port 3 of the plugins we were interested in from trace and let you know how that goes and put them up on the list if successful. > >Otherwise , we shall investigate the root cause a bit further . OK, I'll let you know ASAP. Thanks. > >-- >Regards, > >Olemis - @olemislc
