Postgres not liking "bloodhound" or "postgres" user

[ldr ldr <st...@gmail.com>]

Following the install guide I did:

sudo su - postgres
createuser -U postgres -S -D -R -E -P bloodhound
createdb -U postgres -O bloodhound -E UTF-8 bloodhound

Using the light wrapper `pgwrap` [which supports URL syntax] from a
Python interpreter gives me:
OperationalError: FATAL:  password authentication failed for user "bloodhound"
FATAL:  password authentication failed for user "bloodhound"

Trying to login to postgresql using the bloodhound account (with `psql
-U bloodhound`):
psql: FATAL:  password authentication failed for user "bloodhound"

Seeing as I am only using Postgres for Trac, I tried using the
`postgres` account; but got this error from `bloodhound_setup.py`:

Error: ProgrammingError: relation "system" does not exist

----

How do I get Bloodhound to play nice with Postgres?

Re: Postgres not liking "bloodhound" or "postgres" user

[ldr ldr <st...@gmail.com>]

*bitbucket

On Wed, Nov 20, 2013 at 11:14 AM, ldr ldr <st...@gmail.com> wrote:
> Mmm, well it's too late now. Going to be sticking to github at least
> until the end of the year.
>
> On Wed, Nov 20, 2013 at 4:10 AM, Michael Jinks <mi...@gmail.com> wrote:
>> That's normal. Check the Postgres documentation for why that is.
>> Teaching you to use PostgreSQL is beyond the scope of the Bloodhound
>> project.
>>
>> From your past emails it appears that there is also something wrong
>> with your bloodhound database (within postgres) or the bloodhound role
>> (corresponds to a "user" within postgres). You've said that you set
>> the password to something simple, but you're still getting errors that
>> suggest a bad password, which is why I was trying to coach you through
>> connecting to the database by other means, to see if we could get a
>> better idea of what's going on.
>>
>> Is there some reason why you can't use the sqlite database that comes
>> bundled with Bloodhound? It would be a lot simpler to get running.
>> Even if you don't want to use that long-term, at least you could get
>> started using Bloodhound and then worry about moving to PostgreSQL
>> later.
>>
>>
>>
>>
>> On Tue, Nov 19, 2013 at 7:22 AM, ldr ldr <st...@gmail.com> wrote:
>>> I can connect as postgres user; but then I get those errors regarding
>>> non-presence of "system" table.
>>>
>>> On Tue, Nov 19, 2013 at 4:41 AM, Michael Jinks <mi...@gmail.com> wrote:
>>>> Are you able to create and use other database accounts? Other databases?
>>>>
>>>> Please transcribe (copy and paste) any relevant terminal sessions so
>>>> that we can see exactly what you're typing and the errors you get
>>>> back.

Re: Postgres not liking "bloodhound" or "postgres" user

[ldr ldr <st...@gmail.com>]

Mmm, well it's too late now. Going to be sticking to github at least
until the end of the year.

On Wed, Nov 20, 2013 at 4:10 AM, Michael Jinks <mi...@gmail.com> wrote:
> That's normal. Check the Postgres documentation for why that is.
> Teaching you to use PostgreSQL is beyond the scope of the Bloodhound
> project.
>
> From your past emails it appears that there is also something wrong
> with your bloodhound database (within postgres) or the bloodhound role
> (corresponds to a "user" within postgres). You've said that you set
> the password to something simple, but you're still getting errors that
> suggest a bad password, which is why I was trying to coach you through
> connecting to the database by other means, to see if we could get a
> better idea of what's going on.
>
> Is there some reason why you can't use the sqlite database that comes
> bundled with Bloodhound? It would be a lot simpler to get running.
> Even if you don't want to use that long-term, at least you could get
> started using Bloodhound and then worry about moving to PostgreSQL
> later.
>
>
>
>
> On Tue, Nov 19, 2013 at 7:22 AM, ldr ldr <st...@gmail.com> wrote:
>> I can connect as postgres user; but then I get those errors regarding
>> non-presence of "system" table.
>>
>> On Tue, Nov 19, 2013 at 4:41 AM, Michael Jinks <mi...@gmail.com> wrote:
>>> Are you able to create and use other database accounts? Other databases?
>>>
>>> Please transcribe (copy and paste) any relevant terminal sessions so
>>> that we can see exactly what you're typing and the errors you get
>>> back.

Re: Postgres not liking "bloodhound" or "postgres" user

[Michael Jinks <mi...@gmail.com>]

That's normal. Check the Postgres documentation for why that is.
Teaching you to use PostgreSQL is beyond the scope of the Bloodhound
project.

>From your past emails it appears that there is also something wrong
with your bloodhound database (within postgres) or the bloodhound role
(corresponds to a "user" within postgres). You've said that you set
the password to something simple, but you're still getting errors that
suggest a bad password, which is why I was trying to coach you through
connecting to the database by other means, to see if we could get a
better idea of what's going on.

