perfSONAR User Q&A and Other Discussion

[Johann Hugo <>]

Everything is working fine now after reverse DNS was fixed.

Thanks

Johann

On Mon, Apr 24, 2023 at 9:56 AM Johann Hugo <> wrote:

Thanks Mark. 

Looks like someone broke reverse DNS propagation for my perfSONAR domain. Let me get that fixed first and see what happens.

Regards

Johann

On Fri, Apr 21, 2023 at 4:17 PM Mark Feit <> wrote:

Johann Hugo writes:

 

Since the upgrade a couple of my toolkit servers are not getting their pscheduler tasks any more. Other servers in the mesh are fine. I fixed limits.conf on all of them. Here are the outputs on one of the problematic servers.

 

[root@ps-14-ldn-tele pscheduler.d]# psconfig remote list
…

      "url" : "http://perf-pwa.sanren.ac.za/pub/config/sanren_mesh_2019.json",

I don't see anything funny in the log files:

…

2023/04/21 12:35:08 INFO guid=2E4ED44A-E030-11ED-9B71-BCF47E5E890A action="create" msg=No tasks to create

 

I wasn’t able to pull the mesh from here (server refused connection), so I couldn’t look at it directly.  However, the fact that pSConfig didn’t find any tasks to create means:

 

• None of the addresses specified in the mesh matches the hostname or the IP or FQDN on one of its interfaces
• -OR- no group includes an address that matches the host
• -OR- no task refers to a group that refers to a matching address

 

If your other hosts made the transition without trouble, odds are good something else changed that made pSConfig unable to find a match.  If you want to send me the mesh privately along with the output of `ip a` on that host, I’ll have a look at it for you.

 

Thanks, by the way, for including all of the troubleshooting output.  That helps weed out a lot of potential problems.  We might see about adding checking for host matches to the troubleshooting procedure since that first item is a frequent cause of problems.  I’ve opened a ticket on that:   https://github.com/perfsonar/psconfig/issues/101

 

--Mark