Thanks. It turns out that not all program use $http_proxy in bashrc. For pip, which I had problem I had to use "pip --proxy http://somewhere install pkg".
So, there is not problem with srun. Hope that it helps other too. Regards, Mahmood On Mon, Aug 3, 2020 at 7:28 PM Matthew BETTINGER < matthew.bettin...@external.total.com> wrote: > Hello, > > Not sure what your setup is but check compute nodes route table. Also > might need to turn on ipv4 forwarding on whatever is their default gw. > Then also firewalls can come in to play too. This isn't a slurm issue , > pretty sure! > > Matt > > On 8/2/20, 7:53 AM, "slurm-users on behalf of Mahmood Naderan" < > slurm-users-boun...@lists.schedmd.com on behalf of mahmood...@gmail.com> > wrote: > > 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 > > > I guess that is related to slurm and srun. > Any idea for that? > > > > > > > > > Regards, > Mahmood > > > >
