...
- 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
- Possible causes:
- IOC console session stops logging (also see the maintence section below - logging is monitored daily by a cron job)
There are a couple of possible causes:- Hard IOC - probable cause is that 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
- Soft IOC (or hard IOC - if the steps above don't workthe 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
- if screenlog.0 exists, make a backup copy
- Hard IOC - probable cause is that the iocConsole session has terminated or is in an inconsistent state
...