|
Size: 3804
Comment: Import and modifications from SIM to COMP
|
Size: 3256
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| <<TableOfContents()>> <<Anchor(missinglibs)>> = Missing Libraries on An alamode Machine = Occasionally, you will login to an `alamode` machine and some course provided code will fail to run due some '''very bizarre''' reasons {{{ bb136-12$ ~khellman/COMPGRADING/aenorm /usr/lib/libc.so: No such file or directory }}} Of course, `libc.so` is there: {{{ bb136-12$ file /usr/lib/libc.so /usr/lib/libc.so.6 /usr/lib/libc.so: ASCII text /usr/lib/libc.so.6: symbolic link to libc-2.31.so }}} This seems to be resolved by '''using a different''' `alamode` machine. `bb136-12` won't be fixed until it gets a reboot :( |
/* DO NOT EDIT THIS FILE! moinconfig/cspages/AlamodeAccessCaveatsAndWarnings! */ |
| Line 36: | Line 21: |
| remote$ ssh -J jumpbox.mines.edu bb136-13.mines.edu | remote$ ssh -J jumpbox.mines.edu ctb60-13.mines.edu |
| Line 38: | Line 23: |
| 1. Now is the right time to setup some off-campus aliases in your `remote` machine to make life easier. Pick some `alamode` machine names (let's say you use `bb136-13`, `bb136-19`, and `bb136-07`); everyone seems to have favorite remote login destinations, but for the life of me I don't know why... | 1. Now is the right time to setup some off-campus aliases in your `remote` machine to make life easier. Pick some `alamode` machine names (let's say you use `ctb60-13`, `ctb60-19`, and `ctb60-07`); everyone seems to have favorite remote login destinations, but for the life of me I don't know why... |
| Line 43: | Line 28: |
| HostName bb136-13.mines.edu | HostName ctb60-13.mines.edu |
| Line 48: | Line 33: |
| Hostname bb136-13.mines.edu | Hostname ctb60-13.mines.edu |
| Line 56: | Line 41: |
| And connect directly to `bb136-13.mines.edu`, but possibly with a password required. | And connect directly to `ctb60-13.mines.edu`, but possibly with a password required. |
| Line 64: | Line 49: |
| bb136-13$ mkdir ~/.ssh bb136-13$ chmod 700 ~/.ssh bb136-13$ cat remote.pub >> ~/.ssh/authorized_keys bb136-13$ chmod 700 ~/.ssh/authorized_keys |
ctb60-13$ mkdir ~/.ssh ctb60-13$ chmod 700 ~/.ssh ctb60-13$ cat remote.pub >> ~/.ssh/authorized_keys ctb60-13$ chmod 700 ~/.ssh/authorized_keys |
| Line 72: | Line 57: |
| bb136-13.mines.edu | ctb60-13.mines.edu |
| Line 88: | Line 73: |
| remote-with-vpn$ ssh -X bb136-13.mines.edu bb136-13$ gview output-1010.pdf |
remote-with-vpn$ ssh -X ctb60-13.mines.edu ctb60-13$ gview output-1010.pdf |
| Line 94: | Line 79: |
| remote$ ssh -J jumpbox.mines.edu -X bb136-17.mines.edu bb136-17$ evince output-1010.pdf |
remote$ ssh -J jumpbox.mines.edu -X ctb60-17.mines.edu ctb60-17$ evince output-1010.pdf |
Ugh, Too Many Passwords for alamode ssh Access
If you don't use Mines VPN software, then ssh(1) is your best bet:
First, setup ~/.ssh/authorized_keys properly on your jumpbox.mines.edu account
remote$ scp ~/.ssh/id_rsa.pub MINESLOGIN@jumpbox.mines.edu:./remote.pub remote$ ssh MINESLOGIN@jumpbox.mines.edu : : jumpbox$ mkdir ~/.ssh jumpbox$ chmod 700 ~/.ssh jumpbox$ cat remote.pub >> ~/.ssh/authorized_keys jumpbox$ chmod 700 ~/.ssh/authorized_keys
Now you should be able to "bunny hop" through jumpbox to an alamode machine, if you don't have an authorized_keys setup on alamode yet, you are down to just one password... Test:
remote$ ssh -J jumpbox.mines.edu ctb60-13.mines.edu
Now is the right time to setup some off-campus aliases in your remote machine to make life easier. Pick some alamode machine names (let's say you use ctb60-13, ctb60-19, and ctb60-07); everyone seems to have favorite remote login destinations, but for the life of me I don't know why... For each machine, add the following lines to your ~/.ssh/config file on your personal (remote) machine, adjusted of course for the machine names you've settled on.
# on campus alias Host 13bb HostName ctb60-13.mines.edu User MINESLOGIN # off campus sweetness Host bb13 Hostname ctb60-13.mines.edu ProxyJump jumpbox.mines.edu User MINESLOGIN
Now, from remote which is off campus and not on the Mines VPN, you should be able to do
remote$ ssh bb13
And connect directly to ctb60-13.mines.edu, but possibly with a password required.
If you were asked for a password, then setup authorized_keys in a manner analogous to that on jumpbox (notice how I'm using the ssh just configured in the previous step):
remote$ scp ~/.ssh/id_rsa.pub bb13:./remote.pub remote$ ssh bb13 : : ctb60-13$ mkdir ~/.ssh ctb60-13$ chmod 700 ~/.ssh ctb60-13$ cat remote.pub >> ~/.ssh/authorized_keys ctb60-13$ chmod 700 ~/.ssh/authorized_keys
Since your ${HOME} is shared across all alamode machines, you have to do this on just one alamode destination. Test!
remote$ ssh bb13 'hostname; echo Woot\!' ctb60-13.mines.edu Woot! remote$
You're welcome.
Grrr, I can't see the PDFs generated by grader.sh
Use a PDF viewer installed on the alamode images. Some examples include gview or evince; but xpdf is by the far the fastest.
$ xpdf output-1010.pdf
If you are ssh(1)ing into alamode, use the -X option.
remote-with-vpn$ ssh -X ctb60-13.mines.edu ctb60-13$ gview output-1010.pdf
This even works if you bunny hop through jumpbox
remote$ ssh -J jumpbox.mines.edu -X ctb60-17.mines.edu ctb60-17$ evince output-1010.pdf
Beware the VSCode IDE installed on alamode (Fall 2018)
The integrated terminal in the VSCode has been shown to be whacky when running Python code. If you choose to use this IDE, you are strongly advised to use a separate terminal window to test your SIM.