- About our server
- General rules
- Connect to CHMI linux server via SSH
- Transfer files to/from our linux server via SFTP
- Connecting to the PennVet Storage server from our Linux
- Understanding Linux permissions
- Helpful command line tips
About our server
The CHMI server is a Linux machine running Ubuntu 22.04.1. It has 512Gb of RAM, a 2Tb internal hard drive, and two 6-core Intel Xeon E5-2643v4 CPUs (total of 12 CPU cores). Additional hard drive storage is accessible through a hot-swap bay in the front of the computer and includes two 20Tb drives (mounted as
/rome) and an 20Tb RAID1 arrayed hard drive (mounted as
/venice) – in total 60Tb of storage are available. Software available on this machine changes from time to time, but you can always view a relatively up-to-date listing of informatics tools we have installed here. In addition to this software, we also host RStudio Server Pro on this machine, which allows anyone with an account on the server to run RStudio in their browser with full access to this machine's compute capabilities. We also have Geneious Prime installed and accessible remotely through a desktop sharing protocol.
Use of the server is free-of-charge to approved PennVet labs. However, to protect the machine from abuse and prevent issues with storage, we have a few rules all users must follow. Failure to adhere to these rules will result in a warning. Additional violations will result in suspension of your account. Here are the rules:
- We will set-up your account and install any software you may need. Please do not install software yourself unless you’ve cleared it with me (Dan Beiting) first. You can find a full list of of all the software installed system-wide here.
- In addition to your home account which is located at
/home/usernameon the server, you will also be given a data folder that is located on
/turin/username. All data must be stored in this directory not your
- Data storage space is limited (60Tb goes quickly!), so we periodically monitor storage space and may request that data not currently in use be moved off the server.
- Please be courteous and clean up after yourself. Delete files that aren't needed (e.g. .gz/.tar/.zip files that have been uncompressed).
- We require a strong password for each account. We will set this password for you, and ask that you do not change it. Please do not share this password with anyone outside of your lab. If you need to send this password to a lab mate, please do so using a secure method. We use password pusher for this.
- We are not responsible for backing up your raw data or analysis scripts and files. You should use the PennVet storage server for secure backup (contact PennVet IT for more info).
Connect to CHMI linux server via SSH
In Sept 2020, UPenn began prohibiting all SSH connections through its firewall. As a result, you will need to first use UPenn's GlobalProtect VPN client. Once connected to the VPN (requires your PennKey and password), then you will be able to use SSH to connect to our server (requires your server username and password). Here's how you can connect to the VPN:
- Open your browser and navigate to UPenn's VPN client. You'll be prompted to download GlobalProtect for your computer (you'll only need to do this once).
- Once installed and launched, you should see a small globe icon in your toolbar. Click the globe icon, paste vpn.upenn.edu and click 'connect'.
- You'll be directed back to your browser to authenticate with your PennKey and password. Once connected to the VPN, you can SSH to our server as indicated below.
# connect by entering the line below in your terminal or bash program. Replace 'username' with your username ssh email@example.com
Transfer files to/from our linux server via SFTP
As above with SSH, this will only work if you are connected to UPenn's VPN. There are many ways to transfer files between your local computer and our linux server. We recommend using a file transfer protocol (FTP) client, and find that the FileZilla Client is a good choice because it is free and easy to use.
Connecting to the PennVet Storage server from our Linux
Our Linux server is for computing, not for storage. It is the responsibility of each user (that's you!) to make sure you have your data securely backed-up.
We strongly recommend that you use the PennVet Storage Server, which provides archival tape-based backup of data for PennVet labs. If your lab does not have an account on the storage server, please contact your PI and have them work with PennVet IT support to get this set up. Once set-up you can easily connect to the PennVet Storage Server from our linux.
To move data from our Linux server to the storage server you will either need to be sitting at our Linux, or you will need to contact Dan Beiting to gain access to the Linux via our remote desktop connection service. It is also possible to connect via CLI.
Once connected to (or sitting in front of) our Linux, follow the 4 steps shown in the screenshot below to connect to smb://fileserver.vet.upenn.edu/groups$/
Once you've connected, you'll be asked to enter your credentials and click connect again. See screenshot below:
If you entered the correct credentials, you will see the PennVet Storage Server connection listed on the left-hand side of your file browser. Click on this and you'll see your lab folder(s) displayed (screenshot below). You should now be able to drag files from our Linux to your lab's storage! Transfer time can be lengthy and will depend on how much data you're trying to move.
Understanding Linux permissions
If you're trying to do something to a file or folder on the linux (e.g., delete, move, edit, create) and are unable to, chances are you need to modify the permissions (
chmod), the owner (
chown) or the group (
chgrp). See below and read more about permissions here. You can also use this handy webtool for translating your permissions settings to the correct ‘octals’.
Helpful command line tips
If you’re new to the command-line in Linux, there are lots of online resoures for learning, but here are a few of the commands that will help you move around and carry out basic tasks. Note that many of these may only work if run as
Also, check out this github page for a really awesome list of modern unix tools (each tool requires download and installation if you're not working on our Linux). In particular, dust, lsd and broot are all awesome.
|typing this at the prompt||does this|
ctrl + r (on a Mac)
allows you to search your terminal for previous commands…just start typing
unzip a .tar file
standard would be
list all files and folders in your working diretory with info on permissions
standard would be
lists all files and folders in your working directory sorted by size
standard would be
simpler version of the command above. lists all files in a folder and shows their file size
standard would be
view free/used disk space by drive
counts ALL files in a directory
counts ONLY files in a directory that are of a certain type (in this example, .sam files)
shows only the most recently modified file or directory in your current working directory
group files in directory by file type (extension)
lists all files and folders in your working directory as a tree structure
lists drives and their size (as well as used/free space on each)
pressing up arrow
recalls previous command
takes you to the root directory
takes you to your home directory
takes you up one level in your file directory
takes you up two levels in your file directory
edits permissions on file
makes you the owner of a file
assigns you as the group for the file
removes a folder and all of its contents
downloads a file from a website
show all hidden files in the finder (Mac only)
lists all the python packages (and their versions) installed on the server
opens up the system profile where new program paths can be added to the system PATH
add a new piece of software to the system PATH so it is executable from anywhere
add lines like this to your ~/.bash_profile to create a keyboard shortcut, in this case typing 'something' actually does 'something else'
displays the progress of file manipulation jobs (e.g. from cp, mv, etc)
locates the binary, source, and manual page files for a command.
Micro is a text editor built right into the terminal. You can call ‘micro’ and any text file by name to open and edit that file. Micro is particularly nice since it has some of the ease of. use you are probably arelady familiar with for stand-alone text editors. User-specific customization of micro’s settings can be done by modifying the config file that lives at /home/[USERNAME]/.config/micro/settings.json