Skip to Content.
Sympa Menu

perfsonar-user - [perfsonar-user] Problem with getting pscheduler tasks to archive locally

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Problem with getting pscheduler tasks to archive locally


Chronological Thread 
    < Chronological >      < Thread >
  • From: Brian Tehan <>
  • To: "" <>
  • Subject: [perfsonar-user] Problem with getting pscheduler tasks to archive locally
  • Date: Mon, 24 Jul 2023 13:31:59 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nebraska.edu; dmarc=pass action=none header.from=nebraska.edu; dkim=pass header.d=nebraska.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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=1qwMiaKhKtyogVUBf1gTtgtSHhEHw6NiTiLu2FTGxfQ=; b=Lz02RjkgabqPF/lXfvdTHjBFIaeZEsK66zmGIlOStgCnrCG4Ln7jQLKnkam/O7TaXqbeQ9seZkqcXFhRcCYkCi0o8RfBhX1pC6+1zG6tfz3Ia+Alz7biFQf9eCeJa1RrewA3o0VmMGOZN8ORDFExWalKMOywmr6ODOMFml3gHbvbPa764O4VNQry1Q7ncFRps6j+5h5U6j0Q9H5NqdpsM/LVm3fnrSds3NuAGrrYP+Nw+OuJS/euefC23HGin5i/i5HqK6W1vM8bUHzny2UQcymtVXB1N32QMEQIUma1w1JTCPlWe9R/4mbzqZwFR0x8bdb5dyzpH/U+eQvlAp/m2g==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Z0SgP50gdTXchYAhSOcnTUVvcc5Cfvx+L9e+vLp5SgQmcy1oD7ZG6/Bauqj6VfAx9rx4rg+jYiT3BU2IOnp/WbeAqCCL7hrNdu8tzg6SMc1k5qUQvpuO7+sgu3TWKdWk2z031y83VJ62gaTVvVoi6O8YCi9sMFbOrXdWzMX4NMCDED7MKKkJ6bvpCwduvW6Xc+v0keXJjMtIBCusCo9XAshzetogewWlwqxTG7FtjZkNQ2XrFkAODB27SxmGCOJwRqWdijEHIspYknP85AtovmTAEmQ/ir1xsrkfXa3PR5o1S7/dFBF4+qAwFX/6TFNXW1zl1LwCbySQ1OA6Bae+Tw==

Hello,

 

I’ve updated five nodes to 5.0.3-1.el7 and have re-setup bandwidth tests using pscheduler.  Before 5.0 I used this command to archive the results locally:

pscheduler task --archive @/usr/share/pscheduler/psc-archiver-esmond.json --slip PT1H --sliprand --repeat-cron "36 0-5 * * *" throughput --source 162.127.1.81 --dest 162.127.1.61 --duration PT30S --bandwidth 3221225472 --ip-version 4 --omit PT5S

 

 

I saw that archiving tasks has changed, I ran the  “/usr/lib/perfsonar/archive/perfsonar-scripts/psconfig_archive.sh -n localhost > local_archive.json” command.  I then attempted to run another pscheduler throughput task following the example given but it errors out:

pscheduler task --archive @local_archive.json --slip PT1H --sliprand --repeat-cron "36 0-5 * * *" throughput --source 162.127.1.81 --dest 162.127.1.1 --duration PT30S --bandwidth 3221225472 --ip-version 4 --omit PT5S

Unable to read archive file: [Errno 2] No such file or directory: 'local_archive.json'


I am able to setup throughput tasks with this command (I can see traffic on our monitoring of the upstream ports):

 

pscheduler task --archive @/etc/perfsonar/psconfig/archives.d/http_logstash.json --slip PT1H --sliprand --repeat-cron "36 0-5 * * *" throughput --source 162.127.1.81 --dest 162.127.1.61 --duration PT30S --bandwidth 3221225472 --ip-version 4 --omit PT5S

 

However, this task doesn’t show on the /toolkit/ page for the node or in a maddash throughput mesh.

I also found this page that talks about writing to a local archive and I’ve made sure that my /etc/perfsonar/psconfig/archives.d/http_logstash.json files match the example given (each with their own unique token).

I feel that I’ve got something wrong in my pscheduler commands and that’s why the data isn’t being archived.  Does anyone have an example of a pscheduler CLI command that archives locally that they could share, please?

Thanks.

 



 

Brian Tehan (he/him/his)

Regional Network Engineer

University of Nebraska System

EAB009 6001 Dodge St

Omaha, NE 68182-0051

Office: (402) 554-6428

university of nebraska logo lockup with campuses

 

 


Archive powered by MHonArc 2.6.24.

Top of Page