[Spacewalk-list] problem syncing profiles...

Milan Zazrivec mzazrivec at redhat.com
Wed Apr 11 16:58:42 UTC 2012 

On Wednesday 11 April 2012 18:52:42 Milan Zazrivec wrote:
> On Wednesday 11 April 2012 18:21:56 Ron Parker wrote:
> > I'm running into an issue trying to use the profile sync feature on
> > spacewalk-postqesql 1.7.3.  The GUI allows me to compare and then select
> > the packages to sync, but generates a 500 error when attempting to effect
> > the changes.  The systems are registered correctly in spacewalk, have
> > valid DNS entries, and I can push packages and scripts successfully to
> > them.  I'm not familiar with postgresql and wondering if profile syncing
> > is simply broken for postgresql installs. I didn't see anything about
> > this in the list.  Can anyone offer any insight?
> > 
> > Here is the traceback:
> > -------------------------------------------
> > The following exception occurred while executing this request:
> > GET /rhn/systems/details/packages/profiles/MissingPackageSubmit.do
> > 
> > [...]
> > 
> > Exception:
> > javax.servlet.ServletException:
> > com.redhat.rhn.common.db.WrappedSQLException: ERROR: syntax error at or
> > near ","
> > 
> >  Where: Error occurred on dblink connection named "unnamed": could not
> > 
> > execute command.
> > SQL statement "SELECT  dblink_exec('at_conn',  $1 , true)"
> > PL/pgSQL function "pg_dblink_exec" line 4 at PERFORM
> > SQL statement "SELECT  pg_dblink_exec( 'insert into rhnTransactionPackage
> > (id, operation, name_id, evr_id, package_arch_id)' || ' values (' ||  $1
> > 
> >  || ', ' ||  $2  || ', ' ||  $3  || ', ' ||  $4  || ', ' || ', ' ||  $5 
> >  || ||
> > 
> > ')')"
> > PL/pgSQL function "lookup_transaction_package" line 36 at PERFORM
> > 
> >        at
> > 
> > org.apache.struts.action.RequestProcessor.processException(RequestProcess
> > or .java:520) at
> > org.apache.struts.action.RequestProcessor.processActionPerform(RequestPro
> > ce ssor.java:427) at
> > org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:2
> > 28 ) at
> > com.redhat.rhn.frontend.struts.RhnRequestProcessor.process(RhnRequestProc
> > es sor.java:99) at
> > org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
> > 
> >        at
> > 
> > org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:449)
> > 
> >        at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
> >        at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> >        at
> > 
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicat
> > io nFilterChain.java:290) at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilte
> > rC hain.java:206) at
> > com.redhat.rhn.frontend.servlets.AuthFilter.doFilter(AuthFilter.java:91)
> > 
> >        at
> > 
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicat
> > io nFilterChain.java:235) at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilte
> > rC hain.java:206) at
> > com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFil
> > te r.java:129) at
> > com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(SiteMeshFilter.j
> > av a:77) at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicat
> > io nFilterChain.java:235) at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilte
> > rC hain.java:206) at
> > com.redhat.rhn.frontend.servlets.LocalizedEnvironmentFilter.doFilter(Loca
> > li zedEnvironmentFilter.java:67) at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicat
> > io nFilterChain.java:235) at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilte
> > rC hain.java:206) at
> > com.redhat.rhn.frontend.servlets.EnvironmentFilter.doFilter(EnvironmentFi
> > lt er.java:108) at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicat
> > io nFilterChain.java:235) at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilte
> > rC hain.java:206) at
> > com.redhat.rhn.frontend.servlets.SessionFilter.doFilter(SessionFilter.jav
> > a: 55) at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicat
> > io nFilterChain.java:235) at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilte
> > rC hain.java:206) at
> > com.redhat.rhn.frontend.servlets.SetCharacterEncodingFilter.doFilter(SetC
> > ha racterEncodingFilter.java:97) at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicat
> > io nFilterChain.java:235) at
> > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilte
> > rC hain.java:206) at
> > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve
> > .j ava:233) at
> > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve
> > .j ava:191) at
> > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:
> > 12 7) at
> > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:
> > 10 2) at
> > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.j
> > av a:109) at
> > org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:29
> > 8)
> > 
> >        at
> > 
> > org.apache.jk.server.JkCoyoteHandler.invoke(JkCoyoteHandler.java:190)
> > 
> >        at
> > 
> > org.apache.jk.common.HandlerRequest.invoke(HandlerRequest.java:291)
> > 
> >        at
> >        org.apache.jk.common.ChannelSocket.invoke(ChannelSocket.java:769)
> >        at
> > 
> > org.apache.jk.common.ChannelSocket.processConnection(ChannelSocket.java:6
> > 98 ) at
> > org.apache.jk.common.ChannelSocket$SocketConnection.runIt(ChannelSocket.j
> > av a:891) at
> > org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.
> > ja va:690) at java.lang.Thread.run(Thread.java:679)
> > Caused by: com.redhat.rhn.common.db.WrappedSQLException: ERROR: syntax
> > error at or near ","
> > 
> >  Where: Error occurred on dblink connection named "unnamed": could not
> > 
> > execute command.
> > SQL statement "SELECT  dblink_exec('at_conn',  $1 , true)"
> > PL/pgSQL function "pg_dblink_exec" line 4 at PERFORM
> > SQL statement "SELECT  pg_dblink_exec( 'insert into rhnTransactionPackage
> > (id, operation, name_id, evr_id, package_arch_id)' || ' values (' ||  $1
> > 
> >  || ', ' ||  $2  || ', ' ||  $3  || ', ' ||  $4  || ', ' || ', ' ||  $5 
> >  || ||
> > 
> > ')')"
> > PL/pgSQL function "lookup_transaction_package" line 36 at PERFORM
> > 
> >        at
> > 
> > com.redhat.rhn.common.translation.SqlExceptionTranslator.postgreSqlExcept
> > io n(SqlExceptionTranslator.java:54) at
> > com.redhat.rhn.common.translation.SqlExceptionTranslator.sqlException(Sql
> > Ex ceptionTranslator.java:44) at
> > com.redhat.rhn.common.db.NamedPreparedStatement.execute(NamedPreparedStat
> > em ent.java:141) at
> > com.redhat.rhn.common.db.datasource.CachedStatement.execute(CachedStateme
> > nt .java:453) at
> > com.redhat.rhn.common.db.datasource.CachedStatement.execute(CachedStateme
> > nt .java:430) at
> > com.redhat.rhn.common.db.datasource.CachedStatement.executeUpdate(CachedS
> > ta tement.java:270) at
> > com.redhat.rhn.common.db.datasource.WriteMode.executeUpdate(WriteMode.jav
> > a: 33) at
> > com.redhat.rhn.manager.action.ActionManager.schedulePackageRunTransaction
> > (A ctionManager.java:1063) at
> > com.redhat.rhn.manager.profile.ProfileManager.syncToSystem(ProfileManager
> > .j ava:696) at
> > com.redhat.rhn.frontend.action.rhnpackage.profile.MissingPackageAction.sy
> > nc ToVictim(MissingPackageAction.java:88) at
> > com.redhat.rhn.frontend.action.rhnpackage.profile.MissingPackageAction.re
> > mo vePackagesFromSync(MissingPackageAction.java:152) at
> > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
> > :5 7) at
> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI
> > mp l.java:43) at java.lang.reflect.Method.invoke(Method.java:616)
> > 
> >        at
> > 
> > org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.ja
> > va
> > 
> > :269) at
> > 
> > org.apache.struts.actions.DispatchAction.execute(DispatchAction.java:170)
> > 
> >        at
> > 
> > org.apache.struts.actions.LookupDispatchAction.execute(LookupDispatchActi
> > on .java:146) at
> > org.apache.struts.action.RequestProcessor.processActionPerform(RequestPro
> > ce ssor.java:425) ... 40 more
> > Caused by: org.postgresql.util.PSQLException: ERROR: syntax error at or
> > near ","
> > 
> >  Where: Error occurred on dblink connection named "unnamed": could not
> > 
> > execute command.
> > SQL statement "SELECT  dblink_exec('at_conn',  $1 , true)"
> > PL/pgSQL function "pg_dblink_exec" line 4 at PERFORM
> > SQL statement "SELECT  pg_dblink_exec( 'insert into rhnTransactionPackage
> > (id, operation, name_id, evr_id, package_arch_id)' || ' values (' ||  $1
> > 
> >  || ', ' ||  $2  || ', ' ||  $3  || ', ' ||  $4  || ', ' || ', ' ||  $5 
> >  || ||
> > 
> > ')')"
> > PL/pgSQL function "lookup_transaction_package" line 36 at PERFORM
> > 
> >        at
> > 
> > org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecut
> > or Impl.java:2062) at
> > org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl
> > .j ava:1795) at
> > org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:2
> > 57 ) at
> > org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statemen
> > t. java:479) at
> > org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc
> > 2S tatement.java:367) at
> > org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statemen
> > t. java:360) at
> > com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.execute(NewProxyPrepar
> > ed Statement.java:362) at
> > com.redhat.rhn.common.db.NamedPreparedStatement.execute(NamedPreparedStat
> > em ent.java:138) ... 56 more
> 
> This was fixed recently in commit 7d5b103704271058cef3ec9c605f3daee85fa6bc
> and will be available in next Spacewalk release.

... and if waiting for next Spacewalk release and upgrade is not an option for
you, you are welcome to apply the updated lookup_transaction_package
procedure on your own.

-MZ

More information about the Spacewalk-list mailing list