Squiggles research computer server - Revision history

Vahab: /* Troubleshooting */

2025-04-21T15:23:24Z

Troubleshooting

← Older revision		Revision as of 15:23, 21 April 2025
Line 135:		Line 135:
	;'''Terminating a VNC Session'''		;'''Terminating a VNC Session'''
	:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:		:For situations where session termination is necessary, you can directly close a VNC session through the terminal or opt for manual termination if the direct method is insufficient. To directly terminate a session, use:
	:<code>vncserver -kill :xx</code>		:<code>vncserver -kill :##</code>
	:Replace <code>:xx</code> with your session number.		:Replace <code>:##</code> with your session number.

	;'''Manual Termination of the VNC'''		;'''Manual Termination of the VNC'''
	:For manual termination, proceed to remove the session files with:		:For manual termination, proceed to remove the session files with:
	:<code>rm -f /tmp/.~~Xxx~~-lock</code>		:<code>rm -f /tmp/.X##-lock</code>
	:<code>rm -f /tmp/.X11-unix/~~Xxx~~</code>		:<code>rm -f /tmp/.X11-unix/X##</code>
	:Ensure to replace <code>~~Xxx~~</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.		:Ensure to replace <code>X##</code> with the correct session identifier. This allows for removing stuck or unresponsive sessions that cannot be closed normally.

	;'''Alternative Solution: when Manual Termination of the VNC does not work'''		;'''Alternative Solution: when Manual Termination of the VNC does not work'''

Vahab: /* Troubleshooting */

2025-04-21T15:21:23Z

Troubleshooting

← Older revision		Revision as of 15:21, 21 April 2025
Line 154:		Line 154:
	:<code>cat ~/vnc.log</code>		:<code>cat ~/vnc.log</code>

	;'''VNC ~~Black Screen Issue~~'''		;'''VNC connection‑closed / black‑screen issue'''
	:~~If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python~~ environment ~~interfering~~ with the session. ~~To resolve this issue, deactivate Anaconda Python using the command~~:		:Anaconda’s base environment can interfere with VNC and close the session.
			:Deactivate it after login:
	:<code>conda deactivate</code>		:<code>conda deactivate</code>
	~~:You can run the command twice. Also,~~ you ~~can~~ run ~~this command to check if~~ conda ~~has been deactivated properly~~:
	:<code>~~which python~~</code>		;'''Disable Conda auto‑activation (so you don’t have to run <code>conda deactivate</code> each time)'''
	~~:Alternatively, modify your `~~~/.~~bashrc` script~~, ~~for example, using:~~		:If you seldom need Conda inside VNC, turn off automatic activation:
	:<code>~~nano~~ ~/.bashrc</code>		:* Run <code>conda config --set auto_activate_base false</code> (this updates <code>~/.condarc</code>), or
	~~:and~~ comment out the line ~~starting with~~ <code>~~export PATH=/.../miniconda ..~~</code>.		:* Edit <code>~/.bashrc</code> and comment out / delete the line that calls <code>conda activate base</code>.
	:~~Disconnect~~ and ~~reconnect to squiggles through ssh~~, ~~run `~~conda ~~deactivate`, and then start a new VNC session.~~		:After logging out and back in, Conda will stay inactive by default; activate it later with <code>conda activate <env></code> only when needed.
	~~:You can also adjust the startup file. Here's an example modification to include in your `.vnc~~/~~xstartup` script:~~
	~~<pre style="margin-left: 20px;"~~>
	~~#!/bin/sh~~

	~~unset SESSION_MANAGER~~
	~~unset DBUS_SESSION_BUS_ADDRESS~~
	~~# exec /etc/X11/xinit/xinitrc~~

	~~gnome-session~~
	</pre>		</pre>

Vahab: /* Login to Squiggles */

2025-04-04T21:42:34Z

← Older revision		Revision as of 21:42, 4 April 2025
Line 74:		Line 74:
	\|Priyanka Shah		\|Priyanka Shah
	\|5929		\|5929
			\|-
			\|Setayesh Abiazi Shalmani
			\|5930
	\|-		\|-
	\|Vahab Youssof Zadeh		\|Vahab Youssof Zadeh

Vahab: /* Troubleshooting */

2024-05-17T17:56:25Z

Troubleshooting

@@ Line 125: / Line 125: @@
 === Troubleshooting ===
 ;'''Identifying Active Users'''
 :To compile a list of users with active VNC sessions, which aids in monitoring current access to the VNC service, execute:
@@ Line 180: / Line 149: @@
 :Optional: To check the environment variables active during a VNC session, which can help in troubleshooting further issues, view the VNC environment log:
-:<code>cat ~/vnc_environment.log</code>
+:<code>cat ~/vnc.log</code>

Vahab: /* SSH Tunneling */

2024-05-17T17:52:03Z

SSH Tunneling

