perfSONAR User Q&A and Other Discussion

[Ian Gable <>]

Hi All,

The eventual cause of this problem was tracked by Aaron to be a corrupted 
pinger-landmarks.xml file. The cause of the corruption is unknown. The fix is:

curl 
https://perfsonar-ps.googlecode.com/git/perfSONAR_PS-PingER/etc/pinger-landmarks.xml
 -o /opt/perfsonar_ps/PingER/etc/pinger-landmarks.xml
/opt/perfsonar_ps/toolkit/scripts/discover_external_address
sudo -u perfsonar /opt/perfsonar_ps/mesh_config/bin/generate_configuration
service perfsonarbuoy_ma restart

The above is contained in the gist:
https://gist.github.com/igable/9772512

Thanks again Aaron.

Ian

—
Ian Gable
HEPnet Canada, University of Victoria

+1 250 721 7728





On Mar 25, 2014, at 9:01 AM, Ian Gable 
<>
 wrote:

> Hi Aaron,
> 
> Sorry for the noise on this. In fact there was a line so long on the log 
> that it displayed as 
> ‘@‘
>  in VIM and I didn’t notice:
> 
> Here are the last few lines of the log:
> https://gist.github.com/igable/9764945
> 
> 
> Ian
> 
> —
> Ian Gable
> HEPnet Canada, University of Victoria
> 
> +1 250 721 7728
> 
> 
> 
> 
> 
> On Mar 25, 2014, at 8:51 AM, Ian Gable 
> <>
>  wrote:
> 
>> Aaron,
>> 
>> Suspiciously there is no activity in the log since Feb:
>> https://gist.github.com/igable/9764718
>> 
>> 
>> Also the IP and the rDNS record:
>> 
>> [igable@ps-latency
>>  ~]$ ifconfig
>> em2       Link encap:Ethernet  HWaddr 78:2B:CB:54:B4:D3
>>         inet addr:132.206.245.252  Bcast:132.206.245.255  
>> Mask:255.255.255.224
>>         inet6 addr: fe80::7a2b:cbff:fe54:b4d3/64 Scope:Link
>>         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>         RX packets:28294055 errors:0 dropped:0 overruns:0 frame:0
>>         TX packets:24552044 errors:0 dropped:0 overruns:0 carrier:0
>>         collisions:0 txqueuelen:1000
>>         RX bytes:2601498385 (2.4 GiB)  TX bytes:2023623664 (1.8 GiB)
>> 
>> lo        Link encap:Local Loopback
>>         inet addr:127.0.0.1  Mask:255.0.0.0
>>         inet6 addr: ::1/128 Scope:Host
>>         UP LOOPBACK RUNNING  MTU:16436  Metric:1
>>         RX packets:1521572 errors:0 dropped:0 overruns:0 frame:0
>>         TX packets:1521572 errors:0 dropped:0 overruns:0 carrier:0
>>         collisions:0 txqueuelen:0
>>         RX bytes:950803612 (906.7 MiB)  TX bytes:950803612 (906.7 MiB)
>> 
>> [igable@ps-latency
>>  ~]$ dig -x 132.206.245.252
>> 
>> ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.23.rc1.el6_5.1 <<>> -x 132.206.245.252
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36960
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>> 
>> ;; QUESTION SECTION:
>> ;252.245.206.132.in-addr.arpa.       IN      PTR
>> 
>> ;; ANSWER SECTION:
>> 252.245.206.132.in-addr.arpa. 75120 IN       PTR     
>> ps-latency.clumeq.mcgill.ca.
>> 
>> ;; Query time: 3 msec
>> ;; SERVER: 132.206.85.20#53(132.206.85.20)
>> ;; WHEN: Tue Mar 25 11:50:34 2014
>> ;; MSG SIZE  rcvd: 87
>> 
>> 
>> Ian
>> 
>> 
>> —
>> Ian Gable
>> HEPnet Canada, University of Victoria
>> 
>> +1 250 721 7728
>> 
>> 
>> 
>> 
>> 
>> On Mar 25, 2014, at 5:57 AM, Aaron Brown 
>> <>
>>  wrote:
>> 
>>> Hey Ian,
>>> 
>>> Could you send the log file 
>>> /var/log/perfsonar/discover_external_address.log ?
>>> 
>>> Cheers,
>>> Aaron
>>> 
>>> On Mar 24, 2014, at 5:08 PM, Ian Gable 
>>> <>
>>>  wrote:
>>> 
>>>> Hi Aaron,
>>>> 
>>>> After running /opt/perfsonar_ps/toolkit/scripts/discover_external_address
>>>> 
>>>> I get:
>>>> 
>>>> [root@ps-latency
>>>>  init.d]# ./perfsonarbuoy_ma restart
>>>> ./perfsonarbuoy_ma stop: perfSONAR perfSONAR-BUOY MA Service (pid 5807?) 
>>>> not running
>>>> waiting...
>>>> /opt/perfsonar_ps/perfsonarbuoy_ma/bin/daemon.pl 
>>>> --config=/opt/perfsonar_ps/perfsonarbuoy_ma/etc/daemon.conf 
>>>> --pidfile=perfsonarbuoy_ma.pid --piddir=/var/run 
>>>> --logger=/opt/perfsonar_ps/perfsonarbuoy_ma/etc/daemon_logger.conf 
>>>> --user=perfsonar --group=perfsonar
>>>> ./perfsonarbuoy_ma start: perfSONAR perfSONAR-BUOY MA Service could not 
>>>> be started
>>>> 
>>>> 
>>>> then from the perfsonarbuoy_ma.log:
>>>> 
>>>> 2014/03/24 17:00:08 (5807) ERROR> daemon.pl:380 main:: - Failed to 
>>>> initialize module perfSONAR_PS::Services::MA::perfSONARBUOY on 
>>>> 8085:/perfSONAR_PS/services/pSB
>>>> 2014/03/24 17:03:58 (6121) WARN> daemon.pl:262 main:: - Setting listener 
>>>> queue size to 100
>>>> 2014/03/24 17:03:58 (6121) WARN> daemon.pl:267 main:: - Setting LS 
>>>> registration interval at 60 minutes
>>>> 2014/03/24 17:03:58 (6121) WARN> daemon.pl:272 main:: - Enabling echo 
>>>> service for each endpoint unless specified otherwise
>>>> 2014/03/24 17:03:58 (6121) 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
>>>> 2014/03/24 17:03:58 (6121) ERROR> daemon.pl:380 main:: - Failed to 
>>>> initialize module perfSONAR_PS::Services::MA::perfSONARBUOY on 
>>>> 8085:/perfSONAR_PS/services/pSB
>>>> 
>>>> 
>>>> —
>>>> Ian Gable
>>>> HEPnet Canada, University of Victoria
>>>> 
>>>> +1 250 721 7728
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Mar 24, 2014, at 2:00 PM, Aaron Brown 
>>>> <>
>>>>  wrote:
>>>> 
>>>>> Hey Ian,
>>>>> 
>>>>> Could you try running “ 
>>>>> /opt/perfsonar_ps/toolkit/scripts/discover_external_address “ as root, 
>>>>> and then try to restart the perfsonarbuoy_ma?
>>>>> 
>>>>> Cheers,
>>>>> Aaron
>>>>> 
>>>>> On Mar 24, 2014, at 4:39 PM, Ian Gable 
>>>>> <>
>>>>>  wrote:
>>>>> 
>>>>>> Hi All,
>>>>>> 
>>>>>> I’ve receiving the following error message in my perfsonarbuoy_ma.log:
>>>>>> 
>>>>>> 2014/03/24 15:00:08 (2975) ERROR> daemon.pl:380 main:: - Failed to 
>>>>>> initialize module perfSONAR_PS::Services::MA::perfSONARBUOY on 
>>>>>> 8085:/perfSONAR_PS/services/pSB
>>>>>> 2014/03/24 16:00:08 (4208) WARN> daemon.pl:262 main:: - Setting 
>>>>>> listener queue size to 100
>>>>>> 2014/03/24 16:00:08 (4208) WARN> daemon.pl:267 main:: - Setting LS 
>>>>>> registration interval at 60 minutes
>>>>>> 2014/03/24 16:00:08 (4208) WARN> daemon.pl:272 main:: - Enabling echo 
>>>>>> service for each endpoint unless specified otherwise
>>>>>> 2014/03/24 16:00:08 (4208) 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
>>>>>> 
>>>>>> In the past, I remember this error being caused by having a strange 
>>>>>> entry in the hosts files or by having multiple interfaces with public 
>>>>>> IPs. However this hosts has normal /etc/hosts and only a single 
>>>>>> interface.
>>>>>> 
>>>>>> The web interface of the host can be viewed at: 
>>>>>> http://ps-latency.clumeq.mcgill.ca/toolkit/
>>>>>> 
>>>>>> Ideas?
>>>>>> 
>>>>>> Ian
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> —
>>>>>> Ian Gable
>>>>>> HEPnet Canada, University of Victoria
>>>>>> 
>>>>>> +1 250 721 7728
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 
>