Re: Verbose Debug Info?

[dduncan]

Now this is interesting. 

When I set DEBUG to True I can actually access the Review Board site, or at 
least I no longer got the 500 error. Going to the apache log reveals that 
the original error message has changed to:

[Fri Oct 06 13:40:51.039585 2017] [core:error] [pid 45622:tid 
> 140492367812352] [client 192.168.10.154:53661] AH00037: Symbolic link not 
> allowed or link target not accessible: 
> /var/www/reviewboard/htdocs/static/djblets, referer: http://reviewboard/r/
>

It repeats this message dozens of times. Looking at the details of the 
folder /var/www/reviewboard/htdocs/static revealed:

lrwxrwxrwx 1 root root   70 Oct  3 14:04 admin -> 
> /usr/local/lib/python2.7/dist-packages/reviewboard/htdocs/static/admin
> *lrwxrwxrwx 1 root root   78 Oct  3 14:04 djblets -> 
> /home/me/.local/lib/python2.7/site-packages/djblets/htdocs/static/djblets*
> drwxr-xr-x 2 www-data www-data 4096 Oct  3 14:04 ext
> lrwxrwxrwx 1 root root   68 Oct  3 14:04 lib -> 
> /usr/local/lib/python2.7/dist-packages/reviewboard/htdocs/static/lib
> lrwxrwxrwx 1 root root   67 Oct  3 14:04 rb -> 
> /usr/local/lib/python2.7/dist-packages/reviewboard/htdocs/static/rb
>

Pip was installing to my local directory, not /usr/local/lib/. I checked 
and it turns out the my $PYTHONPATH variable was not set up. To resolve 
this:

   1. Removed Review Board
   2. Set up $Pythonpath in my my .bashrc
   3. Logged out, then logged back in
   4. Installed djblets using pip
   5. Re-installed Review Board

Originally I removed Djblets from my local directory, but this caused 
Review Board installation to fail. For some reason Review Board was still 
verifying the existence Djblets in my local folder. Despite that, after 
setting up Review Board again the symbolic link was pointing to 
/usr/local/lib.


Review Board is now working as expected.


Thank you for your help! Without that debug info I never would have been 
able to reach this next step.


Have a good one,

David

On Friday, October 6, 2017 at 1:33:35 PM UTC-4, Christian Hammond wrote:
>
> That log-related message is harmless, but interesting. It does mean it's 
> reaching Review Board code.
>
> This is generally not something you'll want to turn on unless advised by 
> us, but in your $sitedir/conf/settings_local.py, set:
>
> DEBUG = True
>
> Then restart Apache and load the page. See if you get a more detailed 
> error.
>
> After we resolve this, you'll want to set DEBUG back to False. This 
> actually changes a lot of behavior and makes your install slower and less 
> secure.
>
> Christian
>
> On Thu, Oct 5, 2017 at 1:11 PM,  > wrote:
>
>> Forgot to mention in last message: I talked it over with my supervisor 
>> and, to the best of our knowledge, there are no other Web Services running 
>> on that server.
>>
>>
>> On Thursday, October 5, 2017 at 4:08:36 PM UTC-4, 
>> ddu...@aviationintertec.com wrote:
>>>
>>> Hi Christian,
>>>
>>> Thank you for the reply.
>>>
>>> There is no log being generated in the Review Board folder, but I did 
>>> see something I hadn't noticed before in the apache log:
>>>
>>> [Thu Oct 05 06:25:03.401752 2017] [wsgi:warn] [pid 17317:tid 
 140477232400256] mod_wsgi: Compiled for Python/2.7.11.
 [Thu Oct 05 06:25:03.401833 2017] [wsgi:warn] [pid 17317:tid 
 140477232400256] mod_wsgi: Runtime using Python/2.7.12.
 [Thu Oct 05 06:25:03.401988 2017] [mpm_event:notice] [pid 17317:tid 
 140477232400256] AH00489: Apache/2.4.18 (Ubuntu) mod_wsgi/4.3.0 
 Python/2.7.12 configured -- resuming normal operations
 [Thu Oct 05 06:25:03.402013 2017] [core:notice] [pid 17317:tid 
 140477232400256] AH00094: Command line: '/usr/sbin/apache2'
 *[Thu Oct 05 19:42:51.964780 2017] [wsgi:error] [pid 29333:tid 
 140477126346496] No handlers could be found for logger 
 "djblets.log.middleware"*

>>>
>>> I looked through the djblets.log.middleware documentation on the review 
>>> board site but couldn't find anything about handlers. Have you seen this 
>>> error before? If so what steps were needed to solve it?
>>>
>>> Thank you for your time,
>>> David
>>>
>>> On Thursday, October 5, 2017 at 1:41:34 PM UTC-4, Christian Hammond 
>>> wrote:

 Hi,

 It's not normal on an Ubuntu install to hit a 500 error like this. If 
 you're seeing a 500 this early, it's usually something failing before any 
 requests even get to Review Board. These might appear in the apache 
 error_log in the Review Board site directory's logs/ directory, or maybe 
 in 
 Apache's main error_log in /var/logs. Start by checking those and see if 
 you can find anything that stands out.

 Is this server being used for any other web services?

 Christian

 On Tue, Oct 3, 2017 at 12:15 PM,  wrote:

