2009년 8월 18일 화요일 오전 1:37Hi,
I am using microsoft APIs ( ) to submit jobs to HPC job scheduler. Our application is installed on 2 separate clusters. Both clusters are on different networks and different domains. Things are working well on one cluster, but on the other cluster the jobs submitted by our application get stuck in "Configuring" state.
If I right click on the job which is in "Configuring" state (in the HPC cluster manager) and click submit job, it gets submitted but my application keeps waiting for a response.
Any ideas what might be causing this behavior? Is it something related to permissions?
2009년 8월 18일 화요일 오후 5:55중재자
Have you installed HPC Pack SP1 on your head node?
This can be due to credential issues; make sure you have up-to-date working credentials on your job. You can do this by running "job modify /user:<username>"
2009년 8월 19일 수요일 오전 3:20Thanks for the reply Josh!I have "2.1.1703.0" installed on the cluster. The HPC SP1 link seems to be broken (Top Picks section on the right of the page http://www.microsoft.com/hpc/en/us/default.aspx)yeah...I already tried job modify with my username/password...but it still doesn't go through...the username and password is already set to the correct value.Any other suggestions related to credentials? I think credentials are working fine because of the fact that when I right click on the job and click Submit, it asks me for username/password and submits the job.Prashant
2009년 8월 25일 화요일 오후 11:47중재자
Can you post the code snippet?
2009년 9월 1일 화요일 오후 9:14It was my fault actually....the password while submitting the job was being parsed the wrong way...hence the job was stuck in configuring state...
- 답변으로 표시됨 Josh BarnardModerator 2009년 9월 18일 금요일 오후 11:41
2011년 1월 6일 목요일 오후 6:58Just for others to reference, I had the same issue after starting an Abaqus job via the command line. The solution for us was that my users didn't realize that the command prompt was waiting for a password to be entered. After entering their password properly, the job submitted just fine. If the password was submitted improperly the job would fail. Therefore it leads me to believe that every time a job is stuck on configuring, it's awaiting some type of authentication. I hope this helps!