perfSONAR User Q&A and Other Discussion

[Fernando Redigolo <>]

We are having a similar problem with perfsonar nodes (host not registered globally), but we found some messages on the log that caught our attention. The first ones were shown when the service was restarted:

2014/10/20 17:31:45 (1334) INFO> daemon.pl:170 main:: - Initial LS URL set to http://ls.monipe.rnp.br:8090/lookup/records

2014/10/20 17:31:45 (1334) INFO> daemon.pl:183 main:: - No LS key database found

These were followed by some ‘ duplicate’ verification, followed by these messages below: 

2014/10/20 19:41:00 (8933) ERROR> Base.pm:152 perfSONAR_PS::LSRegistrationDaemon::Base::validate_conf - Multiple entries for ma_locator. Only one is valid

followed by a couple of messages with forbidden address, such as the ones below:

2014/10/20 19:41:02 (8973) INFO> Base.pm:251 perfSONAR_PS::LSRegistrationDaemon::Base::refresh - Record 'eth0' is up, registering

2014/10/20 19:41:02 (8973) ERROR> Base.pm:304 perfSONAR_PS::LSRegistrationDaemon::Base::register - Problem registering service. Will retry full registration next time: 403 Forbidden

I know that this LS he determines belongs to a research project, I am not sure if it is open for registration by people from outside the project, could it be the problem? I have not specified it, it seems to have been determined automatically. Can we manually specify a different LS for testing if there is a problem with this LS ?

Regards,

Fernando Redigolo

On Oct 20, 2014, at 11:21 AM, Andrew Lake <> wrote:

Hi Luis,

Does this host by chance have a private address? If so, in /opt/perfsonar_ps/ls_registration_daemon/etc/ls_registration_daemon.conf set allow_internal_addresses to 1.

Thanks,

Andy

On Oct 17, 2014, at 4:37 PM, Luís Felipe <> wrote:

Sorry for delay.

I tried restart the service and it doesn't start more... In the .log file, the errors appear:

2014/10/17 17:24:44 (6715) ERROR> ICMP_Service.pm:47 perfSONAR_PS::LSRegistrationDaemon::Services::ICMP_Service::init - No address available for service
2014/10/17 17:24:44 (6715) ERROR> Host.pm:300 perfSONAR_PS::LSRegistrationDaemon::Host::init_subordinates - Error: Couldn't initialize service type: Ping Responder
2014/10/17 17:24:44 (6715) ERROR> daemon.pl:318 main::init_site - Error: Couldn't initialize host watcher

But, what this mean?

On 14-10-2014 09:15, Andrew Lake wrote:

Hi,

Garhan's suggestion is a good thing to try to get it back registered quickly. Could one or both of you send your LS Registration Daemon log file (/var/log/perfsonar/ls_registration_daemon.log) so we can try to understand why it crashed in the first place.

Thanks,
Andy

On Oct 13, 2014, at 4:12 PM, Garhan Attebury  wrote:

One of the three 3.4 hosts I provisioned in the past few days had this. Eventually figured out the ls_registration_daemon wasn’t running.

Now -why- it wasn’t running where on the other two hosts it was, I don’t know. Starting up the daemon with “service ls_registration_daemon start” seems to have worked. I have yet to restart the whole server itself so I’ve no idea if there’s an underlying problem. 


Garhan Attebury
Holland Computing Center
University of Nebraska-Lincoln
402-472-7761



On Oct 13, 2014, at 2:46 PM, Luís Felipe  wrote:

Hi,

I updated my hosts to 3.4 and since then some them show the field "Globally Registered" with "No". But when I see the "Administrative Information", all is correctly filled. The weird is: when I save the "Administrative Information" without change anything, the field is changed to "Yes" for a while. After some time, the field is changed to "No" again.

Is this some error in the install process?

Thank you.
Luís Felipe