perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

You can ignore the “Not running” on the main page. Someone else reported the same issue today and it appears to be detecting that service incorrectly. We will push out a bug fix for that shortly.

As for the 500 errors, anything in /var/log/httpd/error_log or any of the files under /var/log/esmond?

Thanks,

Andy

On June 1, 2016 at 12:19:13 PM, () wrote:

I had an unauthorized 401 error in my regular testing logs, but I did a yum
update and rebooted and it went away. Now what I'm dealing with is the
regular testing status on the GUI is showing "Not Running". I checked the
status via the CLI and it said it was not started, so I manually started it,
but it is still showing not connected.

./perfsonar-regulartesting status
perfSONAR Regular Testing (pid 23031?) not running


sudo ./perfsonar-regulartesting start
/usr/lib/perfsonar/bin/regulartesting.pl
--config=/etc/perfsonar/regulartesting.conf --pidfile=regulartesting.pid
--piddir=/var/run --logger=/etc/perfsonar/regulartesting-logger.conf
--user=perfsonar --group=perfsonar --daemonize
./perfsonar-regulartesting start: perfSONAR Regular Testing started


./perfsonar-regulartesting status
perfSONAR Regular Testing (pid 23902) running


Below is what is shown in the regulartesting.log

SERVER ERROR at
/usr/lib/perfsonar/bin/../lib/perfSONAR_PS/RegularTesting/Master/MeasurementAr
chiveChild.pm line 122.
2016/06/01 09:16:20 (24140) ERROR> EsmondBase.pm:53
perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::__ANON__ -
Error writing metadata (500) 500 INTERNAL SERVER ERROR
2016/06/01 09:16:20 (24140) ERROR> MeasurementArchiveChild.pm:209
perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::handle_results
- Problem storing results: Error writing metadata: 500 INTERNAL SERVER ERROR
2016/06/01 09:16:20 (24140) ERROR> MeasurementArchiveChild.pm:125
perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::__ANON__ -
Problem handling test results: Problem storing results: Error writing
metadata: 500 INTERNAL


Any ideas on how to fix this? Or should I just wipe the box and start from
fresh?