Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Issue with "Globally Registered"

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Issue with "Globally Registered"


Chronological Thread 
  • From: Andrew Lake <>
  • To: "Hoover, Christopher" <>
  • Cc: "Voss, Randy W" <>, "''" <>
  • Subject: Re: [perfsonar-user] Issue with "Globally Registered"
  • Date: Mon, 3 Nov 2014 15:07:48 -0500

Hi,

I didn't catch these two threads were related, thanks for the clarification.
It sounds like you are on the right track in that you need to figure out why
the system can't reach http://ndb1.internet2.edu:8090/lookup/records. The
lookup service on ndb1 seems to be running fine, so a routing issue is a safe
bet.

Thanks,
Andy




On Nov 3, 2014, at 12:17 PM, "Hoover, Christopher"
<>
wrote:

> Andrew, we seem to have resolved the reverse DNS issue this morning by
> adding "primary_interface eth0" to
> /opt/perfsonar_ps/toolkit/web/root/gui/services/etc/web_admin.conf and "
> external_address_if_name eth0" to
> /opt/perfsonar_ps/ls_registration_daemon/etc/ls_registration_daemon.conf.
> It now consistently reports perfsonar3.usd.edu as Primary Address, and
> we're able to have both interfaces up with testing addresses for both of
> them being presented under BWCTL, etc.
>
> However, "Globally registered" has been reporting "Unknown" since before
> that, and we no longer appear on the Global Services page. The final line
> of /var/log/perfsonar/ls_registration_daemon.log is:
>
> 2014/11/03 10:14:08 (2072) ERROR> Base.pm:304
> perfSONAR_PS::LSRegistrationDaemon::Base::register - Problem registering
> service. Will retry full registration next time: 500 Can't connect to
> ndb1.internet2.edu:8090 (connect: Network is unreachable)
>
> It was also unable to ping ndb1.internet2.edu, so since the IPs for both
> interfaces are in the same subnet, I suspected a routing issue and
> disabled eth2 (kusdshop1.pbs.usd.edu). This put "Globally registered" to
> "No," at least.
>
> Then, after rebooting, "Globally registered" returned to "Unknown" and
> we're still not on Global Services, but there are no new errors in
> /var/log/perfsonar/ls_registration_daemon.log.
>
> So, after all of the above, we still aren't correctly able to have two
> interfaces up (though now apparently due to a possible routing issue), and
> we still seem not to be correctly registering.
>
> -----Original Message-----
> From:
>
>
> [mailto:]
> On Behalf Of Andrew Lake
> Sent: Monday, November 03, 2014 10:00 AM
> To: Voss, Randy W
> Cc:
> ''
> Subject: Re: [perfsonar-user] Issue with "Globally Registered"
>
> Hi Randy,
>
> Sorry for the delay on this. My guess would be it has to do with the
> reverse DNS on the host mapping to a name other than the one shown on the
> web page. Looking at the Global Services page I find it registered as
> kusdshop1.pbs.usd.edu (the name in reverse DNS) but the toolkit is looking
> for it as perfsonar3.usd.edu. In theory it should be registered under the
> same name as the one displayed. Do you know of there were any manual
> modifications made to
> "/opt/perfsonar_ps/toolkit/web/root/gui/services/etc/web_admin.conf" or
> "/opt/perfsonar_ps/ls_registration_daemon/etc/ls_registration_daemon.conf"?
>
> Thanks,
> Andy
>
>
>
> On Oct 30, 2014, at 10:37 AM, "Voss, Randy W"
> <>
> wrote:
>
>> We restarted the box and it changed to 'Yes' again, but I thought it was
>> worth sending the logs since it seems to keep flipping back and forth on
>> us.
>>
>> Thanks,
>>
>> Randy
>>
>> From: Andrew Lake
>> [mailto:]
>> Sent: Wednesday, October 29, 2014 7:18 AM
>> To: Voss, Randy W
>> Cc:
>> ''
>> Subject: Re: [perfsonar-user] Issue with "Globally Registered"
>>
>> Hi,
>>
>> Can you send /var/log/perfsonar/ls_registration_daemon.log?
>>
>> Thanks,
>> Andy
>>
>>
>> On Oct 28, 2014, at 6:03 PM, "Voss, Randy W"
>> <>
>> wrote:
>>
>>
>> I'm having a problem with a 3.4 install of PerfSonar. Right when we
>> upgraded to 3.4, host status was 'yes' for Globally registered. Since
>> then it has switched to no, even though I do see our server in the lookup
>> service directory. I checked and the ls_registration_daemon is running.
>> I haven't found much more for troubleshooting steps.
>>
>> Thanks,
>>
>> Randy Voss
>> Network & Server Team Leader
>> <image001.png>
>> Information Technology Services
>> 414 E. Clark Street, Slagle Hall - 14F Vermillion, SD 57069
>> 605.658.6000 (office) |
>>
>>
>>
>>
>>
>>
>> <ls_registration_daemon.log>
>




Archive powered by MHonArc 2.6.16.

Top of Page