Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] [non-nasa source] [EXTERNAL] FW: Defining single-ended throughput tests inside a psconfig template

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] [non-nasa source] [EXTERNAL] FW: Defining single-ended throughput tests inside a psconfig template


Chronological Thread 
  • From: Mark Feit <>
  • To: "Uhl, George D. (GSFC-423.0)[SGT INC]" <>, "" <>
  • Subject: Re: [perfsonar-user] [non-nasa source] [EXTERNAL] FW: Defining single-ended throughput tests inside a psconfig template
  • Date: Fri, 13 Sep 2019 21:50:24 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.edu; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=+bq572WsxV4SwoFBaK772DzSbsGExgdVO/MMv6xSr5c=; b=bm550vTqlby1okKnNS4XgfIkhGj1rDzmKXK7fRaOQqUj1W5TVBrnGgj9vs/pB1ipiij7GRW/Xi9tuWTqQSzAeDiIbBpTCXTDbOnXkbRx9Ah4I0as+KB/VNR7BiCEEeC/9L8uJgHaOn1IgEiw/YKP1r3O2ylj0SakwZ09mB59n0xy13kJJGU11QF0CagbcYN/ard9cKp45cwKN15O3pTbmiOl+GgBeuQVA+gcPTqn+aqKV+c41qK8Xuph8KYeTUiJSX/VGr4nebKz7gE7AtII0/vMmo1vI1rQg8cRwWeHScywaG1gRsSWOfLKIoe806tJTTwg13mKwovzzfZs2VgU0Q==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eFSuAMVZcjssNVi6KDITRldlCtRf9K3rkaWktaDwR8OSgkk2TcmUuAhtX5yAXXaETUMyA5THv/FD67QZJcMqonFX3cfT4G94I6LCB2KmFLT/g2i5RvOlUbbuvH9Mi1ZmjVxd2UvRlUC2x2QYkP8JPqUGguYHikxNrgaJmFQ2rpj090V97spO9Udc4T5USMtVtEaSJX9QU1B5FO/exSrs/DeeEy95IjBnTOCh8vH9kaAt472gafIIBC0W9AN2Wj5wrjdWnriPS9jTQmBFor1rnMqWsXxU8DkWsTos42SjMH5Uj6qNbqeOOHx9/LveEQQKdjbtquXwWYr385EUWyEqTw==

Uhl, George D. (GSFC-423.0)[SGT INC] writes:

 

I’m still unable to get the single-ended A-to-B reverse throughput test results to appear in my archives as a B-to-A forward throughput test after including your script in my psconfig template.  There isn’t enough information in /var/log/pscheduler.log to shine a light on what’s happening.  I did try running this with pscheduler on the CLI in debug and archive mode but I don’t see the transformation taking place.

 

The CLI’s --debug switch just debugs the CLI and its interactions with pScheduler, so you won’t get much useful out of that.  (I did write a ticket on making --debug enable per-task/run debugging in the services that run pScheduler behind the scenes:  https://github.com/perfsonar/pscheduler/issues/926.  I don’t guarantee it will happen, but we at least have the idea written down.)

 

  I tried it again but instead of archiving to Esmond, I used syslog and it appears in this case that the transform script might have worked.  Is there a way to track the Esmond archive processing in more detail?

 

Yes, there is.  What you’ll need to do is enable debugging in the archiver service by running “pscheduler debug on archiver” as root on the (lead) server.  That will turn on debugging in the archiver itself and also whatever plugins it runs.  The debug will be in the pScheduler log.  You should see the archiver doing the transform on the measurement and what the plugin is sending to Esmond.

 

If you continue to have problems, drop me a line off-list and we can jump on Zoom and have a look at it.

 

--Mark

 




Archive powered by MHonArc 2.6.19.

Top of Page