Page History

...

• 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 blah 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):-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 hardware or software problems and needs restarting, or other application-specific action
    • 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 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)
    • Reboot or power cycle your IOC
• IOC console session stops logging (also see the maintence section below - logging is monitored daily by a cron job)
  looks like: screenlog.0 is missing OR screenlog.0 is not growing as expected
  There are a couple of possible causes:
  • your IOC has its own copy of screenrc with "deflog on" commented out
    • check to see of there's a $IOC/iocname/screenrc file
    • if so, make sure the "deflog on" is not commented out ("#deflog on")
  • the iocConsole session has terminated or is in an inconsistent state
    • for HARD IOC only do iocConsole -cleanup:
    • First do
      iocConsole iocname -cleanup
    • then
      iocConsole iocname
  • the screen process logging function has hung up somehow (this happens most commonly for soft IOCs, but can probably occur for all IOCs)
    • if screenlog.0 exists, make a backup copy
      cd $IOC_DATA/iocname
      cp screenlog.0 screenlog.0SAVE
    • iocConsole iocname
    • within the iocConsole session, toggle logging off and then on again:
      ctrl-a H
      ctrl-a H
      then exit iocConsole with ctrl-a d

...

Maintenance and monitoring

...