Re: starcluster plugin status code 127
The only difference that I can see is that I have not used arguments to
the plugin. I guess you did remember to set the argument "queue_to_config"
in your config file?
Another possible issue is if you are trying to reconfig a cluster that is
just
in the process of coming up. If you try that command early on, it will
fail because
sge has not been installed yet. Why do you want to config the cluster
afterwards
rather than just on the initial bring up? HTH and let us know what you
find out.
Regards.
Don
On Tue, Dec 20, 2011 at 10:02 PM, Wei Tao <wei.tao_at_tsibiocomputing.com>wrote:
> Hi all,
>
> I tried to implement the queue configuration suggested by Don MacMillen a
> while ago. Here is my plugin code:
>
> from starcluster.clustersetup import ClusterSetup
>
> class SgeConfig(ClusterSetup):
> def __init__(self, queue_to_config):
> self.queue_to_config = queue_to_config
>
> def run(self, nodes, master, user, user_shell, volumes):
> cmd_strg = 'qconf -mattr queue load_thresholds np_load_avg=1.5 %s'
> %self.queue_to_config
> output = master.ssh.execute(cmd_strg)
>
> When I execute "starcluster runplugin <myplugin> <mycluster>", I got:
>
> >>> Running plugin <myplugin>
> !!! ERROR - command 'qconf -mattr queue load_thresholds np_load_avg=1.5
> all.q' failed with status 127
>
> If I sshmaster and run the command directly as this:
>
> root_at_master:~# qconf -mattr queue load_thresholds np_load_avg=1.5 all.q
> root_at_master modified "all.q" in cluster queue list
>
> It works fine. Could someone please point out why the plugin would have a
> status code 127 when direct execution of the command apparently works fine?
>
> Thanks for the help!
>
>
> -Wei
> _______________________________________________
> StarCluster mailing list
> StarCluster_at_mit.edu
> http://mailman.mit.edu/mailman/listinfo/starcluster
>
>
Received on Wed Dec 21 2011 - 01:42:08 EST
This archive was generated by
hypermail 2.3.0.