Description of problem: The clients can not access to the repository, located on the server. Version-Release number of selected component (if applicable): spacewalk-backend-1.8.85-1.el6.noarch spacewalk-backend-xmlrpc-1.8.85-1.el6.noarch spacewalk-backend-config-files-tool-1.8.85-1.el6.noarch spacewalk-backend-applet-1.8.85-1.el6.noarch spacewalk-backend-libs-1.8.85-1.el6.noarch spacewalk-jpp-workaround-1.0.4-1.el6.noarch spacewalk-grail-1.8.49-1.el6.noarch spacewalk-backend-tools-1.8.85-1.el6.noarch spacewalk-java-lib-1.8.181-1.el6.noarch spacewalk-html-1.8.49-1.el6.noarch spacewalk-java-postgresql-1.8.181-1.el6.noarch spacewalk-doc-indexes-1.1.1-1.el6.noarch spacewalk-java-1.8.181-1.el6.noarch spacewalk-repo-1.8-4.el6.noarch spacewalk-java-config-1.8.181-1.el6.noarch spacewalk-base-minimal-1.8.49-1.el6.noarch spacewalk-config-1.8.6-1.el6.noarch spacewalk-backend-sql-1.8.85-1.el6.noarch spacewalk-backend-server-1.8.85-1.el6.noarch spacewalk-backend-xml-export-libs-1.8.85-1.el6.noarch spacewalk-backend-app-1.8.85-1.el6.noarch spacewalk-backend-config-files-1.8.85-1.el6.noarch spacewalk-backend-package-push-server-1.8.85-1.el6.noarch spacewalk-pxt-1.8.49-1.el6.noarch spacewalk-admin-1.8.6-1.el6.noarch spacewalk-monitoring-selinux-1.8.4-1.el6.noarch spacewalk-sniglets-1.8.49-1.el6.noarch spacewalk-certs-tools-1.8.4-1.el6.noarch spacewalk-schema-1.8.89-1.el6.noarch spacewalk-selinux-1.8.2-1.el6.noarch spacewalk-taskomatic-1.8.181-1.el6.noarch spacewalk-search-1.8.6-1.el6.noarch spacewalk-backend-sql-postgresql-1.8.85-1.el6.noarch spacewalk-common-1.8.6-1.el6.noarch spacewalk-backend-config-files-common-1.8.85-1.el6.noarch spacewalk-backend-iss-export-1.8.85-1.el6.noarch spacewalk-backend-iss-1.8.85-1.el6.noarch spacewalk-base-1.8.49-1.el6.noarch spacewalk-monitoring-1.4.1-1.el6.noarch spacewalk-setup-1.8.24-1.el6.noarch spacewalk-branding-1.8.7-1.el6.noarch spacewalk-postgresql-1.8.6-1.el6.noarch spacewalk-setup-jabberd-1.8.7-1.el6.noarch How reproducible: # rhn_check # cat /var/log/up2date [Thu Jan 31 09:12:59 2013] up2date logging into up2date server [Thu Jan 31 09:12:59 2013] up2date successfully retrieved authentication token from up2date server [Thu Jan 31 09:12:59 2013] up2date updateLoginInfo() login info [Thu Jan 31 09:12:59 2013] up2date logging into up2date server [Thu Jan 31 09:12:59 2013] up2date successfully retrieved authentication token from up2date server [Thu Jan 31 09:12:59 2013] up2date updateLoginInfo() login info [Thu Jan 31 09:12:59 2013] up2date logging into up2date server [Thu Jan 31 09:12:59 2013] up2date successfully retrieved authentication token from up2date server [Thu Jan 31 09:12:59 2013] up2date updateLoginInfo() login info [Thu Jan 31 09:12:59 2013] up2date logging into up2date server [Thu Jan 31 09:12:59 2013] up2date successfully retrieved authentication token from up2date server [Thu Jan 31 09:12:59 2013] up2date Traceback (most recent call last): File "/usr/sbin/rhn_check", line 385, in __run_action (status, message, data) = CheckCli.__do_call(method, params, kwargs) File "/usr/sbin/rhn_check", line 377, in __do_call method = getMethod.getMethod(method, "/usr/share/rhn/", "actions") File "/usr/share/rhn/up2date_client/getMethod.py", line 79, in getMethod actions = __import__(modulename) File "/usr/share/rhn/actions/packages.py", line 273, in <module> yum_base = YumAction() File "/usr/share/rhn/actions/packages.py", line 64, in __init__ self.doTsSetup() File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 84, in doTsSetup return self._getTs() File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 99, in _getTs self._getTsInfo(remove_only) File "/usr/lib/python2.6/site-packages/yum/depsolve.py", line 110, in _getTsInfo pkgSack = self.pkgSack File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 897, in <lambda> pkgSack = property(fget=lambda self: self._getSacks(), File "/usr/lib/python2.6/site-packages/yum/__init__.py", line 682, in _getSacks self.repos.populateSack(which=repos) File "/usr/lib/python2.6/site-packages/yum/repos.py", line 294, in populateSack sack.populate(repo, mdtype, callback, cacheonly) File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 165, in populate if self._check_db_version(repo, mydbtype): File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 223, in _check_db_version return repo._check_db_version(mdtype) File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1256, in _check_db_version repoXML = self.repoXML File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1455, in <lambda> repoXML = property(fget=lambda self: self._getRepoXML(), File "/usr/share/yum-plugins/rhnplugin.py", line 577, in _getRepoXML return YumRepository._getRepoXML(self) File "/usr/lib/python2.6/site-packages/yum/yumRepo.py", line 1451, in _getRepoXML raise Errors.RepoError, msg <class 'yum.Errors.RepoError'>: Cannot retrieve repository metadata (repomd.xml) for repository: centos-6-base-x86_64. Please verify its path and try again ########## ## Server: ########## # cat rhn/rhn_taskomatic_daemon.log INFO | jvm 1 | 2013/01/30 17:13:37 | 2013-01-30 17:13:37,492 [DefaultQuartzScheduler_QuartzSchedulerThread] ERROR org.quartz.core.ErrorLogger - An error occured while scanning for the next trigger to fire. INFO | jvm 1 | 2013/01/30 17:13:37 | org.quartz.JobPersistenceException: Couldn't acquire next trigger: ERROR: null value in column "priority" violates not-null constraint [See nested exception: org.postgresql.util.PSQLException: ERROR: null value in column "priority" violates not-null constraint] INFO | jvm 1 | 2013/01/30 17:13:37 | at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1778) INFO | jvm 1 | 2013/01/30 17:13:37 | at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1218) INFO | jvm 1 | 2013/01/30 17:13:37 | at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233) INFO | jvm 1 | 2013/01/30 17:13:37 | * Nested Exception (Underlying Cause) --------------- INFO | jvm 1 | 2013/01/30 17:13:37 | org.postgresql.util.PSQLException: ERROR: null value in column "priority" violates not-null constraint INFO | jvm 1 | 2013/01/30 17:13:37 | at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1608) INFO | jvm 1 | 2013/01/30 17:13:37 | at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1343) INFO | jvm 1 | 2013/01/30 17:13:37 | at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:194) INFO | jvm 1 | 2013/01/30 17:13:37 | at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:451) INFO | jvm 1 | 2013/01/30 17:13:37 | at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:350) INFO | jvm 1 | 2013/01/30 17:13:37 | at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:304) INFO | jvm 1 | 2013/01/30 17:13:37 | at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102) INFO | jvm 1 | 2013/01/30 17:13:37 | at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.insertFiredTrigger(StdJDBCDelegate.java:3360) INFO | jvm 1 | 2013/01/30 17:13:37 | at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1771) INFO | jvm 1 | 2013/01/30 17:13:37 | at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1218) INFO | jvm 1 | 2013/01/30 17:13:37 | at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233) Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
How was the centos-6-base-x86_64 channel created? How was it populated? Is that the only channel that has problems? Did this work and stopped working for this channel or did it never work?
Also, what does # rpm -q quartz output on your Spacewalk?
I propose closing this with INSUFFICIENT_DATA.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days