<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>To be a bit more specific, after I aptitude safe-upgrade a stock ami-0f30d166, SGE is still running just fine until I either reboot the system or build a new AMI from it and launch an instance with it.</div><div><br></div><div>The starcluster -s script sits there for a while when it ought to be setting up SGE, but never appears to do so successfully. Then, when I log in to that instance, none of the sge_* binaries are running. If I start qmaster manually, I can attempt, at least, to submit a job, but the the error that localhost "is no submit host" (how snarky :) )</div><div><br></div><div>I'll see if the system logfiles are helpful at all.</div><div><br></div><div>mjp</div><div><br></div><div><br></div><br><div><div>On Jan 7, 2010, at 1:22 PM, Mark J. Pearrow wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font><br>I've been pulling my hair out trying to create a customized AMI with our neuroimaging softwware on it. It appears that running aptitude safe-upgrade on the AMI upgrades several sun-java packages, which appears to break SGE completely. Has anyone else had this problem? <br><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#144FAE"><br></font></font></div></blockquote></div></body></html>