> Installing Review Board for the first time and can't get past a "500 - 
> Internal Server Error" page on 

Re: Index failure after upgrade to ReviewBoard 2.5.16

[Christian Hammond]

Hi Rob,

Stephen and I dug into this a bit. Turns out the version discrepancy comes
from an error in the upstream tarball's reported version. So you likely do
have only one version of this installed.

I'm going to give you some additional code to place in that fields.py file,
so we can get more information. On line 87, it's doing a:

raise SearchFieldError("The model '%s' does not have a model_attr
'%s'." % (repr(obj), attr))

Can you change that to:

raise SearchFieldError("The model '%s' ('%s' -- %s) does not have a
model_attr '%s' (%s)." % (repr(obj), repr(current_object),
current_object.__class__.__name__, attr, hasattr(current_object, attr)))

Then restart Apache and try again. See what information you get.

Christian

On Fri, Oct 6, 2017 at 11:17 AM, 'Rob Backhurst' via reviewboard <
reviewboard@googlegroups.com> wrote:

> Hi Stephen,
>
> I did think that might be the case, but I have only installed using yum.
> I have a test system setup in the same way (and showing the same
> behaviour) and checked to see if any packages had been installed using pip,
> but they have not...
>
> I’m not not particularly savvy with pip/easy_install though so if you can
> suggest any tricks to show for sure, that would be great.
>
> Thanks
> Rob
>
> Sent from my iPhone
>
> On 6 Oct 2017, at 19:10, Stephen Gallagher 
> wrote:
>
> Rob, did you install ReviewBoard using pip or using the EPEL 7 RPM?
>
> From above, it looks like you may have two copies of Haystack on your
> system, one installed via RPM and the other possibly installed by
> pip/easy_install. You will need to clear out the 2.1.1dev version.
> On Fri, Oct 6, 2017 at 1:32 PM Christian Hammond 
> wrote:
>
>> Hi Rob,
>>
>> It was a couple e-mails ago, but can you actually just attach /
>> usr/lib/python2.7/site-packages/haystack/fields.py? I'll see if that
>> logic differs from what is in 2.3.1.
>>
>> Christian
>>
>> On Fri, Oct 6, 2017 at 12:25 AM, 'Rob Backhurst' via reviewboard <
>> reviewboard@googlegroups.com> wrote:
>>
>>> Sorry, which one line?
>>>
>>> On Friday, 6 October 2017 00:59:12 UTC+1, Christian Hammond wrote:

 Hi Rob,

 That's the version listed in the source code for the version of
 Haystack being run. Not sure if that indicates a packaging problem or what,
 but it's very strange.

 Could you show me that one line in fields.py?

 Christian


 On Thu, Oct 5, 2017 at 13:22 'Rob Backhurst' via reviewboard <
 revie...@googlegroups.com> wrote:

