About 3 months ago, I got a call from our call center that everyone had been kicked off their terminals. A quick look under /dev revealed that all the tty's (all my digi serial devices) for the call center had been re-inited! This occurred at the same time that the office manager was doing a disable/enable on a bummed out dumb terminal (I have a script that runs asroot to do this). I have 4 more cases in the last 3 months - all occurring when a enable/disable was done.
I have been able to re-create this by the following. 1. Running this script (see below) 2. Putting the system under a heavy, heavy, heavy load. Doing just #1 does nothing. I let it run like this for two days and I couldn't recreate it.
Note - the script is to just provoke the situation. It is not the script we are running to do the enable/disable.
Script:
l /dev/tty[a-d]*
while [ 0 ]
do
date
disable ttyc01
sleep 2
enable ttyc01
sleep 2
done
The equipement used are Digi c/con16 concentrators, 3 Digi AccelePort Host controllers and many wy60 dumb terminals.
I have recreated it on two 5.0.6 servers and I am trying to re-create on a 5.0.4 server. The hardware is a Dell PowerEdge 6600 with 4 gbs of ram, quad 2.5 ghz Xeon processors.
I have been able to re-create this by the following. 1. Running this script (see below) 2. Putting the system under a heavy, heavy, heavy load. Doing just #1 does nothing. I let it run like this for two days and I couldn't recreate it.
Note - the script is to just provoke the situation. It is not the script we are running to do the enable/disable.
Script:
l /dev/tty[a-d]*
while [ 0 ]
do
date
disable ttyc01
sleep 2
enable ttyc01
sleep 2
done
The equipement used are Digi c/con16 concentrators, 3 Digi AccelePort Host controllers and many wy60 dumb terminals.
I have recreated it on two 5.0.6 servers and I am trying to re-create on a 5.0.4 server. The hardware is a Dell PowerEdge 6600 with 4 gbs of ram, quad 2.5 ghz Xeon processors.