perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi,

It might help, looks like maybe the auth credentials are wrong for the regular testing. The following should regenerate them:

rm -rf /var/lib/pgsql/data/*

/opt/perfsonar_ps/toolkit/scripts/system_environment/configure_esmond 

/opt/perfsonar_ps/toolkit/scripts/system_environment/configure_regular_testing

/etc/init.d/httpd restart

/etc/init.d/regular_testing start

Andy

On Oct 9, 2014, at 4:37 PM, Zhi-Wei Lu <> wrote:

Hi Andy,

 

We were able to get back on track with the GUI by following your recipe, but we are getting problems of storing data, do we need to re-initialize postgres database?

 

Here were some errors that we saw on out log file:

 

2014/10/09 13:36:51 (10175) WARN> daemon:103 main::__ANON__ - Warned: Use of uninitialized value in pattern match (m//) at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/MeasurementArchives/EsmondBase.pm line 334.

2014/10/09 13:36:51 (10175) DEBUG> EsmondBase.pm:251 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::send_post - Writing to esmond at http://localhost/esmond/perfsonar/archive/

2014/10/09 13:36:51 (10175) DEBUG> EsmondBase.pm:252 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::send_post - Esmond request: {"tool-name":"bwctl/ping","source":"169.237.246.133","time-probe-interval":1,"measurement-agent":"169.237.246.133","destination":"128.120.80.74","ip-ttl":"255","ip-transport-protocol":"icmp","ip-packet-size":"995","event-types":[{"event-type":"failures"},{"event-type":"packet-count-sent"},{"event-type":"histogram-rtt","summaries":[{"summary-type":"aggregation","summary-window":"86400"},{"summary-type":"statistics","summary-window":"86400"},{"summary-type":"statistics","summary-window":"0"}]},{"event-type":"histogram-ttl-reverse"},{"event-type":"packet-duplicates-bidir"},{"event-type":"packet-loss-rate-bidir"},{"event-type":"packet-count-lost-bidir"},{"event-type":"packet-reorders-bidir"}],"time-interval":"300","subject-type":"point-to-point","input-destination":"p51.noc.ucdavis.edu","sample-size":10,"input-source":"169.237.246.133"}

2014/10/09 13:36:51 (10175) DEBUG> EsmondBase.pm:257 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::send_post - Esmond repsonse:

2014/10/09 13:36:51 (10175) ERROR> EsmondBase.pm:53 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::__ANON__ - Error writing metadata (401) 401 UNAUTHORIZED

2014/10/09 13:36:51 (10175) ERROR> MeasurementArchiveChild.pm:209 perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::handle_results - Problem storing results: Error writing metadata: 401 UNAUTHORIZED

2014/10/09 13:36:51 (10175) ERROR> MeasurementArchiveChild.pm:125 perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::__ANON__ - Problem handling test results: Problem storing results: Error writing metadata: 401 UNAUTHORIZED at /opt/perfsonar_ps/regular_testing/bin/../lib/perfSONAR_PS/RegularTesting/Master/MeasurementArchiveChild.pm line 122.

 

Thank you very much for your help.

 

Zhi-Wei Lu

IET-CR-Network Operations Center

University of California, Davis

(530) 752-0155

 

From: Andrew Lake [mailto:andy@es.net] 
Sent: Wednesday, October 08, 2014 5:13 PM
To: Zhi-Wei Lu
Cc: 
Subject: Re: [perfsonar-user] perfSonar 3.4x web gui missing in action

 

Hi,

 

Prior to RC3 (and again when we released RC3) we provided some special upgrade instructions for RC2 users to prevent this. RC2 points at the CentOS SCL repo, which decided to add their own version of python27-mod_wsgi which does not work with the standard apache and overwrites the version we provided.

 

No worries though, you should be able to get your host back to normal. Run the following:

 

yum remove centos-release-SCL python27-mod_wsgi python27 python27-python httpd24-httpd httpd24-apr httpd24-apr-util httpd24-httpd-tools httpd24-runtime scl-utils

yum clean all

rm -rf /var/lib/pgsql/data/*

yum install perl-perfSONAR_PS-Toolkit perl-perfSONAR_PS-Toolkit-SystemEnvironment

reboot

 

Thanks,

Andy

 

 

On Oct 8, 2014, at 6:17 PM, Zhi-Wei Lu <> wrote:

Hi all,

 

We have a perfSonar 3.4rc2 test box running. We have recently updated the system and it has those perfSONAR packages:

 

perl-perfSONAR-OPPD-MP-Shared-3.4-2.pSPS.noarch

perl-perfSONAR_PS-Toolkit-3.4-25.pSPS.noarch

perl-perfSONAR_PS-LSCacheDaemon-3.4-1.pSPS.noarch

perl-perfSONAR_PS-MeshConfig-Shared-3.4-12.pSPS.noarch

perl-perfSONAR-OPPD-MP-BWCTL-3.4-2.pSPS.noarch

perl-perfSONAR_PS-RegularTesting-3.4-15.pSPS.noarch

perl-perfSONAR_PS-Toolkit-SystemEnvironment-3.4-25.pSPS.noarch

perl-perfSONAR_PS-SimpleLS-BootStrap-client-3.4-3.pSPS.noarch

perl-perfSONAR-OPPD-MP-OWAMP-3.4-2.pSPS.noarch

perl-perfSONAR_PS-serviceTest-3.4-13.pSPS.noarch

perl-perfSONAR-OPPD-MP-server-3.4-1.pSPS.noarch

perl-perfSONAR_PS-LSRegistrationDaemon-3.4-2.pSPS.noarch

perl-perfSONAR_PS-MeshConfig-JSONBuilder-3.4-12.pSPS.noarch

perl-perfSONAR-OPPD-MP-server-3.4-2.pSPS.noarch

perl-perfSONAR_PS-MeshConfig-Agent-3.4-12.pSPS.noarch

 

The perfsonar daemon appears to be running on the system, but the web GUIS is not

 

/etc/init.d/httpd status

httpd is stopped

 

/etc/init.d/httpd start

Starting httpd: Syntax error on line 1 of /etc/httpd/conf.d/apache-esmond.conf:

Invalid command 'WSGIScriptAlias', perhaps misspelled or defined by a module not included in the server configuration

                                                           [FAILED]

 

The wsgi modules for the (system) httpd is not installed.  However, I noticed that there is a new package httpd24 along with its own wsgi module, I am able to start the httpd24-httpd daemon, but the familiar toolkit is nowhere to be seen on the web GUI.

 

Could someone shed some light on how I suppose get the new perfSONAR going?

 

Thank you very much for your help.

 

Zhi-Wei Lu

IET-CR-Network Operations Center

University of California, Davis

(530) 752-0155