perfSONAR User Q&A and Other Discussion

[<>]

Rade,

 

Thank you for the response!

 

I can recall that during the install there was an nonerror or warning related to the derby jar file, something that it can’t “stat” for the file.

The error was at the end of the ui RPM install.

 

Unfortunately I don’t have these logs now. Sorry.

 

Here’s my environment:

 

[root@ldtcperfs01 ~]# uname -a

Linux ldtcperfs01.fremont.lamrc.net 2.6.32-573.1.1.el6.x86_64 #1 SMP Sat Jul 25 17:05:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

[root@ldtcperfs01 ~]# rpm -qa | grep tomcat

tomcat6-servlet-2.5-api-6.0.24-90.el6.x86_64

tomcat6-6.0.24-90.el6.x86_64

tomcat6-lib-6.0.24-90.el6.x86_64

tomcat6-jsp-2.1-api-6.0.24-90.el6.x86_64

tomcat6-el-2.1-api-6.0.24-90.el6.x86_64

[root@ldtcperfs01 ~]# rpm -qa | grep java

java_cup-0.10k-5.el6.x86_64

java-1.5.0-gcj-1.5.0.0-29.1.el6.x86_64

tzdata-java-2015e-1.el6.noarch

java-1.7.0-openjdk-1.7.0.85-2.6.1.3.el6_7.x86_64

java-1.6.0-openjdk-1.6.0.36-1.13.8.1.el6_7.x86_64

[root@ldtcperfs01 ~]# rpm -qa | grep perf

perl-perfSONAR_PS-MeshConfig-JSONBuilder-3.5-0.4.rc1.pSPS.noarch

perl-perfSONAR-OPPD-MP-Shared-3.5-0.1.rc1.pSPS.noarch

perfsonar-ui-web-1.5.1-1.noarch

perl-perfSONAR_PS-Toolkit-service-watcher-3.5-0.11.rc1.pSPS.noarch

perl-perfSONAR_PS-Toolkit-security-3.5-0.11.rc1.pSPS.noarch

iperf-2.0.5-12.el6.x86_64

perl-perfSONAR_PS-Toolkit-Library-3.5-0.11.rc1.pSPS.noarch

perl-perfSONAR-OPPD-MP-server-3.5-0.1.rc1.pSPS.noarch

perl-perfSONAR-OPPD-MP-OWAMP-3.5-0.1.rc1.pSPS.noarch

perl-perfSONAR_PS-Toolkit-Install-Scripts-3.5-0.11.rc1.pSPS.noarch

perl-perfSONAR_PS-RegularTesting-3.5-0.2.rc1.pSPS.noarch

perl-perfSONAR_PS-Toolkit-SystemEnvironment-3.5-0.11.rc1.pSPS.noarch

perl-perfSONAR_PS-MeshConfig-GUIAgent-3.5-0.4.rc1.pSPS.noarch

perl-perfSONAR_PS-Toolkit-sysctl-3.5-0.11.rc1.pSPS.noarch

perl-perfSONAR_PS-Toolkit-3.5-0.11.rc1.pSPS.noarch

perl-perfSONAR_PS-Toolkit-ntp-3.5-0.11.rc1.pSPS.noarch

perl-perfSONAR_PS-MeshConfig-Shared-3.5-0.4.rc1.pSPS.noarch

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

perl-perfSONAR_PS-serviceTest-3.5-0.1.rc1.pSPS.noarch

perl-perfSONAR_PS-LSRegistrationDaemon-3.5-0.2.rc1.pSPS.noarch

perl-perfSONAR_PS-Nagios-3.5-0.1.rc1.pSPS.noarch

perl-perfSONAR_PS-MeshConfig-Agent-3.5-0.4.rc1.pSPS.noarch

iperf3-3.1b3-1.el6.x86_64

perl-perfSONAR-OPPD-MP-BWCTL-3.5-0.1.rc1.pSPS.noarch

[root@ldtcperfs01 ~]#

 

--- Eugene

 

 

From: Rade Martinović [mailto:]
Sent: Wednesday, August 12, 2015 1:55 PM
To: Nesterenko, Eugene;
Subject: Re: [perfsonar-user] RE: Perfsonar UI errors - new install

 

Hi Eugene,

 

I am the developer of the perfSONAR UI. 

 

First, I am sorry for not responding to you sooner. Although I am on the vacation I could have reacted much sooner. Ivan contacted me directly but I didn't have the time to take a serious look at the problem you have reported until now. 

 

About the problem, I have tested the RPM with Centos 6 VMs. Although I did not test it thoroughly with ps toolkit installed. There may be some inter-dependencies that caused Derby driver not ending up in the proper directory.

 

I want to give you kudos for solving the problem yourself. I would appreciate if you could share with me the version of Centos, Tomcat, ps toolkit and psUI you have used so I could recreate this problem on my testing VMs and solve it.

 

If you are have suggestions, comments or bug reports on psUI, please share those with me, or here at perfsonar-user, I am always interested in feedback from users. 

 

Best regards,

 

-- Rade

Sent from Outlook