| ... | ... | @@ -164,6 +164,8 @@ nds_query -n <nds server here > -k |
|
|
|
|
|
|
|
If it fails all the time, it may be a proxy issue, restart the nds-proxy service on nds-1 (or nds.ligo).
|
|
|
|
|
|
|
|
Check access from outside of the cluster and inside (at lho/llo use nds-1 as the server name in the above query for internal access from the head nodes). If you can access nds2 data from only one side (inside/outside of the cluster) then it is a proxy issue.
|
|
|
|
|
|
|
|
If it fails part of the time it may be a node behind the proxy having issues, check the nds2-io-node processes on nds-2 & nds-3 (or the nds2 process on nds.ligo and nds-alt.ligo). Restart those if needed.
|
|
|
|
|
|
|
|
#### Simple live data check
|
| ... | ... | |
