perfSONAR User Q&A and Other Discussion

[Victor Olifer <>]

Hi Aaron, 

Thanks, it fixed the problem. So, it’s some web interface bug that doesn’t put the port number in regular_testing.conf, isn’t it? 

As for  my guess that it worked before – I might accidentally enter a host address in [address]:888 form and it was put into the config file 'as is’.

Aaron, another question - is it possible to get rid of deleted test results (or any results)? I understand this option  wasn’t included deliberately but maybe you have some script that cleaning some particular data in the database? 

Thanks, 

Victor   

From: Aaron Brown <>
Date: Wednesday, 17 December 2014 14:56
To: VictorO <>
Cc: "" <>
Subject: Re: [perfsonar-user] non-standard OWAMP control port

Hey Victor,

Can you try manually editing /opt/perfsonar_ps/regular_testing/etc/regular_testing.conf, and change the “address” fields in the owamp test to take the form: “[address]:888”, and then restart the regular_testing daemon, and then see if it starts working? That’s not changed, so I’m surprised it ever worked.

Cheers,

Aaron

On Dec 16, 2014, at 7:02 AM, Victor Olifer <> wrote:

Hi, 

Sorry if somebody has already risen this but I just discovered that toolkit 3.4 doesn’t support non-standard OWAMP control ports and always uses the default value  861 even when some other port was specified in Add New Host  pane.  It can be seen in different ways: 

-  tcpdump shows that owamp requests go out with 861 instead of 888 in my case; 

- regular_testing.log has repeating OWPControlOpen(apus.carnet.hr): Couldn't open 'control' connection to server: Connection refused

- regular_testing.conf has no information about a OWAMP control port value at all. 

What’s more the web page of Add New Host allows to enter a non-standard OWAMP port value only initially but doesn’t have  afield for a port when I open it for editing the Test member parameters. 

At the same time owping –c 10 apus.carnet.hr:888 works without any problems, showing plausible data for both directions. 

I believe that after installation toolkit 3.4 didn’t have this problem, it appeared very recently, maybe last week (probably after some auto update?). 

Does anybody else use a non-standard owamp control port? 

Best, 

Victor  

Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.

Jisc Collections and Janet Ltd. is a wholly owned Jisc subsidiary and a company limited by guarantee which is registered in England under Company No. number 2881024, VAT No. GB 197 0632 86. The registered office is: Lumen House, Library Avenue, Harwell, Didcot, Oxfordshire, OX11 0SG. T 01235 822200.