Page History

...

• Unsuccessful attempt to start an iocConsole session, 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 blah blah"
  • Possible causes: hard iocs
    • the IOC or terminal server are powered down, or not connected to the network
    • there is a hardware problem with the terminal server or IOC
    • the IOC may be is incorrectly entered in screeniocs (e.g. wrong port)
    • the terminal server port may need needs resetting.
    • prior iocConsole session may need needs cleaning up
  • 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:
      iocTSmgr iocname
    • try iocConsole -cleanup
      (you must be logged in as iocegr or fiocegr to run iocTSmgr)
    • iocConsole iocname -cleanup
  • Possible causes: soft iocs
    • the IOC may be incorrectly entered in screeniocs (e.g. wrong executable or host)
    • prior iocConsole session may need cleaning up
  • Things to try:
    • check screeniocs to make sure the data for your IOC are correct
    • if it's ok to kill the IOC process and restart it, then try
      iocConsole iocname -cleanup
      and
      restart the ioc

• Hard IOC console session starts and connects to the terminal server, but there is no 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 hardware or software problems and needs restarting, or other application-specific action
    • the IOC may be is incorrectly entered in screeniocs (e.g. wrong port)
    • the terminal server port may need needs 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
      iocTSmgr iocname
      (you must be logged in as iocegr or fiocegr to run iocTSmgr)
    • Reboot or power cycle your IOC

...