Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] perfSONAR 4.0 updates

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] perfSONAR 4.0 updates


Chronological Thread 
  • From: Andrew Lake <>
  • To: "" <>
  • Subject: [perfsonar-user] perfSONAR 4.0 updates
  • Date: Fri, 21 Apr 2017 12:01:46 -0700
  • Ironport-phdr: 9a23:fU/lVhKPZwT+GeNVCtmcpTZWNBhigK39O0sv0rFitYgRLf/xwZ3uMQTl6Ol3ixeRBMOAuqwC0Lad6vu8EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQtFiT68bL9oIhi7ogrdutQYjIZtN6081gbHrnxUdupM2GhmP0iTnxHy5sex+J5s7SFdsO8/+sBDTKv3Yb02QaRXAzo6PW814tbrtQTYQguU+nQcSGQWnQFWDAXD8Rr3Q43+sir+tup6xSmaIcj7Rq06VDi+86tmTgLjhSEaPDA77W7XkNR9gqJcrh2uqRJxwJPabp+JO/dlZKzRYckXSHBbU8pNVSFMBJ63YYsVD+oGOOZVt5Xwp10TohukGwatCv7kxDlSiX/1w6IxzuMsHhvA3AM9H9MDq2rbrM7vOKcUT++10LDFwDPeZP1Y3jf97ZLHchEnofyUQb1wcdTexlUsFwzdllWQqIrlPzyN2eQJtGib9PFgWfi3i24jrQx6vzuhxt80h4XUmI4YyUrI+CtjzIs6ONG0Uk92bN28HJdOqy2XM5F6T8AiTm1ypio2174LtYS6cSUOzpks2gTRZOadc4eS5xLuTOaRLil8hHJiYL+/iQi9/Ea6xu34Tca01ExGriVCktnSrnwN1hrT5dabSvZl40utxzWC2xrd5+1eLk04iLDXJp8iz7Iok5ocq0XDHiv4mEXsi6+Wc10p9fKu6+v6YrTrvYGTN5RuhgH4LKsuhtSzAf4kPQgWQ2ib5eO82aX7/ULnWrVKgOY2kq7fsJ/AP8QXv7O5AxRL3YY58Bu/Czam0M8EnXkcMl5JYhOHj471O17QOvD4C+mwg0iynDtx2f/JI6DhUd3xKS2JiLr7c6167UdGjRcowMp35pRIB6sHLe6pHEL9qZaQWgc0KQKvxODuEpBgzY4EcWOJHqKDNq7O6xmF6v95cMeWY4pAkTDxMfU6r9rnjnJxzVYbcbiB0IBRbn2kSKc1a36FaGbh149SWVwBuRAzGbTn

All,

First of all thanks to everyone for a successful perfSONAR 4.0 release so far.  I think for most its gone reasonably smooth, but as is to be expected for any large release, some of you ran into a few issues. We have tried to address such issues as quickly as possible. Below are a list of updates that have gone out the past few days, and thanks to all of you that reported them:

1. An issue with the test listing and graphs was fixed that was preventing measurements from being displayed because of a mix of http and https. This was fixed in perfsonar-graphs-4.0.0.1.

2. We added some additional checks to the pscheduler-server package to verify postgresql is running before performing database setup. This was the cause of some database issues a few encountered. This is fixed in pscheduler-server-1.0.0.1

3. We fixed an issue with the ISOs where pscheduler databases were not setup correctly if the network was not up by a certain point in the boot process. It was a race condition so it did not affect everyone. If you did encounter this simply run “yum reinstall pscheduler-server”. This is fixed in the ISOs with 2017Apr21 in the name. 

4. We updated the firewall scripts to leave open the NDT ports so those of you running CentOS 6 hosts that already had NDT running will continue to operate. Our intention was not to break existing installs, though do keep in mind that new installs of 4.0 will not have NDT and on October 17, 2017 NDT support on perfSONAR will be dropped when we also end-of-life perfSONAR 3.5.1 and web100 kernels. The firewall ports were re-opened in perfsonar-toolkit-security-4.0.0.1

5. The 4.0 version of nagios-plugins-perfsonar package was not copied over to the main EL6 repo, so some of you saw complaints about missing check_ping_loss.pl commands in MaDDash if you had ping tests to display. This file has since been copied over.

Those should address some of the more common issues we have seen so far. Please keep us posted if you encounter anything else. 

Thank you,
The perfSONAR Development Team





Archive powered by MHonArc 2.6.19.

Top of Page