perfSONAR User Q&A and Other Discussion

[Winnie Lacesso <>]

Dear Perfsonar experts,

Bandwidth box was rebooted 6 Feb. I notice (today, might've been same 
before but didn't notice then) that its main web page says NDT is running. 

The documentation says NDT & NPAD should not run on any box running 
Regular Testing, which both our Bandwidth & Latency boxes are.

So click on Enabled Services in the web admin - but NDT is not checked on! 
But the web interface says it's running. How does it determine that? 

There are indeed ndt processes running.

root     21697     1  0 Feb08 ?        00:00:00 /usr/sbin/web100srv -a -s -l 
/var/log/ndt/web100srv.log
root     21700     1  0 Feb08 ?        00:00:00 /usr/sbin/fakewww -f 
/index.html -s -l /var/log/ndt/fakewww_access.log -e 
/var/log/ndt/fakewww_error.log

rpm -qf says both /usr/sbin/web100srv & /usr/sbin/fakewww are part of 
ndt-server package.

Since the box was rebooted 6 Feb, something has since started these since 
it was rebooted.
chkconfig does not show any ndt; I guess something did chkconfig --del on  
them; yet something else also started the above ndt processes.

ndt-3.6.5.2-6.el6.i386.rpm
ndt-client-3.6.5.2-6.el6.i386.rpm
ndt-server-3.6.5.2-7.i386.rpm

Unfortunately trying to yum remove ndt* wants to remove some  
perl-perfSONAR_PS-Toolkit* packages, so they must instead be properly SHUT  
OFF.

Our Latency box webpage shows that ndt is Disabled, chkconfig shows ndt as  
off, but it too has an ndt-server process running

root     18163     1  0 03:58 ?        00:00:00 /usr/sbin/fakewww -f 
/index.html -s -l /var/log/ndt/fakewww_access.log -e 
/var/log/ndt/fakewww_error.log

It too was rebooted 6 Feb so something started this one in the wee hours  
just today.

From the main web page for either Bw or Lat box, "NDT Log Analysis" says 
"No NDT test results were found." The /var/log/ndt/* lots are just full of 
probes from APNIC, LANIC, google, & other places I don't welcome.

What surreptitiously starts these ndt processes & how to get it to STOP? 

The firewall config for both of these (built by someone else) ACCEPTs 
packets to 7123* - That will change to DROP right now.

* the network these are on is un-firewalled for ports > 1024; handy in a 
way, dangerous in another way.

VERY Grateful for advice!

Winnie Lacesso / Bristol University Particle Physics Computing Systems
HH Wills Physics Laboratory, Tyndall Avenue, Bristol, BS8 1TL, UK