...
- 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):
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)
- Possible causes:
...