Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
help!! Scheduler is unresponsive RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Yesterday I didn't have any problems submitting jobs to the head node from a client PC.

    Today the client just hangs when I do a job submit via a command line call.

    I checked that all the services and ran diagnostics on the headnode.  IT does have warning (see below). but it had these same warning yesterday and still worked fine.

    here is the output of the diagnositc test.


    Thursday, October 8, 2015 3:20 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    after a while the client PC produces the message: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond

    Thursday, October 8, 2015 4:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The diagnostics result looks okay. The message from the client machine indicates that it can't talk to the scheduler. Thus, please check whether your client has connectivity issues with the headnode.

    Qiufang Shi

    Friday, October 9, 2015 3:54 AM