[Spacewalk-list] Package Search Failing, Ident Authentication Failed

23 views
Skip to first unread message

Glennie, Jonathan - 0443 - MITLL

unread,
Mar 28, 2012, 11:48:29 AM3/28/12
to spacewa...@redhat.com

Hello-

 

On spacewalk 1.6, running a package search in the GUI displays a red banner that reads “Could not execute query package_name”.  /var/log/rhn/search/rhn_search_daemon.log shows the following:

 

INFO   | jvm 1    | 2012/03/28 11:25:41 | 2012-03-28 11:25:41,792 [Thread-8] ERROR com.redhat.satellite.search.rpc.handlers.IndexHandler - Caught exception:

INFO   | jvm 1    | 2012/03/28 11:25:41 | org.postgresql.util.PSQLException: FATAL: Ident authentication failed for user "spaceuser"

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:291)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:108)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:66)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at org.postgresql.jdbc2.AbstractJdbc2Connection.<init>(AbstractJdbc2Connection.java:125)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at org.postgresql.jdbc3.AbstractJdbc3Connection.<init>(AbstractJdbc3Connection.java:30)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at org.postgresql.jdbc3g.AbstractJdbc3gConnection.<init>(AbstractJdbc3gConnection.java:22)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at org.postgresql.jdbc3g.Jdbc3gConnection.<init>(Jdbc3gConnection.java:24)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at org.postgresql.Driver.makeConnection(Driver.java:393)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at org.postgresql.Driver.connect(Driver.java:267)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at java.sql.DriverManager.getConnection(DriverManager.java:620)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at java.sql.DriverManager.getConnection(DriverManager.java:200)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.ibatis.common.jdbc.SimpleDataSource.popConnection(SimpleDataSource.java:580)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.ibatis.common.jdbc.SimpleDataSource.getConnection(SimpleDataSource.java:222)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransaction.init(JdbcTransaction.java:48)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.ibatis.sqlmap.engine.transaction.jdbc.JdbcTransaction.getConnection(JdbcTransaction.java:89)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.ibatis.sqlmap.engine.mapping.statement.GeneralStatement.executeQueryForList(GeneralStatement.java:123)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForList(SqlMapExecutorDelegate.java:615)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.ibatis.sqlmap.engine.impl.SqlMapExecutorDelegate.queryForList(SqlMapExecutorDelegate.java:589)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.ibatis.sqlmap.engine.impl.SqlMapSessionImpl.queryForList(SqlMapSessionImpl.java:118)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.redhat.satellite.search.db.Query.loadList(Query.java:66)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.redhat.satellite.search.rpc.handlers.IndexHandler.screenHits(IndexHandler.java:203)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.redhat.satellite.search.rpc.handlers.IndexHandler.search(IndexHandler.java:150)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.redhat.satellite.search.rpc.handlers.IndexHandler.search(IndexHandler.java:101)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at java.lang.reflect.Method.invoke(Method.java:616)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at redstone.xmlrpc.handlers.ReflectiveInvocationHandler.execute(ReflectiveInvocationHandler.java:217)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at redstone.xmlrpc.handlers.ReflectiveInvocationHandler.invoke(ReflectiveInvocationHandler.java:133)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at redstone.xmlrpc.XmlRpcDispatcher.dispatch(XmlRpcDispatcher.java:123)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at redstone.xmlrpc.XmlRpcServer.execute(XmlRpcServer.java:83)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at com.redhat.satellite.search.rpc.XmlRpcInvoker.handle(XmlRpcInvoker.java:73)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at simple.http.Dispatcher.run(Dispatcher.java:83)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at simple.util.process.Daemon.execute(Daemon.java:121)

INFO   | jvm 1    | 2012/03/28 11:25:41 |       at simple.util.process.Daemon.run(Daemon.java:106)

INFO   | jvm 1    | 2012/03/28 11:25:41 | Mar 28, 2012 11:25:41 AM redstone.xmlrpc.XmlRpcDispatcher writeError

INFO   | jvm 1    | 2012/03/28 11:25:41 | WARNING: redstone.xmlrpc.XmlRpcFault: FATAL: Ident authentication failed for user "spaceuser"

 

 

Is there a config file that I can check to see what credentials it is using?  The account and password that is using has been the same since day 1 although we re-ran the setup to use the FQDN of the server instead of the CN, not sure if that would have any impact on this or not. 

 

 

 

-Jon

Paul Robert Marino

unread,
Mar 29, 2012, 5:44:43 PM3/29/12
to spacewa...@redhat.com

You shouldn't be using ident auth in postgresql.
Instead you should be using md5 auth. Or simmilar mechanisim.
Ident auth is really only avalible because it makes the initial configuration easier, and some times its used for scripts so they don't need to contain passwords, however that's a bad security practice.
If it worked before and stopped working now it probably because it can't do remote ident verification which is handeled by xinetd.
To really fix the problem you need to edit the /var/lib/pgsql/data/gp_hba.conf file and change the auth mechanisim to md5.
Not if both are configured postgresql will honor the first entry from the top that matches the user and database.

_______________________________________________
Spacewalk-list mailing list
Spacewa...@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list

Glennie, Jonathan - 0443 - MITLL

unread,
Apr 2, 2012, 2:37:46 PM4/2/12
to spacewa...@redhat.com

Changing the auth method in pg_hba.conf to md5 and then restarting postgres worked.  Thank you very much! 

Paul Robert Marino

unread,
Apr 2, 2012, 5:33:41 PM4/2/12
to spacewa...@redhat.com

Glad I could help

Reply all
Reply to author
Forward
0 new messages