<div dir="ltr"><div><div><div>Hey John,<br><br>Thanks for the reply. What we were able to see initially was that something ran away with the system RAM (processes are killed by the OoM killer).
I've built a VM with 8GB (4GB Reserved) RAM while testing today, and used the additional time it bought me to run down the logs in /tmp as you suggested. They didn't have anything going on, but on a whim I fired up 'top' and noticed that commands which run from my SUPERMASSIVEHUGE post script were running before the OS was even installed, so I checked the setup and sure enough... post script was set up as a PRE script. And now I feel like an idiot.<br>
<br></div>Thanks again for the nudge. I changed my post-script-setup-as-a-pre-script over to a proper post script, and everything worked as expected.<br><br></div>- Jonathan<br></div>(And you shut up, Jesse... you couldn't figure it out either!)<br>
<div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Feb 20, 2013 at 4:31 PM, Jon Miller <span dir="ltr"><<a href="mailto:jonebird@gmail.com" target="_blank">jonebird@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I have lately gotten good leads when looking at the temp files being generated in /tmp on the client. Try switching over to VT2 and poking around. Other than that, you may get some clues by watching your apache access logs and see what was being requested right before the client died. <div>
<br></div><div>Good luck,</div><div>Jon</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Wed, Feb 20, 2013 at 1:10 PM, Jonathan Scott <span dir="ltr"><<a href="mailto:lists@xistenz.org" target="_blank">lists@xistenz.org</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div><div><div><div><div>Hello again folks. I'm not quite sure why I'm
having so many issues with my Spacewalk 1.8 install lately, but I come
seeking assistance once again.<br><br></div>I seem unable to use my
CentOS v6 kickstarts at all (32 and 64bit). When attempting to start, I
get as far as anaconda trying to load when it exits with the following
error: "Anaconda died after receiving signal 9. install exited
abnormally [1/1]". This only happens when I use a kickstart based off of
my Spacewalk 1.8 server, 1.7 does not have this issue. I don't have issues with my
similarly seeded CentOS v5 kickstarts. This seems completely isolated to
v6 and just to this Spacewalk install.<br>
<br></div>Infos:<br>- Fully updated Spacewalk 1.8 on CentOS v6.3<br>- CentOS-6.3-x86_64-bin-DVD[12].iso dated 6 July 2012 on the file system<br></div>- Base Satellite Software channel last updated 29 Aug 2012<br></div>- Anaconda version listed as 13.21.176 in the error message on both Spacewalk 1.7 and 1.8 kickstarts<br>
<br></div><div>I've attempted to downgrade to CentOS v6.2 on both the distribution source and base software channel, but I still get the same error.<br><br></div><div>Any insight and/or a push in the right direction would be much appreciated. I'm completely stumped.<br>
<br></div>Thanks!<span><font color="#888888"><br></font></span></div><span><font color="#888888">Jonathan<br></font></span></div>
<br></div></div>_______________________________________________<br>
Spacewalk-list mailing list<br>
<a href="mailto:Spacewalk-list@redhat.com" target="_blank">Spacewalk-list@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/spacewalk-list" target="_blank">https://www.redhat.com/mailman/listinfo/spacewalk-list</a><br></blockquote></div><br></div>
</blockquote></div><br></div></div></div></div></div>