[Spacewalk-list] Spacewalk 2.0 UI shows repo cache continually in-progress

Avi Miller avi.miller at oracle.com
Sat Jan 17 05:18:30 UTC 2015


Hi,

> On 17 Jan 2015, at 5:45 am, Burnett, Robert Mark <Robert.Burnett at verizon.com> wrote:
> 
> My question to the list, is how to remove a queued repodata task to taskomatic.  I seems I have a task stuck in the queue and it is unable to rebuild the repo cache, until this task is removed or completes but it never does complete. 

How much memory do you have available for Taskomatic? It's likely that the repo is too large for the default memory limit and it's running out of memory. I know that I've had to bump up the default Taskomatic and Tomcat memory limits to get the metadata to generate.

Check /usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf and tweak the following:

# Initial Java Heap Size (in MB)
wrapper.java.initmemory=256

# Maximum Java Heap Size (in MB)
wrapper.java.maxmemory=2048

(Notice I've bumped my maxmemory up to 2GB in this instance).

Cheers,
Avi

--
Oracle <http://www.oracle.com>
Avi Miller | Product Management Director | +61 (3) 8616 3496
Oracle Linux and Virtualization
417 St Kilda Road, Melbourne, Victoria 3004 Australia





More information about the Spacewalk-list mailing list