perfSONAR User Q&A and Other Discussion

["Garnizov, Ivan (RRZE)" <>]

Hi ChanJin Park,

 

Please note pS 4.0 has still not reached final release state, so it should be expected to have some deficiencies.

You have to keep in mind and understand, that pS 4.0 will bring a totally new experience on test coordination and test trigger process. Namely pS team introduces a new scheduler service – pscheduler.

From your email it does not become clear, if the remote system is also pS4.0 RC2 deployment.

In all cases information about the events and possible issues should be sought in /var/log/pscheduler/pscheduler.log

 

To be able to further help you it would be nice, if you can provide us with the configuration in /etc/perfsonar/meshconfig-agent-tasks.conf

Please make sure you remove the password fields, if there are any.

 

With regards to your verification test: As I have noted the pS 4.0 introduces a new coordination mechanism/tool pscheduler. Your test currently demonstrates only that your system is still able to coordinate a measurement with older pS releases.

 

Regards,

Ivan Garnizov

 

GEANT SA1T2: pS deployments GN Operations

GEANT SA2T3: pS development team

GEANT SA3T5: eduPERT team

 

 

From: [mailto:] On Behalf Of ???_KISTI
Sent: Mittwoch, 8. Februar 2017 04:00
To:
Subject: [perfsonar-user] Questions aboud perfsonar 4.0

 

 

Hello!

 

I’m ChanJin Park working on KISTI(KREONET).

 

I have downloaded perfsonar 4.0(pS-Toolkit-4.0rc2-CentOS7-FullInstall-x86_64-2016Nov01) and installed it on dell server(R720).

 

After that I have set configure Test on web UI, but I can get Test Results.

 

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

 

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

So I tried bwctl to 134.75.250.194 on terminal. It worked well.

 

---result----------------------------------------------------------------------------------------------

 

[root@localhost init.d]# bwctl -c 134.75.250.194

bwctl: Using tool: iperf3

bwctl: 17 seconds until test results available

 

SENDER START

Connecting to host 134.75.250.194, port 5294

[ 15] local 134.75.250.115 port 59540 connected to 134.75.250.194 port 5294

[ ID] Interval           Transfer     Bandwidth       Retr  Cwnd

[ 15]   0.00-1.00   sec  18.7 MBytes   157 Mbits/sec    0    387 KBytes

[ 15]   1.00-2.00   sec  11.2 MBytes  94.4 Mbits/sec    0    390 KBytes

[ 15]   2.00-3.00   sec  11.2 MBytes  94.4 Mbits/sec    0    390 KBytes

[ 15]   3.00-4.00   sec  11.2 MBytes  94.4 Mbits/sec    0    390 KBytes

[ 15]   4.00-5.00   sec  11.2 MBytes  94.4 Mbits/sec    0    390 KBytes

[ 15]   5.00-6.00   sec  11.2 MBytes  94.4 Mbits/sec    0    390 KBytes

[ 15]   6.00-7.00   sec  11.2 MBytes  94.4 Mbits/sec    0    390 KBytes

[ 15]   7.00-8.00   sec  11.2 MBytes  94.4 Mbits/sec    0    390 KBytes

[ 15]   8.00-9.00   sec  11.2 MBytes  94.4 Mbits/sec    0    390 KBytes

[ 15]   9.00-10.00  sec  11.2 MBytes  94.4 Mbits/sec    0    393 KBytes

- - - - - - - - - - - - - - - - - - - - - - - - -

[ ID] Interval           Transfer     Bandwidth       Retr

[ 15]   0.00-10.00  sec   120 MBytes   101 Mbits/sec    0             sender

[ 15]   0.00-10.00  sec   112 MBytes  94.3 Mbits/sec                  receiver

 

iperf Done.

 

SENDER END

------------------------------------------------------------------------------------------------------

 

NTP also works well

-----result---------------------------------------------------------------------------------------------------------------------------------------

[root@localhost init.d]# ntpq -p

     remote           refid      st t when poll reach   delay   offset  jitter

==============================================================================

+114.207.245.175 141.223.182.106  2 u  163  512  377    4.264   -8.970   0.762

114.207.245.166 .INIT.          16 u    - 1024    0    0.000    0.000   0.000

*210.98.16.100   210.98.22.61     2 u  177  512  377    0.656    0.921   0.254

+210.98.16.101   210.98.16.100    3 u  442  512  377    1.123    1.108   3.804

 

 

So I checked log but I couldn’t find regulartesing log. And I couldn’t perfsonar-regulartesting file on /etc/init.d.

 

 

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

 

 

[root@localhost init.d]# ls

bwctl-server.pid  functions   network                             perfsonar-generate_motd  pscheduler-archiver  pscheduler-scheduler  README

cassandra         netconsole  perfsonar-configure_nic_parameters  perfsonar-psb_to_esmond  pscheduler-runner    pscheduler-ticker

 

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

 

I don’t know why it dosen’t work. Could you help me ??

 

Thaknks.

 

-------------------------------------------------------------------------------------------------------

ChanJin Park <>

Researcher, KREONET operation and service Div of Supercomputing/KRONET Center

Korea Institute of Science and Technology Information.

245 Deahangno, Yuseong, Daejeon, Korea, 34141

Phone : +82-42-869-1999  Fax : +82-42-869-0509

--------------------------------------------------------------------------------------------------------