This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
operations:starting_eremotectrl [2016/05/23 23:40] Warren Hankey |
operations:starting_eremotectrl [2016/07/30 01:21] Ellen Manning |
||
---|---|---|---|
Line 13: | Line 13: | ||
**Troubleshooting** | **Troubleshooting** | ||
+ | |||
+ | Common problems that cause E-remote to not respond include: | ||
+ | |||
+ | * E-remote is no longer connecting to the field system computer. Anything but a green rectangle in the bottom right hand corner of e-remote is bad. | ||
+ | * The field system computer is no longer connected to the internet. Check this by pinging pcfs[hb|ke|yg] (or just opening a VNC session). | ||
+ | * The field system has crashed. VNC into pcfs[hb|ke|yg] and make sure the field system software is running. If not, start it by entering <code> fs </code> into an empty terminal. You will have to restart the setup procedure. | ||
+ | * It's just decided to have a fit, in which case simply closing the e-remote session and re-opening it may fix it. If the field system has been running the whole time and the problem is with the e-remote software only, you will NOT have to restart the entire setup procedure as the schedule should have been running the whole time. | ||
+ | |||
If you still don't see any status window updates the server process may need re-starting. Exit from e-remote control, open a terminal in the VNC session on pcfs[hb|ke|yg] and type | If you still don't see any status window updates the server process may need re-starting. Exit from e-remote control, open a terminal in the VNC session on pcfs[hb|ke|yg] and type |