Where stands for the process ID # listed by ps or top. If a process is obviously causing a problem, you can stop it with: kill Otherwise, once you’re logged in via a terminal, you can look at running processes with top or ps commands. It’s not quite as drastic as rebooting ALTHOUGH it will affect other users with remote sessions, so DON’T try this unless you are indeed the only person logged in (use the ps command to check): sudo /usr/sbin/service lxdm restart This will end your local session, similarly to doing ctrl-alt-backspace when at the computer. If it appears you are connecting, but the local session (that includes connecting with NoMachine, and with X2Go with the option “ connect to the local desktop”) is unresponsive or giving you trouble, you can restart the X desktop manager. If you’re having difficulties with NoMachine but it was working before, you can try restarting the NX server: sudo systemctl restart rvice MATE, KDE, GNOME, etc) if you were using “ connect to the local desktop”. With X2Go, also try a remote session (e.g. If you are not getting to the desktop screen using either McGill VPN + NoMachine or X2Go, you can try the other one. If you are not alone, best to contact the others, but you can also look at running processes with ps or one of these to see what is running: top Unfortunately, who or w don’t include everything, so you can use: ps -fp $(pgrep "x2goagent|nxnode|bash|tcsh") | egrep -v "^(root|nx)" You should however also consider that other users may be using the system, so please always check that first. The obvious thing when you don’t have ongoing computations or unsaved work is to reboot. You can now choose to reboot or troubleshoot some more. If you are able to log in, it already confirmed the system is on and your credentials are good. If it doesn’t show many lines with response times, and 100% packet loss once you stop, the system likely has to be restarted on site. You can also double check with: ping Ĭtrl-c to stop pinging. Someone probably has to go restart the system on site. There’s not much that can be done remotely in that case. If you get the error no route to host, the system is offline or unresponsive. You can then attempt to connect to your workstation: ssh -x This can cause a variety of issues, including difficulties connecting, and should be taken care of first. Once logged in, you may receive a warning if your home folder is full. Then click Open and enter your username and password. For Linux/MacOS: ssh can use the Chrome SSH extension, or PuTTY on Windows. This will tell you if the system is on and responsive, if your password works, and it allows you to restart services, your session, or even reboot the system. Possibly the most informative step is to try to login on the workstation via ssh. However, you can also quickly try a few basic steps, described here. First and foremost, you can always contact BIC IT to get help.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |