Hi Mahmood,
I had the same problem some time ago when I took control of the cluster and
wanted to update the OS. While the login node has access to internet, the
calculation nodes are connected to the login node and is a private network.
Therefore, the only machine with access to the internet was
This is very likely by design of the cluster and/or network. Otherwise
users could use the cluster to mine bitcoin and such.
Brian Andrus
On 8/2/2020 7:11 AM, Mahmood Naderan wrote:
I thought that maybe srun doesn't transfer all settings from the head
node to the compute node.
The wget comman
I thought that maybe srun doesn't transfer all settings from the head node
to the compute node.
The wget command works on frontend but doesn't work on the compute.
mahmood@main-proxy:~$ wget google.com
--2020-08-02 16:05:55-- http://google.com/
Resolving google.com (google.com)... 216.58.215.238,
Probably unrelated to slurm entirely, and most likely has to do with
lower-level network diagnostics. I can guarantee that it’s possible to access
Internet resources from a compute node. Notes and things to check:
1. Both ping and http/https are IP protocols, but are very different (ping
isn’t
Hi
A frontend machine is connected to the internet and from that machine, I
use srun to get a bash on another node. But it seems that the node is
unable to access the internet. The http_proxy and https_proxy are defined
in ~/.bashrc
mahmood@main-proxy:~$ ping google.com
PING google.com (216.58.215
