perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Whoops, shouldn’t go from memory, the option is just an address not a URL. Example:

{

    “pscheduler-assist-server”: “127.0.0.1",

    “remotes”: [...]

}

On January 17, 2019 at 10:09:26 AM, Andrew Lake () wrote:

Hi Ezra,

A couple things to try:

1. Can you visit "https://localhost/pscheduler” on the problematic host? A call to that URL returns the hostname, so it is possible the error is in scheduler’s lookup of the hostname, not connecting to the server itself.

2. If #1 seems to be working fine in /etc/perfsonar/psconfig/pscheduler-agent.json you can add a “pscheduler-assist-server” option set to something like “https://127.0.0.1/pscheduler” or use the address of the host to see if that helps. Not sure why the localhost lookup would not be working. Example:

{

    “pscheduler-assist-server”: https://127.0.0.1/pscheduler”,

    “remotes”: [...]

}

Thanks,

Andy

On January 16, 2019 at 6:03:33 PM, Ezra Kissel () wrote:

Hi,

After performing a CentOS 7 bundle install of 4.1 and pointing the
pscheduler instance to an existing Mesh configuration, the scheduler
works correctly and is running tests according to the pscheduler log.
However, the Toolkit webUI, and output of 'psconfig pscheduler-tasks' is
empty.

Looking at the output of
/var/log/perfsonar/psconfig-pscheduler-agent-transactions.log we see the
following Errors:

2019/01/16 13:25:01 INFO guid=0948A0DE-19BC-11E9-976C-E03174F665AE
action="list" url="https://localhost/pscheduler msg=Getting task list from
https://localhost/pscheduler
2019/01/16 13:25:01 ERROR guid=0948A0DE-19BC-11E9-976C-E03174F665AE
action="list" url="https://localhost/pscheduler msg=Error getting hostname
from https://localhost/pscheduler: HTTP/1.1 404 Not Found
2019/01/16 13:25:01 ERROR guid=0948A0DE-19BC-11E9-976C-E03174F665AE
url="https://localhost/pscheduler action="check_assist_server" msg=Error
checking assist server: HTTP/1.1 404 Not Found

However, this URL is perfectly resolvable from the command line:

[ezkissel@um-ps01 ~]$ curl https://localhost/pscheduler/tasks -k
["https://localhost/pscheduler/tasks/8917f287-0d7e-4d74-bedc-4010cb5ca9c4",
"https://localhost/pscheduler/tasks/6fa7615c-5273-4c39-b1e1-5503d172c26c",
"https://localhost/pscheduler/tasks/e4be97b3-e44d-4a32-8b6f-ceb2de76d556",
"https://localhost/pscheduler/tasks/e173668d-9d38-424d-9e97-3035506323de",
"https://localhost/pscheduler/tasks/7cebe09a-16b3-403c-beb7-eced912dfda7",
"https://localhost/pscheduler/tasks/5b14b6b0-c180-46c8-90cc-4b2e56b37543",
"https://localhost/pscheduler/tasks/e8fa8d3e-98a7-45e1-9d96-ea07a6a2cc0c",
"https://localhost/pscheduler/tasks/a198de56-f1a0-43ea-b9b3-27492cd249cc",
"https://localhost/pscheduler/tasks/41a339dc-d63f-4c38-9502-7c4e6317dd07"]

For context, this is the second host we setup in this manner, i.e. using
the CentOS bundle install. The first one is working fine but it is a
single-homed host. The same log above on the first host shows the
pscheduler client is using the FQDN instead of localhost. This second
host is multi-homed but 'localhost' resolution is working fine so it's
unclear why that resolution is failing.

https://github.com/perfsonar/perl-shared/blob/master/lib/perfSONAR_PS/Client/PScheduler/TaskManager.pm#L118

Another data point is that /var/lib/perfsonar/psconfig/psc_tracker is
not generated on the second, multi-homed host. We are not sure if this
is a symptom of the previous errors or the cause. On the first host
that file is generated and works correctly:

[ezkissel@iu-ps01 ~]$ cat /var/lib/perfsonar/psconfig/psc_tracker
{
"archives" : {
"+afor695Bl0KlYEfcsJW/Q" : "nzmF+zjtFIb6seWzuIpYmQ",
"HMdfRseLSjUtK0X1GXnvfA" : "HMdfRseLSjUtK0X1GXnvfA"
},
"leads" : {
"https://iu-ps01.open.sice.indiana.edu/pscheduler" : {
"success_time" : 1547647170
}
}
}

We are at a loss at the moment as the two hosts are nearly identical
configuration-wise except that one is multi-homed and the other is not.

Any ideas?

thanks,
- ezra
--
To unsubscribe from this list: https://lists.internet2.edu/sympa/signoff/perfsonar-user