[Spacewalk-list] fe_sendauth: no password supplied

[Patrick Hurrelmann]

On 07.03.2012 14:56, Patrick Hurrelmann wrote:
> On 07.03.2012 14:38, Patrick Hurrelmann wrote:
>> On 07.03.2012 14:05, Jan Pazdziora wrote:
>>> On Wed, Mar 07, 2012 at 12:18:59PM +0100, Patrick Hurrelmann wrote:
>>>> CREATE FUNCTION
>>>>  create_varnull_constriants
>>>> ----------------------------
>>>>                           0
>>>> (1 row)
>>>>
>>>> psql:/var/log/spacewalk/schema-upgrade/20120307-112200-script.sql:5172:
>>>> ERROR:  could not establish connection
>>>> DETAIL:  fe_sendauth: no password supplied
>>>>
>>>> CONTEXT:  SQL statement "SELECT  dblink_connect('at_conn', 'dbname=' ||
>>>> current_database())"
>>>
>>> I assume you get the same error when you run
>>>
>>> 	select * from dblink('dbname=' || current_database(), 'select 1 + 2') as t(id integer) ;
>>>
>>> in your psql.
>>>
>>> What is in your /var/lib/pgsql/data/pg_hba.conf?
>>>
>>
>> Hi Jan,
>>
>> yes, the result is the same and there is no difference whether unix
>> socket or tcp/ip is used.
>>
>> % psql -d spacewalk -U spacewalk -h localhost
>> Password for user spacewalk: xxxx
>> psql (8.4.9)
>> Type "help" for help.
>>
>> spacewalk=# select * from dblink('dbname=' || current_database(),
>> 'select 1 + 2') as t(id integer) ;
>> ERROR:  could not establish connection
>> DETAIL:  fe_sendauth: no password supplied
>>
>> spacewalk=# \q
>> % psql -d spacewalk -U spacewalk
>> Password for user spacewalk:
>> psql (8.4.9)
>> Type "help" for help.
>>
>> spacewalk=# select * from dblink('dbname=' || current_database(),
>> 'select 1 + 2') as t(id integer) ;
>> ERROR:  could not establish connection
>> DETAIL:  fe_sendauth: no password supplied
>>
>>
>> PostgreSQL is running locally and the content of pg_hba.conf is:
>>
>> local   all         all                               md5
>> host    all         all         127.0.0.1/32          md5
>> host    all         all         ::1/128               md5
>>
>> So, all connections need md5.
>>
>> Regards
>> Patrick
>>
> 
> When setting the local connections to trust in pg_hba.conf the above
> query works. But isn't that contrary to
> https://fedorahosted.org/spacewalk/wiki/PostgreSQLServerSetup which
> suggests to use md5?
> 
> Regards
> Patrick
> 

Additionally I just restored the old 1.6 database and performed the
upgrade again. This time it finished without problems.

% spacewalk-schema-upgrade
Schema upgrade: [spacewalk-schema-1.6.42-1.el6] ->
[spacewalk-schema-1.7.55-1.el6]
Searching for upgrade path: [spacewalk-schema-1.6.42-1] ->
[spacewalk-schema-1.7.55-1]
Searching for upgrade path: [spacewalk-schema-1.6.42] ->
[spacewalk-schema-1.7.55]
Searching for upgrade path: [spacewalk-schema-1.6] -> [spacewalk-schema-1.7]
The path: [spacewalk-schema-1.6] -> [spacewalk-schema-1.7]
Planning to run spacewalk-sql with
[/var/log/spacewalk/schema-upgrade/20120307-150155-script.sql]
Hit Enter to continue or Ctrl+C to interrupt:
Executing spacewalk-sql, the log is in
[/var/log/spacewalk/schema-upgrade/20120307-150155-to-spacewalk-schema-1.7.log].
The database schema was upgraded to version [spacewalk-schema-1.7.55-1.el6].

Regards
Patrick

-- 
Lobster LOGsuite GmbH, Hauptstraße 67, D-82327 Tutzing

HRB 178831, Amtsgericht München
Geschäftsführer: Dr. Martin Fischer, Rolf Henrich