On 30 Sep 2011, at 13:18, Stephen Jones wrote:
> Hi,
>
> If everyone an early adopter, is anyone an early adopter? While we
> ponder that, I've got something to say/ask about emi-cream and
> emi-torque. Maybe an early-adopter could enlighten me?
>
> The plan was to fix a new new emi-cream onto our existing (separate)
> glite_TORQUE_server cluster. But I discovered that emi-torque (server
> and utils) is built to use MUNGE to safety transmit the login details.
> This is a new thing.
>
> Unfortunately, due to MUNGE, the emi-cream can't qsub from a system
> using emi-torque-utils to a batch cluster headnode that uses
> glite_TORQUE_server (job array syntax is also new). This would mean
> that, by design, emi-cream cannot work with a standalone
> glite_TORQUE_server cluster -- the whole lot has to be updated at once.
> This could deserve a GGUS ticket, but I'm not sure of the facts -- is it
> possible to run emi-cream/emi-torque-utils with an existing
> glite_TORQUE_server?
... I'm pretty sure that's what we do
Ok, strictly, no - we're using what looks like the SL5 native Torque, probably inherited from Centos, not the gLite one.
> Should it be possible to qsub from a
> system using emi-torque-utils to a batch cluster headnode that uses
> glite_TORQUE_server?
I've been able to qsub, and I can assure you that we're defiatly using ruserok (and not munge) on our torque head node, and the emi-torque-utils where I submitted from.
What error message are you actually seeing - it could be down to the different authentication keys in the different builds of torque?
|