The software described in this documentation is either no longer supported or is in extended support.
Oracle recommends that you upgrade to a current supported release.
To synchronize software channels:
Go to Channels, select Manage Software Channels and then select the required channel.
On the Channel Details page, select Repositories and then select Sync.
On the Channel Repositories page:
Check the following check boxes as required:
- Do not sync erratas
Select if you do not want to synchronize any errata that are available for the channel.
- Create kickstartable tree
Select if you want to be able to associate a kickstart profile with the channel.
NoteULN and the Oracle Linux yum server do not host the boot image files that you require to create a kickstartable tree. Instead, you can obtain the files from a Oracle Linux Media Pack DVD image and make them available on a local file system. See Chapter 4, Provisioning Client Systems.
- Terminate upon any error
Select if you want synchronization to stop if an error occurs.
Synchronize the software channel:
To perform an immediate manual synchronization, click Sync Now.
To schedule a recurring synchronization job, select the preferred schedule and times, and click Schedule.
You can specify a schedule using Quartz format, for example
0 30 22 ? * *would specify that Spacewalk should resynchronize the channel every day at 10:30 PM. Using Quartz format is the only way to schedule a synchronization several times a day. For example:0 0 0,2,22 ? * *would specify that synchronization should take place at 10 PM, midnight, and 2 AM.ImportantScheduling a recurring synchronization job creates a Taskomatic job. If the job does not seem to be running, Taskomatic might have crashed due to insufficient memory. The default amount of memory allocated to Taskomatic memory is too small to generate the repository metadata. For this reason, Oracle recommends using cron jobs to run spacewalk-repo-sync. However, this only ensures that the package synchronization works. Creating the metadata is always performed by Taskomatic.
The solution is to increase the JVM memory settings in the configuration file for the Taskomatic daemon
/usr/share/rhn/config-defaults/rhn_taskomatic_daemon.conf. The suggested minimum value forwrapper.java.maxmemoryis 4096 to 8192 MB, depending on the size of the repositories that must be synchronized.Similar memory issues can also occur in the web interface if you have big data sets, such as a large number of servers or packages. The solution is to increase the Tomcat memory limits in the
/etc/sysconfig/tomcat6(Oracle Linux 6) or/etc/sysconfig/tomcat(Oracle Linux 7) file. Edit theJAVA_OPTSenvironment variable, and increase the-Xms(the start or initial amount of memory) and-Xmx(the maximum amount of memory) parameters.