perfSONAR User Q&A and Other Discussion

[Andrew Lake <>]

Hi Zach,

I was able to recreate locally with a 3.4.2 install and there are a couple more commands you need to run. Rather than having you run those by hand, I uploaded a new RPM that will run them for you and should fix the upgrade path in question. As of the time I'm writing this email it probably hasn’t made its way to all the mirrors yet. You can try a “yum update esmond”, but if you don’t get anything and are feeling impatient you can run “yum install https://cvs3.internet2.edu/svn/software/trunk/rpms/el6/x86_64/main/RPMS/esmond-2.0.2-3.el6.x86_64.rpm” to get it immediately. After the update completes the regular_testing errors should go away almost immediately.

Thanks,

Andy

On March 21, 2016 at 1:25:58 PM, Zach Bare () wrote:

Ok Andy,

I ran the commands you said to run, and It appeared to run without error. I am not yet seeing improvement though. Here is the log I am getting after I made the change.

Zach Bare Network Engineer, KINBER 717-963-7490 | 717-469-5461 | | 5775 Allentown Blvd., Suite 101, Harrisburg, PA 17112

Mark Your Calendars - 2016 KINBER Annual Conference April 11-13, at the DoubleTree by Hilton in Philadelphia!

On Mon, Mar 21, 2016 at 12:24 PM, Garnizov, Ivan (RRZE) <> wrote:

Hi Zach,

 

I am the other guy, that reported that problem.

In fact I have both cases with one upgrade failed and one successful upgrade from 3.4.x to 3.5.1

With the failed upgrade I lost the data, which was acceptable for this deployment and which speeded up the process.

This might as well be your use case, if you are doing these installs one at a time and/or from fresh.

 

There are additional steps, though, if these fail. These come again from Andy.

 

Best regards,

Ivan

 

 

 

From: [mailto:] On Behalf Of Andrew Lake
Sent: Montag, 21. März 2016 16:59
To: Zach Bare
Cc: PerfSonar Users
Subject: Re: [perfsonar-user] Regular Testing Error Message

 

Hi Zach,

 

What do you get when you run the following?

 

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

 

I believe it might fix the issue. Someone else reported a similar problem when going straight from 3.4.X to 3.5.1. The above commands will likely spit out some warnings about IP fields, but if it otherwise completes it will likely fix your issue. 

 

Thanks,

Andy

 

 

On March 21, 2016 at 11:43:39 AM, Zach Bare () wrote:

Andy,

 

I've attached the two log files you requested. Note that I shut the server down over the weekend, so there will be a gap in the log time stamps. 

 

Thanks for your help.

 

Zach Bare Network Engineer, KINBER 717-963-7490 |717-469-5461 | | 5775 Allentown Blvd., Suite 101, Harrisburg, PA 17112

Mark Your Calendars - 2016 KINBER Annual Conference April 11-13, at the DoubleTree by Hilton in Philadelphia!

 

On Mon, Mar 21, 2016 at 9:32 AM, Andrew Lake <> wrote:

Hi,

 

Do you have any errors in /var/log/httpd/error_log or /var/log/esmond/django.log? Could you please send those if you do and I can take a look.

 

Thanks,

Andy

 

 

 

On March 18, 2016 at 4:24:26 PM, Zach Bare () wrote:

2016/03/18 15:51:24 (18918) ERROR> EsmondBase.pm:53 perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::__ANON__ - Error writing metadata (500) 500 INTERNAL SERVER ERROR

2016/03/18 15:51:24 (18918) ERROR> MeasurementArchiveChild.pm:209 perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::handle_results - Problem storing results: Error writing metadata: 500 INTERNAL SERVER ERROR

2016/03/18 15:51:24 (18918) 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.

 

---

---