perfSONAR User Q&A and Other Discussion

["Robinson, John-Paul" <>]

By way of an update, I was able to fix the lsregistration configuration by manually editing the config file.  It seems that the status on the toolkit web page that our site wasn't global registering was indeed accurate.   The root cause seems to have been the auto discovery of interfaces and addresses.   Our ConnectX card was on interface enp3s0.  It was either the fact that this was an undetected interface or that Alma9 has moved away from the tradition ifcfg based interface configuretions that prevented the site from being able to discover it's IP address.

By turning off autodiscover_interfaces and adding the following stanza, I was able to avoid the lsregistration start up errors and warnings and get a successful registration.  The toolkit web page then showed the site was registered.

        autodiscover_interfaces    0

        primary_interface       enp3s0

        host_name ps-sd.rc.uab.edu

        address 138.26.220.66

        mtu 9000

        capacity 40000

        <interface>

             if_name enp3s0

        </interface>

I don't think the mtu and capacity are strictly necessary but the Perl code was throwing warnings during startup that the values were uninitialized, ie. it couldn't discover them from the host.   I added them just to avoid any non-INFO level mesages during startup.

I'm still debugging the bi directional tests and test archive issues.

---

From: Robinson, John-Paul <>
Sent: Thursday, March 14, 2024 11:05 AM
To: <>
Subject: Oddities with the Alama9 install of pst5.0.8

 

Hi Folks,

We reinstalled our perfsonar node using Alama9 and following the perfsonar toolkit install here with straight cut-n-paste.

https://docs.perfsonar.net/install_el.html

I've seen some oddities on the install compared to our prior install (4.4 on centos6). 

• I haven't been able to update the host information configuration via the web UI.  I can fill out the form, but when I press save it just resets to blank. 

• I worked around this by editing the underlying config file /etc/perfsonar/lsregistrationdaemon.conf directly.
• Unfortunately, I can't seem to set the organization name.  There isn't a field for it in the file and I haven't guessed the correct one yet.

The site overview says my NTP config is not active and not registered

• I'm hoping these are UI inconsistencies: chronyd is running and so is the perfsonar-lsregistration service.

I noticed I couldn't import my old test data, because it seems Cassandra is not used.

• That's OK, just confirming my understanding.

I defined new tests and they are running but I only see performance data in one direction (the tests show bidirectional in the web UI) and, more disturbingly, when I click on the graphs there is an error "Error retrieving data No data found in the measurement archive" instead of a graph.

• I've checked all my running processes and they are all active except for "perfsonar-generate_motd.service" and "perfsonar-configure_nic_parameters.service" which exited.
• looks like the nic config is attempting to use old style ifcfg changes "perfsonar-configure_nic_parameters[1294]: ls: cannot access '/etc/sysconfig/network-scripts/ifcfg"

Here's our site for reference https://ps-sd.rc.uab.edu/toolkit/

Thanks for any insights you can provide on the above.

John-Paul