perfSONAR User Q&A and Other Discussion

[Aaron Brown <>]

Hey Shawn,

Comments inline

On Jan 15, 2015, at 1:55 PM, Shawn McKee <> wrote:

Hi Dan,

Here are some more example "error" messages that likely aren't.  I am not sure if Aaron has fixed any of these already.

The following are all classified as 'error' level:

<171>Jan 15 13:40:56 psum06.aglt2.org bwctld[8390]: FILE=bwctld.c, LINE=446, Reservation Status: time=1421347256 action="remove" sender=129.93.5.165 receiver=192.41.230.62 tool=iperf res_start=1421347221 res_end=1421347255 test_start=1421347223

<171>Jan 15 13:40:55 psum02.aglt2.org bwctld[15734]: FILE=bwctld.c, LINE=446, Reservation Status: time=1421347255 action="new" sender=192.41.230.60 receiver=164.58.29.118 tool=traceroute res_start=1421347258 res_end=1421347272 test_start=1421347260

In the next bwctl release, these will all be debug level (i.e. you’ll need to use the ‘verbose’ option in bwctld.conf to see them).

<11>Jan 15 13:40:54 psum02.aglt2.org bwtraceroute: Client 'ps-bandwidth.clumeq.mcgill.ca' accepted test request at time 1421347260.090573

This is a property of the same command-line flag meaning “get verbose information from the server” and “provide verbose information in the bwctl client” so won’t be an easy fix

<171>Jan 15 13:40:55 psum02.aglt2.org bwctld[15734]: FILE=bwctld.c, LINE=795, Test Reservation Information: Current Time: 1421347255, Fuzz: 1.873047, Reservation Start: 1421347258, Reservation End: 1421347273, Test Start Time: 1421347260

<171>Jan 15 13:47:45 psum02.aglt2.org bwctld[15734]: FILE=bwctld.c, LINE=826, Time Slots

<171>Jan 15 13:50:09 psum02.aglt2.org bwctld[15734]: FILE=bwctld.c, LINE=831, Time Slot 58: 1421347826 to 1421347827: 1 reservations

See above about the next release

<11>Jan 15 13:52:00 psum02.aglt2.org bwtraceroute: Server 'psum02.aglt2.org' accepted test request at time 1421347926.615590

This one may be an error, but perhaps warning?

<171>Jan 15 13:46:26 psum02.aglt2.org bwctld[3271449]: FILE=endpoint.c, LINE=1314, PeerAgent: Peer cancelled test before expected

This is an error. It means the test failed. We could maybe swap it to be a warning or something.

My logging system would appreciate anything you can do to fix these :)

Thanks,

Shawn

On Thu, Jan 15, 2015 at 9:37 AM, Daniel Doyle <> wrote:

Hiro,

That message is a debug or maybe info message that appears to be logging at the incorrect level of error. It's actually the "success" message of that function, so seeing it is a good thing. You could stop it by making the log4perl configuration not log errors, although I would strongly not recommend that because it would mean actual errors would be getting ignored as well and future debugging of any issues would be quite hard.

I'll go ahead and commit this as a fix in the repository, but in the meanwhile if you want to manually shut it up you can edit line 107 in /opt/perfsonar_ps/regular_testing/lib/perfSONAR_PS/RegularTesting/Master/SelfScheduledTestChild.pm

from

$logger->error

to

$logger->debug


Thanks,
-Dan

On Jan 14, 2015, at 10:38 AM, Hironori Ito <> wrote:

> Hello.
>
> I see the following messages repeatedly in the log (regular_testing.log).
>
>
> 2015/01/14 10:35:28 (2232) ERROR> SelfScheduledTestChild.pm:107
> perfSONAR_PS::RegularTesting::Master::SelfScheduledTestChild::save_results
> - Enqueued test results for measurement archive: esmond_latency_localhost
>
>
> My question is what the message means.  Is this instance of Perfsonar
> broken or configured incorrectly?  If not, can this be stopped by
> changing configuration?
>
> thanks,
>
> Hiro

Dan Doyle
GlobalNOC Software Developer
1-812-856-3892