Troubleshooting

This page contains a list of the most commonly found problems and warnings, and explains how serious they are and (hopefully) how to fix or work around them.

Quick List

Select item from list to navigate to detailed description
  1. The re-pointing information doesn't appear on the Planning Tools timeline plot. Instead there is a big orange bar!
  2. Error when checking the ORL file syntax is "yyyy-mm-dd hh:mm:ss FATAL parameter error stop"
  3. When checking that CPT can compile, get the error
    "2009-03-26 11:48:24 FATAL sequence non-allocated in plans EIS.orl(19)
    [2009-03-26 09:55:00.0] EIS_LOAD_OBSTBL_REAL"
  4. Checking script "eis_cp_compilation_check" failed!
  5. CPT gives the error "ERROR OG NUMBER OVERFLOW FOR EIS_RUNSEQ_088_OG: 511"
  6. When checking compilation (using "sh tool/coplnchk.sh"), get the error
    "2009-07-28 11:42:39 FATAL object or script beyond the Plan-term EIS.orl(222) [EIS_LOAD_OBSTBL_REAL]
    2009-07-28 11:42:39 FATAL exe_schedule create process error stop"
  7. There is a problem logging into or using the ope-gw machine
  8. Error message in eis_cp_compilation_check: "There should be 1 CP_HEX -- halting"
  9. sswidl crashes with a segmentation fault at start on eisco
  10. Planning Tools reports the error "Encountered a problem (2); Aborting"
  11. The re-point file is correctly seen in the planning tool but the studies are all pointed to [0,0]

Detailed List

  1. Issue The re-pointing information doesn't appear on the Planning Tools timeline plot. Instead there is a big orange bar!
    Reporter Harry Warren
    Origin 3-days of CP files are read either side of the current planning start position. In most cases this is sufficient. However, for longer period OP Periods this may not be.
    Solution Go to the menu-bar in the Planning Tools and select Tools → Preferences, and in the "CP Files" tab use the "Number of days" droplist to increase the time window to search for CP files (default is 3 days). Click Apply.
    2. TOP OF PAGE
  2. Issue Checking the ORL file syntax (using "sh tool/coorlchk.sh") on the ISACS account results in the following error;
    yyyy-mm-dd hh:mm:ss FATAL parameter error stop
    Reporter Harry Warren
    Origin The eisco $HOME/cmdpln/latest directory contains more than one ORL file (generated by testing/running CPT). This compilation checking script assumes there is only one ORL file.
    Solution Remove all previous versions of the orl file, leaving the latest version
    Notes This issue has been resolved by forcing the Planning Tools to delete any existing ORL files in this directory before creating a new one.
    3. TOP OF PAGE
  3. Issue When checking that the CPT can compile (using "sh tool/pdlchk.sh") the following error occurs;
    2009-03-26 11:48:24 FATAL sequence non-allocated in plans EIS.orl(19)
    [2009-03-26 09:55:00.0] EIS_LOAD_OBSTBL_REAL
    Reporter Ignacio Ugarte
    Origin The wrong time for the table upload was used
    Solution Edit the ORL file with the right time and update the EIS planning status to 'Re-submitted'. ORL file location at eisco@ISAS machine: ../eisco/cmdpln/latest/EIS_YYYYMMDDXXXX.orl
    Notes Do NOT to run CPT again!
    4. TOP OF PAGE
  4. Issue Checking script "eis_cp_compilation_check" failed!
    Reporter Ignacio Ugarte
    Origin Tested CPT but didn't run it
    Solution Go back to Stage 3 and run CPT, then follow on from there
    5. TOP OF PAGE
  5. Issue CPT gives the following error;
    ERROR OG NUMBER OVERFLOW FOR EIS_RUNSEQ_088_OG: 511
    Reporter Peter Young
    Origin This error arises when exceeding 60 OGs in the plan; where an OG corresponds to one individual time-tagged study.
    Solution Reduce the number of studies on the timeline to ensure that a maximum of 60 OGs are used per plan (OP) period.
    Notes The 60 OGs use per plan limit is imposed by the spacecraft.
    6. TOP OF PAGE
  6. Issue When checking that the plan can compile (using "sh tool/coplnchk.sh") the following error occurs;;
    2009-07-28 11:42:39 FATAL object or script beyond the Plan-term EIS.orl(222) [EIS_LOAD_OBSTBL_REAL]
       2009-07-28 11:42:39 FATAL exe_schedule create process error stop
    Reporter Kitagawa
    Origin You are checking today's plan post-deadline.
    Solution  Run the post-deadline check (using "sh tool/pdlchk.sh")
    Notes -
    7. TOP OF PAGE
  7. Issue There is a problem logging into or using the ope-gw machine
    Reporter Khalid
    Origin System maintenance
    Solution Try using the ssh2 machine instead
    Notes -
    8. TOP OF PAGE
  8. Issue Error message in eis_cp_compilation_check: "There should be 1 CP_HEX -- halting"
    Reporter Ignacio Ugarte
    Origin The /home/flare/slb/cp directory contains more than one EIS*.hex file. This compilation checking script assumes there is only one HEX file.
    Solution Remove all previous versions of the HEX file, leaving the latest version. CP writing permissions are required: contact Chief Planner.
    Notes -
    9. TOP OF PAGE
  9. Issue sswidl crashes with a segmentation fault at start on eisco
    Reporter David Williams
    Origin X Windows forwarding over SSH, if you are using Mac OS X "Leopard" (i.e. OS 10.5)
    Solution Either:
    1. use "ssh -X" instead of "ssh -Y" when logging onto OPE-GW and EISCO
    2. start a Terminal from the X11 application (choose "Applications -> Terminal" from the menu bar) and try logging in with this terminal instead
    Notes -
    10. TOP OF PAGE
  10. Issue Planning Tools reports the error "Encountered a problem (2); Aborting"
    Reporter David Williams
    Origin Planning Tools bug - being investigated!
    Solution If you see this, change the view on the timeline, then return to the original view (e.g. use the arrows) to go forward in time (to where there are less studies to read from the database), then use the back arrow.
    Notes Under investigation.
    11. TOP OF PAGE
  11. Issue The re-point file is correctly seen in the planning tool but the studies are all pointed to [0,0]
    Reporter David Brooks
    Origin The re-point file format is incorrect. There is no section for "New AOCS tracking parameters after the memory upload".
    Solution Contact the CP to re-make the re-point file.
    Notes This has only been encountered when a new pointing table is made on a non-upload day, but we don't know why it happened so it's possible it could occur some other time.
    12. TOP OF PAGE
Contents:
RP CO Operations Links:
Operations:
Links: