<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://giwiki.gi.ucsc.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Tkell</id>
	<title>UCSC Genomics Institute Computing Infrastructure Information - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://giwiki.gi.ucsc.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Tkell"/>
	<link rel="alternate" type="text/html" href="http://giwiki.gi.ucsc.edu/index.php?title=Special:Contributions/Tkell"/>
	<updated>2026-06-10T06:20:42Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.40.0</generator>
	<entry>
		<id>http://giwiki.gi.ucsc.edu/index.php?title=Slurm_Best_Practices&amp;diff=809</id>
		<title>Slurm Best Practices</title>
		<link rel="alternate" type="text/html" href="http://giwiki.gi.ucsc.edu/index.php?title=Slurm_Best_Practices&amp;diff=809"/>
		<updated>2026-06-02T20:45:17Z</updated>

		<summary type="html">&lt;p&gt;Tkell: /* Slurm Interactive Sessions */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
PLEASE READ THIS CAREFULLY!  It will guide you on how to best use Slurm to get your work done as efficiently as possible without causing issues for other users.&lt;br /&gt;
&lt;br /&gt;
== Test Your Jobs! ==&lt;br /&gt;
&lt;br /&gt;
This is the number one thing to remember.  Test your job batch by running one or two jobs by themselves first and check how long it takes to run, how much memory and CPU it needs, and how much disk I/O it needs.  Ask for more resources than you think you need, but when the job ends, use '''seff &amp;lt;job_id&amp;gt;''' to see how much CPU, RAM, time, etc the job used.  Then when you schedule more of that same type of job, you can better know how much, in terms of resources, to ask for.  '''THIS IS VERY IMPORTANT'''.  When you ask for resources, Slurm pins those resources and no one else can use them.  So, you need to know how much your job will use before launching a bunch of them.  Don't just use a co-worker's script they gave you and run it blindly.  '''UNDERSTAND''' what the script does and how it works!!  Failure to understand how a script someone gave you works can crash the cluster and grind operations to a halt.&lt;br /&gt;
&lt;br /&gt;
== Disk I/O ==&lt;br /&gt;
&lt;br /&gt;
Also of critical importance is making sure your jobs are not overrunning disk I/O on our shared filesystems, especially '''/private/groups'''.  If your jobs read the same data in more than once, it is often a good idea to copy your data, as part of your job script, to /data/tmp/ first, then your job can read that data locally on each node very fast, then be sure to delete the data at the end of your job script so others can use the space.&lt;br /&gt;
&lt;br /&gt;
To clarify, '''/data/tmp''' exists ''on each cluster node''.  Do not copy your data to /data/tmp on the login nodes (mustard, emerald, crimson and razzmatazz).  Have your slurm batch script copy the data to '''/data/tmp''' as part of the job workflow, and it will get copied to '''/data/tmp''' on whatever node the job is scheduled to run on.&lt;br /&gt;
&lt;br /&gt;
You can also watch to see if your jobs create a massive spike in filesystem bandwidth by watching the Grafana filesystem bandwidth page:&lt;br /&gt;
&lt;br /&gt;
http://grafana.prism/d/d545805a-843b-4f75-8efe-f2a4510d9d98/phoenix-cluster-aggregate-statistics?orgId=1&amp;amp;refresh=1m&lt;br /&gt;
&lt;br /&gt;
 username: guest&lt;br /&gt;
 password: MoreStats4me&lt;br /&gt;
&lt;br /&gt;
If you see a big spike in read and/or write bandwidth right as your job starts, then you are probably using a very large amount of filesystem I/O and may want to consider running fewer concurrent jobs.&lt;br /&gt;
&lt;br /&gt;
== Limit Number of Concurrent Jobs ==&lt;br /&gt;
&lt;br /&gt;
It is almost always good to limit the number of concurrent jobs that Slurm will run at once from your batch.  If your batch has 100 jobs, and you just launch it without limits, Slurm will try to run them all at once, or, if the queue if full, it will try to run them as soon as it can.  This can often lead to:&lt;br /&gt;
&lt;br /&gt;
 1: Pushing other jobs aside&lt;br /&gt;
 2: Creating excessive disk and network I/O&lt;br /&gt;
 3: Forcing other jobs in the queue to wait for long periods of time to start&lt;br /&gt;
