perfSONAR User Q&A and Other Discussion

[Aaron Brown <>]

Hey Mark,

Could you try applying this patch: http://ndb1.internet2.edu/~aaron/improve_discover_lookup_service_error.patch

You’ll need to download it, and then apply it by running:

patch -d /opt/perfsonar_ps/ls_registration_daemon -p1 -i /path/to/improve_discover_lookup_service_error.patch

That will give us a better understanding of the error that you’re seeing. It may be something related to network connectivity on startup.

Cheers,

Aaron

On Jan 22, 2015, at 6:03 PM, Mark Foster <> wrote:

It seems like with increasing frequency, the ls_registration_daemon fails to start when one of my systems is rebooted.  I can manually start the daemon, and that appears to solve the problem at least until the next reboot.

This system is running 3.4.1.-1.psPS, as are my other systems. This netinstall system was upgraded from an earlier release, while the others were installed with 3.4 from the beginning. That's about the only difference I can find.

I do see the following from the ls_registration_daemon.log

2015/01/22 14:54:14 (1623) ERROR> LookupService.pm:72 perfSONAR_PS::Utils::LookupService::discover_lookup_services - Problem retrieving http://ps1.es.net:8096/lookup/activehosts.json: 500
2015/01/22 14:54:14 (1623) ERROR> daemon.pl:167 main:: - Unable to determine ls_instance

(I can wget the specific json url just fine, so it's not actual access to that file...)

I dug around a bit in the config files and couldn't find anything obvious....

-- Mark