Skip to Content.
Sympa Menu

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

Subject: perfSONAR User Q&A and Other Discussion

List archive

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


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: Brian Tehan <>, "" <>
  • Subject: Re: [perfsonar-user] Problem with getting pscheduler tasks to archive locally
  • Date: Thu, 27 Jul 2023 16:03:41 +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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=4NEdlOMRiIOmgJgVMvvYx6/GZk2AtKMH1dcOcQvxMVM=; b=l1ACQo++iXZi9ZSTVY9r2Upu8tOjJtp9A4Eslah9QXRobzkWWFOobN9R8GZuoAflMIUjeK/ogGsC5xfIHxTcnZ33fSmo4QmrhPQbGHXyR8/HSH0kwYpDojkPI57ReT/bOw/c1j7HTLPCPgAcpuvG4P0GdqpyhBHjGp0X7UNP25HH13Vq/5N8Mbl25zXGkp/uKueleROzdA5NrjTx0zpQ/PyVAsnaT0+vhlJfwlecMJqqCaLEKjGTBNktfTmQdBDB1UGVAOYaUFlNCS/v5G/hZ3UEbYYDuZetfn51tZqRQi3P3kVh2E1BKYtFJSY//ZGAE19o/sI9cR9EybfNwAzkQg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Y2XxsSMr1BMeLaIOO6mrQ30yfyfNoiIBGlGSzfD1JdrgoCGd0Lszl9VNLB7LHAYKDVxutACX5b2uT1S3zu6idhn4dQnbi4UH/wlxKQOcdud1btX+QUUw/n1kdfnV8v31/bEuMAHNp3FqJYvPGKkj65ws8XT2UIslAAIlABXZPs2C6Y4z+iBI44vrcFDI33WtS0IP1rDe3S+fgSu750zs9ED8RvqWpSMsxNUbGE6gKdo+biaZd0IJxHqj9Z3q8VFmtlMU4bYpgZpY6ChynOeOc+NMd88RYkJWnFLh033YP/LGiwj6JuetWZjS7JfPQO+Bc/fAXFwb/fMpUTvuWzYI+Q==

Brian Tehan writes:

 

Yes, I believe that the file is built in the right place: /home/**user**/ local_archive.json

 

Based on the runs below, it looks like it found it.  The file name gets passed straight through to the system, which is where that error came from. 

 

$ pscheduler task --archive @local_archive.json throughput --source 162.127.1.81 --dest 162.127.1.85 --duration PT30S --bandwidth 52428800 --ip-version 4 --omit PT5S

… 

$ pscheduler result --archivings https://162.127.1.81/pscheduler/tasks/d4cb2662-bb44-4f91-97d9-f3e3c423275d/runs/a6143c41-dafb-45e4-8f15-5f60fa013dc2

2023-07-27T09:09:48-05:00 on 162.127.1.81 and 162.127.1.85 with iperf3:

…

Archivings:

  To http, Unfinished

    2023-07-27T09:10:32-05:00 Failed to put result: 400: Could not resolve host: {% scheduled_by_address %}; Name or service not known

 

Ah, there’s the problem.  The “{% … %}” substitutions are a function of pSConfig; pScheduler takes what it’s given literally.  Replace those with a host name and you should be in business.

 

--Mark

 


Archive powered by MHonArc 2.6.24.

Top of Page