&lt;br /&gt;
In the case of 100 jobs, you can utilize the '''--array''' parameter to limit the maximum number of jobs to run concurrently, as such (in your batch script, for example:&lt;br /&gt;
&lt;br /&gt;
 #SBATCH --array=0-99%10&lt;br /&gt;
&lt;br /&gt;
That indicates that of your 100 jobs, they will be assigned task ID numbers of 0-99, and it will only allow 10 of them to run at once.  You can also use this option on the command line if launching via '''sbatch''' on the command line or similar using '''--array=0-99%10''' as an argument to '''sbatch''' on the command line.&lt;br /&gt;
&lt;br /&gt;
Remember that the cluster is a shared resource, and everyone needs to have relatively equal time on it - as much as possible.&lt;br /&gt;
&lt;br /&gt;
== Job Prioritization ==&lt;br /&gt;
&lt;br /&gt;
Each queued job has a priority score. Jobs start when sufficient resources (CPUs, GPUs, memory, licenses) are available and not already reserved for jobs with a higher priority.&lt;br /&gt;
&lt;br /&gt;
To see the priorities of your currently pending jobs you can use the command '''sprio -u $USER'''.&lt;br /&gt;
&lt;br /&gt;
'''Job Age'''&lt;br /&gt;
&lt;br /&gt;
Job priority slowly rises with time as a pending job gets older -1 point per hour for up to 3 weeks.&lt;br /&gt;
&lt;br /&gt;
'''Job Size or &amp;quot;TRES&amp;quot; (Trackable RESources)'''&lt;br /&gt;
&lt;br /&gt;
This slightly favors jobs which request a larger count of CPUs (or memory or GPUs) as a means of countering their otherwise inherently longer wait times.&lt;br /&gt;
&lt;br /&gt;
Whole-node jobs and others with a similarly high count of cores-per-node will get a priority boost (visible in the “site factor” of sprio). This is to help whole-node jobs get ahead of large distributed jobs with many tasks spread over many nodes.&lt;br /&gt;
&lt;br /&gt;
'''Nice values'''&lt;br /&gt;
&lt;br /&gt;
It is possible to give a job a &amp;quot;nice&amp;quot; value which is subtracted from its priority. You can do that with the --nice option of sbatch or the scontrol update command. The command scontrol top &amp;lt;jobid&amp;gt; adjusts nice values to increase the priority of one of your jobs at the expense of any others you have in the same partition.&lt;br /&gt;
&lt;br /&gt;
'''Holds'''&lt;br /&gt;
&lt;br /&gt;
Jobs with a priority of 0 are in a &amp;quot;held&amp;quot; state and will never start without further intervention. You can hold jobs with the command scontrol hold &amp;lt;jobid&amp;gt; and release them with scontrol release &amp;lt;jobid&amp;gt;. Jobs can also end up in this state when they get requeued after a node failure.&lt;br /&gt;
&lt;br /&gt;
== Slurm Interactive Sessions ==&lt;br /&gt;
&lt;br /&gt;
A SLURM interactive session reserves resources on compute nodes allowing you to use them interactively as you would the login nodes. Interactive sessions are limited to a maximum time of 5 hours.&lt;br /&gt;
&lt;br /&gt;
'''WARNING''': An interactive session will, once it starts, use the entire requested block of CPU time and other resources unless earlier exited, even if unused. Don't forget to exit an interactive session once finished.  And also, VERY important to remember, don't start an interactive session with the maximum available walltime just to pin the node for yourself so your jobs don't have to wait in the queue.  This is extremely bad etiquette, and people often notice when idle interactive sessions exist and complain about it.  '''Just don't do it.'''  If you have a need for an interactive session, launch it, run your code and then exit as soon as you are done.&lt;br /&gt;
&lt;br /&gt;
There are two main commands that can be used to make a session, '''srun''' and '''salloc''', both of which use most of the same options available to '''sbatch'''.&lt;br /&gt;
&lt;br /&gt;
'''Using srun --pty bash'''&lt;br /&gt;
&lt;br /&gt;
srun will add your resource request to the queue. When the allocation starts, a new bash session will start up on one of the granted nodes.&lt;br /&gt;
&lt;br /&gt;
For example;&lt;br /&gt;
&lt;br /&gt;
 srun --job-name &amp;quot;InteractiveJob&amp;quot; --cpus-per-task 8 --mem-per-cpu 1500 --time 24:00:00 --pty bash&lt;br /&gt;
&lt;br /&gt;
You will receive a message.&lt;br /&gt;
 srun: job 10256812 queued and waiting for resources&lt;br /&gt;
And when the job starts:&lt;br /&gt;
 srun: job 10256812 has been allocated resources&lt;br /&gt;
&lt;br /&gt;
For a full description of srun and its options, see the schedmd documentation.&lt;br /&gt;
&lt;br /&gt;
'''Using salloc'''&lt;br /&gt;
&lt;br /&gt;
salloc functions similarly '''srun --pty bash''' in that it will add your resource request to the queue. However the allocation starts, a new bash session will start up on the login node. This is useful for running a GUI on the login node, but your processes on the compute nodes.&lt;br /&gt;
&lt;br /&gt;
For example:&lt;br /&gt;
 salloc --job-name &amp;quot;InteractiveJob&amp;quot; --cpus-per-task 8 --mem-per-cpu 1500 --time 24:00:00&lt;br /&gt;
You will receive a message.&lt;br /&gt;
 salloc: Pending job allocation 10256925&lt;br /&gt;
 salloc: job 10256925 queued and waiting for resources&lt;br /&gt;
And when the job starts;&lt;br /&gt;
 salloc: job 10256925 has been allocated resources&lt;br /&gt;
 salloc: Granted job allocation 10256925 &lt;br /&gt;
Note the that you are still on the login node mustard or emerald, however you will now have permission to ssh to any node you have a session on.&lt;/div&gt;</summary>
		<author><name>Tkell</name></author>
	</entry>
	<entry>
		<id>http://giwiki.gi.ucsc.edu/index.php?title=Setting_Up_The_VPN_on_MacOS&amp;diff=808</id>
		<title>Setting Up The VPN on MacOS</title>
		<link rel="alternate" type="text/html" href="http://giwiki.gi.ucsc.edu/index.php?title=Setting_Up_The_VPN_on_MacOS&amp;diff=808"/>
		<updated>2026-06-02T18:26:41Z</updated>

		<summary type="html">&lt;p&gt;Tkell: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
NOTE:  If you are installing the VPN for the first time, start here.  If you are simply reinstalling tunnelblick, or installing tunnelblick on a new computer, skip down to the section '''Installing Tunnelblick'''.&lt;br /&gt;
&lt;br /&gt;
== Make Sure Your Account Forms Have Been Submitted ==&lt;br /&gt;
&lt;br /&gt;
'''Before''' following these instructions, please ensure that you have filled out an account request form and completed all the training and requirements as detailed here:&lt;br /&gt;
&lt;br /&gt;
[[Requirement_for_users_to_get_GI_VPN_access]]&lt;br /&gt;
&lt;br /&gt;
After completing those requirements, you should have received a welcome email from us explaining that your account is ready.  Once you have received that email, continue following these instructions.  '''If you already have a VPN Account with us, you may skip this step and continue on to Installing Tunnelblick'''.&lt;br /&gt;
&lt;br /&gt;
For MacOS, you will be installing &amp;quot;Tunnelblick&amp;quot;, an OpenVPN client software package for Mac.  Do not install this software on public or shared computers!&lt;br /&gt;
&lt;br /&gt;
== Make Sure You Have Enrolled in Duo ==&lt;br /&gt;
&lt;br /&gt;
Before installing Tunnelblick, you must have enrolled your cell phone for Duo MFA using your CruzID account with UCSC.  Most folks already have this from when they first started at UCSC.  If you don't yet have a CruzID, please contact your sponsor/PI and ask them to help you acquire a CruzID.  If you have a CruzID but haven't yet enrolled your cell phone, please follow the instructions here to enroll your phone:&lt;br /&gt;
&lt;br /&gt;
 https://its.ucsc.edu/mfa/enroll.html&lt;br /&gt;
&lt;br /&gt;
After confirming your cell phone MFA enrollment, or if you have already done this a while ago, continue to install Tunnelblick.  &lt;br /&gt;
&lt;br /&gt;
== Installing Tunnelblick ==&lt;br /&gt;
&lt;br /&gt;
Download the OpenVPN configuration file we will be using.  This website is protected by CruzID, simply login using your CruzID credentials:&lt;br /&gt;
&lt;br /&gt;
 https://logserv.gi.ucsc.edu/prism-duo.ovpn&lt;br /&gt;
&lt;br /&gt;
Download that file to your Desktop by right-clicking on the link above and selecting &amp;quot;Save Link As...&amp;quot;, and save it to your Desktop or some other area you will remember.&lt;br /&gt;
&lt;br /&gt;
Next, you will need to download Tunnelblick (the latest Stable Version) from this link:&lt;br /&gt;
&lt;br /&gt;
 https://tunnelblick.net/downloads.html&lt;br /&gt;
&lt;br /&gt;
Once you have downloaded Tunnelblick, double-click on it and proceed through the installation steps.  At the end it will ask if you have any configuration files, say &amp;quot;Yes&amp;quot; and click &amp;quot;OK&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
After installation, in your Finder, you may want to navigate to the Applications folder and drag the Tunnelblick icon to your dock for easy launching.&lt;br /&gt;
&lt;br /&gt;
After launching Tunnelblick from the Applications folder, you will see a small &amp;quot;tunnel&amp;quot; icon on the top right of your screen, next to the date and WiFi icon.  Drag the configuration file ('''prism-duo.ovpn''') on your Desktop to the little Tunnelblick icon on the top right of your screen to install the new profile.  It will ask you to type in your computer password (do that).  It will also ask you if you want to install for &amp;quot;Only You&amp;quot; or &amp;quot;All Users&amp;quot;.  Select &amp;quot;Only You&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
== Login to the VPN ==&lt;br /&gt;
&lt;br /&gt;
You should be able to click on that icon again in the top right, then click &amp;quot;Connect prism-duo&amp;quot; from the resulting menu to start the VPN.  &amp;quot;Prism&amp;quot; is the name of our firewalled environment.  Use the username and temporary password that we sent to you in your account creation welcome email to login to the VPN for the first time.  After typing in your username and password, you will be sent a Duo MFA push to your phone.  Accept that push, and then you will be connected.&lt;br /&gt;
&lt;br /&gt;
Once you authenticate to the VPN (username/password/MFA), then login via SSH to 'mustard.prism' for example, and you will be asked to change your password.&lt;br /&gt;
&lt;br /&gt;
If you are not familiar with SSH, then you will need to open the &amp;quot;Terminal&amp;quot; application which can be found in your Applications Folder under &amp;quot;Utilities&amp;quot;.  After launching &amp;quot;Terminal&amp;quot; you will connect to mustard by typing:&lt;br /&gt;
&lt;br /&gt;
 ssh username@mustard.prism&lt;br /&gt;
&lt;br /&gt;
Where &amp;quot;username&amp;quot; is the username we sent you in the welcome email (incidentally it is also your CruzID username).  It will ask you for a password, just type in the password we sent you in your account creation welcome email.  When you type the password, the characters '''will not''' echo to the screen, so it will not show you what you are typing.  Once logging in successfully to mustard, it will as you to change your password (if it your first time logging in - otherwise just login as usual).  It will ask for you current password one more time, then it will ask you to choose a new password, which you will need to enter two times.  Again, whatever password you choose '''will not''' echo to the screen.  You new password must be:&lt;br /&gt;
&lt;br /&gt;
 1: At least 10 characters long&lt;br /&gt;
 2: At least 3 character classes (lowercase, uppercase, number and/or special character)&lt;br /&gt;
&lt;br /&gt;
Once you change your password, it will log you out of mustard.  '''Then, log out of the VPN''' (click the Tunnelblick icon on the top right of your screen and select &amp;quot;disconnect&amp;quot;).  This step is very important.  Then, log back into the VPN using your '''new''' password.  It will send another Duo MFA push to your phone, then you should be logged in!&lt;br /&gt;
&lt;br /&gt;
Then feel free to ssh to any of our firewalled servers (using your new password).  Note the following page for available resources:&lt;br /&gt;
&lt;br /&gt;
 https://giwiki.gi.ucsc.edu/index.php?title=Firewalled_Computing_Resources_Overview&lt;br /&gt;
&lt;br /&gt;
== Troubleshooting ==&lt;br /&gt;
&lt;br /&gt;
If you're able to connect to the VPN, but can't reach any GI resources behind the firewall, your local network settings may be interfering. &lt;br /&gt;
&lt;br /&gt;
* Try restarting your computer.&lt;br /&gt;
* Make sure you don't have any other VPN software active. &lt;br /&gt;
&lt;br /&gt;
If you are still unable to connect, try these steps:&lt;br /&gt;
&lt;br /&gt;
* Disconnect from the Tunnelblick VPN.&lt;br /&gt;
* Open System Settings &amp;gt; Wi-Fi (or Network if you're connected to a wired network connection)&lt;br /&gt;
* Find the network you're connected to and click &amp;quot;Details...&amp;quot;, then navigate to the &amp;quot;DNS&amp;quot; section&lt;br /&gt;
* Delete any DNS servers that have been manually added, such as 8.8.8.8 or 1.1.1.1.&lt;br /&gt;
* Click OK then reconnect to the VPN&lt;br /&gt;
&lt;br /&gt;
You can also enable &amp;quot;Allow changes to manually-set network settings&amp;quot; in Tunnelblick &amp;gt; Configurations &amp;gt; Advanced.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
As always, if you have any questions, please email '''cluster-admin@soe.ucsc.edu''' for help.&lt;/div&gt;</summary>
		<author><name>Tkell</name></author>
	</entry>
	<entry>
		<id>http://giwiki.gi.ucsc.edu/index.php?title=Setting_Up_The_VPN_on_MacOS&amp;diff=807</id>
		<title>Setting Up The VPN on MacOS</title>
		<link rel="alternate" type="text/html" href="http://giwiki.gi.ucsc.edu/index.php?title=Setting_Up_The_VPN_on_MacOS&amp;diff=807"/>
		<updated>2026-06-02T18:20:52Z</updated>

		<summary type="html">&lt;p&gt;Tkell: /* Installing Tunnelblick */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
NOTE:  If you are installing the VPN for the first time, start here.  If you are simply reinstalling tunnelblick, or installing tunnelblick on a new computer, skip down to the section '''Installing Tunnelblick'''.&lt;br /&gt;
&lt;br /&gt;
== Make Sure Your Account Forms Have Been Submitted ==&lt;br /&gt;
&lt;br /&gt;
'''Before''' following these instructions, please ensure that you have filled out an account request form and completed all the training and requirements as detailed here:&lt;br /&gt;
&lt;br /&gt;
[[Requirement_for_users_to_get_GI_VPN_access]]&lt;br /&gt;
&lt;br /&gt;
After completing those requirements, you should have received a welcome email from us explaining that your account is ready.  Once you have received that email, continue following these instructions.  '''If you already have a VPN Account with us, you may skip this step and continue on to Installing Tunnelblick'''.&lt;br /&gt;
&lt;br /&gt;
For MacOS, you will be installing &amp;quot;Tunnelblick&amp;quot;, an OpenVPN client software package for Mac.  Do not install this software on public or shared computers!&lt;br /&gt;
&lt;br /&gt;
== Make Sure You Have Enrolled in Duo ==&lt;br /&gt;
&lt;br /&gt;
Before installing Tunnelblick, you must have enrolled your cell phone for Duo MFA using your CruzID account with UCSC.  Most folks already have this from when they first started at UCSC.  If you don't yet have a CruzID, please contact your sponsor/PI and ask them to help you acquire a CruzID.  If you have a CruzID but haven't yet enrolled your cell phone, please follow the instructions here to enroll your phone:&lt;br /&gt;
&lt;br /&gt;
 https://its.ucsc.edu/mfa/enroll.html&lt;br /&gt;
&lt;br /&gt;
After confirming your cell phone MFA enrollment, or if you have already done this a while ago, continue to install Tunnelblick.  &lt;br /&gt;
&lt;br /&gt;
== Installing Tunnelblick ==&lt;br /&gt;
&lt;br /&gt;
Download the OpenVPN configuration file we will be using.  This website is protected by CruzID, simply login using your CruzID credentials:&lt;br /&gt;
&lt;br /&gt;
 https://logserv.gi.ucsc.edu/prism-duo.ovpn&lt;br /&gt;
&lt;br /&gt;
Download that file to your Desktop by right-clicking on the link above and selecting &amp;quot;Save Link As...&amp;quot;, and save it to your Desktop or some other area you will remember.&lt;br /&gt;
&lt;br /&gt;
Next, you will need to download Tunnelblick (the latest Stable Version) from this link:&lt;br /&gt;
&lt;br /&gt;
 https://tunnelblick.net/downloads.html&lt;br /&gt;
&lt;br /&gt;
Once you have downloaded Tunnelblick, double-click on it and proceed through the installation steps.  At the end it will ask if you have any configuration files, say &amp;quot;Yes&amp;quot; and click &amp;quot;OK&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
After installation, in your Finder, you may want to navigate to the Applications folder and drag the Tunnelblick icon to your dock for easy launching.&lt;br /&gt;
&lt;br /&gt;
After launching Tunnelblick from the Applications folder, you will see a small &amp;quot;tunnel&amp;quot; icon on the top right of your screen, next to the date and WiFi icon.  Drag the configuration file ('''prism-duo.ovpn''') on your Desktop to the little Tunnelblick icon on the top right of your screen to install the new profile.  It will ask you to type in your computer password (do that).  It will also ask you if you want to install for &amp;quot;Only You&amp;quot; or &amp;quot;All Users&amp;quot;.  Select &amp;quot;Only You&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
== Login to the VPN ==&lt;br /&gt;
&lt;br /&gt;
You should be able to click on that icon again in the top right, then click &amp;quot;Connect prism-duo&amp;quot; from the resulting menu to start the VPN.  &amp;quot;Prism&amp;quot; is the name of our firewalled environment.  Use the username and temporary password that we sent to you in your account creation welcome email to login to the VPN for the first time.  After typing in your username and password, you will be sent a Duo MFA push to your phone.  Accept that push, and then you will be connected.&lt;br /&gt;
&lt;br /&gt;
Once you authenticate to the VPN (username/password/MFA), then login via SSH to 'mustard.prism' for example, and you will be asked to change your password.&lt;br /&gt;
&lt;br /&gt;
If you are not familiar with SSH, then you will need to open the &amp;quot;Terminal&amp;quot; application which can be found in your Applications Folder under &amp;quot;Utilities&amp;quot;.  After launching &amp;quot;Terminal&amp;quot; you will connect to mustard by typing:&lt;br /&gt;
&lt;br /&gt;
 ssh username@mustard.prism&lt;br /&gt;
&lt;br /&gt;
Where &amp;quot;username&amp;quot; is the username we sent you in the welcome email (incidentally it is also your CruzID username).  It will ask you for a password, just type in the password we sent you in your account creation welcome email.  When you type the password, the characters '''will not''' echo to the screen, so it will not show you what you are typing.  Once logging in successfully to mustard, it will as you to change your password (if it your first time logging in - otherwise just login as usual).  It will ask for you current password one more time, then it will ask you to choose a new password, which you will need to enter two times.  Again, whatever password you choose '''will not''' echo to the screen.  You new password must be:&lt;br /&gt;
&lt;br /&gt;
 1: At least 10 characters long&lt;br /&gt;
 2: At least 3 character classes (lowercase, uppercase, number and/or special character)&lt;br /&gt;
&lt;br /&gt;
Once you change your password, it will log you out of mustard.  '''Then, log out of the VPN''' (click the Tunnelblick icon on the top right of your screen and select &amp;quot;disconnect&amp;quot;).  This step is very important.  Then, log back into the VPN using your '''new''' password.  It will send another Duo MFA push to your phone, then you should be logged in!&lt;br /&gt;
&lt;br /&gt;
Then feel free to ssh to any of our firewalled servers (using your new password).  Note the following page for available resources:&lt;br /&gt;
&lt;br /&gt;
 https://giwiki.gi.ucsc.edu/index.php?title=Firewalled_Computing_Resources_Overview&lt;br /&gt;
&lt;br /&gt;
As always, if you have any questions, please email '''cluster-admin@soe.ucsc.edu''' for help.&lt;/div&gt;</summary>
		<author><name>Tkell</name></author>
	</entry>
</feed>