Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] problem with "python esmond/manage.py list" command after 3.5.1 upgrade

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] problem with "python esmond/manage.py list" command after 3.5.1 upgrade


Chronological Thread 
  • From: Humberto Galiza <>
  • To: "Christopher J. Tengi" <>
  • Cc: PerfSonar Users <>
  • Subject: Re: [perfsonar-user] problem with "python esmond/manage.py list" command after 3.5.1 upgrade
  • Date: Wed, 9 Mar 2016 13:49:29 -0300

Hi folks,

I have the same scenario, and I’m getting the same error as Chris described
after my perfSonar servers upgraded to the latest version. This is what I’m
getting on /var/log/perfsonar/regulartesting.log:


2016/03/09 17:48:00 (16417) ERROR> MeasurementArchiveChild.pm:125
perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::__ANON__ -
Problem handling test results: Problem storing results: Error writing data:
405 METHOD NOT ALLOWED at
/usr/share/perl5/perfSONAR_PS/RegularTesting/Master/MeasurementArchiveChild.pm
line 122.
2016/03/09 17:48:02 (16421) ERROR> EsmondBase.pm:65
perfSONAR_PS::RegularTesting::MeasurementArchives::EsmondBase::__ANON__ -
Error writing data (405) 405 METHOD NOT ALLOWED
2016/03/09 17:48:02 (16421) ERROR> MeasurementArchiveChild.pm:209
perfSONAR_PS::RegularTesting::Master::MeasurementArchiveChild::handle_results
- Problem storing results: Error writing data: 405 METHOD NOT ALLOWED

Any thoughts?


Humberto Galiza ..::.. Senior Network Engineer
AmLight: http://www.amlight.net
AMPATH (ASN 20080): http://www.ampath.net
P:+55 (19) 3787-3367
M:+55 (19) 971-445-570
Skype: humbertogaliza

> On Mar 9, 2016, at 12:58 PM, Christopher J. Tengi
> <>
> wrote:
>
> We are using IP-based authentication on our MA, and I noticed today that we
> were getting a number of “401 UNAUTHORIZED” errors for an endpoint that I
> *thought* I had added for IP auth. So, I got onto the MA and tried using
> the list command (after doing the python27 shuffle). Here are the results:
>
> ==========
> (esmond)[root@perfsonar-ma-2
> esmond]# python esmond/manage.py list
> System check identified some issues:
>
> WARNINGS:
> api.IfRef.ipAddr: (fields.W900) IPAddressField has been deprecated. Support
> for it (except in historical migrations) will be removed in Django 1.9.
> HINT: Use GenericIPAddressField instead.
> api.LSPOpStatus.dstAddr: (fields.W900) IPAddressField has been deprecated.
> Support for it (except in historical migrations) will be removed in Django
> 1.9.
> HINT: Use GenericIPAddressField instead.
> api.LSPOpStatus.srcAddr: (fields.W900) IPAddressField has been deprecated.
> Support for it (except in historical migrations) will be removed in Django
> 1.9.
> HINT: Use GenericIPAddressField instead.
> ==========
>
> If there is another way to list the users/hosts I’ve added for IP-based
> authentication, I’d be happy to use it, but I *think* this is what I’m
> supposed to use, right? Assuming that this may be upgrade-related, please
> let me know what I can do to help resolve this issue. If it’s me, just slap
> me. :-)
>
> Thanks,
> /Chris
>




Archive powered by MHonArc 2.6.16.

Top of Page