Description of problem: Repositories do not complete synchronization. Taskomatic crashes Version-Release number of selected component (if applicable): spacewalk 1.7 postgresql How reproducible: consistent Steps to Reproduce: 1. Initialize a reposync either by cron or manually 2. 3. Actual results: incomplete repodata Expected results: completed reposync and complete repodata Additional info: Result of crashing taskomatic -rw-r--r-- 1 root root 10 Dec 23 06:11 filelists.xml.gz.new -rw-r--r-- 1 root root 10 Dec 23 06:11 other.xml.gz.new -rw-r--r-- 1 root root 10 Dec 23 06:11 primary.xml.gz.new [Thread-56] ERROR com.redhat.rhn.taskomatic.task.ChannelRepodata - com.redhat.rhn.common.db.WrappedSQLException: Ran out of memory retrieving query results.
These are the last few entries from rhn_taskomatic.log INFO | jvm 1 | 2013/01/01 01:40:08 | 2013-01-01 01:40:08,020 [Thread-953] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Channel Modified Date:2013-01-01 00:00:02 EST INFO | jvm 1 | 2013/01/01 01:43:00 | 2013-01-01 01:42:59,677 [Thread-953] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Generating new repository metadata for channel 'fedora17-x86_64-updates'(sha1) 11083 packages, 3129 errata INFO | jvm 1 | 2013/01/01 01:43:44 | 2013-01-01 01:43:44,683 [Thread-954] INFO com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter - Generating new repository metadata for channel 'fedora17-i386-updates'(sha256) 13257 packages, 3198 errata ERROR | wrapper | 2013/01/01 01:59:30 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2013/01/01 01:59:31 | JVM did not exit on request, terminated STATUS | wrapper | 2013/01/01 01:59:32 | JVM exited in response to signal SIGKILL (9). ERROR | wrapper | 2013/01/01 01:59:32 | Unable to start a JVM STATUS | wrapper | 2013/01/01 01:59:32 | <-- Wrapper Stopped
Could you please upgrade to Spacewalk 1.8 where the memory issue of channel repodata generation was addressed and let us know if it fixes the problem for you as well?
I am using 1.8 currently. I've upgraded since I opened this bug
Are any more logs needed?
I actually have the same issue with version 1.9 on CentOS 6.4 / 64bit: INFO | jvm 1 | 2013/05/11 19:23:13 | 2013-05-11 19:23:13,964 [DefaultQuartzScheduler_Worker-8] INFO com.redhat.rhn.taskomatic.task.RepoSyncTask - Syncing repos for channel: Fedora 18 (x86_64) ERROR | wrapper | 2013/05/11 19:24:54 | JVM appears hung: Timed out waiting for signal from JVM. ERROR | wrapper | 2013/05/11 19:24:56 | JVM did not exit on request, terminated STATUS | wrapper | 2013/05/11 19:24:57 | JVM exited in response to signal SIGKILL (9). ERROR | wrapper | 2013/05/11 19:24:57 | Unable to start a JVM STATUS | wrapper | 2013/05/11 19:24:57 | <-- Wrapper Stopped
This seem to be caused by incorrect handling of stdout and stderr of spacewalk-repo-sync. I'm closing it as duplicate of bug 820612. If you disagree please reopen the bug. *** This bug has been marked as a duplicate of bug 820612 ***
This BZ closed some time during 2.5, 2.6 or 2.7. Adding to 2.7 tracking bug.