Is there some reason why you can't use the sqlite database that comes
bundled with Bloodhound? It would be a lot simpler to get running.
Even if you don't want to use that long-term, at least you could get
started using Bloodhound and then worry about moving to PostgreSQL
later.




On Tue, Nov 19, 2013 at 7:22 AM, ldr ldr <st...@gmail.com> wrote:
> I can connect as postgres user; but then I get those errors regarding
> non-presence of "system" table.
>
> On Tue, Nov 19, 2013 at 4:41 AM, Michael Jinks <mi...@gmail.com> wrote:
>> Are you able to create and use other database accounts? Other databases?
>>
>> Please transcribe (copy and paste) any relevant terminal sessions so
>> that we can see exactly what you're typing and the errors you get
>> back.

Re: Postgres not liking "bloodhound" or "postgres" user

[ldr ldr <st...@gmail.com>]

I can connect as postgres user; but then I get those errors regarding
non-presence of "system" table.

On Tue, Nov 19, 2013 at 4:41 AM, Michael Jinks <mi...@gmail.com> wrote:
> Are you able to create and use other database accounts? Other databases?
>
> Please transcribe (copy and paste) any relevant terminal sessions so
> that we can see exactly what you're typing and the errors you get
> back.

Re: Postgres not liking "bloodhound" or "postgres" user

[Michael Jinks <mi...@gmail.com>]

Are you able to create and use other database accounts? Other databases?

Please transcribe (copy and paste) any relevant terminal sessions so
that we can see exactly what you're typing and the errors you get
back.

Re: Postgres not liking "bloodhound" or "postgres" user

[ldr ldr <st...@gmail.com>]

I get the same error.

I tried setting the password of the bloodhound user manually using
`\password` and even the plain-text logging `alter user bloodhound
with password 'new_password'`

On Tue, Nov 19, 2013 at 3:15 AM, Michael Jinks <mi...@gmail.com> wrote:
> This looks like you're having Postgres trouble outside of Bloodhound.
>
> One step at a time. What happens if you set the bloodhound user's
> password to something simple (just for now) and try the connection
> again? If that works, we know it's a password issue; if it doesn't, we
> know we have to look somewhere else.
>
> Can you show us a transcript of what happens why you run 'psql -d
> bloodhound bloodhound'?
>
>
>
>
> On Mon, Nov 18, 2013 at 9:35 AM, ldr ldr <st...@gmail.com> wrote:
>> Following the install guide I did:
>>
>> sudo su - postgres
>> createuser -U postgres -S -D -R -E -P bloodhound
>> createdb -U postgres -O bloodhound -E UTF-8 bloodhound
>>
>> Using the light wrapper `pgwrap` [which supports URL syntax] from a
>> Python interpreter gives me:
>> OperationalError: FATAL:  password authentication failed for user "bloodhound"
>> FATAL:  password authentication failed for user "bloodhound"
>>
>> Trying to login to postgresql using the bloodhound account (with `psql
>> -U bloodhound`):
>> psql: FATAL:  password authentication failed for user "bloodhound"
>>
>> Seeing as I am only using Postgres for Trac, I tried using the
>> `postgres` account; but got this error from `bloodhound_setup.py`:
>>
>> Error: ProgrammingError: relation "system" does not exist
>>
>> ----
>>
>> How do I get Bloodhound to play nice with Postgres?

Re: Postgres not liking "bloodhound" or "postgres" user

[Michael Jinks <mi...@gmail.com>]

This looks like you're having Postgres trouble outside of Bloodhound.

One step at a time. What happens if you set the bloodhound user's
password to something simple (just for now) and try the connection
again? If that works, we know it's a password issue; if it doesn't, we
know we have to look somewhere else.

Can you show us a transcript of what happens why you run 'psql -d
bloodhound bloodhound'?




On Mon, Nov 18, 2013 at 9:35 AM, ldr ldr <st...@gmail.com> wrote:
> Following the install guide I did:
>
> sudo su - postgres
> createuser -U postgres -S -D -R -E -P bloodhound
> createdb -U postgres -O bloodhound -E UTF-8 bloodhound
>
> Using the light wrapper `pgwrap` [which supports URL syntax] from a
> Python interpreter gives me:
> OperationalError: FATAL:  password authentication failed for user "bloodhound"
> FATAL:  password authentication failed for user "bloodhound"
>
> Trying to login to postgresql using the bloodhound account (with `psql
> -U bloodhound`):
> psql: FATAL:  password authentication failed for user "bloodhound"
>
> Seeing as I am only using Postgres for Trac, I tried using the
> `postgres` account; but got this error from `bloodhound_setup.py`:
>
> Error: ProgrammingError: relation "system" does not exist
>
> ----
>
> How do I get Bloodhound to play nice with Postgres?