perfSONAR User Q&A and Other Discussion

[Shkelzen Rugovac <>]

Hi Andrew,

I just restarted all the services you suggested in the same order. 

However, interesting enough while running the pscheduler command it gives the following error:

[root@ps02 ~]# pscheduler task --archive @/usr/share/pscheduler/psc-archiver-esmond.json idle --duration PT5S curl -k https://127.0.0.1/esmond/perfsonar/archive/

Unable to read archive file: [Errno 2] No such file or directory: '/usr/share/pscheduler/psc-archiver-esmond.json'

And indeed the file is missing:

[root@ps02 ~]# ls /usr/share/pscheduler/psc-archiver-esmond.json

ls: cannot access /usr/share/pscheduler/psc-archiver-esmond.json: No such file or directory

It looks like an important archiver file is just missing!

FYI, here are the installed perfsonar rpms:

[root@ps02 ~]# rpm -qa|grep perfsonar

libperfsonar-pscheduler-perl-4.0.2.1-1.el7.centos.noarch

perfsonar-traceroute-viewer-4.0.1-1.el7.centos.noarch

perfsonar-toolkit-ntp-4.0.2-1.el7.centos.noarch

libperfsonar-perl-4.0.2.1-1.el7.centos.noarch

perfsonar-oppd-shared-4.0-1.el7.centos.noarch

perfsonar-graphs-4.0.2-1.el7.centos.noarch

perfsonar-testpoint-4.0.2-1.el7.centos.noarch

perfsonar-toolkit-compat-database-4.0.2-1.el7.centos.noarch

libperfsonar-esmond-perl-4.0.2.1-1.el7.centos.noarch

perfsonar-toolkit-library-4.0.2-1.el7.centos.noarch

perfsonar-oppd-server-4.0-1.el7.centos.noarch

perfsonar-meshconfig-agent-4.0.2.1-1.el7.centos.noarch

perfsonar-oppd-owamp-4.0-1.el7.centos.noarch

perfsonar-lscachedaemon-4.0-1.el7.centos.noarch

perfsonar-core-4.0.2-1.el7.centos.noarch

perfsonar-toolkit-4.0.2-1.el7.centos.noarch

libperfsonar-sls-perl-4.0.2.1-1.el7.centos.noarch

libperfsonar-toolkit-perl-4.0.2.1-1.el7.centos.noarch

perfsonar-lsregistrationdaemon-4.0.2-1.el7.centos.noarch

perfsonar-toolkit-systemenv-testpoint-4.0.2-1.el7.centos.noarch

perfsonar-oppd-bwctl-4.0-1.el7.centos.noarch

perfsonar-toolkit-sysctl-4.0.2-1.el7.centos.noarch

perfsonar-toolkit-security-4.0.2-1.el7.centos.noarch

perfsonar-toolkit-systemenv-4.0.2-1.el7.centos.noarch

perfsonar-toolkit-install-4.0.2-1.el7.centos.noarch

perfsonar-meshconfig-jsonbuilder-4.0.2.1-1.el7.centos.noarch

perfsonar-tools-4.0.2-1.el7.centos.noarch

libperfsonar-regulartesting-perl-4.0.2.1-1.el7.centos.noarch

perfsonar-meshconfig-shared-4.0.2.1-1.el7.centos.noarch

perfsonar-toolkit-servicewatcher-4.0.2-1.el7.centos.noarch

perfsonar-common-4.0.2-1.el7.centos.noarch

Cheers,

Shkelzen

2017-12-12 17:38 GMT+01:00 Doug Wussler <>:

Andrew –

 

We do not use IPv6 here.  However, during the install I do not configure the network card.  Perhaps your ISO has some default IPv6 settings?.  After the system boots up, the first thing I do is configure the networking scripts, which are exclusively IPv4.  I also disable references to IPv6 but apparently this comes too late.  I will try your suggestions later today and let you know what I find.  Thank you.

 

Doug Wussler

Florida State University

 

 

From: Andrew Lake <>
Date: Tuesday, December 12, 2017 at 10:33 AM
To: Doug Wussler <>, Shkelzen Rugovac <>
Cc: "" <>
Subject: Re: [perfsonar-user] Django error after a fresh install

 

On December 12, 2017 at 10:20:27 AM, Andrew Lake () wrote:

The Django error is new, so we can dig closer at that. 

Actually I was looking at the stacktrace wrong, the Cassandra connect exception is part of the Django stacktrace (I was reading it as two different things initially, doh). That means we are likely hitting the known cassandra IPv6 only issue. The real question now becomes if your hosts indeed booted with an IPv4 address, why is it still failing.  If not, either assigning one one or following the FAQ should be the fix. 

--

Shkelzen RUGOVAC       

Université Libre de Bruxelles
Bd du Triomphe, CP230
1050 Bruxelles - Belgium

Office at VUB:
Building G - Level 0 - Room 147

Tel: (+32) 2 629 33 26