perfSONAR User Q&A and Other Discussion

[Aaron Brown <>]

Hey David,

On 3/5/13 5:53 PM, "David Mitchell" 
<>
 wrote:

>Aaron,
>
>thanks for the help. I'm getting there. The docs didn't mentions a
>different GUI package but I found it easily. I also found I needed to add
>the various config files to
>/opt/perfsonar_ps/toolkit/etc/config_daemon.conf. The generate_gui_script
>also complained about maddash not being in the file with this error:
>[mitchell@ps
> bin]$ ./generate_gui_configuration
>2013/03/05 15:51:12 (9736) ERROR> ConfigClient.pm:128
>perfSONAR_PS::NPToolkit::ConfigManager::ConfigClient::restartService -
>Problem restarting service maddash: Method restartService returned error:
>Access denied: no service maddash in list at
>/opt/perfsonar_ps/toolkit/bin/../lib/perfSONAR_PS/NPToolkit/ConfigManager/
>ConfigDaemon.pm line 164.
>2013/03/05 15:51:12 (9736) ERROR> GUIAgent.pm:388
>perfSONAR_PS::MeshConfig::GUIAgent::__restart_service - Problem
>restarting maddash: Couldn't restart service maddash via toolkit daemon
>at 
>/opt/perfsonar_ps/mesh_config/bin/../lib/perfSONAR_PS/MeshConfig/GUIAgent.
>pm line 343.
>2013/03/05 15:51:12 (9736) ERROR> GUIAgent.pm:258
>perfSONAR_PS::MeshConfig::GUIAgent::__configure_guis - Problem restarting
>service maddash: Problem restarting maddash: Couldn't restart service
>maddash via toolkit daemon at
>/opt/perfsonar_ps/mesh_config/bin/../lib/perfSONAR_PS/MeshConfig/GUIAgent.
>pm line 343.
>
>
>
> but adding it just go a different complaint seen below. I presume I need
>to define this service somewhere, but I'm not sure where:
>[mitchell@ps
> bin]$ ./generate_gui_configuration
>2013/03/05 15:52:08 (9775) ERROR> ConfigClient.pm:128
>perfSONAR_PS::NPToolkit::ConfigManager::ConfigClient::restartService -
>Problem restarting service maddash: Method restartService returned error:
>Invalid service: maddash at
>/opt/perfsonar_ps/toolkit/bin/../lib/perfSONAR_PS/NPToolkit/ConfigManager/
>ConfigDaemon.pm line 175.
>2013/03/05 15:52:08 (9775) ERROR> GUIAgent.pm:388
>perfSONAR_PS::MeshConfig::GUIAgent::__restart_service - Problem
>restarting maddash: Couldn't restart service maddash via toolkit daemon
>at 
>/opt/perfsonar_ps/mesh_config/bin/../lib/perfSONAR_PS/MeshConfig/GUIAgent.
>pm line 343.
>2013/03/05 15:52:08 (9775) ERROR> GUIAgent.pm:258
>perfSONAR_PS::MeshConfig::GUIAgent::__configure_guis - Problem restarting
>service maddash: Problem restarting maddash: Couldn't restart service
>maddash via toolkit daemon at
>/opt/perfsonar_ps/mesh_config/bin/../lib/perfSONAR_PS/MeshConfig/GUIAgent.
>pm line 343.
>
>I am able to restart maddash-server by hand and the GUI now loads, so I
>am making progress! Thanks for bearing with all my questions!

With the 3.3 version of the Toolkit, you won't have that issue. In the
interim, it's probably easiest to just set "restart_services" to 0 in the
gui_agent_configuration.conf, and then just restart the service manually.
You can also set "use_toolkit" to 0, and then it'll try writing those
files directly instead of trying to use the toolkit configuration daemon.

Cheers,
Aaron

