iBootBar Login Timeout Error

Symptom

  • Ingest stalls. Terminal window shows stalled prompt to log into iBootBar while attempting power cycle

Possible Causes

  • Windows telnet client conflict

Troubleshooting

Instructions from Denny Hackel email 2021-07-21

The interferometer_cycle.py script was getting stuck when the software would strike out. I tried to use the script manually in python and it wasn’t able to login.

I turned on the Windows Telnet Client by doing these steps.
– Click Start
– Select Control Panel
– Choose Programs and Features.
– Click Turn Windows features on or off.
– Select the Telnet Client option.
– Click OK. A dialog box appears to confirm installation.

Then opened a cmd.exe terminal and ran “telnet 169.254.44.254”. It automatically logged in and ran some commands. I am really not sure what it was doing but it set groups and stuff. Running “telnet 169.254.44.254” again from the command prompt brought up the “User Name” prompt. So it appears something needed to be initialized. After this I tried the interferometer_cycle.py script and it worked.

I turned the Windows Telnet Client off and the interferometer_cycle.py script still works.

More information on when interferometer_cycle.py script gets run.
The AERI ingest software does have safeguards to reconnect and if needed, attempt to cycle software and hardware to automatically correct it. The “go.sh” script is responsible for starting all the AERI software on computer startup. When the FTSW software loses contact with the interferometer “go.sh” tries to start data collection 4 times, separated by 90 seconds, before immediately rebooting the computer. Each time the computer reboots a strike file is created. After the first reboot the script will try to start data collection another 4 times followed by waiting 5 minutes before rebooting the computer a second time. After the second reboot “go.sh” will try to start data collection another 4 times and then wait 15 minutes before rebooting the computer for a third time. After the third reboot and another 4 times trying to start data collection the software gives up until a manual reboot or daily restart. If at any time during the day the ingest software dies, due to interferometer failure or otherwise, it should pick up where it left off in this cycle. Sometimes a full power cycle of all the hardware helps.