perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Mark,

Can you send me the file /opt/perfsonar_ps/ls_registration_daemon/etc/ls_registration_daemon.conf and the full contents of /var/log/perfsonar/ls_registration_daemon.log? All those warnings look a little suspicious when you start it. The web page is accurate that your host is not getting registered in the LS at the moment. Also strange that it is having trouble with activehosts.json initially but then you can get it, hopefully the files above will shed some light.

Thanks,

Andy

On Jan 23, 2015, at 7:29 AM, Mark Maciolek <> wrote:

hi,

Having similar issue, it is chkconfig on.

Will not manually restart though or I should say it starts but the web pages still reports as No.

https://nautilus.sr.unh.edu/toolkit/

etc/init.d/ls_registration_daemon restart
/etc/init.d/ls_registration_daemon stop: LS Registration Daemon stopped
waiting...
/opt/perfsonar_ps/ls_registration_daemon/bin/daemon.pl --config=/opt/perfsonar_ps/ls_registration_daemon/etc/ls_registration_daemon.conf --pidfile=/var/run/ls_registration_daemon.pid --logger=/opt/perfsonar_ps/ls_registration_daemon/etc/ls_registration_daemon-logger.conf --user=perfsonar --group=perfsonar
Use of uninitialized value $latency in substitution (s///) at /opt/perfsonar_ps/ls_registration_daemon/bin/../lib/perfSONAR_PS/Utils/LookupService.pm line 102.
Use of uninitialized value in numeric gt (>) at /opt/perfsonar_ps/ls_registration_daemon/bin/../lib/perfSONAR_PS/Utils/LookupService.pm line 45.
Use of uninitialized value $primary_ls_latency in numeric gt (>) at /opt/perfsonar_ps/ls_registration_daemon/bin/../lib/perfSONAR_PS/Utils/LookupService.pm line 45.
Use of uninitialized value $primary_ls_latency in numeric eq (==) at /opt/perfsonar_ps/ls_registration_daemon/bin/../lib/perfSONAR_PS/Utils/LookupService.pm line 45.
/etc/init.d/ls_registration_daemon start: LS Registration Daemon started

On 1/23/2015 3:44 AM, Garnizov, Ivan (RRZE) wrote:

Hi Mark,

 

Please do:

 

sudo chkconfig ls_registration_daemon --list

 

on this system and one of the others ("the others were installed with 3.4 from the beginning ").

 

You are telling us also, that:

 

" I can manually start the daemon, and that appears to solve the problem at least until the next reboot "

 

So my guess is: there is a difference!

 

Best regards,

Ivan

 

-----Original Message-----
From: [] On Behalf Of Mark Foster
Sent: Thursday, January 22, 2015 11:04 PM
To:
Subject: [perfsonar-user] ps3.4: ls_registration_daemon not starting at reboot

 

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

 

 

-- 

Mark Maciolek
Network Administrator
Morse Hall Room 339
603-862-3050
https://www.unh.edu/research/support-units/research-computing-center