perfSONAR User Q&A and Other Discussion

[Charley Kneifel <>]

Hi Michael,

 

Screen shot attached – Click on Tput (TCP) to deselect it – then click on Tput (TCP) to select it and Firefox stops responding.  (Screenshot is from  52.0.2 (32 bit)- not ESR but I had the same problem on the Extended Support Release.  I have waited several minutes and it never recovered and I have to kill the Firefox process.

 

Doesn’t happen with Chrome

 

 

 

Here is the screenshot showing the web-console – the last line (Use of getPreventDefault() is deprecated… appears when I click on Tput (TCP)

 

 

This is the output /var/log/messages after I click the second time on Tput (TCP)

 

 

Apr 10 12:39:10 ps-node-e journal: runner INFO     35417: Posted result to https://192.168.202.88/pscheduler/tasks/451f5439-566d-445b-bc78-e71de764f474/runs/4844ba51-4a0c-444f-81d0-ef3c8b6d6a83

Apr 10 12:39:15 ps-node-e powstream[2381]: OWPControlOpen([ps-node-d]:861): Couldn't open 'control' connection to server: Connection refused

Apr 10 12:39:15 ps-node-e powstream[2381]: OWPControlOpen([ps-node-d]:861): Waiting 0.2102016 seconds before retrying

Apr 10 12:39:15 ps-node-e powstream[2381]: OWPControlOpen([ps-node-d]:861): Couldn't open 'control' connection to server: Connection refused

Apr 10 12:39:15 ps-node-e powstream[2381]: OWPControlOpen([ps-node-d]:861): Waiting 59.996879999 seconds before retrying

Apr 10 12:39:15 ps-node-e powstream[2383]: OWPControlOpen([ps-node-d]:861): Couldn't open 'control' connection to server: Connection refused

Apr 10 12:39:15 ps-node-e powstream[2383]: OWPControlOpen([ps-node-d]:861): Waiting 0.2041016 seconds before retrying

Apr 10 12:39:15 ps-node-e powstream[2383]: OWPControlOpen([ps-node-d]:861): Couldn't open 'control' connection to server: Connection refused

Apr 10 12:39:15 ps-node-e powstream[2383]: OWPControlOpen([ps-node-d]:861): Waiting 59.997068000 seconds before retrying

Apr 10 12:39:18 ps-node-e powstream[2381]: SIGTERM/SIGINT Caught: Exiting.

Apr 10 12:39:18 ps-node-e powstream[3159]: OWPControlOpen([ps-node-d]:861): Couldn't open 'control' connection to server: Connection refused

Apr 10 12:39:18 ps-node-e powstream[3159]: OWPControlOpen([ps-node-d]:861): Couldn't open 'control' connection to server: Connection refused

Apr 10 12:39:18 ps-node-e powstream[3159]: OWPControlOpen([ps-node-d]:861): Waiting 59.998906000 seconds before retrying

Apr 10 12:39:18 ps-node-e powstream[2383]: SIGTERM/SIGINT Caught: Exiting.

Apr 10 12:39:18 ps-node-e powstream[3161]: OWPControlOpen([ps-node-d]:861): Couldn't open 'control' connection to server: Connection refused

Apr 10 12:39:18 ps-node-e powstream[3161]: OWPControlOpen([ps-node-d]:861): Couldn't open 'control' connection to server: Connection refused

Apr 10 12:39:18 ps-node-e powstream[3161]: OWPControlOpen([ps-node-d]:861): Waiting 59.998335999 seconds before retrying

Apr 10 12:39:21 ps-node-e journal: runner INFO     35414: Posted result to https://192.168.202.88/pscheduler/tasks/fefcbd28-f07e-41ff-a068-faee36471560/runs/81eae058-f4cf-4f01-8f03-37df8022ff2a

Apr 10 12:39:25 ps-node-e journal: runner INFO     35416: Posted result to https://192.168.202.88/pscheduler/tasks/133bb615-2535-4911-b064-d7253e212ba8/runs/fbf9cc73-3885-485d-9767-fe44f818b9f8

Apr 10 12:39:26 ps-node-e journal: runner INFO     35413: Posted result to https://192.168.202.88/pscheduler/tasks/f2e01f92-33d6-421e-b62f-f49b5ab397ee/runs/c37909ec-c972-4517-a415-c9eb64ff9725

Apr 10 12:39:29 ps-node-e journal: runner INFO     36694: Running https://ps-node-e.kneifel.local/pscheduler/tasks/92678bbf-5009-4253-b6c9-e5f4fc48154d/runs/191ab35e-2adb-4d4f-aafc-507560b3f8c5

Apr 10 12:39:29 ps-node-e journal: runner INFO     36694: With traceroute: trace --dest ps-node-a --ip-version 4 --source 192.168.202.88

Apr 10 12:39:29 ps-node-e journal: runner INFO     36693: Running https://ps-node-e.kneifel.local/pscheduler/tasks/a33d18c7-23d9-4742-bc63-254fe1bfcaa0/runs/21fa6d7e-cba8-4c71-9b3b-f4be4755a085

Apr 10 12:39:29 ps-node-e journal: runner INFO     36693: With traceroute: trace --dest ps-node-b --ip-version 4 --source 192.168.202.88

Apr 10 12:39:29 ps-node-e journal: runner INFO     36694: Run succeeded.

Apr 10 12:39:29 ps-node-e journal: runner INFO     36693: Run succeeded.

Apr 10 12:39:32 ps-node-e journal: runner INFO     36697: Running https://ps-node-e.kneifel.local/pscheduler/tasks/7c5119e0-6ce0-42a6-8392-90c7c6438468/runs/90f673db-08e9-4051-8aea-2e2429d5fb2e

Apr 10 12:39:32 ps-node-e journal: runner INFO     36697: With ping: rtt --count 10 --dest ps-node-c --interval PT1S --ip-version 4 --source 192.168.202.88 --length 1000 --ttl 255

Apr 10 12:39:37 ps-node-e journal: runner INFO     35412: Posted result to https://192.168.202.88/pscheduler/tasks/7c27dbdf-477b-40c2-a002-85d21f9b7c05/runs/5f3ea76f-9d04-4d91-b7fd-dfc284a185f0

Apr 10 12:39:37 ps-node-e journal: runner INFO     35418: Posted result to https://192.168.202.88/pscheduler/tasks/6beccdad-a1c7-40e2-803e-9d7c53025c8c/runs/91cc5669-3294-4268-8830-d059ab70c72b

 

-----Original Message-----
From: Michael Johnson [mailto:]
Sent: Monday, April 10, 2017 11:57 AM
To: Charley Kneifel <>
Cc: Garnizov, Ivan (RRZE) <>; Andrew Lake <>;
Subject: Re: [perfsonar-user] perfSONAR 4.0rc3 now available for testing!

 

Hi Charley,

 

I've tried to reproduce this on a couple other hosts, and I'm not having any luck. Can you provide a bit more detail as to what is going on?

 

When you say your browser "hangs," or "crashes" whare are you seeing? Does it stop responding entirely? Do you see a "loading" indicator that never goes away? Does the entire browser window go away? Some other behavior?

 

If possible, could you provide the following?

- A screenshot

- A list of errors that show up if you go to Tools -> Web Developer -> Web console (if you see these, you can ignore them):

"Warning: Each child in an array or iterator should have a unique "key" prop. Check the render method of `chart1`."

OR

"Warning: Failed propType: Invalid prop `children` supplied to `ChartContainer`. Check the render method of `chart1`."

 

Do you see this in other browsers?

 

Thanks,

Michael

 

On Sat, Apr 08, 2017 at 11:52:02AM +0000, Charley Kneifel wrote:

>Hello Ivan,

> 

> 

>I am able to reliably crash my browser (Firefox ESR 52.0.2 32bit) by:

> 

> 

>Selecting test results (click on details)

> 

>In the new tab/window that pops up click on the blue Tput (TCP) selector to remove that data from the graph

> 

>click on the blue Tput (TCP) to add that data back to the graph - my browser will hang.

> 

> 

>It does not happen if I do the same thing with any of the other data elements selectors (Tput (UDP), Loss (UDP), ...)

> 

> 

>Charley

> 

> 

> 

> 

>________________________________

>From: <> on behalf of Charley Kneifel <>

>Sent: Wednesday, April 5, 2017 2:26 PM

>To: Garnizov, Ivan (RRZE); Andrew Lake;

>Subject: RE: [perfsonar-user] perfSONAR 4.0rc3 now available for testing!

> 

> 

>Hello Ivan,

> 

>Sorry for the delay – here is a screenshot (of I hope the right screen)

> 

> 

> 

>[cid:]

> 

> 

> 

>From: Garnizov, Ivan (RRZE) []

>Sent: Tuesday, April 4, 2017 9:34 AM

>To: Charley Kneifel <>; Andrew Lake <>;

>Subject: RE: [perfsonar-user] perfSONAR 4.0rc3 now available for testing!

> 

> 

> 

>Hi Charley,

> 

> 

> 

>Could you please share a snapshot of the configuration dashboard?

> 

>pS dev team will consider an option in the administrative interface to configure web_admin.conf to allow for internal addresses, but it might be too late to support you at this stage of the development.

> 

> 

> 

>Regards,

> 

>Ivan Garnizov

> 

> 

> 

>GEANT SA1T2: pS deployments GN Operations

> 

>GEANT SA2T3: pS development team

> 

>GEANT SA3T5: eduPERT team

> 

> 

> 

> 

> 

>From: > [] On Behalf Of Charley Kneifel

>Sent: Montag, 3. April 2017 23:57

>To: Andrew Lake; >

>Subject: Re: [perfsonar-user] perfSONAR 4.0rc3 now available for testing!

> 

> 

> 

>I deployed a 4.0 RC3 server last night and noticed a couple of things -

> 

> 

> 

>1) I deployed from the full ISO

> 

> 

> 

>2) Running on VMWare vSphere 5.5

