perfSONAR User Q&A and Other Discussion

[Roderick Mooi <>]

Hi!

This is related to my previous email “Mesh config for bwctl scheduled tests using time_slot” but should precede it.

ref: http://docs.perfsonar.net/config_regular_testing.html#config-regular-testing-schedules

I setup a test via the perfsonar GUI (toolkit web interface) and then attempted to change it to a time-scheduled test by changing the <schedule> section as follows:

    <schedule>

time_slot   17:00|19:00|21:00|1:00|3:00

        type   time_schedule

    </schedule>

I then restarted the regulartesting service. No errors but no test/bwctl processes either. I was expecting this to translate to a bwctl process with —schedule 17:00,19:00,21:00,1:00,3:00.

In the regulartesting.log I see entries like this:

2016/07/13 16:18:02 (48626) ERROR> CmdRunner.pm:148 perfSONAR_PS::RegularTesting::Utils::CmdRunner::run - Command exited, will restart in 300 seconds : /usr/bin/bwctl -s p1p1 -c x.x.x.x -T iperf3,iperf -B p1p1 -4 --schedule 17:00|19:00|21:00|1:00|3:00 -p -d /var/lib/perfsonar/regulartesting/bwctl_Oi0xl -v -P 1 -t 25 -O 5 -i 1 --parsable

Ah ok, | instead of ,’s. I tried changing <schedule> to:

    <schedule>

time_slot   17:00,19:00,21:00,1:00,3:00

        type   time_schedule

    </schedule> 

And it works! (bwctl process correctly started)

Thanks a lot!

Roderick

--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean.

Please consider the environment before printing this email.