[Starcluster] upgrading AMI breaks SGE

[Mark J. Pearrow]

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.

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

I'll see if the system logfiles are helpful at all.

mjp



On Jan 7, 2010, at 1:22 PM, Mark J. Pearrow wrote:
> 
> 
> 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? 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/starcluster/attachments/20100108/7873eeb1/attachment.htm