[Lerftest-ctrls] Internet access from jlabl1.jlab.org
Sonya Hoobler
sonya at slac.stanford.edu
Mon Oct 22 13:38:31 EDT 2018
Hi Hugo,
> 1 - Could not even ping rhel6-64
Yes, I think this probably caused me to investigate the wrong issue.
> 2 - Typo at the jlabl1 host... I always miss the "l" before the 1.
I did not have a typo. (I'm very aware of that pesky "l".)
Still, my original problem was that I suddenly had this error while
performing cvs operations:
ssh: connect to host localhost port 8888: Connection refused
I exited all programs and login sessions, logged back in, and tried again.
I also tried another port but the behavior was the same. So I think
something was wrong.
I'll get in touch if it happens again.
Thanks again for your help, Hugo and Wesley!
Sonya
On Mon, 22 Oct 2018, Slepicka, Hugo Henrique wrote:
> Hi Sonya,
>
> In my case at least I had two issues:
>
> 1 - Could not even ping rhel6-64
> 2 - Typo at the jlabl1 host... I always miss the "l" before the 1.
>
> Cheers,
> Hugo
>
> On 10/22/18, 10:29 AM, "Sonya Hoobler" <sonya at slac.stanford.edu> wrote:
>
> Hi Hugo, Wesley,
>
> Yes, it is now working, thanks.
>
> Do we understand why it wasn't working before? I am not doing anything
> differently now.
>
> Thanks,
> Sonya
>
>
> On Mon, 22 Oct 2018, Slepicka, Hugo Henrique wrote:
>
> > Hi Wesley,
> >
> > I am sorry for the issue..
> > It was really a typo in my case?
> > Now all seems to be working properly.
> > I can establish my ssh tunnel and ssh into rhel6-64?
> > Everything should be back to work.
> >
> > Sonya, make sure to create your tunnel.
> > Here is mine as an example:
> >
> > ssh -fNT -L 6660:rhel6-64.slac.stanford.edu:22 slepicka at jlabl1.jlab.org
> >
> > After that you can ssh into rhel6 to test with:
> > ssh -p 6660 slepicka at localhost
> >
> > Cheers,
> > Hugo
> >
> > From: Wesley Moore <wmoore at jlab.org>
> > Date: Monday, October 22, 2018 at 9:29 AM
> > To: "Slepicka, Hugo Henrique" <slepicka at slac.stanford.edu>
> > Cc: "Hoobler, Sonya" <sonya at slac.stanford.edu>, "lerftest-ctrls at jlab.org" <lerftest-ctrls at jlab.org>, "Williams Jr., Ernest L." <ernesto at slac.stanford.edu>, "Pascual, Patrick James" <ppascual at slac.stanford.edu>
> > Subject: Re: [Lerftest-ctrls] Internet access from jlabl1.jlab.org
> >
> > Email typo? You mean jlabl1, not jlab1 right?
> >
> > Wesley
> > ________________________________
> > From: Slepicka, Hugo Henrique <slepicka at slac.stanford.edu>
> > Sent: Monday, October 22, 2018 12:12:07 PM
> > To: Wesley Moore
> > Cc: Hoobler, Sonya; lerftest-ctrls at jlab.org; Williams Jr., Ernest L.; Pascual, Patrick James
> > Subject: Re: [Lerftest-ctrls] Internet access from jlabl1.jlab.org
> >
> > Hi Wesley,
> >
> > The issue that I noticed is that we can?t establish the tunnel now using jlab1... the process stops into connecting to jlab1.
> > Looks like we lost access to that machine with our SLAC accounts?
> >
> > Hugo
> > Sent from my iPhone
> >
> > On Oct 22, 2018, at 9:07 AM, Wesley Moore <wmoore at jlab.org<mailto:wmoore at jlab.org>> wrote:
> >
> > It looks like your tunnels to jlabl1 aren't setup (connection refused to localhost:8888). From jlabl#, ssh to slac is working fine even though ping is blocked at the FW.
> >
> >
> >
> > # Example:
> > wmoore at jlabl5.jlab.org<mailto:wmoore at jlabl5.jlab.org>> ssh rhel6-64.slac.stanford.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__rhel6-2D64.slac.stanford.edu&d=DwMGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=ciUk5UntV_Tki6hcVr3CdQ&m=A_eZkbrZ9w0Y9wMuBoOMOwlslN8CKBQLarMfkeV4cQM&s=8lNA5kwWPUCZe9xd4PJkzqiYn_o5CfehhAIcI-pTj0I&e=>
> > The authenticity of host 'rhel6-64.slac.stanford.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__rhel6-2D64.slac.stanford.edu&d=DwMGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=ciUk5UntV_Tki6hcVr3CdQ&m=A_eZkbrZ9w0Y9wMuBoOMOwlslN8CKBQLarMfkeV4cQM&s=8lNA5kwWPUCZe9xd4PJkzqiYn_o5CfehhAIcI-pTj0I&e=> (134.79.120.162)' can't be established.
> > RSA key fingerprint is SHA256:WVLfceuj9hUJCUZ21mWVx7OBKGH9IelGkdmvzvHjjcQ.
> > RSA key fingerprint is MD5:82:61:15:e9:36:3c:88:b0:7a:6e:2b:c2:2a:cc:5d:de.
> > Are you sure you want to continue connecting (yes/no)? yes
> > Warning: Permanently added 'rhel6-64.slac.stanford.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__rhel6-2D64.slac.stanford.edu&d=DwMGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=ciUk5UntV_Tki6hcVr3CdQ&m=A_eZkbrZ9w0Y9wMuBoOMOwlslN8CKBQLarMfkeV4cQM&s=8lNA5kwWPUCZe9xd4PJkzqiYn_o5CfehhAIcI-pTj0I&e=>,134.79.120.162' (RSA) to the list of known hosts.
> > wmoore at rhel6-64.slac.stanford.edu<mailto:wmoore at rhel6-64.slac.stanford.edu>'s password:
> >
> > Wesley
> > ________________________________
> > From: Sonya Hoobler <sonya at slac.stanford.edu<mailto:sonya at slac.stanford.edu>>
> > Sent: Monday, October 22, 2018 11:58:41 AM
> > To: Wesley Moore
> > Cc: Slepicka, Hugo Henrique; lerftest-ctrls at jlab.org<mailto:lerftest-ctrls at jlab.org>; Williams Jr., Ernest L.; Pascual, Patrick James
> > Subject: Re: [Lerftest-ctrls] Internet access from jlabl1.jlab.org<http://jlabl1.jlab.org>
> >
> > Great, thank you.
> >
> > Sonya
> >
> >
> > On Mon, 22 Oct 2018, Wesley Moore wrote:
> >
> >> Not yet. Actively working on it though.
> >>
> >>
> >> Wesley
> >>
> >> ________________________________
> >> From: Sonya Hoobler <sonya at slac.stanford.edu<mailto:sonya at slac.stanford.edu>>
> >> Sent: Monday, October 22, 2018 11:43:13 AM
> >> To: Slepicka, Hugo Henrique
> >> Cc: Wesley Moore; lerftest-ctrls at jlab.org<mailto:lerftest-ctrls at jlab.org>; Williams Jr., Ernest L.; Pascual, Patrick James
> >> Subject: Re: [Lerftest-ctrls] Internet access from jlabl1.jlab.org<http://jlabl1.jlab.org>
> >>
> >> Hi Wesley,
> >>
> >> Any news on this?
> >>
> >> Thanks,
> >> Sonya
> >>
> >>
> >> On Fri, 19 Oct 2018, Sonya Hoobler wrote:
> >>
> >>> Thanks for looking into it, Hugo.
> >>>
> >>> I'll wait to hear from Wesley.
> >>>
> >>> Sonya
> >>>
> >>>
> >>> On Fri, 19 Oct 2018, Slepicka, Hugo Henrique wrote:
> >>>
> >>>> Hi Wesley and Sonya,
> >>>>
> >>>> I just tried from home and rhel6-64.slac.stanford.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__rhel6-2D64.slac.stanford.edu&d=DwMGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=ciUk5UntV_Tki6hcVr3CdQ&m=A_eZkbrZ9w0Y9wMuBoOMOwlslN8CKBQLarMfkeV4cQM&s=8lNA5kwWPUCZe9xd4PJkzqiYn_o5CfehhAIcI-pTj0I&e=> can be reached with
> >>>> no problems from my internet connection in here.
> >>>> slepicka at TID-PC94483:~ $ ping rhel6-64.slac.stanford.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__rhel6-2D64.slac.stanford.edu&d=DwMGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=ciUk5UntV_Tki6hcVr3CdQ&m=A_eZkbrZ9w0Y9wMuBoOMOwlslN8CKBQLarMfkeV4cQM&s=8lNA5kwWPUCZe9xd4PJkzqiYn_o5CfehhAIcI-pTj0I&e=>
> >>>> PING rhel6-64e.slac.stanford.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__rhel6-2D64e.slac.stanford.edu&d=DwMGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=ciUk5UntV_Tki6hcVr3CdQ&m=A_eZkbrZ9w0Y9wMuBoOMOwlslN8CKBQLarMfkeV4cQM&s=Z0DoNsGm_Vgm4A_Cy8C3dt7fD0wJ-Im-pLtF4z6G49k&e=> (134.79.120.159): 56 data bytes
> >>>> 64 bytes from 134.79.120.159: icmp_seq=0 ttl=52 time=17.301 ms
> >>>> 64 bytes from 134.79.120.159: icmp_seq=1 ttl=52 time=18.111 ms
> >>>> 64 bytes from 134.79.120.159: icmp_seq=2 ttl=52 time=14.991 ms
> >>>> 64 bytes from 134.79.120.159: icmp_seq=3 ttl=52 time=14.401 ms
> >>>> 64 bytes from 134.79.120.159: icmp_seq=4 ttl=52 time=13.660 ms
> >>>> ^C
> >>>> --- rhel6-64e.slac.stanford.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__rhel6-2D64e.slac.stanford.edu&d=DwMGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=ciUk5UntV_Tki6hcVr3CdQ&m=A_eZkbrZ9w0Y9wMuBoOMOwlslN8CKBQLarMfkeV4cQM&s=Z0DoNsGm_Vgm4A_Cy8C3dt7fD0wJ-Im-pLtF4z6G49k&e=> ping statistics ---
> >>>> 5 packets transmitted, 5 packets received, 0.0% packet loss
> >>>> round-trip min/avg/max/stddev = 13.660/15.693/18.111/1.716 ms
> >>>>
> >>>> Some weird issues are back to the VDI machine... If I try from the VDI
> >>>> machine to ssh as softegr into lclsapp1 I asks me for my password again.
> >>>> That happened in the past but it was fixed.
> >>>> If I go through a regular SSH connection to hallgw and from there to
> >>>> lclsapp1 as softegr the SSH works...
> >>>>
> >>>> Once I am connected to the JLab system (lclsapp1) I can't establish my SSH
> >>>> Tunnel as before:
> >>>>
> >>>> [softegr at lclsapp1 slepicka]$ ssh -fNT -v -L
> >>>> 6660:rhel6-64.slac.stanford.edu:22<https://urldefense.proofpoint.com/v2/url?u=http-3A__rhel6-2D64.slac.stanford.edu-3A22&d=DwMGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=ciUk5UntV_Tki6hcVr3CdQ&m=A_eZkbrZ9w0Y9wMuBoOMOwlslN8CKBQLarMfkeV4cQM&s=0BpM6bkXNfAuDum4lsm77SktvGJ24pWNo2_eyB3J9Hw&e=> slepicka at jlab1.jlab.org<mailto:slepicka at jlab1.jlab.org>
> >>>> OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013
> >>>> debug1: Reading configuration data /etc/ssh/ssh_config
> >>>> debug1: Applying options for *
> >>>> debug1: Connecting to jlab1.jlab.org<http://jlab1.jlab.org> [192.70.245.101] port 22.
> >>>>
> >>>> If I try to ping jlab1.jlab.org<http://jlab1.jlab.org> it fails.
> >>>>
> >>>> @Wesley did something change on the JLab network?
> >>>>
> >>>> Cheers,
> >>>> Hugo
> >>>>
> >>>>
> >>>> On 10/18/18, 6:05 PM, "Lerftest-ctrls on behalf of Slepicka, Hugo Henrique"
> >>>> <lerftest-ctrls-bounces at jlab.org<mailto:lerftest-ctrls-bounces at jlab.org> on behalf of slepicka at slac.stanford.edu<mailto:slepicka at slac.stanford.edu>>
> >>>> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> I will take a look at that and get back to you later tonight.
> >>>>
> >>>> Cheers,
> >>>> Hugo
> >>>>
> >>>> Sent from my iPhone
> >>>>
> >>>> > On Oct 18, 2018, at 5:52 PM, Wesley Moore <wmoore at jlab.org<mailto:wmoore at jlab.org>> wrote:
> >>>> >
> >>>> > Looks more like an issue with an ssh tunnel you guys setup. Does that
> >>>> ring a bell?
> >>>> >
> >>>> > Wesley
> >>>> >
> >>>> > On 10/18/18, 8:44 PM, "Sonya Hoobler" <sonya at slac.stanford.edu<mailto:sonya at slac.stanford.edu>> wrote:
> >>>> >
> >>>> > Okay, my image was too large and is holding up the submission.
> >>>> >
> >>>> > The test was:
> >>>> >
> >>>> > cd /usr/local/lcls/tools/edm/display/llrf
> >>>> > cvs stat rf_ampset_diag.edl
> >>>> >
> >>>> > But I have to leave work now, so I'll have to come back to this
> >>>> tomorrow.
> >>>> > Thanks for your help so late!
> >>>> >
> >>>> > Sonya
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> >> On Thu, 18 Oct 2018, Sonya Hoobler wrote:
> >>>> >>
> >>>> >> Yes, I've attached a screenshot of an example command (can't
> >>>> copy/paste).
> >>>> >>
> >>>> >> I could use scp as a temporary solution if we can get access between
> >>>> jlabl1
> >>>> >> and rhel6-64.slac.stanford.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__rhel6-2D64.slac.stanford.edu&d=DwMGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=ciUk5UntV_Tki6hcVr3CdQ&m=A_eZkbrZ9w0Y9wMuBoOMOwlslN8CKBQLarMfkeV4cQM&s=8lNA5kwWPUCZe9xd4PJkzqiYn_o5CfehhAIcI-pTj0I&e=> (which we used to have, right?
> >>>> checking my
> >>>> >> memory).
> >>>> >>
> >>>> >> Thanks,
> >>>> >> Sonya
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >>
> >>>> >>> On Fri, 19 Oct 2018, Wesley Moore wrote:
> >>>> >>>
> >>>> >>> Can you send me a cvs and git command to try? I'll see what the
> >>>> network
> >>>> >>> traffic looks like to see if that well highlight the issue.
> >>>> >>>
> >>>> >>> Wesley
> >>>> >>>
> >>>> >>> On 10/18/18, 8:13 PM, "Sonya Hoobler" <sonya at slac.stanford.edu<mailto:sonya at slac.stanford.edu>>
> >>>> wrote:
> >>>> >>>
> >>>> >>> Hmm, I seem to be able to ping the world (google, FNAL) from my
> >>>> SLAC
> >>>> >>> machine (using rhel6-64c.slac.stanford.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__rhel6-2D64c.slac.stanford.edu&d=DwMGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=ciUk5UntV_Tki6hcVr3CdQ&m=A_eZkbrZ9w0Y9wMuBoOMOwlslN8CKBQLarMfkeV4cQM&s=8gPC4_CMRmGFwnz6Sf_i4Ruod-UBqFNbCLt0TWfYKn0&e=> at the moment) but
> >>>> cannot
> >>>> >>> ping
> >>>> >>> rhel6-64c from jlabl1.
> >>>> >>>
> >>>> >>> Do you have a favorite domain to ping or other test I should run
> >>>> from
> >>>> >>> jlabl1.jlab.org<http://jlabl1.jlab.org>?
> >>>> >>>
> >>>> >>> Thanks,
> >>>> >>> Sonya
> >>>> >>>
> >>>> >>>
> >>>> >>>> On Fri, 19 Oct 2018, Wesley Moore wrote:
> >>>> >>>>
> >>>> >>>> It looks to be proxied. So it should work from the lcls hosts
> >>>> also.
> >>>> >>> I'll have to see it there's something special required for cvs/git,
> >>>> but I
> >>>> >>> know git works through the proxy. Possible issue on the slac side
> >>>> (maybe
> >>>> >>> not open to the world)?
> >>>> >>>>
> >>>> >>>> Wesley
> >>>> >>>>
> >>>> >>>> On 10/18/18, 8:01 PM, "Sonya Hoobler" <sonya at slac.stanford.edu<mailto:sonya at slac.stanford.edu>>
> >>>> wrote:
> >>>> >>>>
> >>>> >>>> Hi Wesley,
> >>>> >>>>
> >>>> >>>> If I remember correctly, jlabl1.jlab.org<http://jlabl1.jlab.org> (and friends) should
> >>>> have
> >>>> >>>> internet access, but it does not seem to currently. For example,
> >>>> I
> >>>> >>> am
> >>>> >>>> unable to ping rhel6-64.slac.stanford.edu<https://urldefense.proofpoint.com/v2/url?u=http-3A__rhel6-2D64.slac.stanford.edu&d=DwMGaQ&c=lz9TcOasaINaaC3U7FbMev2lsutwpI4--09aP8Lu18s&r=ciUk5UntV_Tki6hcVr3CdQ&m=A_eZkbrZ9w0Y9wMuBoOMOwlslN8CKBQLarMfkeV4cQM&s=8lNA5kwWPUCZe9xd4PJkzqiYn_o5CfehhAIcI-pTj0I&e=>. (I also suspect this
> >>>> is
> >>>> >>> why
> >>>> >>>> remote cvs/git is not currently working.)
> >>>> >>>>
> >>>> >>>> Should I be using a different server?
> >>>> >>>>
> >>>> >>>> Thanks,
> >>>> >>>> Sonya
> >>>> >>>>
> >>>> >>>>
> >>>> >>>>
> >>>> >>>>
> >>>> >>>
> >>>> >>
> >>>> >
> >>>> >
> >>>> > _______________________________________________
> >>>> > Mailing List: Lerftest-ctrls at jlab.org<mailto:Lerftest-ctrls at jlab.org>
> >>>> > https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
> >>>> > Wiki: https://wiki.jlab.org/lerf/index.php/Network
> >>>>
> >>>> _______________________________________________
> >>>> Mailing List: Lerftest-ctrls at jlab.org<mailto:Lerftest-ctrls at jlab.org>
> >>>> https://mailman.jlab.org/mailman/listinfo/lerftest-ctrls
> >>>> Wiki: https://wiki.jlab.org/lerf/index.php/Network
> >>>>
> >>>>
> >>>
> >>
> >
>
>
>
More information about the Lerftest-ctrls
mailing list