Page History

...

• Unsuccessful attempt to start an iocConsole session, with no socket found 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" and returns to the Linux prompt.
  <when a real example arises, I will cut/paste it in here!>
  • Possible causes: soft iocs - for a soft ioc, this error condition indicates that the soft IOC cannot start due to some IOC software or configuration problem
  • Things to try:
    • have a look at the screenlog file: $IOC_DATA/iocname/screenlog.0. There are often error messages from the IOC indicating why it's having problems. Problems previously observed in screenlog.0 include:
      • $IOC/iocname bin directory or executable name not found (problem with make)
      • segmentation fault - IOC executable cannot run
    • check screeniocs to make sure the data for your IOC are correct
  • 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 is incorrectly entered in screeniocs (e.g. wrong port)
    • the terminal server port needs resetting.
    • prior iocConsole session 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

• Unsuccessful attempt to start an iocConsole session, with dead screen error message from iocConsole:
  looks like this:
  ...
  iocScreen: /home/screen/bin/screen -r -S laci/sioc-li17-ky00
  There is a screen on:
  10660.sioc-li17-ky00 (Dead ???)
  Remove dead screens with 'screen -wipe'.
  There is no screen to be attached matching sioc-li17-ky00.
  ...
  • Cause:
    • a previously running SCREEN session was killed without deleting its socket pipe file.
  • To fix:
    • iocConsole <iocname> -cleanup
    • please note: this will kill a soft IOC that is running. (unlikely that the ioc can run under these circumstances though)
  • Possible causes: soft iocs - for a soft ioc, this error condition indicates that the soft IOC cannot start
  • Things to try:
    • have a look at the screenlog file: $IOC_DATA/iocname/screenlog.0. There are often error messages from the IOC indicating why it's having problems. Problems previously observed in screenlog.0 include:
      • $IOC/iocname bin directory or executable name not found (problem with make)
      • segmentation fault - IOC executable cannot run
    • check screeniocs to make sure the data for your IOC are correct

• 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 is incorrectly entered in screeniocs (e.g. wrong port)
    • the terminal server port 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

...