Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Data from MA not available after upgrade to 3.4

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Data from MA not available after upgrade to 3.4


Chronological Thread 
  • From: Andrew Lake <>
  • To: "Uhl, George D. (GSFC-423.0)[SGT INC]" <>
  • Cc: "" <>
  • Subject: Re: [perfsonar-user] Data from MA not available after upgrade to 3.4
  • Date: Tue, 7 Oct 2014 19:41:05 -0400

Hi,

Do you get the same error in the httpd logs as before?

Thanks,
Andy


On Oct 7, 2014, at 3:34 PM, "Uhl, George D. (GSFC-423.0)[SGT INC]" <> wrote:

Andy,

cassandra was failing because I changed the system hostname and it didn't resolve to a FQDN.  Once I restored the name, cassandra was able to start.  However, I'm still unable to retrieve data.  I attached cassandra.log.

From: Andrew Lake <>
Date: Tuesday, October 7, 2014 3:18 PM
To: George Uhl <>
Cc: "" <>
Subject: Re: [perfsonar-user] Data from MA not available after upgrade to 3.4

Hi George,

Thanks that does help. It usually just means cassandra is not running. Can you try the following?

/sbin/service cassandra restart
/sbin/service httpd restart

If that doesn't work can you send me /var/log/cassandra/cassandra.log.

Thanks,
Andy


On Oct 7, 2014, at 3:04 PM, "Uhl, George D. (GSFC-423.0)[SGT INC]" <> wrote:

Andy,

This might be more helpful.  From /var/log/esmond/django.log:

2014-10-07 14:56:36,173 [ERROR] /opt/esmond/lib/python2.7/site-packages/django/core/handlers/base.py: Internal Server Error: /esmond/perfsonar/archive/
Traceback (most recent call last):
  File "/opt/esmond/lib/python2.7/site-packages/django/core/handlers/base.py", line 103, in get_response
    resolver_match = resolver.resolve(request.path_info)
  File "/opt/esmond/lib/python2.7/site-packages/django/core/urlresolvers.py", line 319, in resolve
    for pattern in self.url_patterns:
  File "/opt/esmond/lib/python2.7/site-packages/django/core/urlresolvers.py", line 347, in url_patterns
    patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)
  File "/opt/esmond/lib/python2.7/site-packages/django/core/urlresolvers.py", line 342, in urlconf_module
    self._urlconf_module = import_module(self.urlconf_name)
  File "/opt/esmond/lib/python2.7/site-packages/django/utils/importlib.py", line 35, in import_module
    __import__(name)
  File "/opt/esmond/esmond/urls.py", line 8, in <module>
    from esmond.api.perfsonar.api import perfsonar_api
  File "/opt/esmond/esmond/api/perfsonar/api.py", line 47, in <module>
    'histogram': db.raw_cf,
AttributeError: 'NoneType' object has no attribute 'raw_cf'


This error is generated every time I click on the 3.4 toolkit GUI "View Test Results/Throughput Latency Graphs".

-George



From: Andrew Lake <>
Date: Tuesday, October 7, 2014 2:28 PM
To: George Uhl <>
Cc: "" <>
Subject: Re: [perfsonar-user] Data from MA not available after upgrade to 3.4

Hi George,

What's the URL of your toolkit? I can try querying your MA and seeing if any of the data looks funny or if it's something else.

Thanks,
Andy


On Oct 7, 2014, at 12:55 PM, "Uhl, George D. (GSFC-423.0)[SGT INC]" <> wrote:

Hi,

After performing the upgrade 3.3 to 3.4, I'm getting the following error:

Error retrieving test data: undefined

Thanks,
George Uhl
NASA GSFC


<cassandra.log>




Archive powered by MHonArc 2.6.16.

Top of Page