No I didn't, I failed to apply this important step mentioned on the
documentation

http://www.reviewboard.org/docs/manual/1.6/admin/upgrading/upgrading-reviewboard/

This is now working, sorry for the trouble and thanks again.

On Tue, May 22, 2012 at 6:43 PM, Christian Hammond <chip...@chipx86.com> wrote:
> Did you restart the web server after the upgrade?
>
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board - http://www.reviewboard.org
> VMware, Inc. - http://www.vmware.com
>
>
> On Tue, May 22, 2012 at 9:37 AM, Gauthier Segay <gauthier.se...@gmail.com>
> wrote:
>>
>> Hello Christian, thanks for your help
>>
>> here is the output:
>>
>> ~ $ python
>> Python 2.7.1 (r271:86832, Apr 15 2011, 08:52:24)
>> [GCC 4.4.3] on linux2
>> Type "help", "copyright", "credits" or "license" for more information.
>> >>> import reviewboard
>> >>> print reviewboard.__file__
>>
>> /usr/lib/python2.7/site-packages/ReviewBoard-1.6.6-py2.7.egg/reviewboard/__init__.pyc
>> >>>
>>
>> When I browse the server application, I get the correct 1.6.6 displayed on
>> top of the pages
>>
>> reviewboard is not installed on the machine running post-review
>>
>>
>> On Tuesday, 22 May 2012 18:24:05 UTC+2, Christian Hammond wrote:
>>>
>>> It sounds like it may still be using the 1.5.5 version of Review Board.
>>> On the server, run Python and type:
>>>
>>>     import reviewboard
>>>    print reviewboard.__file__
>>>
>>> And see what path it's showing. Hopefully it's the 1.6.6 path.
>>>
>>> Christian
>>>
>>> --
>>> Christian Hammond - chip...@chipx86.com
>>> Review Board - http://www.reviewboard.org
>>> VMware, Inc. - http://www.vmware.com
>>>
>>>
>>> On Tue, May 22, 2012 at 8:31 AM, Gauthier Segay wrote:
>>>>
>>>> Hello,
>>>>
>>>> I've upgraded an install from 1.5.5 to 1.6.6, the upgrade went fine fine
>>>>
>>>> I now encounter an issue with post-review (which I also updated), the
>>>> command is outputing this:
>>>>
>>>> >>> Got HTTP error: 500:
>>>>
>>>> ... (html of error 500 from reviewboard)
>>>>
>>>> Error creating review request: HTTP 500
>>>>
>>>> on the server error log, I can find this stack trace:
>>>>
>>>> ERROR:django.request:Internal Server Error:
>>>> /api/review-requests/3777/draft/
>>>> Traceback (most recent call last):
>>>>  File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py",
>>>> line 117, in get_response
>>>>    response = middleware_method(request, e)
>>>>  File
>>>> "/usr/lib/python2.7/site-packages/Djblets-0.6.7-py2.7.egg/djblets/log/middleware.py",
>>>> line 220, in process_exception
>>>>    request.user, request.build_absolute_uri(),
>>>>  File
>>>> "/usr/lib/python2.7/site-packages/django/contrib/auth/middleware.py",
>>>> line 9, in __get__
>>>>    request._cached_user = get_user(request)
>>>>  File
>>>> "/usr/lib/python2.7/site-packages/django/contrib/auth/__init__.py",
>>>> line 109, in get_user
>>>>    backend = load_backend(backend_path)
>>>>  File
>>>> "/usr/lib/python2.7/site-packages/django/contrib/auth/__init__.py",
>>>> line 23, in load_backend
>>>>    raise ImproperlyConfigured('Module "%s" does not define a "%s"
>>>> authentication backend' % (module, attr))
>>>> ImproperlyConfigured: Module "reviewboard.accounts.backends" does not
>>>> define a "StandardAuthBackend" authentication backend
>>>>
>>>> I run post-review this way:
>>>>
>>>> c:\python27\scripts\post-review --server=servername
>>>> --revision-range=... --repository-url=... --debug --username=...
>>>> --password=... --publish --target-groups=... --summary=...
>>>> --description-file=...
>>>>
>>>> The post-review command is failing when ran by SYSTEM account on a
>>>> windows box, it works when I run it from a user session, is there
>>>> anything I should look at regarding authentification or any idea how
>>>> to fix the issue described in server error log?
>>>>
>>>> I went to the administration settings / authentication page and saved
>>>> the settings so authentication method is "Standard Registration", but
>>>> I'm still encountering the issue
>>>>
>>>> Thanks for your help
>>>>
>>>> --
>>>> Want to help the Review Board project? Donate today at
>>>> http://www.reviewboard.org/donate/
>>>> Happy user? Let us know at http://www.reviewboard.org/users/
>>>> -~----------~----~----~----~------~----~------~--~---
>>>> To unsubscribe from this group, send email to
>>>> reviewboard+unsubscr...@googlegroups.com
>>>> For more options, visit this group at
>>>> http://groups.google.com/group/reviewboard?hl=en
>>>
>>>
>> --
>> Want to help the Review Board project? Donate today at
>> http://www.reviewboard.org/donate/
>> Happy user? Let us know at http://www.reviewboard.org/users/
>> -~----------~----~----~----~------~----~------~--~---
>> To unsubscribe from this group, send email to
>> reviewboard+unsubscr...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/reviewboard?hl=en
>
>
> --
> Want to help the Review Board project? Donate today at
> http://www.reviewboard.org/donate/
> Happy user? Let us know at http://www.reviewboard.org/users/
> -~----------~----~----~----~------~----~------~--~---
> To unsubscribe from this group, send email to
> reviewboard+unsubscr...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/reviewboard?hl=en

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Reply via email to