Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Error writing metadata (500) Internal server error

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Error writing metadata (500) Internal server error


Chronological Thread 
  • From: Andrew Lake <>
  • To: perfsonar-user <>, Daniel Manzo <>
  • Subject: Re: [perfsonar-user] Error writing metadata (500) Internal server error
  • Date: Mon, 17 Oct 2016 06:49:11 -0700
  • Ironport-phdr: 9a23:nmkc+hWpEHDd+LKjOH1jtDgvULrV8LGtZVwlr6E/grcLSJyIuqrYZhePt8tkgFKBZ4jH8fUM07OQ6P+wHzFbqs/c+Fk5M7VyFDY9wf0MmAIhBMPXQWbaF9XNKxIAIcJZSVV+9Gu6O0UGUOz3ZlnVv2HgpWVKQka3HUNPK+/0Ao/fidisn6D3osWLIlYAuD3oeb5oIg6xqwzL89QNjJEqfr480BXSpX1BYaFL3m5yDVOVgxvm4Mqspthu/zkG/7oN/shBXKGyWq0+X7sQWDgvNWE44IvuvB/RSiOF72oRSCMdlR8eUCbf6xSvd5H9qCbl/s502yTSacTwQaEcVC/k6ap3Hky7wBwbPiI0pTmEwvd7i7hW9Vf4/0Ry
  • Ironport-phdr: 9a23:nn+S8xxbuERfOijXCy+O+j09IxM/srCxBDY+r6Qd0OofIJqq85mqBkHD//Il1AaPBtSBra8ewLSN+4nbGkU4qa6bt34DdJEeHzQksu4x2zIaPcieFEfgJ+TrZSFpVO5LVVti4m3peRMNQJW2WVTerzWI4CIIHV2nbEwud76zR9SZ0Z///tvx0qWbWx9Piju5bOE6BzSNhiKViPMrh5B/IL060BrDrygAUe1XwWR1OQDbxE6ktY+YtaRu+CVIuv8n69UIEeCjJ/x5HvRkC2E+Pno7/8rtvAOGUBCC/DNISmgMnAFPBQHfqQzhU43Zsy3mu/B71TXAe8D6UOZwERir6aZmTFfNgSEVMHZt/GjRi8F0yqdSpgCmjxZ20oPOJoqSMawtULnaeIYzQ2ZbU9kZcyVCD8voZo0DHsIMJqBeopWr9AhGlge3GQT5XLCn8TRPnHKjmPRii+k=

Hi,

Those errors look completely independent of MaDDash. It looks like an issue on your measurement archive. What is in /var/log/httpd/error_log and /var/log/esmond/django.log on the host with the problematic archive?

Thanks,
Andy


On October 17, 2016 at 9:40:39 AM, Daniel Manzo () wrote:

Hi all,

 

My current perfSONAR setup is an HP server with 8 GB of RAM and an OS of RHEL 6.8. I installed using the CentOS bundle method with perfsonar-toolkit. After installing MaDDash 2.0 from the staging repo, I realized that perfsonar-graphs updated to 4.0, which is not compatible with the version of perfsonar-toolkit I have (3.5.1). I used yum to remove MaDDash and the staging repo, but I have not been able to see the graphs on the web interface. It just shows a red bar with “Error loading test listing: Internal Server Error”. I have been getting the same three errors in regulartesting.log for a while and have not been able to fix them:

 

2016/10/16 01:00:41 (8232) ERROR> EsmondBase.pm:53 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::__ANON__ - Error writing metadata (500) 500 Internal Server Error

2016/10/16 01:00:41 (8232) ERROR> MeasurementArchiveChild.pm:209 perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::handle_results - Problem storing results: Error writing metadata: 500 Internal Server Error

2016/10/16 01:00:41 (8232) ERROR> MeasurementArchiveChild.pm:125 perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::__ANON__ - Problem handling test results: Problem storing results: Error writing metadata: 500 Internal Server Error at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/RegularTesting/Master/MeasurementArchiveChild.pm line 122.

2016/10/16 01:00:41 (8233) ERROR> EsmondBase.pm:53 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::__ANON__ - Error writing metadata (500) 500 Internal Server Error

2016/10/16 01:00:41 (8233) ERROR> MeasurementArchiveChild.pm:209 perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::handle_results - Problem storing results: Error writing metadata: 500 Internal Server Error

2016/10/16 01:00:41 (8233) ERROR> MeasurementArchiveChild.pm:125 perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::__ANON__ - Problem handling test results: Problem storing results: Error writing metadata: 500 Internal Server Error at /usr/lib/perfsonar/bin/../lib/perfSONAR_PS/RegularTesting/Master/MeasurementArchiveChild.pm line 122.

 

I have tried the following steps to fix the problem:

rm –rf /var/lib/pgsql/data/*

/usr/lib/perfsonar/scripts/system_environment/configure_esmond

/usr/lib/perfsonar/scripts/system_environment/configure_regulartesting

/etc/init.d/httpd restart

/etc/init.d/perfsonar-regulartesting restart

cd /usr/lib/esmond

source /opt/rh/python27/enable

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

. bin/activate

python esmond/manage.py migrate

 

Maybe there is something else that I need to remove that was leftover from MaDDash 2.0 that is affecting the database/test results? Any advice or tips would be very helpful.

 

Thanks,

 

Dan Manzo

Scientific Computing Competence Ctr

_______________________

 

Bayer: Science For A Better Life

 

Bayer Business and Technology Services LLC

BBTS-IAO-COMM TECH NAIT College Program

Building B16

Pittsburgh, PA 15205-9741, USA

Tel:        412-777-2171

Mobile:   412-525-8332

E-mail:   

Web:      http://www.bayer.com

 




Archive powered by MHonArc 2.6.19.

Top of Page