[SCHEDULER-561]  Startup with bad weather - another issue
Type Bug
Priority High
Severity Major
Component Dispatch Scheduler Engine
Fixed In Version [3.3] 3.3
Versions Affected [3.3] 3.3
Severity Closed
Resolution Complete
Reported By Bob Denny
Resources Bob Denny
Start Date 1/15/2011

Description 
14-Jan-2011 23:12:58.4: ++ Observatory Startup ++

14-Jan-2011 23:12:58.4: Start ACP Sequencer's StartupObs script

14-Jan-2011 23:13:08.4: Sequencer is now active

14-Jan-2011 23:15:55.4: Sequencer is no longer active

14-Jan-2011 23:15:55.5: -- Weather Unsafe --

14-Jan-2011 23:15:56.5: **EXCEPTION IN SCHEDULER:

14-Jan-2011 23:15:56.5: Startup (re)connected weather and it is unsafe. It should have already been connected. Contact the developer.

14-Jan-2011 23:15:56.5: Traceback:

at DC3.Scheduler.Engine.DoStartupIf(Boolean openDome)

at DC3.Scheduler.Engine.Run()

Comments
1/18/2011 3:16:15 PM   Bob Denny 

 

  SVN Comment
 

 

  Author
  rbdenny
 

 

  Repository
  svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
 

 

  SVN Revision
  145
 

 

  Affected files
  /trunk/Scheduler/ACPSequencer.cs (Modified)

 

 

  Check-in comment
  Log reconnects at SuperDebug level in ACP Sequencer.
GEM:561
1/18/2011 3:14:52 PM   Bob Denny 
That did it. Needed to suppress logging of (re)connects except for SuperDebug.
1/15/2011 6:03:12 PM   Bob Denny 

 

  SVN Comment
 

 

  Author
  rbdenny
 

 

  Repository
  svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
 

 

  SVN Revision
  140
 

 

  Affected files
  /trunk/Scheduler/Engine.cs (Modified)

 

 

  Check-in comment
  Catch startup connecting to unsafe weather, fatal condition. Conn weather if possible before test.
GEM:561
1/15/2011 6:00:12 PM   Bob Denny 
Use new sequencer ConnectWeather to force it to connect before the initial poll.
1/14/2011 4:59:00 PM   Bob Denny 
The scheduler showed Dead (Unsafe Weather) but the weather was safe! It was connected to ACP.