perfsonar-user - Re: [perfsonar-user] psconfig not pulled by testpoint
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Danial Ebling <>
- To: Joachim Hunosøe <>, Szymon Trocha <>
- Cc: "" <>
- Subject: Re: [perfsonar-user] psconfig not pulled by testpoint
- Date: Thu, 1 Jun 2023 19:51:47 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=uen.org; dmarc=pass action=none header.from=uen.org; dkim=pass header.d=uen.org; 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=nPLmZKmqQjR+G6AS1fBJ8oQ+jhg1qQ3KaZtyuYk6iGM=; b=UidbrAM1lu9mSPCnEk7B85UyqQiwe5l3dDtReHeFN817ILKY/nrExpjSVSL585aBuzZFakafMOFFbzP1arOxhj4fQ4FbaajU/t9pkUvs9zmYgQotPqX3k69mG6WaWCuWZp5i3She97FE2YzLsLheHmM+yR9yy7pwHS72/UzaK1EnrwMW95oiOeFScZSUQUsMNQiQ765QClVPF3n3pB4ApjjmsqHKuMjTgQuqT3Hg+hipuXEkxL9il4g82EPgN0HBBjJPdqhsuO+9Ye/BFW4R5/ogxvhU0vYOrNSkyx1mtp/zSjD16RVPkGvrYic02NcYYftpa7KD753kglRu/yDG2A==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ORHbGysLKsc2gTzZHS88ClJzfplBiDcvHD0B1Yt4gTz/m014dol2KAKx0Bot2+FMjxjNbceg2TLBoD9uSWiBKAtAI74USYIxgZisYh7t51CHyFoTQI5vMSPN8ymtmCTyWikaNo4+2ryVBjkZcsKWT4tWf6vFXa1LJgSYpjFjWLBMWmjOF9wauSTJUa4qr19GXUFjK/NV9Ubh+NfugMgpxKt8rwCsgTmkzdOinMHUuigynpPun0E9eCQo6sIcKDa4adfdMJztP+povKZI7QBlWBZkjT+T+kZhCJWT+avFwNEEDZA9DptvYrEhV1RBCWe/hH3V4WjjvtKaivIyN7O+Sg==
Hi Joachim,
I just ran into this on a new mesh – same symptoms where the remote config looked OK, and everything validated successfully, but no tasks were added from the remote configs. I had FQDNs in my address fields on the config template, but they weren’t real records that could be resolved, just ones manually entered in /etc/hosts on my testpoint boxes. Even though the testpoint can locally resolve those FQDNs (and reverse lookups work with those records), the tasks weren’t getting picked up by the testpoint. My suspicion is that the scripts run their own lookups against the host DNS servers, so my /etc/hosts FQDNs were not getting picked up as local addresses.
I was able to fix this by adding the measurement interface IP and the testpoint’s FQDN with the “match-addresses” field in the pSConfig agent file (/etc/perfsonar/psconfig/pscheduler-agent.json) or via ‘psconfig agentctl pscheduler match-addresses’.
Danial Ebling Utah Education Network
From:
<> on behalf of Joachim Hunosøe <> #### psconfig remote list
=== pScheduler Agent === [ { "url" : "https://maddash-01.nordu.net/psconfig/throughput.json", "configure-archives" : true }, { "url" : "https://maddash-01.nordu.net/psconfig/throughput2.json", "configure-archives" : true } ]
#### psconfig pscheduler-stats
perl: warning: Falling back to the standard locale ("C"). Agent Last Run Start Time: 2023/05/11 13:14:13 Agent Last Run End Time: 2023/05/11 13:14:14 Agent Last Run Process ID (PID): 2982 Agent Last Run Log GUID: B949CCC6-EFFD-11ED-AA08-9758F0661561 Total tasks managed by agent: 0
#### pscheduler troubleshoot
nunoc@dk-nbi-pstp01:~$ pscheduler troubleshoot Performing basic troubleshooting of dk-nbi-pstp01.ndgf.org.
dk-nbi-pstp01.ndgf.org:
Measuring MTU... 65535 (Local) Looking for pScheduler... OK. Fetching API level... 5 Checking clock... OK. Exercising API... Archivers... Contexts... Tests... Tools... OK. Fetching service status... OK. Checking services... Ticker... Scheduler... Runner... Archiver... OK. Checking limits... OK. Idle test.... 7 seconds... Finished... Checking archiving... OK.
pScheduler appears to be functioning normally.
####
psconfig pscheduler-tasks
{ "tasks" : [] }
Best regards System Engineer
+45 5374 7719
|
- Re: [perfsonar-user] psconfig not pulled by testpoint, Danial Ebling, 06/01/2023
- Re: [perfsonar-user] psconfig not pulled by testpoint, Joachim Hunosøe, 06/02/2023
Archive powered by MHonArc 2.6.24.