You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/userguides/negishi/faqs.md
+46-47Lines changed: 46 additions & 47 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ Negishi differs from the previous Community Clusters in several significant aspe
29
29
* GCC compiler with OpenMPI or MVAPICH2 MPI libraries are recommended for software development on Negishi. You can enable this software with `module load gcc openmpi` (default) or `module load gcc mvapich2`.
30
30
* If you use Jupyter notebooks, JupyterHub on Negishi will be available only via the [OnDemand Gateway](https://gateway.negishi.rcac.purdue.edu) rather than the freestanding version as on some previous systems. Other RCAC systems will transition to OnDemand as well, following Negishi.
31
31
32
-
#### Upcoming 2023
32
+
**Starting from 2023**
33
33
34
34
* A subset of Negishi compute nodes contain AMD Radeon Instinct MI210 accelerator cards which can significantly improve performance of compute-intensive workloads. These can be utilized by submitting jobs to the `gpu` queue (add `-A gpu` to your job submission command).
35
35
* A selection of GPU-enabled ROCm application containers from the AMD InfinityHub collection is installed.
@@ -51,13 +51,13 @@ If you plan to use `hsi` or `htar` commands to access Fortress tape archive from
51
51
52
52
### /usr/bin/xauth: error in locking authority file
53
53
54
-
#### Problem
54
+
**Problem**
55
55
56
56
I receive this message when logging in:
57
57
58
58
`/usr/bin/xauth: error in locking authority file`
59
59
60
-
#### Solution
60
+
**Solution**
61
61
62
62
Your home directory disk quota is full. You may check your quota with `myquota`.
63
63
@@ -76,11 +76,11 @@ There are several common locations that tend to grow large over time and are mer
76
76
77
77
### My SSH connection hangs
78
78
79
-
#### Problem
79
+
**Problem**
80
80
81
81
Your console hangs while trying to connect to a RCAC Server.
82
82
83
-
#### Solution
83
+
**Solution**
84
84
85
85
This can happen due to various reasons. Most common reasons for hanging SSH terminals are:
86
86
@@ -92,101 +92,101 @@ If neither of the suggestions above work, please [contact support](https://www.r
92
92
93
93
### ThinLinc session frozen
94
94
95
-
#### Problem
95
+
**Problem**
96
96
97
97
Your ThinLinc session is frozen and you can not launch any commands or close the session.
98
98
99
-
#### Solution
99
+
**Solution**
100
100
101
101
This can happen due to various reasons. The most common reason is that you ran something memory-intensive inside that ThinLinc session on a front-end, so parts of the ThinLinc session got killed by Cgroups, and the entire session got stuck.
102
102
103
103
***If you are using a web-version ThinLinc remote desktop (inside the browser):**
104
104
105
-
The web version does not have the capability to kill the existing session, only the standalone client does. Please install the standalone client and follow the steps below:
105
+
The web version does not have the capability to kill the existing session, only the standalone client does. Please install the standalone client and follow the steps below:
106
106
107
-
[ThinLinc](accounts.md#thinlinc)
107
+
[ThinLinc](accounts.md#thinlinc)
108
108
109
109
***If you are using a ThinLinc client:**
110
110
111
-
Close the ThinLinc client, reopen the client login popup, and select `End existing session`.
111
+
Close the ThinLinc client, reopen the client login popup, and select `End existing session`.
Select "End existing session" and try "Connect" again.
118
118
119
119
### ThinLinc session unreachable
120
120
121
-
#### Problem
121
+
**Problem**
122
122
123
123
When trying to login to ThinLinc and re-connect to your existing session, you receive an error *"Your ThinLinc session is currently unreachable"*.
124
124
125
-
#### Solution
125
+
**Solution**
126
126
127
127
This can happen if the specific login node your existing remote desktop session was residing on is currently offline or down, so ThinLinc can not reconnect to your existing session. Most often the session is non-recoverable at this point, so the solution is to terminate your existing ThinLinc desktop session and start a new one.
128
128
129
129
***If you are using a web-version ThinLinc remote desktop (inside the browser):**
130
130
131
-
The web version does not have the capability to kill the existing session, only the standalone client does. Please install the standalone client and follow the steps below:
131
+
The web version does not have the capability to kill the existing session, only the standalone client does. Please install the standalone client and follow the steps below:
132
132
133
-
[ThinLinc](accounts.md#thinlinc)
133
+
[ThinLinc](accounts.md#thinlinc)
134
134
135
135
***If you are using a ThinLinc client:**
136
136
137
-
Close the ThinLinc client, reopen the client login popup, and select `End existing session`.
137
+
Close the ThinLinc client, reopen the client login popup, and select `End existing session`.
Select "End existing session" and try "Connect" again.
143
+
Select "End existing session" and try "Connect" again.
144
144
145
145
### How to disable ThinLinc screensaver
146
146
147
-
#### Problem
147
+
**Problem**
148
148
149
149
Your ThinLinc desktop is locked after being idle for a while, and it asks for a password to refresh it. It means the "screensaver" and "lock screen" functions are turned on, but you want to disable these functions.
150
150
151
-
#### Solution
151
+
**Solution**
152
152
153
153
If your screen is locked, close the ThinLinc client, reopen the client login popup, and select `End existing session`.
Under "Lock Screen" tab, turn off the "Enable Lock Screen" option.
182
182
183
183
### I worked on Negishi after I graduated/left Purdue, but can not access it anymore
184
184
185
-
#### Problem
185
+
**Problem**
186
186
187
187
You have graduated or left Purdue but continue collaboration with your Purdue colleagues. You find that your access to Purdue resources has suddenly stopped and your password is no longer accepted.
188
188
189
-
#### Solution
189
+
**Solution**
190
190
191
191
Access to all resources depends on having a valid Purdue Career Account. Expired Career Accounts are removed twice a year, during Spring and October breaks (more details at the [official page](https://www.purdue.edu/apps/account/IAMO/Purdue_CareerAccount_Expiration.jsp)). If your Career Account was purged due to expiration, you will not be be able to access the resources.
192
192
@@ -201,48 +201,47 @@ After your R4P is completed and Career Account is restored, please note two addi
201
201
202
202
### cannot connect to X server / cannot open display
203
203
204
-
#### Problem
204
+
**Problem**
205
205
206
206
You receive the following message after entering a command to bring up a graphical window
207
207
208
208
`cannot connect to X server``cannot open display`
209
209
210
-
#### Solution
210
+
**Solution**
211
211
212
212
This can happen due to multiple reasons:
213
213
214
214
1. Reason: Your SSH client software does not support graphical display by itself (e.g. SecureCRT or PuTTY).
215
-
* Solution: Try using a client software like ThinLinc or MobaXterm as described in the [SSH X11 Forwarding guide](accounts.md#ssh-x11-forwarding).
216
-
2. Reason: You did not enable X11 forwarding in your SSH connection.
217
-
218
-
* Solution: If you are in a Windows environment, make sure that X11 forwarding is enabled in your connection settings (e.g. in MobaXterm or PuTTY). If you are in a Linux environment, try
215
+
* Solution: Try using a client software like ThinLinc or MobaXterm as described in the [SSH X11 Forwarding guide](accounts.md#ssh-x11-forwarding).
219
216
220
-
`ssh -Y -l username hostname`
217
+
2. Reason: You did not enable X11 forwarding in your SSH connection.
218
+
* Solution: If you are in a Windows environment, make sure that X11 forwarding is enabled in your connection settings (e.g. in MobaXterm or PuTTY). If you are in a Linux environment, try `ssh -Y -l username hostname`
221
219
222
220
3. Reason: If you are trying to open a graphical window within an interactive PBS job, make sure you are using the `-X` option with `qsub` after following the previous step(s) for connecting to the front-end. Please see the example in the [Interactive Jobs guide](../run_jobs/interactive_jobs).
221
+
223
222
4. Reason: If none of the above apply, make sure that you are [within quota of your home directory](#usrbinxauth-error-in-locking-authority-file).
224
223
225
224
### bash: command not found
226
225
227
-
#### Problem
226
+
**Problem**
228
227
229
228
You receive the following message after typing a command
230
229
231
230
`bash: command not found`
232
231
233
-
#### Solution
232
+
**Solution**
234
233
235
234
This means the system doesn't know how to find your command. Typically, you need to load a module to do it.
236
235
237
236
### bash: module command not found
238
237
239
-
#### Problem
238
+
**Problem**
240
239
241
240
You receive the following message after typing a command, e.g. module load intel
242
241
243
242
`bash: module command not found`
244
243
245
-
#### Solution
244
+
**Solution**
246
245
247
246
The system cannot find the module command. You need to source the modules.sh file as below
248
247
@@ -264,15 +263,15 @@ or
264
263
265
264
* You can learn about processor layout on Negishi nodes using the following command:
* Please note that NUMA information is useful for advanced MPI/OpenMP/GPU optimizations. For most users, using default NUMA settings in MPI or OpenMP would give you the best performance.
0 commit comments