Wednesday, November 17, 2010 9:38 AM
We are trying to setup service accounts to access the Headnode and add jobs to HPC.
We have two types of accounts
Account Type N - Account to logon as a Service Account but with no Admin Privileges
Account Type P - Account privileges to do stuff on the box with admin rights and access from the Network but won't allow logging onto the server
We have this distinction to avoid any one particular account to be used for hacking servers.
The AccountType P is ruled out since we have to connect to the headNode.
However I get the following exception when I try creating a job at HPC with Account type N.
"Could not connect to the scheduler. The user may not be authorized to connect to the scheduler or the scheduler service might not be running. " at
Scheduler HpcJobScheduler = = new Scheduler(); HpcJobScheduler.Connect(headNode);For now the problem is solved when I mannually grant the account admin privileges on the Head node.
But cannot afford to do the same on production. Any ideas?
Monday, May 23, 2011 5:46 PMDid you ever hear a resolution to this?
Wednesday, May 25, 2011 6:57 PM
Just to clarify Account Type N is a member of the HPC Cluster as a standard user? Are you using the a custom job template, and are there any special permissions set?