None of these should apply in 2011 and on. If they do, they should be added to the troubleshooting page.
And lots of other lines… This error occurs when the cluster has been updated since you last logged on. You need to remove a file and create a new one. In a terminal window, type:
>rm ~/.ssh/known_hosts >OnRenderNodes uptime
>rm ~/.ssh/known_hosts >sh -c 'for node in r1 r2 r3 r4 r5 ; do ssh -o StrictHostKeyChecking=no $node true ; done'
If you use OnRenderNodes uptime, the computer will ask you “Are you sure you want to continue connecting (yes/no)?” Answer yes each time. Then you should be able to run applications again. You can have this problem for a new account as well ( New account and post-upgrade ssh problem). To fix that, start with OnRenderNodes uptime and answer yes to the “Are you sure…” questions or use the for node in… command.
For example: Caught exception Viewer: Head device “Head2” not found while initializing Vrui state object
This error was caused by a setting in the Vrui.config file, which sets up the environment. The program did not find the head tracking device called “Head2” because it was no longer installed in the CAVES. If you get an error related to “initializing Vrui state object” you might want to look for Vrui configuration problems.
This will be a problem with inconsistent terminology in VRUI configuration files. Prior to VRUI 1.0-068, the configuration file contained sections called “DesktopTools”, “CAVETools”, etc. depending on the hardware environment. With build 68, the section was renamed just “Tools”. Older applications and some custom configuration files, might not have been updated to this new convention. To solve this problem, you need to make sure the configuration file sections are consistently named.