perfSONAR User Q&A and Other Discussion

[Casey Russell <>]

Group,

     I think I've answered my own question, it would appear that it's the authentication token failing (then not failing back to IP authentication).  Either that, or my IP authentication isn't working.  

The following is from one of the test hosts (pscheduler.log)

Sep 29 17:17:07 ps-ku-bw archiver WARNING  14873162: Failed to archive https://localhost/pscheduler/tasks/e4680bda-019f-43a4-91e1-3669a457f59d/runs/cc2ab95c-986c-4e3e-8161-02d18a1d41ee to esmond: 401: Invalid token.

The results of the run are here:

https://ps-ku-bw.perfsonar.kanren.net/pscheduler/tasks/e4680bda-019f-43a4-91e1-3669a457f59d/runs/cc2ab95c-986c-4e3e-8161-02d18a1d41ee?pretty

is that interpretation of what's happening correct?  

If so, I'll have to go through Mesh configurations and test hosts and remove the authentication info (API username and key) from everywhere the MA is configured.

Sincerely,

Casey Russell

Network Engineer

785-856-9809

2029 Becker Drive, Suite 282
Lawrence, Kansas 66047

On Fri, Sep 29, 2017 at 4:40 PM, Casey Russell <> wrote:

Group,

     I've recently activated my new central MA, but posts to the esmond database seem to be failing.  

2001:49d0:23c0:1003::2 - - [29/Sep/2017:16:33:37 -0500] "POST /esmond/perfsonar/archive/ HTTP/1.1" 401 27 "-" "python-requests/2.6.0 CPython/2.6.6 Linux/2.6.32-696.6.3.el6.x86_64"

2001:49d0:23c0:1003::2 - - [29/Sep/2017:16:33:37 -0500] "POST /esmond/perfsonar/archive/ HTTP/1.1" 401 27 "-" "python-requests/2.6.0 CPython/2.6.6 Linux/2.6.32-696.6.3.el6.x86_64"

2001:49d0:23c0:1003::2 - - [29/Sep/2017:16:33:38 -0500] "POST /esmond/perfsonar/archive/ HTTP/1.1" 401 27 "-" "python-requests/2.6.0 CPython/2.6.6 Linux/2.6.32-696.6.3.el6.x86_64"

2001:49d0:23c0:1003::2 - - [29/Sep/2017:16:33:38 -0500] "POST /esmond/perfsonar/archive/ HTTP/1.1" 401 27 "-" "python-requests/2.6.0 CPython/2.6.6 Linux/2.6.32-696.6.3.el6.x86_64"

2001:49d0:23c0:1003::2 - - [29/Sep/2017:16:33:38 -0500] "POST /esmond/perfsonar/archive/ HTTP/1.1" 401 27 "-" "python-requests/2.6.0 CPython/2.6.6 Linux/2.6.32-696.6.3.el6.x86_64"

The 401 would indicate that they're "unauthorized" although they should be allowed by IP (v6) 

(esmond)[root@ps-dashboard esmond]# python esmond/manage.py add_user_ip_address kanren_v6 2001:49d0::/32

<clipping some stuff here for brevity>

Setting timeseries permissions.

IP 2001:49d0::/32 already assigned to kanren_v6, skipping creation

My reading of the documentation indicates if these testing hosts in the mesh are trying to submit an old API key and username, when that fails, it will fall back to IP authorization.  Is that correct?  Is this 401 caused by something in the httpd configs and not esmond specifically?  

I'm open to any guidance here.

Sincerely,

Casey Russell

Network Engineer

785-856-9809

2029 Becker Drive, Suite 282
Lawrence, Kansas 66047