> 

> 

> 

>3) ran through the full GUI install as described in the docs (http://docs.perfsonar.net/release_candidates/4.0rc3/install_centos_fullinstall.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.perfsonar.net_release-5Fcandidates_4.0rc3_install-5Fcentos-5Ffullinstall.html&d=DwMFAg&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=puiDgVtY0d9ihL712u5hZ-0qjRq1IgTNK3sSfBWM_zQ&m=SJuHhAQkD0AsUGBd7ogsWr8keOwAoitD4w7BELoDNEU&s=gBXcnJd_bOiCsGF9P_1VcVLJvKVmNq6Zf2JjdCfJzlM&e=>)

> 

> 

> 

>4) System installed and then came back up and was able to login via the VMWare console but I noticed that VM did not have a proper name.

> 

> 

> 

>I was able to get things going by use of the hostnamectl to give it a hostname, but I didn't see anyplace to have set that in the installation phase (but it's likely I missed something).  It did properly get an IP address from the DHCP server, just not the name.

> 

> 

> 

>The only other oddity is that the VM shows up with the memory in RED in the configuration dashboard with only 1.6/4 GB of RAM in use - the documentation states minimums of 4GB - should that be higher for the new version?

> 

> 

> 

>As usual I had to edit lsregistrationdaemon.conf and web_admin.conf to allow for internal addresses (shouldn't that be an option in the administrative interface?  We use them internally on our private network for testing).

> 

> 

> 

>Charley

> 

> 

> 

> 

> 

> 

> 

> 

> 

> 

> 

> 

> 

>________________________________

> 

>From: > <>> on behalf of Andrew Lake <>>

>Sent: Monday, March 27, 2017 3:01 PM

>To: >; >

>Subject: [perfsonar-user] perfSONAR 4.0rc3 now available for testing!

> 

> 

> 

>All,

> 

> 

> 

>The third release candidate of perfSONAR 4.0 is now available for testing. As always, please DO NOT install this on EXISTING production hosts as it is not the final release (see the CentOS 7 section below if you are planning a new deployment). We anticipate that this will be the last release candidate prior to the final release, and its date will be dependent on the results of this round of community testing. You'll note that we had a much-larger-than-usual gap between RC2 in November and this release. That time has been spent extensively testing and optimizing the code, as this is probably the largest software change in the project's history and we want to be really sure we get it right. We anticipate that the time between RC3 and the final will be significantly shorter. Expect more details on preparing for this release in a follow-up email. For more details on various topics relevant to this RC, see the sections below:

> 

> 

> 

>============================================

> 

>Changes since 4.0RC2

> 

>============================================

> 

>See our release notes at: http://www.perfsonar.net/release-notes/version-4-0-rc3/<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.perfsonar.net_release-2Dnotes_version-2D4-2D0-2Drc3_&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=puiDgVtY0d9ihL712u5hZ-0qjRq1IgTNK3sSfBWM_zQ&m=14-sky3g5HsKz6C3EgNKfpyPCutuNlflm2xWbwdAo2I&s=Vdi_g9LVlBX0GsooES5-2y2eHTkp5GYC4ZccmQqVihc&e=>

> 

> 

> 

>==============================================

> 

>Getting 4.0RC3

> 

>============================================

> 

>In terms of obtaining this release, many of you probably have it via auto-updates if you tested our previous release candidates. If not, please see http://docs.perfsonar.net/release_candidates/4.0rc3/install_rcs.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.perfsonar.net_release-5Fcandidates_4.0rc3_install-5Frcs.html&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=puiDgVtY0d9ihL712u5hZ-0qjRq1IgTNK3sSfBWM_zQ&m=14-sky3g5HsKz6C3EgNKfpyPCutuNlflm2xWbwdAo2I&s=AiAmNHgkOXaBdeoKIAQRitzNYGO9g6dpBjUhQZQE-Gk&e=> for instructions on how to obtain it. In general, the best place for documentation on this RC can be found at http://docs.perfsonar.net/release_candidates/4.0rc3<https://urldefense.proofpoint.com/v2/url?u=http-3A__docs.perfsonar.net_release-5Fcandidates_4.0rc3&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=puiDgVtY0d9ihL712u5hZ-0qjRq1IgTNK3sSfBWM_zQ&m=14-sky3g5HsKz6C3EgNKfpyPCutuNlflm2xWbwdAo2I&s=Mh6Hx1LHBwM-dyglmXd-PUB6HvISxU3e38O43DmL140&e=>. Also please see our checklist at https://github.com/perfsonar/project/wiki/Toolkit-Testing-Checklist<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_perfsonar_project_wiki_Toolkit-2DTesting-2DChecklist&d=DwMFaQ&c=imBPVzF25OnBgGmVOlcsiEgHoG1i6YHLR0Sj_gZ4adc&r=puiDgVtY0d9ihL712u5hZ-0qjRq1IgTNK3sSfBWM_zQ&m=14-sky3g5HsKz6C3EgNKfpyPCutuNlflm2xWbwdAo2I&s=gT2XsBaKyVhguT54yVSn6IrAJTpZFVIvx8xVm_d85UY&e=> for things to look for after upgrading.

> 

> 

> 

>============================================

> 

>CentOS 7

> 

>============================================

> 

>We know many of you have been waiting on 4.0 so you can start a CentOS 7 deployment. If you are in this category, we suggest you download and install RC3. You will be able to auto-update it to the final and we are comfortable enough with it on CentOS 7 that you should have a relatively stable deployment. You are also welcome to wait, but we know some of you are really anxious to play with CentOS 7 and the software should be in a state where you can comfortably do so.

> 

> 

> 

>Thank you,

> 

>The perfSONAR Development Team

> 

> 

> 

> 

 

 

 

--

Michael Johnson

GlobalNOC Software Engineering

Indiana University

812-856-2771