![]() Remove the *.pid files for broken sessions in your ` $HOME/.vnc` directory and kill any associated processes associated with those sessions, visible under ` ps -u ` at the command line.Select Kill server, highlight the broken session, and hit Ok.Remove any broken/dead sessions that are still listed as options under your session listing.If you are seeing the error message "Failure to connect to server - check session logs for details" after trying to Start server, you will want to check your session listing to see if a new session has been added since running Start server and then try to manually connect to that session: A common error we're seeing is that users will sometimes fail to automatically connect to a newly created session, though the session is created.ssh'ing to our VNC servers (czvnc, rzvnc, scfvnc) will allow you to see if your login files produce output/error messages there.For example, `module` commands like ` module load` will not work on our VNC servers.cshrc, etc.) do not produce error messages on our VNC servers. ![]() Check that your home directory usage is under quota. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |