perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

On Fri, Jul 31, 2015 at 7:15 AM, Winnie Lacesso <> wrote:

Happy Friday!

And actually - Happy SysAdmin day too! (to us all!)
http://sysadminday.com/
July 31, 2015 - 16th Annual System Administrator Appreciation Day !

On Fri, 24 Jul 2015, Shawn McKee wrote:
> The /opt/perfsonar_ps/regular_testing/etc/regular_testing.conf will contain
> the IP address but as long as you are using the mesh configuration, the next

Erm, one can't contradict the PerfSonar experts, but I don't see *any* IP
addrs in regular_testing.conf, at all. Lots & lots of FQDN, among them the
perfsonar host in question.

I guess I should have said *might* instead of *will*. Depending on the setup it'll have either the IP or FQDN, in your case it sounds like the FQDN so no further changes needed,

 

Righto, they are now on the new subnet, GOC-DB is changed.

A tiny concern, /var/log/perfsonar/regular_testing.log is logging what look
like errors:

2015/07/31 11:51:52 (31039) ERROR> MeasurementArchiveChild.pm:125
perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::__ANON__ -
Problem handling test results: Problem storing results: Error writing
metadata: 500 Can't connect to localhost:80 (connect: Connection refused) at
/opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Master/MeasurementArchiveChild.pm
line 122.

I don't see any IP addr embedded in /etc/httpd/conf* or  /etc/cassandra/*

/var/log/httpd/error_log logs errors too:

[Fri Jul 31 12:05:55 2015] [error] path= ['/opt/esmond/esmond', '/opt/esmond/src/dlnetsnmp/lib', '/opt/esmond', '/opt/esmond/esmond_client', '/opt/esmond/lib/python27.zip', '/opt/esmond/lib/python2.7', '/opt/esmond/lib/python2.7/plat-linux2', '/opt/esmond/lib/python2.7/lib-tk', '/opt/esmond/lib/python2.7/lib-old', '/opt/esmond/lib/python2.7/lib-dynload', '/opt/rh/python27/root/usr/lib/python2.7', '/opt/rh/python27/root/usr/lib/python2.7/plat-linux2', '/opt/esmond/lib/python2.7/site-packages']
[Fri Jul 31 12:05:56 2015] [error] cassandra_db [INFO] Checking/creating column families
[Fri Jul 31 12:05:56 2015] [error] cassandra_db [INFO] Schema check done
[Fri Jul 31 12:05:56 2015] [error] cassandra_db [DEBUG] Opening ConnectionPool
[Fri Jul 31 12:05:56 2015] [error] cassandra_db [INFO] Connected to ['localhost:9160']

As it happens the room they're in is losing power tonight so they'll be
shutdown by 16:00 today & rebooted Monday morning.
Hopefully all will be well on the new subnet.

Let me know if the error in regular_testing.log persists on reboot. It can't connect to localhost port 80 which would likely only happen if Apache is not up. Have those error messages stopped? I am wondering if apache was down for some reason and then came back. Looks like from the apache log you sent all was well from apache's perspective at 12:05.