Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] perfsonarbuoy_ma will not start

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] perfsonarbuoy_ma will not start


Chronological Thread 
  • From: Andrew Lake <>
  • To: Mark Maciolek <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] perfsonarbuoy_ma will not start
  • Date: Mon, 17 Nov 2014 10:05:54 -0500

Hi Mark,

You need to change the URLs for the MAs in your maddash config to take the
form http://<hostname>/esmond/perfsonar/archive where <hostname> is the
address of your toolkit host. What's the name of the host where you don't
think esmond is working? The two UNH hosts I see seem to have working
instances, but I may be looking at the wrong hosts.

Thanks,
Andy




On Nov 17, 2014, at 9:46 AM, Mark Maciolek
<>
wrote:

> hi,
>
> Tests are working, esmond archive is not, Maddash does not work since
> upgrade to 3.4
>
> Mark
>
> On 11/17/2014 9:17 AM, Andrew Lake wrote:
>> Hi,
>>
>> After the 3.4 upgrade perfSONARBUOY is no longer used. The measurement
>> archive is now handled by a software package called esmond. You also do
>> not need discover_external_address. The address discovery has been moved
>> into the individual components that needs the address. The fact that
>> perfSONARBUOY will not start should not affect your tests.
>>
>> Thanks,
>> Andy
>>
>>
>> On Nov 15, 2014, at 10:45 AM, Mark Maciolek
>> <>
>> wrote:
>>
>>> hi,
>>>
>>> 2014/11/15 10:39:21 (18195) FATAL> perfSONARBUOY.pm:238
>>> perfSONAR_PS::Services::MA::perfSONARBUOY::init - With LS registration
>>> enabled, you need to specify either the service accessPoint for the
>>> service or the external_address
>>>
>>> After the upgrade to 3.4 discover_external_address was removed.
>>>
>>> Restoring it from backups gives this error when trying to run it.
>>>
>>> /opt/perfsonar_ps/toolkit/scripts/discover_external_address
>>> Base class package "perfSONAR_PS::NPToolkit::Config::pSPSServiceDaemon"
>>> is empty.
>>> (Perhaps you need to 'use' the module which defines that package first,
>>> or make that module available in @INC (@INC contains:
>>> /opt/perfsonar_ps/toolkit/scripts/../lib /usr/local/lib64/perl5
>>> /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl
>>> /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .).
>>> at
>>> /opt/perfsonar_ps/toolkit/scripts/../lib/perfSONAR_PS/NPToolkit/Config/PingER.pm
>>> line 21.
>>>
>>> Try reinstall and get this message:
>>>
>>> Installed package
>>> perl-perfSONAR_PS-perfSONARBUOY-config-3.3.2-1.pSPS.noarch (from
>>> Internet2) not available.
>>>
>>> Any suggestions on how to fix this?
>>>
>>> Mark
>>
>
> --
>
> Mark Maciolek
> Network Administrator
> Morse Hall Room 339
> 603-862-3050
> https://www.unh.edu/research/support-units/research-computing-center
>
>
> ---
> This email is free from viruses and malware because avast! Antivirus
> protection is active.
> http://www.avast.com
>




Archive powered by MHonArc 2.6.16.

Top of Page