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" and returns to the Linux prompt.
  • 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
  • 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 its 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

...