Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
breakout [2018/12/27 09:40] beckmanf [Running long jobs] |
breakout [2020/10/05 15:20] dke update system summary |
||
|---|---|---|---|
| Line 11: | Line 11: | ||
| * Intel X540-T2 10GB Base-T Ethernet Netzwerkanschluss | * Intel X540-T2 10GB Base-T Ethernet Netzwerkanschluss | ||
| * 4 x NVIDIA Geforce GTX 1080 mit GP104 Pascal, 2560 Cores, 8 GB RAM | * 4 x NVIDIA Geforce GTX 1080 mit GP104 Pascal, 2560 Cores, 8 GB RAM | ||
| - | * Debian Linux Jessie, NVIDIA Cuda, Torch | + | * Debian Linux Jessie |
| - | * NVidia Treiber 410.78 | + | * NVidia Treiber 450.80.02 |
| - | * Kernel 3.16.51-3 | + | * Kernel 4.9.0-13 |
| - | * Cuda 10 | + | * Cuda 10, Cuda 8 |
| + | * Tensorflow, Torch | ||
| + | * Docker 19.03.13, Nvidia-docker | ||
| ===== Nutzungshinweise ===== | ===== Nutzungshinweise ===== | ||
| Line 150: | Line 152: | ||
| </code> | </code> | ||
| - | Now you can start a program. You can leave the tmux session (and the program) running when you type CTRL-b d. This will detach you from the tmux session. Then you can logout from you ssh session and keep everything running on the breakout. The you can login to breakout via ssh again. You can reattach to tmux with | + | Now you can start a program. You can leave the tmux session (and the program) running when you type CTRL-b d. This will detach you from the tmux session. Then you can logout from you ssh session and keep everything running on the breakout. Then you can login to breakout via ssh again. You can reattach to tmux with |
| <code> | <code> | ||
| Line 156: | Line 158: | ||
| </code> | </code> | ||
| - | Then you should see the output from your running program. | + | You should see the output from your running program. |
| === kerberos - keep your file system alive === | === kerberos - keep your file system alive === | ||
| Line 226: | Line 228: | ||
| == Start a job with automatic kerberos ticket renew == | == Start a job with automatic kerberos ticket renew == | ||
| - | You can do the ticket renew process automatically. When you start a job with "krenew", then your existing kerberos ticket will be copied to a new ticket cache location and the renew process is automatically done until the renew time expires or the job is done. To start the example from pytorch imagenet training, this would be done like this: | + | You can do the ticket renew process automatically. When you start a job with "krenew", then your existing kerberos ticket will be copied to a new ticket cache location and the renew process is automatically done until the renew time expires or the job is done. The ticket cache is copied because the kerberos cache that you received at login (here: /tmp/krb5cc_12487_ssddef) will be deleted at logout. To start the example from pytorch imagenet training, this would be done like this: |
| <code> | <code> | ||
| Line 232: | Line 234: | ||
| </code> | </code> | ||
| - | If you do this inside a tmux session, then you detach and logout. The job will run for up to seven days. | + | If you do this inside a tmux session, then you can detach and logout. The job will run for up to seven days. When you login later you can check the status of the jobs kerberos ticket again with klist. You have to provide the filename of the jobs ticket cache. |
| + | |||
| + | <code> | ||
| + | klist /tmp/krb5cc_12487_ftXjk0 | ||
| + | </code> | ||
| + | |||
| + | In my example the new cache name from krenew was /tmp/krb5cc_12487_ftXjk0. | ||
| + | |||
| + | == Login via Public Key Authentication == | ||
| + | |||
| + | When you login via Public Key Authentication, then you do not receive a new kerberos ticket. If you do not have a valid kerberos ticket, then you cannot access "$HOME/.ssh/authorized_keys" and you are falling back to default password login and receive a new kerberos ticket. If you did the login via Public Key, then your "klist" will not show any kerberos ticket because that is active from some other login session. However you can still run "kinit" and receive a new kerberos ticket. That will be stored in the default kerberos ticket cache location at "/tmp/krb5cc_<uid>". | ||
| ==== PyTorch ==== | ==== PyTorch ==== | ||
| Line 324: | Line 336: | ||
| </code> | </code> | ||
| - | The training takes about 5 days on the breakout. Refer to "Running long jobs" to see how you can run that long jobs on the breakout. | + | The training takes about 5 days on the breakout. Refer to [[#Running long jobs]] to see how you can run that long jobs on the breakout. |
| ==== Bauingenieure - Photoscan ==== | ==== Bauingenieure - Photoscan ==== | ||