I have been posting to the Rocks list. If I can get manual fixes here, they may be able to suggest Rocks equivalents.
Thanks -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Pat Haley Email: pha...@mit.edu Center for Ocean Engineering Phone: (617) 253-6824 Dept. of Mechanical Engineering Fax: (617) 253-8125 MIT, Room 5-213 http://web.mit.edu/phaley/www/ 77 Massachusetts Avenue Cambridge, MA 02139-4301 ________________________________________ From: Chris Dagdigian [d...@sonsorol.org] Sent: Wednesday, May 25, 2016 1:25 PM To: Patrick Haley Cc: MacMullan IV, Hugh; users@gridengine.org Subject: Re: [gridengine users] All queues dropped because of overload or full Something is fundamentally broken with Grid Engine. An empty "qconf -sql" means that SGE is unaware of *any* cluster queues -- at the very least you should see the default all.q show up And also this is clear via blank "qstat -f' output -- SGE simply does not think that any compute nodes or SGE cluster queues even exist Sad to say though that the root cause and real fix is likely via ROCKS. SGE does not break this way naturally -- something went sideways during the ROCKS upgrade or one of the ROCKS specific upgrade or autoinstall scripts. You may need to ask the ROCKS people how to force a reinstall of SGE -- anything manual that we propose on this list would likely not persist since ROCKS likes to do a lot of automated provisioning and service management behind the scenes. Chris Pat Haley wrote: > > It looks similar but one big difference is when I run "qconf -sh" I > see all my compute nodes listed along with my frontend. However > "qconf -sql" is empty. > > Thanks _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
