perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Marian,

I think the issue you ran into only happens on CentOS 6 if you are pointing to the centos-sclo repo, which we don’t by default (or didn’t in 3.5.1 when we last provided CentOS 6 ISOs). Looks like there is an update to the python27 package from SCL that throws an error if that is installed I ran into the same thing on a couple ESnet hosts that point at centos-sclo. Looking for a fix now. Usually before you run any of the esmond commands on CentOS 6 you have to do the following:

cd /usr/lib/esmond

source /opt/rh/python27/enable

/opt/rh/python27/root/usr/bin/virtualenv --prompt="(esmond)" .

. bin/activate

The "/opt/rh/python27/root/usr/bin/virtualenv “ is throwing an exception with the latest python27 from SCL. Its quite possible the same error led to your multiple passwords, you should be able to just delete the incorrect one. I may need to figure out the way around the exception above for you to be able to do so.

Thanks,

Andy

On November 29, 2017 at 5:37:30 AM, Marian Babik () wrote:

Hi,
following update to 4.0.2, I got back the familiar Error loading test listing: Internal Server Error while trying to access the toolkit page.

Please see below the error from /var/log/httpd24/error_log and I also noticed that I have duplicated measurement archive sections in /etc/perfsonar/meshconfig-agent-tasks.conf (with two different passwords). Is there a way to reset this ?

As a general comment, it would be great to have dysfunctional esmond reported somehow, especially if it happens after an upgrade, having a set of simple tests to run once the upgrade is done (like pscheduler troubleshoot, etc.) to check if all is working fine would be great to spot a dysfunctional node. In my view, having esmond running but not working is a major issue since measurements while executed are getting lost.

Thanks,
Marian

[Wed Nov 29 11:12:33.625928 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] mod_wsgi (pid=14956): Exception occurred processing WSGI script '/usr/lib/esmond/esmond/wsgi.py'.
[Wed Nov 29 11:12:33.626073 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] Traceback (most recent call last):
[Wed Nov 29 11:12:33.626163 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] File "/usr/lib/esmond/esmond/wsgi.py", line 28, in application
[Wed Nov 29 11:12:33.626247 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] return get_wsgi_application()(environ, start_response)
[Wed Nov 29 11:12:33.626327 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] File "/usr/lib/esmond/lib/python2.7/site-packages/django/core/wsgi.py", line 13, in get_wsgi_application
[Wed Nov 29 11:12:33.626391 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] django.setup(set_prefix=False)
[Wed Nov 29 11:12:33.626452 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] File "/usr/lib/esmond/lib/python2.7/site-packages/django/__init__.py", line 22, in setup
[Wed Nov 29 11:12:33.626547 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] configure_logging(settings.LOGGING_CONFIG, settings.LOGGING)
[Wed Nov 29 11:12:33.626603 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] File "/usr/lib/esmond/lib/python2.7/site-packages/django/conf/__init__.py", line 53, in __getattr__
[Wed Nov 29 11:12:33.626667 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] self._setup(name)
[Wed Nov 29 11:12:33.626721 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] File "/usr/lib/esmond/lib/python2.7/site-packages/django/conf/__init__.py", line 41, in _setup
[Wed Nov 29 11:12:33.626807 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] self._wrapped = Settings(settings_module)
[Wed Nov 29 11:12:33.626854 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] File "/usr/lib/esmond/lib/python2.7/site-packages/django/conf/__init__.py", line 116, in __init__
[Wed Nov 29 11:12:33.626896 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] raise ImproperlyConfigured("The SECRET_KEY setting must not be empty.")
[Wed Nov 29 11:12:33.627038 2017] [wsgi:error] [pid 14956] [remote 127.0.0.1:51872] ImproperlyConfigured: The SECRET_KEY setting must not be empty.