perfSONAR User Q&A and Other Discussion

[Shawn McKee <>]

Right, ignore my other email :)   I should have read ahead in my emails.

Shawn

On Mon, Mar 28, 2016 at 6:04 PM, Michael Reece <> wrote:

Never mind Shawn, the new path was there I just wasn't reading it right.

On Mon, Mar 28, 2016 at 5:59 PM, Michael Reece <> wrote:

Thank you for the reply Shawn, but when I checked for the location of the file I wanted (agent configuration), it still seems to be in the same place: /opt/perfsonar_ps/mesh_config/etc/agent_configuration.conf

However, when I go to that location on my machine, there are no files. But there are also no files on the other nodes yet they are working fine, so I assumed that the agent configuration file must be somewhere else. Perhaps I am misreading the link that was sent to me. I checked the path given at:
http://docs.perfsonar.net/release_candidates/3.5.1/config_files.html#config-files-meshconfig-conf-agent

Please somebody correct me if I am checking the wrong location. Just confused as to where the agent configuration is, since it must be somewhere on the machines. Otherwise, how do they know the URL of the central configuration JSON file which tell the nodes what tests to run?

On Mon, Mar 21, 2016 at 8:06 PM, Shawn McKee <> wrote:

Hi Michael,

With the 3.5.1 upgrade the paths to most files in your installation were migrated to a more FHS friendly location.   See http://docs.perfsonar.net/release_candidates/3.5.1/config_files.html for the new location of files.

By default perfSONAR is setup to auto-upgrade and I expect that is what happened to your nodes.   This is actually a good thing in most cases as you get the newest security patches ASAP.  The downside is that this can break your instances but most people consider that an acceptable trade-off.

If that is not your issue please post some more details about which version you are running.  Thanks,

Shawn McKee/University of Michigan

On Mon, Mar 21, 2016 at 6:54 PM, Michael Reece <> wrote:

I have a pretty weird problem. All of the testing done on my 6 node mesh is through a central configuration file. But oddly, every single one of the the nodes in my mesh are missing an agent_configuration.conf at the path /perfsonar_ps/mesh_config/etc/

From my understanding, the agent_configuration.conf tells the node where the URL of the mesh.json is located, allowing the nodes to perform the tests. I really don't understand how it is possible for nodes of my mesh to be working with the agent_configuration.conf missing, but I promise you that they are. Moreover, all of my scripts are missing (build_json, generate_configuration, validate_configuration, etc.)

I find this very confusing and don't understand 2 things:

1. Why did my agent_configuration.conf, scripts and basically everything in the directory mesh_config suddenly disappear from all 6 of my nodes?
   
2. How are these nodes able to communicate with MaDDash without an agent_configuration.conf being present?

I wouldn't care so much about this if I wasn't trying to add another node to the mesh and having trouble doing so. I think it may be because the new node doesn't have the agent_configuration.conf but that begs the question of how the other nodes are functioning.

If you would like to see the mesh.json, MaDDash.yaml, or any other file which may help diagnose the problem, please ask and I'll gladly attach it.

Thanks in advance