perfSONAR User Q&A and Other Discussion

[Kaushik Srinivasan <>]

Hi,

This is the error we get in the Maddash page shown on our central server.

Also there is no perfsonar-regulartesting package in our testpoint. (Note: Our testpoint is a perfsonar testpoint).

Regards

Kaushik

On Fri, Feb 23, 2018 at 2:48 PM, Jason Watt <> wrote:

Oops, nevermind, I misread what you were looking for.

On Fri, Feb 23, 2018 at 12:45 PM, Jason Watt <> wrote:

That was deprecated in 4.x.  It took me a while to figure this out and eventually found this:

https://www.perfsonar.net/release-notes/version-4-0/

• The /usr/lib/perfsonar/bin/generate_configuration script and associated cron are gone and now handled by the new perfsonar-meshconfig-agent daemon
• The /usr/lib/perfsonar/bin/generate_gui_configuration script and associated cron are gone and now handled by the new perfsonar-meshconfig-guiagent daemon. This daemon will now create traceroute and ping dashboards by default if you have the tests defined.

On Fri, Feb 23, 2018 at 12:40 PM, Kaushik Srinivasan <> wrote:

Hi all,

I moved from Debian to CentOS for the Central Management Server. I came across the same problem.

The binary generate_gui_configuration is missing.

Following Adam's advice I ran " /usr/lib/perfsonar/perfsonar_meshconfig_guiagent -c /etc/perfsonar/meshconfig-guiagent.conf -v" command.

The output is

2018/02/23 19:36:17 (3106) DEBUG> perfsonar_meshconfig_guiagent:178 main:: - No service check interval specified. Defaulting to 60 minutes

2018/02/23 19:36:17 (3106) DEBUG> perfsonar_meshconfig_guiagent:183 main:: - No configuration file check interval specified. Defaulting to 60 seconds

2018/02/23 19:36:17 (3106) DEBUG> Utils.pm:119 perfSONAR_PS::Client::Utils::send_http_request - Sending HTTP GET to https://perfsonar-server.dynv6.net/minidmz.json

2018/02/23 19:36:18 (3106) DEBUG> GUIAgent.pm:297 perfSONAR_PS::MeshConfig::GUIAgent::__write_file - No changes to configuration, so not updating

2018/02/23 19:36:18 (3106) DEBUG> GUIAgent.pm:91 perfSONAR_PS::MeshConfig::GUIAgent::__send_error_messages - No errors reported

2018/02/23 19:36:18 (3106) DEBUG> perfsonar_meshconfig_guiagent:231 main:: - Time until next record refresh is 3599 seconds

There are no errors. But the generate_gui_configuration is still missing.

Any idea why the file is not being generated?

Thanks.

Regards

Kaushik

On Sun, Feb 18, 2018 at 4:35 PM, <> wrote:

Heya,

 

I think I ran into this same issue when I installed maddash for the first time (on Ubuntu, though). I think it’s supposed to generate the config automatically on service start but you can also manually kick it off using the below:

 

/usr/lib/perfsonar/perfsonar_meshconfig_guiagent -c /etc/perfsonar/meshconfig-guiagent.conf -v

 

Another thing to note if this is your first PerfSonar install on debian, make sure to also install the package numactl, as iperf relies on this library to be installed and it’s not part of the toolkit package.  

 

Cheers

Adam

 

From: [mailto:] On Behalf Of Kaushik Srinivasan
Sent: Sunday, 18 February 2018 6:02 AM
To:
Subject: [perfsonar-user] Maddash for Debian

 

Hi all,

 

I have tried to configure Maddash on Debian Stretch (9) and have run into a missing binary.

 

I was able to follow the steps of Perfsonar Auto-Configuration as specified in the official page 

(http://software.es.net/maddash/mesh_config.html#advanced-perfsonar-auto-configuration) 

by replacing yum with apt-get.

 

But for the step 

Run the following command to generate your maddash configuration for the first time:

/usr/lib/perfsonar/bin/generate_gui_configuration

 

The binary generate_gui_configuration is missing. Without this the maddash server crashes on opening the gui page in a browser. 

 

How can I solve this?

 

Thanks in advance

 

Regards

Kaushik Srinivasan