[Spacewalk-list] Spacewalk 2.0 Oracle ULN repo sync

Bauer-Lee, Sue Sue.Bauer-Lee at multiplan.com
Tue Oct 14 16:27:13 UTC 2014


Thanks much! I had already increased memory once and missed the OOM after that. per your suggestion, I again increased memory to 16GB this time and all is well.  The docs I saw certainly suggested something different. :(

Any response wrt searchable archives for the list??

From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Avi Miller
Sent: Monday, October 13, 2014 3:30 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Spacewalk 2.0 Oracle ULN repo sync

Hi,

If you have Oracle Linux support, you should log an SR for this. :)

Having said that, there is nothing besides an out-of-memory condition I can think of that would cause a kill signal. Can you check /var/log/messages for any OOM-killer activity? The amount of memory required for a sync of the latest repositories is around 6-8GB just for the repo-sync tool. Your VM should probably have at least 16GB to support the database and other processes.

We'd need far more information, including the appropriate logs, to troubleshoot this further.

On 14 Oct 2014, at 12:44 am, Bauer-Lee, Sue <Sue.Bauer-Lee at multiplan.com<mailto:Sue.Bauer-Lee at multiplan.com>> wrote:


Good morning all -

I recently installed Spacewalk 2.0 from the Oracle public repo in order to use the ULN plugin.
After a hiccup here and there trying to find correct documentation for certain things, all seems to be installed and running. Base OS is EL 6.5, Oracle XE 11.2.

I setup 2 repos to start with and tried syncing them this weekend - both  from the web interface and the command line. Both regularly received a 'killed' signal as various points of the sync but roughly 50-65% through. Checking through as many of the logs as I could think of to check, I don't seem to be able to find a cause.

The syncs attempts were made both simultaneously and separately. After the first failures, I did increase memory and CPU resources to my VM,  thinking it was a resource related issue.
I've also verified that our network WAN connection has no rate limiting imposed. :)

Has anyone else experienced this? Any suggestions/ideas for cause/resolution (we really need to stick with 'uln')?

For reference :
spacewalk-repo-sync -t uln -c ol6_x86_64_latest -u uln:///ol6_x86_64_latest<uln://ol6_x86_64_latest>
spacewalk-repo-sync -t uln -c el5_x86_64_latest -u uln:///el5_x86_64_latest<uln://el5_x86_64_latest>

On a side note: is there a 'search' option for the archives of this list??

Thanks  in advance for your assistance. :)


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com<http://www.symanteccloud.com/>
______________________________________________________________________
NOTICE OF CONFIDENTIALITY: This message and any attachments contains confidential information belonging to the sender intended only for the use of the individual or entity named above. If you are not the intended recipient, be advised that copying, disclosure or reliance upon the contents is strictly prohibited. If you have received this message in error please notify the sender immediately.
_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com<mailto:Spacewalk-list at redhat.com>
https://www.redhat.com/mailman/listinfo/spacewalk-list

--
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


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________


NOTICE OF CONFIDENTIALITY: This message and any attachments contains confidential information belonging to the sender intended only for the use of the individual or entity named above. If you are not the intended recipient, be advised that copying, disclosure or reliance upon the contents is strictly prohibited. If you have received this message in error please notify the sender immediately.



______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20141014/45d0df6c/attachment.htm>


More information about the Spacewalk-list mailing list