@@ Line 9: / Line 9: @@
 * If prompted, select "others" and then "squiggles" to specify the server you wish to access.
 * Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.
 === Login to Squiggles ===

Vahab: /* Login to Squiggles */

2024-05-17T17:50:16Z

← Older revision		Revision as of 17:50, 17 May 2024
Line 9:		Line 9:
	* If prompted, select "others" and then "squiggles" to specify the server you wish to access.		* If prompted, select "others" and then "squiggles" to specify the server you wish to access.
	* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.		* Account approval generally takes 1-3 days. For any issues, contact Help-RCC at <help-rcc@mcw.edu>.

			===== SSH Tunneling =====
			* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:
			<code>ssh -L 59##:localhost:59## USER@squiggles.rcc.mcw.edu</code>
			where USER is your rcc user account and ## is the selected port number

			* '''PuTTY (Windows):'''
			[https://www.chiark.greenend.org.uk/~sgtatham/putty/ Download PuTTY] for SSH tunneling and refer to the images below for configuration:

			PuTTY is an open-source software used for SSH Tunneling (or SSH Port Forwarding).

			[[File:Putty config1.PNG]]
			[[File:Putty config2 tunnel.PNG]]

	=== Login to Squiggles ===		=== Login to Squiggles ===
Line 19:		Line 32:
	\|-		\|-
	\|Jeff Stout		\|Jeff Stout
	\|5910,5911		\|5910, 5911
	\|-		\|-
	\|Joe Heffernan		\|Joe Heffernan
	\|5912		\|5912
			\|-
			\|Manoj Raghavan
			\|5913, 5998, 5999
	\|-		\|-
	\|Candida Ustine		\|Candida Ustine
	\|5914		\|5914
	\|-
	~~\|Manoj Raghavan~~
	~~\|5913~~
	\|-		\|-
	\|Chad Carlson		\|Chad Carlson
Line 81:		Line 94:
	\|5935		\|5935
	\|-		\|-
	\|Cameron J Stewart		\|Rupesh Chikara
			\|5944
			\|-
			\|Cameron J Stewart
	\|5992		\|5992
	\|-
	~~\|Rupesh Chikara~~
	~~\|5944~~
	\|}		\|}

	===== SSH Tunneling =====		===== SSH Tunneling =====
	* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:		* '''PowerShell Method (Mac/Linux/Windows):''' In a bash shell, terminal, or Windows PowerShell, execute the following to set up an SSH tunnel for the VNC Viewer:

Vahab: /* Login to Squiggles */

2024-05-17T17:45:10Z

← Older revision		Revision as of 17:45, 17 May 2024
Line 75:		Line 75:
	\|5929		\|5929
	\|-		\|-
	\|Vahab ~~Youssofzadeh~~		\|Vahab Youssof Zadeh
	\|5931		\|5931
	\|-		\|-

Vahab: /* Login to Squiggles */

2024-05-17T17:44:49Z

← Older revision		Revision as of 17:44, 17 May 2024
Line 83:		Line 83:
	\|Cameron J Stewart		\|Cameron J Stewart
	\|5992		\|5992
			\|-
	\|Rupesh Chikara		\|Rupesh Chikara
	\|5944		\|5944

Vahab: /* Login to Squiggles */

2024-05-17T17:44:19Z

← Older revision		Revision as of 17:44, 17 May 2024
Line 83:		Line 83:
	\|Cameron J Stewart		\|Cameron J Stewart
	\|5992		\|5992
			\|Rupesh Chikara
			\|5944
	\|}		\|}
	===== SSH Tunneling =====		===== SSH Tunneling =====

Vahab: /* Troubleshooting */

2024-05-17T17:43:48Z

Troubleshooting

← Older revision		Revision as of 17:43, 17 May 2024
Line 125:		Line 125:
	:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:		:If you encounter a black screen after logging into VNC, it could be due to the Anaconda Python environment interfering with the session. To resolve this issue, deactivate Anaconda Python using the command:
	:<code>conda deactivate</code>		:<code>conda deactivate</code>
	~~:Alternativey, modify your `.vnc/xstartup` script e.g., using,~~

	:~~<code>nano ~/~~.~~vnc/xstartupc</code>~~		:You can run the command twice. Also, you can run this command,

	:to ~~adjust~~ the `PATH` and deactivate ~~Conda before starting~~ the ~~desktop environment~~. Here's an example modification to include in your `.vnc/xstartup` script:		:<code>which python</code>

			:to check it conda has been deactivated properly.

			:Alternativey, modify your `~/.bashrc` script e.g., using,

			:<code>nano ~/.bashrc</code>

			:and comment out the line starting with, <code>export PATH=/.../miniconda ..</code>

			:disconnect and reconnect to squiggles through ssh, run conda deactivate, and then start a new vnc session

			:You can also adjust the startup file. Here's an example modification to include in your `.vnc/xstartup` script:

	<pre style="margin-left: 20px;">		<pre style="margin-left: 20px;">