Conference humane::scheduler

1161.0. "Engine Shutdown Remote Node Down" by BSS::G_MCINTOSH (Touch Not the Cat, Bot the Glove) Fri Sep 20 1996 15:12

    Anyone heard of this problem where Sched engine shutdown 
    apparently because remote agent was down?
    
Scheduler (3.0-02) engine was no longer launching any scheduled jobs and
was not responding to 'run job' or 'close part' commands, it was        
responding to 'show job' commands.  It had been in this state for       
over an hour (looking at a job scheduled to run which never started).   
Showing a job which ran earlier in the morning, it took 12 minutes      
from scheduled time to start time.  Apparently the problem started      
earlier and degraded.                                                   
       
I finally stopped the scheduler (all components) on the server. Upon    
restart, it took over 15 minutes for queued commands (run job, close    
part, etc.) to be processed.  This is extremely unusual, typically      
command processing once everything is started is less than a minute.    
       
Suspecting the problem might have been caused or aggravated by a remote 
agent having been down for over 24 hours due to a hardware failure, I   
closed all partitions for that agent and held all related jobs.  The    
engine slow down did not repeat after that.  By appearances, a remote   
agent off the air for an extended period may cause problems... however, 
that could be coincidental.                                             

Thanks for any thoughts......Glenn