Page History

...

iocConsole's error messages and conditions are not always 100% clear!  Here are a few situations you may encounter at some point:

• Wiki Markup
  *Your IOC hasn't been added to screeniocs yet:

  
  

  * looks like this:

  
  

  \[softegr@lcls-builder script\]$ iocConsole xyz

  
  

  Error: iocConsole is terminating...ioc was not included in screeniocs file

• Unsuccessful attempt to connect to the terminal server for your hard IOC, with error message from iocConsole:
  looks like this:
  <when a real example arises, I will cut/paste it in here!>
  screen writes out a message with something like "blah blah blah no socket found blah"
  • Possible causes:
    • the IOC or terminal server are powered down, or not connected to the network
    • there is a hardware problem with the IOC
    • the IOC may be incorrectly entered in screeniocs (e.g. wrong port)
    • the terminal server port may need resetting.
  • Things to try:
    • check screeniocs to make sure the data for your IOC are correct
    • check to make sure the IOC and terminal server are up, and connected properly to the network (ping, etc.)
    • try iocConsole cleanup (see overview above for more info on cleanup):
      iocConsole <iocname> -cleanup
    • try resetting the terminal server port for the IOC:
      iocTSmgr <iocname>
      (you must be logged in as iocegr or fiocegr to run iocTSmgr)

• Hard IOC console session starts and connects to the terminal server, but there is to EPICS prompt or response from the IOC
  looks like this:
  Trying 172.27.68.102...
  Connected to ts-li20-nw02.slac.stanford.edu (172.27.68.102).
  Escape character is '^]'.
  < then no response to a carriage return or other IOC command >
  • Possible causes:
    • the IOC is powered down, or not connected properly to the terminal server
    • the IOC is having serious hardware or software problems
    • there is a hardware problem with the IOC
    • the IOC may be incorrectly entered in screeniocs (e.g. wrong port)
    • the terminal server port mayneed resetting.
  • Things to try:
    • check screeniocs to make sure the data for your IOC are correct
    • check to make sure the IOC and terminal server are up, and connected properly to the network (ping, etc.)
    • try resetting the terminal server port for the IOC (unlikely to help - but worth a try!)
      iocTSmgr <iocname>
      (you must be logged in as iocegr or fiocegr to run iocTSmgr)

...