>
>-David
>
>On Mar 5, 2013, at 1:09 PM, Aaron Brown 
><>
> wrote:
>
>> Hey David,
>> 
>> Comments inline
>> 
>> Cheers,
>> Aaron
>> 
>> On 3/5/13 1:36 PM, "David Mitchell" 
>> <>
>>  wrote:
>> 
>>> 
>>> On Feb 28, 2013, at 8:45 AM, Aaron Brown 
>>> <>
>>>  wrote:
>>> 
>>>> Hey David,
>>>> 
>>>> On 2/27/13 12:50 PM, "David Mitchell" 
>>>> <>
>>>>  wrote:
>>>> 
>>>>> I'm trying to use the mesh generator to setup a new mesh of bwtcl and
>>>>> owamp tests. I've been following the directions on the Wiki. I have
>>>>> created the json configuration file using the build_json script and
>>>>> updated the agent_configuration.conf to point to the file. That all
>>>>> seems
>>>>> to work OK. When I run the generate_configuration script it produces
>>>>> quite a few errors about being unable to update files. I'm not sure
>>>>> what
>>>>> other folks do to run this script, as by default the files are owned
>>>>>by
>>>>> user perfsonar and that account is locked.
>>>> 
>>>> The default cron jobs run as the perfsonar user, but could conceivably
>>>> run
>>>> as root as well, or some other user capable of writing those files and
>>>> restarting the services. Another option is to run the scripts that
>>>>write
>>>> the files as the perfsonar user, and then have a root user restart the
>>>> services, if you want to lock down what the root user is doing some.
>>> 
>>> I'm really just looking for the path of least resistance while I
>>> troubleshoot the installation. Once it's working I'm fine with the cron
>>> job.
>> 
>> It's probably easiest to run as root while testing.
>> 
>>>>> When it completes, there is a maddash configuration dumped in json
>>>>> format
>>>>> in /opt/maddash/maddash-webui/xsede-mesh.json. That would be great
>>>>>but
>>>>> I
>>>>> thought maddash was reading /etc/maddash/maddash-server/maddash.yaml
>>>>> for
>>>>> it's configuration. I was going to work through this apparent
>>>>> disconnect
>>>>> before I try and troubleshoot whether the measurements are being
>>>>> properly
>>>>> scheduled. I do have an older version of the maddash software and a
>>>>> configuration set up. Would that be breaking things? According to yum
>>>>> I'm
>>>>> up to date on all of the perfsonar and maddash packages. Thanks in
>>>>> advance,
>>>> 
>>>> I'm not sure why xsede-mesh.json got dumped into that directory. It
>>>> should
>>>> write the maddash.yaml file, and in fact, it can't write anything
>>>>other
>>>> than that for maddash.
>>> 
>>> Wait, that's my own forgetfulness. I plead that I only work on this
>>> periodically. That's where I stuffed the json file for other agents to
>>> get. I can't find any place where the generate_configuration script
>>>even
>>> tries to write a maddash.yaml file though. It should try to somewhere
>>> though right? Or am I mistake and the mesh generator just takes care of
>>> the test setup?
>> 
>> The generate_configuration script only takes care of setting up the
>>tests.
>> The generate_gui_configuration script (part of the
>> perl-perfSONAR_PS-MeshConfig-GUI package) writes the maddash.yaml.
>> 
>>> 
>>> -David
>>> 
>>>> 
>>>> Cheers,
>>>> Aaron
>>>> 
>>>>> 
>>>>> -David Mitchell
>>>>> 
>>>>> -----------------------------------------------------------------
>>>>> | David Mitchell 
>>>>> ()
>>>>>        Network Engineer IV  |
>>>>> | Tel: (303) 497-1845                      National Center for  |
>>>>> | FAX: (303) 497-1818                      Atmospheric Research |
>>>>> -----------------------------------------------------------------
>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>>> -----------------------------------------------------------------
>>> | David Mitchell 
>>> ()
>>>        Network Engineer IV  |
>>> | Tel: (303) 497-1845                      National Center for  |
>>> | FAX: (303) 497-1818                      Atmospheric Research |
>>> -----------------------------------------------------------------
>>> 
>>> 
>>> 
>>> 
>> 
>> 
>
>-----------------------------------------------------------------
>| David Mitchell 
>()
>       Network Engineer IV  |
>| Tel: (303) 497-1845                      National Center for  |
>| FAX: (303) 497-1818                      Atmospheric Research |
>-----------------------------------------------------------------
>
>