> Hi Christian,
>
> We deinately only have version 2.3.1 installed.
>
> python-django-haystack 2.3.1-1.el7
>
> Why would it think we're using 2.1.1 dev? Can we force it to look in
> the correct place?
>
> Thanks
> Rob
>
> On Tuesday, 3 October 2017 09:12:26 UTC+1, Rob Backhurst wrote:
>
>> Hi,
>>
>> I upgraded our ReviewBoard system from 2.5.10 to 2.5.16 - since then,
>> indexing doesn't seem to complete.
>> The index starts OK, but after a while stops with this error...
>>
>> ERROR:root:Error updating reviews using default
>> Traceback (most recent call last):
>>   File 
>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>> line 189, in handle_label
>> self.update_backend(label, using)
>>   File 
>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>> line 234, in update_backend
>> do_update(backend, index, qs, start, end, total, self.verbosity)
>>   File 
>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>> line 89, in do_update
>> backend.update(index, current_qs)
>>   File 
>> "/usr/lib/python2.7/site-packages/haystack/backends/whoosh_backend.py",
>> line 191, in update
>> doc = index.full_prepare(obj)
>>   File "/usr/lib/python2.7/site-packages/haystack/indexes.py", line
>> 207, in full_prepare
>> self.prepared_data = self.prepare(obj)
>>   File "/usr/lib/python2.7/site-packages/haystack/indexes.py", line
>> 198, in prepare
>> self.prepared_data[field.index_fieldname] = field.prepare(obj)
>>   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line
>> 159, in prepare
>> return self.convert(super(CharField, self).prepare(obj))
>>   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line
>> 87, in prepare
>> raise SearchFieldError("The model '%s' does not have a model_attr
>> '%s'." % (repr(obj), attr))
>> SearchFieldError: The model '' does
>> not have a model_attr 'commit'.
>> Traceback (most recent call last):
>>   File "/usr/bin/rb-site", line 9, in 
>> load_entry_point('ReviewBoard==2.5.16', 'console_scripts',
>> 'rb-site')()
>>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py",

Re: Index failure after upgrade to ReviewBoard 2.5.16

['Rob Backhurst' via reviewboard]

Hi Stephen,

I did think that might be the case, but I have only installed using yum.
I have a test system setup in the same way (and showing the same behaviour) and 
checked to see if any packages had been installed using pip, but they have 
not...

I’m not not particularly savvy with pip/easy_install though so if you can 
suggest any tricks to show for sure, that would be great.

Thanks
Rob

Sent from my iPhone

> On 6 Oct 2017, at 19:10, Stephen Gallagher  wrote:
> 
> Rob, did you install ReviewBoard using pip or using the EPEL 7 RPM?
> 
> From above, it looks like you may have two copies of Haystack on your system, 
> one installed via RPM and the other possibly installed by pip/easy_install. 
> You will need to clear out the 2.1.1dev version. 
>> On Fri, Oct 6, 2017 at 1:32 PM Christian Hammond  
>> wrote:
>> Hi Rob,
>> 
>> It was a couple e-mails ago, but can you actually just attach 
>> /usr/lib/python2.7/site-packages/haystack/fields.py? I'll see if that logic 
>> differs from what is in 2.3.1.
>> 
>> Christian
>> 
>>> On Fri, Oct 6, 2017 at 12:25 AM, 'Rob Backhurst' via reviewboard 
>>>  wrote:
>>> Sorry, which one line?
>>> 
 On Friday, 6 October 2017 00:59:12 UTC+1, Christian Hammond wrote:
 Hi Rob,
 
 That's the version listed in the source code for the version of Haystack 
 being run. Not sure if that indicates a packaging problem or what, but 
 it's very strange.
 
 Could you show me that one line in fields.py?
 
 Christian
 
 
> On Thu, Oct 5, 2017 at 13:22 'Rob Backhurst' via reviewboard 
>  wrote:
> Hi Christian,
> 
> We deinately only have version 2.3.1 installed.
> 
> python-django-haystack 2.3.1-1.el7
> 
> Why would it think we're using 2.1.1 dev? Can we force it to look in the 
> correct place?
> 
> Thanks
> Rob
> 
>> On Tuesday, 3 October 2017 09:12:26 UTC+1, Rob Backhurst wrote:
> 
>> Hi,
>> 
>> I upgraded our ReviewBoard system from 2.5.10 to 2.5.16 - since then, 
>> indexing doesn't seem to complete.
>> The index starts OK, but after a while stops with this error...
>> 
>> ERROR:root:Error updating reviews using default
>> Traceback (most recent call last):
>>   File 
>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>>  line 189, in handle_label
>> self.update_backend(label, using)
>>   File 
>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>>  line 234, in update_backend
>> do_update(backend, index, qs, start, end, total, self.verbosity)
>>   File 
>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>>  line 89, in do_update
>> backend.update(index, current_qs)
>>   File 
>> "/usr/lib/python2.7/site-packages/haystack/backends/whoosh_backend.py", 
>> line 191, in update
>> doc = index.full_prepare(obj)
>>   File "/usr/lib/python2.7/site-packages/haystack/indexes.py", line 207, 
>> in full_prepare
>> self.prepared_data = self.prepare(obj)
>>   File "/usr/lib/python2.7/site-packages/haystack/indexes.py", line 198, 
>> in prepare
>> self.prepared_data[field.index_fieldname] = field.prepare(obj)
>>   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line 159, 
>> in prepare
>> return self.convert(super(CharField, self).prepare(obj))
>>   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line 87, 
>> in prepare
>> raise SearchFieldError("The model '%s' does not have a model_attr 
>> '%s'." % (repr(obj), attr))
>> SearchFieldError: The model '' does not 
>> have a model_attr 'commit'.
>> Traceback (most recent call last):
>>   File "/usr/bin/rb-site", line 9, in 
>> load_entry_point('ReviewBoard==2.5.16', 'console_scripts', 
>> 'rb-site')()
>>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
>> line 1964, in main
>> command.run()
>>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
>> line 1884, in run
>> site.run_manage_command(args[0], args[1:])
>>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
>> line 712, in run_manage_command
>> execute_from_command_line([__file__, cmd] + params)
>>   File 
>> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", 
>> line 399, in execute_from_command_line
>> utility.execute()
>>   File 
>> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", 
>> line 392, in execute
>> self.fetch_command(subcommand).run_from_argv(self.argv)
>>   File 
>> "/usr/lib/python2.7/site-packages/django/core/management/base.py", 

Re: Index failure after upgrade to ReviewBoard 2.5.16

['Rob Backhurst' via reviewboard]

Hi Christian, I’ll send the file to you asap.

Thanks
Rob

Sent from my iPhone

> On 6 Oct 2017, at 18:31, Christian Hammond  wrote:
> 
> Hi Rob,
> 
> It was a couple e-mails ago, but can you actually just attach 
> /usr/lib/python2.7/site-packages/haystack/fields.py? I'll see if that logic 
> differs from what is in 2.3.1.
> 
> Christian
> 
>> On Fri, Oct 6, 2017 at 12:25 AM, 'Rob Backhurst' via reviewboard 
>>  wrote:
>> Sorry, which one line?
>> 
>>> On Friday, 6 October 2017 00:59:12 UTC+1, Christian Hammond wrote:
>>> Hi Rob,
>>> 
>>> That's the version listed in the source code for the version of Haystack 
>>> being run. Not sure if that indicates a packaging problem or what, but it's 
>>> very strange.
>>> 
>>> Could you show me that one line in fields.py?
>>> 
>>> Christian
>>> 
>>> 
 On Thu, Oct 5, 2017 at 13:22 'Rob Backhurst' via reviewboard 
  wrote:
 Hi Christian,
 
 We deinately only have version 2.3.1 installed.
 
 python-django-haystack 2.3.1-1.el7
 
 Why would it think we're using 2.1.1 dev? Can we force it to look in the 
 correct place?
 
 Thanks
 Rob
 
> On Tuesday, 3 October 2017 09:12:26 UTC+1, Rob Backhurst wrote:
 
> Hi,
> 
> I upgraded our ReviewBoard system from 2.5.10 to 2.5.16 - since then, 
> indexing doesn't seem to complete.
> The index starts OK, but after a while stops with this error...
> 
> ERROR:root:Error updating reviews using default
> Traceback (most recent call last):
>   File 
> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>  line 189, in handle_label
> self.update_backend(label, using)
>   File 
> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>  line 234, in update_backend
> do_update(backend, index, qs, start, end, total, self.verbosity)
>   File 
> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>  line 89, in do_update
> backend.update(index, current_qs)
>   File 
> "/usr/lib/python2.7/site-packages/haystack/backends/whoosh_backend.py", 
> line 191, in update
> doc = index.full_prepare(obj)
>   File "/usr/lib/python2.7/site-packages/haystack/indexes.py", line 207, 
> in full_prepare
> self.prepared_data = self.prepare(obj)
>   File "/usr/lib/python2.7/site-packages/haystack/indexes.py", line 198, 
> in prepare
> self.prepared_data[field.index_fieldname] = field.prepare(obj)
>   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line 159, 
> in prepare
> return self.convert(super(CharField, self).prepare(obj))
>   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line 87, in 
> prepare
> raise SearchFieldError("The model '%s' does not have a model_attr 
> '%s'." % (repr(obj), attr))
> SearchFieldError: The model '' does not 
> have a model_attr 'commit'.
> Traceback (most recent call last):
>   File "/usr/bin/rb-site", line 9, in 
> load_entry_point('ReviewBoard==2.5.16', 'console_scripts', 
> 'rb-site')()
>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
> line 1964, in main
> command.run()
>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
> line 1884, in run
> site.run_manage_command(args[0], args[1:])
>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
> line 712, in run_manage_command
> execute_from_command_line([__file__, cmd] + params)
>   File 
> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", 
> line 399, in execute_from_command_line
> utility.execute()
>   File 
> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", 
> line 392, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File "/usr/lib/python2.7/site-packages/django/core/management/base.py", 
> line 242, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File "/usr/lib/python2.7/site-packages/django/core/management/base.py", 
> line 285, in execute
> output = self.handle(*args, **options)
>   File 
> "/usr/lib/python2.7/site-packages/reviewboard/reviews/management/commands/index.py",
>  line 21, in handle
> call_command('update_index')
>   File 
> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", 
> line 159, in call_command
> return klass.execute(*args, **defaults)
>   File "/usr/lib/python2.7/site-packages/django/core/management/base.py", 
> line 285, in execute
> output = self.handle(*args, **options)
>   File 
> 

Re: Index failure after upgrade to ReviewBoard 2.5.16

[Stephen Gallagher]

Rob, did you install ReviewBoard using pip or using the EPEL 7 RPM?

>From above, it looks like you may have two copies of Haystack on your
system, one installed via RPM and the other possibly installed by
pip/easy_install. You will need to clear out the 2.1.1dev version.
On Fri, Oct 6, 2017 at 1:32 PM Christian Hammond 
wrote:

> Hi Rob,
>
> It was a couple e-mails ago, but can you actually just attach /
> usr/lib/python2.7/site-packages/haystack/fields.py? I'll see if that
> logic differs from what is in 2.3.1.
>
> Christian
>
> On Fri, Oct 6, 2017 at 12:25 AM, 'Rob Backhurst' via reviewboard <
> reviewboard@googlegroups.com> wrote:
>
>> Sorry, which one line?
>>
>> On Friday, 6 October 2017 00:59:12 UTC+1, Christian Hammond wrote:
>>>
>>> Hi Rob,
>>>
>>> That's the version listed in the source code for the version of Haystack
>>> being run. Not sure if that indicates a packaging problem or what, but it's
>>> very strange.
>>>
>>> Could you show me that one line in fields.py?
>>>
>>> Christian
>>>
>>>
>>> On Thu, Oct 5, 2017 at 13:22 'Rob Backhurst' via reviewboard <
>>> revie...@googlegroups.com> wrote:
>>>
 Hi Christian,

 We deinately only have version 2.3.1 installed.

 python-django-haystack 2.3.1-1.el7

 Why would it think we're using 2.1.1 dev? Can we force it to look in
 the correct place?

 Thanks
 Rob

 On Tuesday, 3 October 2017 09:12:26 UTC+1, Rob Backhurst wrote:

> Hi,
>
> I upgraded our ReviewBoard system from 2.5.10 to 2.5.16 - since then,
> indexing doesn't seem to complete.
> The index starts OK, but after a while stops with this error...
>
> ERROR:root:Error updating reviews using default
> Traceback (most recent call last):
>   File
> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
> line 189, in handle_label
> self.update_backend(label, using)
>   File
> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
> line 234, in update_backend
> do_update(backend, index, qs, start, end, total, self.verbosity)
>   File
> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
> line 89, in do_update
> backend.update(index, current_qs)
>   File
> "/usr/lib/python2.7/site-packages/haystack/backends/whoosh_backend.py",
> line 191, in update
> doc = index.full_prepare(obj)
>   File "/usr/lib/python2.7/site-packages/haystack/indexes.py", line
> 207, in full_prepare
> self.prepared_data = self.prepare(obj)
>   File "/usr/lib/python2.7/site-packages/haystack/indexes.py", line
> 198, in prepare
> self.prepared_data[field.index_fieldname] = field.prepare(obj)
>   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line
> 159, in prepare
> return self.convert(super(CharField, self).prepare(obj))
>   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line 87,
> in prepare
> raise SearchFieldError("The model '%s' does not have a model_attr
> '%s'." % (repr(obj), attr))
> SearchFieldError: The model '' does
> not have a model_attr 'commit'.
> Traceback (most recent call last):
>   File "/usr/bin/rb-site", line 9, in 
> load_entry_point('ReviewBoard==2.5.16', 'console_scripts',
> 'rb-site')()
>   File
> "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", line
> 1964, in main
> command.run()
>   File
> "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", line
> 1884, in run
> site.run_manage_command(args[0], args[1:])
>   File
> "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", line 
> 712,
> in run_manage_command
> execute_from_command_line([__file__, cmd] + params)
>   File
> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", 
> line
> 399, in execute_from_command_line
> utility.execute()
>   File
> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", 
> line
> 392, in execute
> self.fetch_command(subcommand).run_from_argv(self.argv)
>   File
> "/usr/lib/python2.7/site-packages/django/core/management/base.py", line
> 242, in run_from_argv
> self.execute(*args, **options.__dict__)
>   File
> "/usr/lib/python2.7/site-packages/django/core/management/base.py", line
> 285, in execute
> output = self.handle(*args, **options)
>   File
> "/usr/lib/python2.7/site-packages/reviewboard/reviews/management/commands/index.py",
> line 21, in handle
> call_command('update_index')
>   File
> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", 
> line
> 159, in call_command
> return klass.execute(*args, **defaults)
>   File
> 

Re: Error after High Sierra upgrade

[Christian Hammond]

Hi Kev,

Newer versions of Python are very strict when it comes to SSL certificate
validation. They don't trust self-signed certificates by default. As we're
going through the standard HTTPS machinery in Python, we're limited by what
Python does here.

Python doesn't necessarily use Apple's trusted certificate store. If you
run this command, you'll see where it's checking:

$ python -c 'import ssl; print ssl.get_default_verify_paths()'

Christian

On Fri, Oct 6, 2017 at 10:53 AM, Kevin Brock  wrote:

> After upgrading my macOS system to 10.13, and upgrading RBTools to 0.7.10,
>  I started seeing a certificate error when I run rbt post.
>
> ERROR: Could not reach the Review Board server at https://reviewboard.
> yourcompany.com: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify
> failed (_ssl.c:590)
>
> I saw in various discussion groups that there were similar errors a while
> back related to the upgrade from Python 2.6 to Python 2.7, and Apple
> upgraded to 2.7 on High Sierra, but those problems were supposed to be
> fixed several versions of RBTools ago, weren't they?  I saw one message
> saying that the fix would be in 0.7.3...
>
> The relevant certificate *is* self-signed, but is marked as trusted for
> all uses in Keychain Access.  Everything was working fine before the
> upgrade.
>
> Is there a fix known for this problem?
>
> Kev
>
>
>
>
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "reviewboard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Christian Hammond
President/CEO of Beanbag 
Makers of Review Board 

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Error after High Sierra upgrade

[Kevin Brock]

After upgrading my macOS system to 10.13, and upgrading RBTools to 0.7.10, 
 I started seeing a certificate error when I run rbt post.

ERROR: Could not reach the Review Board server at 
https://reviewboard.yourcompany.com: [SSL: CERTIFICATE_VERIFY_FAILED] 
certificate verify failed (_ssl.c:590)

I saw in various discussion groups that there were similar errors a while 
back related to the upgrade from Python 2.6 to Python 2.7, and Apple 
upgraded to 2.7 on High Sierra, but those problems were supposed to be 
fixed several versions of RBTools ago, weren't they?  I saw one message 
saying that the fix would be in 0.7.3...

The relevant certificate *is* self-signed, but is marked as trusted for all 
uses in Keychain Access.  Everything was working fine before the upgrade.

Is there a fix known for this problem?

Kev





-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Verbose Debug Info?

[Christian Hammond]

That log-related message is harmless, but interesting. It does mean it's
reaching Review Board code.

This is generally not something you'll want to turn on unless advised by
us, but in your $sitedir/conf/settings_local.py, set:

DEBUG = True

Then restart Apache and load the page. See if you get a more detailed error.

After we resolve this, you'll want to set DEBUG back to False. This
actually changes a lot of behavior and makes your install slower and less
secure.

Christian

On Thu, Oct 5, 2017 at 1:11 PM,  wrote:

> Forgot to mention in last message: I talked it over with my supervisor
> and, to the best of our knowledge, there are no other Web Services running
> on that server.
>
>
> On Thursday, October 5, 2017 at 4:08:36 PM UTC-4,
> ddu...@aviationintertec.com wrote:
>>
>> Hi Christian,
>>
>> Thank you for the reply.
>>
>> There is no log being generated in the Review Board folder, but I did see
>> something I hadn't noticed before in the apache log:
>>
>> [Thu Oct 05 06:25:03.401752 2017] [wsgi:warn] [pid 17317:tid
>>> 140477232400256] mod_wsgi: Compiled for Python/2.7.11.
>>> [Thu Oct 05 06:25:03.401833 2017] [wsgi:warn] [pid 17317:tid
>>> 140477232400256] mod_wsgi: Runtime using Python/2.7.12.
>>> [Thu Oct 05 06:25:03.401988 2017] [mpm_event:notice] [pid 17317:tid
>>> 140477232400256] AH00489: Apache/2.4.18 (Ubuntu) mod_wsgi/4.3.0
>>> Python/2.7.12 configured -- resuming normal operations
>>> [Thu Oct 05 06:25:03.402013 2017] [core:notice] [pid 17317:tid
>>> 140477232400256] AH00094: Command line: '/usr/sbin/apache2'
>>> *[Thu Oct 05 19:42:51.964780 2017] [wsgi:error] [pid 29333:tid
>>> 140477126346496] No handlers could be found for logger
>>> "djblets.log.middleware"*
>>>
>>
>> I looked through the djblets.log.middleware documentation on the review
>> board site but couldn't find anything about handlers. Have you seen this
>> error before? If so what steps were needed to solve it?
>>
>> Thank you for your time,
>> David
>>
>> On Thursday, October 5, 2017 at 1:41:34 PM UTC-4, Christian Hammond wrote:
>>>
>>> Hi,
>>>
>>> It's not normal on an Ubuntu install to hit a 500 error like this. If
>>> you're seeing a 500 this early, it's usually something failing before any
>>> requests even get to Review Board. These might appear in the apache
>>> error_log in the Review Board site directory's logs/ directory, or maybe in
>>> Apache's main error_log in /var/logs. Start by checking those and see if
>>> you can find anything that stands out.
>>>
>>> Is this server being used for any other web services?
>>>
>>> Christian
>>>
>>> On Tue, Oct 3, 2017 at 12:15 PM,  wrote:
>>>
 Installing Review Board for the first time and can't get past a "500 -
 Internal Server Error" page on start up. I followed all of the set up
 instructions from the webpage,checked to make sure that Apache is using
 wsgi, and confirmed that the username and password I gave ReviewBoard work
 correctly with PostgresSQL.

 Is there a way to enable logging from the command line? Or at least get
 more verbose debugging info? As of right now Review Board is not writing
 any log files, and there are no errors in the Apache log file, so I have no
 leads on how to fix this problem.


 *Installation Info*Ubuntu 16.04.3 LTS
 Apache 2.4.18
 PostgreSQL 9.5.9
 rb-site 2.5.16
 Python 2.7.12

 --
 Supercharge your Review Board with Power Pack:
 https://www.reviewboard.org/powerpack/
 Want us to host Review Board for you? Check out RBCommons:
 https://rbcommons.com/
 Happy user? Let us know! https://www.reviewboard.org/users/
 ---
 You received this message because you are subscribed to the Google
 Groups "reviewboard" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to reviewboard...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>>
>>> --
>>> Christian Hammond
>>> President/CEO of Beanbag 
>>> Makers of Review Board 
>>>
>> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "reviewboard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Christian Hammond
President/CEO of Beanbag 
Makers of Review Board 

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out 

Re: Index failure after upgrade to ReviewBoard 2.5.16

[Christian Hammond]

Hi Rob,

It was a couple e-mails ago, but can you actually just attach /
usr/lib/python2.7/site-packages/haystack/fields.py? I'll see if that logic
differs from what is in 2.3.1.

Christian

On Fri, Oct 6, 2017 at 12:25 AM, 'Rob Backhurst' via reviewboard <
reviewboard@googlegroups.com> wrote:

> Sorry, which one line?
>
> On Friday, 6 October 2017 00:59:12 UTC+1, Christian Hammond wrote:
>>
>> Hi Rob,
>>
>> That's the version listed in the source code for the version of Haystack
>> being run. Not sure if that indicates a packaging problem or what, but it's
>> very strange.
>>
>> Could you show me that one line in fields.py?
>>
>> Christian
>>
>>
>> On Thu, Oct 5, 2017 at 13:22 'Rob Backhurst' via reviewboard <
>> revie...@googlegroups.com> wrote:
>>
>>> Hi Christian,
>>>
>>> We deinately only have version 2.3.1 installed.
>>>
>>> python-django-haystack 2.3.1-1.el7
>>>
>>> Why would it think we're using 2.1.1 dev? Can we force it to look in the
>>> correct place?
>>>
>>> Thanks
>>> Rob
>>>
>>> On Tuesday, 3 October 2017 09:12:26 UTC+1, Rob Backhurst wrote:
>>>
 Hi,

 I upgraded our ReviewBoard system from 2.5.10 to 2.5.16 - since then,
 indexing doesn't seem to complete.
 The index starts OK, but after a while stops with this error...

 ERROR:root:Error updating reviews using default
 Traceback (most recent call last):
   File 
 "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
 line 189, in handle_label
 self.update_backend(label, using)
   File 
 "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
 line 234, in update_backend
 do_update(backend, index, qs, start, end, total, self.verbosity)
   File 
 "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
 line 89, in do_update
 backend.update(index, current_qs)
   File 
 "/usr/lib/python2.7/site-packages/haystack/backends/whoosh_backend.py",
 line 191, in update
 doc = index.full_prepare(obj)
   File "/usr/lib/python2.7/site-packages/haystack/indexes.py", line
 207, in full_prepare
 self.prepared_data = self.prepare(obj)
   File "/usr/lib/python2.7/site-packages/haystack/indexes.py", line
 198, in prepare
 self.prepared_data[field.index_fieldname] = field.prepare(obj)
   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line
 159, in prepare
 return self.convert(super(CharField, self).prepare(obj))
   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line 87,
 in prepare
 raise SearchFieldError("The model '%s' does not have a model_attr
 '%s'." % (repr(obj), attr))
 SearchFieldError: The model '' does
 not have a model_attr 'commit'.
 Traceback (most recent call last):
   File "/usr/bin/rb-site", line 9, in 
 load_entry_point('ReviewBoard==2.5.16', 'console_scripts',
 'rb-site')()
   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py",
 line 1964, in main
 command.run()
   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py",
 line 1884, in run
 site.run_manage_command(args[0], args[1:])
   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py",
 line 712, in run_manage_command
 execute_from_command_line([__file__, cmd] + params)
   File 
 "/usr/lib/python2.7/site-packages/django/core/management/__init__.py",
 line 399, in execute_from_command_line
 utility.execute()
   File 
 "/usr/lib/python2.7/site-packages/django/core/management/__init__.py",
 line 392, in execute
 self.fetch_command(subcommand).run_from_argv(self.argv)
   File "/usr/lib/python2.7/site-packages/django/core/management/base.py",
 line 242, in run_from_argv
 self.execute(*args, **options.__dict__)
   File "/usr/lib/python2.7/site-packages/django/core/management/base.py",
 line 285, in execute
 output = self.handle(*args, **options)
   File 
 "/usr/lib/python2.7/site-packages/reviewboard/reviews/management/commands/index.py",
 line 21, in handle
 call_command('update_index')
   File 
 "/usr/lib/python2.7/site-packages/django/core/management/__init__.py",
 line 159, in call_command
 return klass.execute(*args, **defaults)
   File "/usr/lib/python2.7/site-packages/django/core/management/base.py",
 line 285, in execute
 output = self.handle(*args, **options)
   File 
 "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
 line 184, in handle
 return super(Command, self).handle(*items, **options)
   File "/usr/lib/python2.7/site-packages/django/core/management/base.py",
 line 385, in handle
 label_output = self.handle_label(label, **options)
   File 
 

Review Board 3.0 beta 2 is out -- beta testers needed!

[Christian Hammond]

Hi everyone,

We just put out a release of Review Board 3.0 beta 2. There's a lot of new
features in this release, and at this point we're feature-complete,
focusing on bug fixing. Some of the highlights include:

* Highlighting of new updates and discussions on review requests
* Ability to revoke Ship Its
* Ability to require the reviewer's verification on closed issues
* OAuth2 Provider support
* Emoji shortcodes
* CircleCI and Travis CI integration
* On-the-fly search indexing
* Lots more

We'd like to get the RC1 (Release Candidate 1) release out in two weeks. In
the meantime, we're focusing on bug fixing and documentation.

We could really use your help on testing this release (on a test server,
not production!). Installing the beta on a test server, along with a copy
of your database, and ensuring everything works will help us to ship a
better final release of 3.0.

If you use or develop in-house extensions, we'd like your feedback as well.
We've done a lot of work on our extension capabilities, adding improved
support for custom fields and review request actions, and we could use
feedback here.

Our release announcement for beta 2 is here:
https://www.reviewboard.org/news/2017/10/05/review-board-3-0-beta-2-here/

Christian

-- 
Christian Hammond
President/CEO of Beanbag 
Makers of Review Board 

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Index failure after upgrade to ReviewBoard 2.5.16

['Rob Backhurst' via reviewboard]

Sorry, which one line?

On Friday, 6 October 2017 00:59:12 UTC+1, Christian Hammond wrote:
>
> Hi Rob,
>
> That's the version listed in the source code for the version of Haystack 
> being run. Not sure if that indicates a packaging problem or what, but it's 
> very strange.
>
> Could you show me that one line in fields.py?
>
> Christian
>
>
> On Thu, Oct 5, 2017 at 13:22 'Rob Backhurst' via reviewboard <
> revie...@googlegroups.com > wrote:
>
>> Hi Christian,
>>
>> We deinately only have version 2.3.1 installed.
>>
>> python-django-haystack 2.3.1-1.el7
>>
>> Why would it think we're using 2.1.1 dev? Can we force it to look in the 
>> correct place?
>>
>> Thanks
>> Rob
>>
>> On Tuesday, 3 October 2017 09:12:26 UTC+1, Rob Backhurst wrote:
>>
>>> Hi,
>>>
>>> I upgraded our ReviewBoard system from 2.5.10 to 2.5.16 - since then, 
>>> indexing doesn't seem to complete.
>>> The index starts OK, but after a while stops with this error...
>>>
>>> ERROR:root:Error updating reviews using default
>>> Traceback (most recent call last):
>>>   File 
>>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>>>  
>>> line 189, in handle_label
>>> self.update_backend(label, using)
>>>   File 
>>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>>>  
>>> line 234, in update_backend
>>> do_update(backend, index, qs, start, end, total, self.verbosity)
>>>   File 
>>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>>>  
>>> line 89, in do_update
>>> backend.update(index, current_qs)
>>>   File 
>>> "/usr/lib/python2.7/site-packages/haystack/backends/whoosh_backend.py", 
>>> line 191, in update
>>> doc = index.full_prepare(obj)
>>>   File "/usr/lib/python2.7/site-packages/haystack/indexes.py", line 207, 
>>> in full_prepare
>>> self.prepared_data = self.prepare(obj)
>>>   File "/usr/lib/python2.7/site-packages/haystack/indexes.py", line 198, 
>>> in prepare
>>> self.prepared_data[field.index_fieldname] = field.prepare(obj)
>>>   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line 159, 
>>> in prepare
>>> return self.convert(super(CharField, self).prepare(obj))
>>>   File "/usr/lib/python2.7/site-packages/haystack/fields.py", line 87, 
>>> in prepare
>>> raise SearchFieldError("The model '%s' does not have a model_attr 
>>> '%s'." % (repr(obj), attr))
>>> SearchFieldError: The model '' does not 
>>> have a model_attr 'commit'.
>>> Traceback (most recent call last):
>>>   File "/usr/bin/rb-site", line 9, in 
>>> load_entry_point('ReviewBoard==2.5.16', 'console_scripts', 
>>> 'rb-site')()
>>>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
>>> line 1964, in main
>>> command.run()
>>>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
>>> line 1884, in run
>>> site.run_manage_command(args[0], args[1:])
>>>   File "/usr/lib/python2.7/site-packages/reviewboard/cmdline/rbsite.py", 
>>> line 712, in run_manage_command
>>> execute_from_command_line([__file__, cmd] + params)
>>>   File 
>>> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 
>>> 399, in execute_from_command_line
>>> utility.execute()
>>>   File 
>>> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 
>>> 392, in execute
>>> self.fetch_command(subcommand).run_from_argv(self.argv)
>>>   File 
>>> "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 
>>> 242, in run_from_argv
>>> self.execute(*args, **options.__dict__)
>>>   File 
>>> "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 
>>> 285, in execute
>>> output = self.handle(*args, **options)
>>>   File 
>>> "/usr/lib/python2.7/site-packages/reviewboard/reviews/management/commands/index.py",
>>>  
>>> line 21, in handle
>>> call_command('update_index')
>>>   File 
>>> "/usr/lib/python2.7/site-packages/django/core/management/__init__.py", line 
>>> 159, in call_command
>>> return klass.execute(*args, **defaults)
>>>   File 
>>> "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 
>>> 285, in execute
>>> output = self.handle(*args, **options)
>>>   File 
>>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>>>  
>>> line 184, in handle
>>> return super(Command, self).handle(*items, **options)
>>>   File 
>>> "/usr/lib/python2.7/site-packages/django/core/management/base.py", line 
>>> 385, in handle
>>> label_output = self.handle_label(label, **options)
>>>   File 
>>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>>>  
>>> line 189, in handle_label
>>> self.update_backend(label, using)
>>>   File 
>>> "/usr/lib/python2.7/site-packages/haystack/management/commands/update_index.py",
>>>  
>>> line 234, in update_backend
>>> do_update(backend, index, qs, start, end, total, self.verbosity)
>>>   File 
>>>