perfSONAR User Q&A and Other Discussion

[Antoine Delvaux <>]

Hello,

After analysis, it looks like the perfsonar-meshconfig update to 4.0 RC1 on Debian/Ubuntu is due to a mistake on our side.  These packages were supposed to be restricted to the staging repository but they get passed the control mesh and landed in the release repository.

This has just been corrected an hour ago and we reverted to the 3.5.1.2 packages.

If your host as automatically upgraded to those 4.0-RC1 packages, you need to restore the previous packages through a manual process.  This is started by this command:

apt-get remove perfsonar-meshconfig-agent perfsonar-meshconfig-guiagent perfsonar-meshconfig-jsonbuilder perfsonar-meshconfig-shared

The bundle package perfsonar-testpoint will get uninstalled at the same time (or any other bundle package that you might have), this is normal.  Then, you can re-install the correct version with:

apt-get update

apt-get install perfsonar-testpoint

or (if you don't use the perfsonar-testpoint bundle or any other bundle), you can directly install the meshconfig with:

apt-get update

apt-get install perfsonar-meshconfig-agent

This should give you back a working system.  If this is not the case, please report here on the list.

Sorry for this mishandling of repository on our side.

Antoine.

Le 15 sept. 2016 à 14:22, John Simpkins <> a écrit :

Same!

Unpacking perfsonar-meshconfig-shared (4.0~2.rc1-1~bpo70+1) over (3.5.1.2-1~bpo70+1) ...

Preparing to unpack .../perfsonar-meshconfig-agent_4.0~2.rc1-1~bpo70+1_all.deb ...

Unpacking perfsonar-meshconfig-agent (4.0~2.rc1-1~bpo70+1) over (3.5.1.2-1~bpo70+1) ...

On Thu, Sep 15, 2016 at 8:55 AM Andrew Lake <> wrote:

Hi,

You didn't miss anything, we didn’t announce the RC yet. We’ll likely officially announce it next week. You must be pointing at Internet2-staging which is our testing repository. Your hosts are part of the WLCG/OSG testbed, correct? We pushed some RPMs to the staging repo so we could get the RPMs to a few well-known places prior to the wider announcement. The problem you encountered on the one host with pscheduler should be fixed next auto-update I think (I still need to push another set of RPMs). There was a problem with one of the pscheduler RPMs disabling itself on upgrade (basically it was disabling itself in the uninstall step without checking if it was a true uninstall or the uninstall of an old package so a new one could be installed as part of an update). Hoping to correct that shortly. Thanks for checking though and sorry for the surprise. 

Thanks,

Andy

On September 14, 2016 at 7:06:06 PM, Michael Petry () wrote:

I noticed that two of my systems that are set for autoupdate picked up toolkit4.0 last night.  Did I miss an announcement?

Mike

P.S. One system seems to run fine, but the other is has pscheduler disabled and error loading test results.