Re: wsgi issue in 5.0.4

[Adam Weremczuk]

Hi Laurent,

I have an existing and fully working 3.0.18 site. I've never had to do
anything special about WSGI, just "sudo apt install libapache2-mod-wsgi"
and copy the template config files.

I've compared 3.0.18 and 5.0.4 and key config files differ significantly
(apache-wsgi.conf, reviewboard.wsgi).

What struck me is one apache2 config line:

3.0.18:  *WSGIScriptAlias "/"
"/var/www/rebo.mydomain.com/htdocs/reviewboard.wsgi/
<http://rebo.mydomain.com/htdocs/reviewboard.wsgi/>"*

5.0.4:  *WSGIScriptAlias "/"
"/var/www/rebo.mydomain.com/htdocs/reviewboard.wsgi
<http://rebo.mydomain.com/htdocs/reviewboard.wsgi>"*

Note the lack of trailing slash in the latter. Unfortunately adding a slash
and rebooting hasn't fixed my problem.

Could somebody running 5.0.X on Debian 10 / 11 care to share their working
apache2 config and reviewboard.wsgi?

Not sure how much Red Hat version would differ but no harm sharing that as
well please.

Regards,
Adam


On Tue, 18 Apr 2023 at 21:15, Laurent Marechal  wrote:

> Hello,
>
> Had a similar issue in the past. The error is kind of generic but in my
> case it appeared after moving to Python3 for ReviewBoard while Python2 was
> still the OS installation (thanks old RH).
>
> The root cause was not having the WSI setup correctly. You need to update
> the wsgi file with:
>
> WSGIDaemonProcess ...
> WSGIProcessGroup ...
>
> You need to set them-up in the wsgi that you are using (reviewboard.wsgi I
> think), the template created by the installation does not contain them.
> Note you might get the same error if you try to run multiple wsgi
> applications on the same http server.
>
> Regards,
>
> Laurent\
>
>
> On Tue, Apr 18, 2023 at 8:29 PM Adam Weremczuk 
> wrote:
>
>> Hi all,
>>
>> Trying to install on Debian 11 with Apache2 and MariaDB.
>>
>> After site installation and apache configuration the html doesn't render
>> and I'm getting:
>>
>> 
>> 
>>  
>>   HTTP 500 - Review Board is taking a nap
>> (...)
>>
>> Error log:
>>
>> [Tue Apr 18 18:21:03.923609 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263] mod_wsgi (pid=647): Failed
>> to exec Python script file '/var/www/rebo/htdocs/reviewboard.wsgi'.
>> [Tue Apr 18 18:21:03.923909 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263] mod_wsgi (pid=647):
>> Exception occurred processing WSGI script
>> '/var/www/rebo/htdocs/reviewboard.wsgi'.
>> [Tue Apr 18 18:21:03.924326 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263] Traceback (most recent call
>> last):
>> [Tue Apr 18 18:21:03.924542 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263]   File
>> "/var/www/rebo/htdocs/reviewboard.wsgi", line 9, in 
>> [Tue Apr 18 18:21:03.924672 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263] from reviewboard.wsgi
>> import application
>> [Tue Apr 18 18:21:03.924810 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263]   File
>> "/usr/local/lib/python3.9/dist-packages/reviewboard/wsgi.py", line 33, in
>> 
>> [Tue Apr 18 18:21:03.924937 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263] application =
>> get_wsgi_application()
>> [Tue Apr 18 18:21:03.925055 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263]   File
>> "/usr/local/lib/python3.9/dist-packages/django/core/wsgi.py", line 12, in
>> get_wsgi_application
>> [Tue Apr 18 18:21:03.925176 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263]
>> django.setup(set_prefix=False)
>> [Tue Apr 18 18:21:03.925309 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263]   File
>> "/usr/local/lib/python3.9/dist-packages/django/__init__.py", line 24, in
>> setup
>> [Tue Apr 18 18:21:03.925431 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263]
>> apps.populate(settings.INSTALLED_APPS)
>> [Tue Apr 18 18:21:03.925537 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263]   File
>> "/usr/local/lib/python3.9/dist-packages/django/apps/registry.py", line 83,
>> in populate
>> [Tue Apr 18 18:21:03.925646 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.5:55263] raise
>> RuntimeError("populate() isn't reentrant")
>> [Tue Apr 18 18:21:03.925794 2023] [wsgi:error] [pid 647:tid
>> 140449104779008] [client 10.200.20.

Re: wsgi issue in 5.0.4

[Adam Weremczuk]

I'm running WSGI in the default embedded mode:

# mod_wsgi Embedded Mode configuration
#
# This default configuration enables Embedded Mode, but you can remove
# this and uncomment Daemon Mode below.
#
# Embedded mode is simpler to configure, but daemon mode is recommended
# in production environments.
WSGIPassAuthorization On
WSGIScriptAlias "/" "/var/www/rebo/htdocs/reviewboard.wsgi"


On Tue, 18 Apr 2023 at 19:28, Adam Weremczuk  wrote:

> Hi all,
>
> Trying to install on Debian 11 with Apache2 and MariaDB.
>
> After site installation and apache configuration the html doesn't render
> and I'm getting:
>
> 
> 
>  
>   HTTP 500 - Review Board is taking a nap
> (...)
>
> Error log:
>
> [Tue Apr 18 18:21:03.923609 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263] mod_wsgi (pid=647): Failed to
> exec Python script file '/var/www/rebo/htdocs/reviewboard.wsgi'.
> [Tue Apr 18 18:21:03.923909 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263] mod_wsgi (pid=647): Exception
> occurred processing WSGI script '/var/www/rebo/htdocs/reviewboard.wsgi'.
> [Tue Apr 18 18:21:03.924326 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263] Traceback (most recent call
> last):
> [Tue Apr 18 18:21:03.924542 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263]   File
> "/var/www/rebo/htdocs/reviewboard.wsgi", line 9, in 
> [Tue Apr 18 18:21:03.924672 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263] from reviewboard.wsgi
> import application
> [Tue Apr 18 18:21:03.924810 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263]   File
> "/usr/local/lib/python3.9/dist-packages/reviewboard/wsgi.py", line 33, in
> 
> [Tue Apr 18 18:21:03.924937 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263] application =
> get_wsgi_application()
> [Tue Apr 18 18:21:03.925055 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263]   File
> "/usr/local/lib/python3.9/dist-packages/django/core/wsgi.py", line 12, in
> get_wsgi_application
> [Tue Apr 18 18:21:03.925176 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263]
> django.setup(set_prefix=False)
> [Tue Apr 18 18:21:03.925309 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263]   File
> "/usr/local/lib/python3.9/dist-packages/django/__init__.py", line 24, in
> setup
> [Tue Apr 18 18:21:03.925431 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263]
> apps.populate(settings.INSTALLED_APPS)
> [Tue Apr 18 18:21:03.925537 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263]   File
> "/usr/local/lib/python3.9/dist-packages/django/apps/registry.py", line 83,
> in populate
> [Tue Apr 18 18:21:03.925646 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263] raise
> RuntimeError("populate() isn't reentrant")
> [Tue Apr 18 18:21:03.925794 2023] [wsgi:error] [pid 647:tid
> 140449104779008] [client 10.200.20.5:55263] RuntimeError: populate()
> isn't reentrant
>
> It looks like a problem with wsgi.
>
> dpkg -l | grep -i wsgi
> ii  libapache2-mod-wsgi-py3   4.7.1-3+deb11u1amd64
>Python 3 WSGI adapter module for Apache
>
> How do I fix the error?
>
> Regards,
> Adam
>

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CALC-DAHzA3WEbW6yX5vrAm2K-mUeJEH_6-fr1KcBNefou6df-g%40mail.gmail.com.

wsgi issue in 5.0.4

[Adam Weremczuk]

Hi all,

Trying to install on Debian 11 with Apache2 and MariaDB.

After site installation and apache configuration the html doesn't render
and I'm getting:



 
  HTTP 500 - Review Board is taking a nap
(...)

Error log:

[Tue Apr 18 18:21:03.923609 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263] mod_wsgi (pid=647): Failed to
exec Python script file '/var/www/rebo/htdocs/reviewboard.wsgi'.
[Tue Apr 18 18:21:03.923909 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263] mod_wsgi (pid=647): Exception
occurred processing WSGI script '/var/www/rebo/htdocs/reviewboard.wsgi'.
[Tue Apr 18 18:21:03.924326 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263] Traceback (most recent call
last):
[Tue Apr 18 18:21:03.924542 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263]   File
"/var/www/rebo/htdocs/reviewboard.wsgi", line 9, in 
[Tue Apr 18 18:21:03.924672 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263] from reviewboard.wsgi
import application
[Tue Apr 18 18:21:03.924810 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263]   File
"/usr/local/lib/python3.9/dist-packages/reviewboard/wsgi.py", line 33, in

[Tue Apr 18 18:21:03.924937 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263] application =
get_wsgi_application()
[Tue Apr 18 18:21:03.925055 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263]   File
"/usr/local/lib/python3.9/dist-packages/django/core/wsgi.py", line 12, in
get_wsgi_application
[Tue Apr 18 18:21:03.925176 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263]
django.setup(set_prefix=False)
[Tue Apr 18 18:21:03.925309 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263]   File
"/usr/local/lib/python3.9/dist-packages/django/__init__.py", line 24, in
setup
[Tue Apr 18 18:21:03.925431 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263]
apps.populate(settings.INSTALLED_APPS)
[Tue Apr 18 18:21:03.925537 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263]   File
"/usr/local/lib/python3.9/dist-packages/django/apps/registry.py", line 83,
in populate
[Tue Apr 18 18:21:03.925646 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263] raise
RuntimeError("populate() isn't reentrant")
[Tue Apr 18 18:21:03.925794 2023] [wsgi:error] [pid 647:tid
140449104779008] [client 10.200.20.5:55263] RuntimeError: populate() isn't
reentrant

It looks like a problem with wsgi.

dpkg -l | grep -i wsgi
ii  libapache2-mod-wsgi-py3   4.7.1-3+deb11u1amd64
   Python 3 WSGI adapter module for Apache

How do I fix the error?

Regards,
Adam

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CALC-DAGJfP6LyStj-NmAa1SAAW62J9sVOWkSxOZhEE80BdWuMA%40mail.gmail.com.

Re: migrating 3.0.18 between servers

[Adam Weremczuk]

Hmmm, something wrong with my db migration steps?

user@source:~$ sudo mysqldump -h localhost -u root -p -d reviewboard >
/tmp/reviewboard.sql
user@source:~$ sudo scp /tmp/reviewboard.sql user@destination:/tmp/

user@destination:~$ sudo mysql -h localhost -u root -p

mysql> DROP DATABASE reviewboard;
Query OK, 82 rows affected (0.26 sec)

mysql> CREATE DATABASE reviewboard;
Query OK, 1 row affected (0.00 sec)

mysql> quit
Bye

user@destination:~$ sudo mysql -h localhost -u root -p reviewboard <
/tmp/reviewboard.sql

What I'm finding strange is the diff between .sql dumps of the source
production site and the blank mirror destination site:

diff reviewboard-destination-orig.sql reviewboard-source.sql
1c1
< -- MySQL dump 10.13  Distrib 5.7.34, for Linux (x86_64)
---
> -- MySQL dump 10.13  Distrib 5.7.31, for Linux (x86_64)
5c5
< -- Server version 5.7.34
---
> -- Server version 5.7.31
45c45
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=8 DEFAULT CHARSET=utf8;
82c82
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=8 DEFAULT CHARSET=utf8;
145c145
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=172 DEFAULT CHARSET=utf8;
207c207
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=17 DEFAULT CHARSET=utf8;
222c222
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=17 DEFAULT CHARSET=utf8;
237c237
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;
300c300
< ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=8 DEFAULT CHARSET=utf8;
320c320
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8;
361c361
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=127 DEFAULT CHARSET=utf8;
402c402
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=113 DEFAULT CHARSET=utf8;
419c419
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=50 DEFAULT CHARSET=utf8;
456c456
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=1361 DEFAULT CHARSET=utf8;
489c489
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=732 DEFAULT CHARSET=utf8;
513c513
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=14 DEFAULT CHARSET=utf8;
635c635
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;
886c886
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=509 DEFAULT CHARSET=utf8;
993c993
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=8 DEFAULT CHARSET=utf8;
1016c1016
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=65 DEFAULT CHARSET=utf8;
1043c1043
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;
1063c1063
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;
1105c1105
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=223 DEFAULT CHARSET=utf8;
1125c1125
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=509 DEFAULT CHARSET=utf8;
1145c1145
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=8 DEFAULT CHARSET=utf8;
1165c1165
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=65 DEFAULT CHARSET=utf8;
1245c1245
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=50 DEFAULT CHARSET=utf8;
1265c1265
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=116 DEFAULT CHARSET=utf8;
1305c1305
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=17 DEFAULT CHARSET=utf8;
1325c1325
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=16 DEFAULT CHARSET=utf8;
1425c1425
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=79 DEFAULT CHARSET=utf8;
1466c1466
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;
1606c1606
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=3 DEFAULT CHARSET=utf8;
1725c1725
< ) ENGINE=InnoDB DEFAULT CHARSET=utf8;
---
> ) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=utf8;
1895c1895
< -- Dump completed on 2023-04-04 20:17:29
---
> -- Dump completed on 2023-04-04 19:18:07


On Thu, 6 Apr 2023 at 15:35, David Trowbridge  wrote:

> Adam,
>
> SECRET_KEY is necessary, and needs to be the same between the two servers.
> The missing Site sounds like something didn't 

Re: migrating 3.0.18 between servers

[Adam Weremczuk]

...or perhaps the SECRET_KEY feature can be disabled?

On Tue, 4 Apr 2023 at 22:30, Adam Weremczuk  wrote:

> Hi all,
>
> Following my previous struggle I've decided to simplify things and set up
> an almost identical destination server:
>
> Source:
>
> Debian 9.13
> MySQL 5.7.31
> Python 2.7.13
> ReviewBoard 3.0.18
>
> Destination:
>
> Debian 9.13
> MySQL 5.7.34
> Python 2.7.13
> ReviewBoard 3.0.18
>
> Same steps as before:
> - install and configure everything on destination the same way (users,
> names, even passwords) + create a blank site with the same name
> - migrate the database and entire site directory /var/www/mysite
>
> I have tried SECRET_KEY from conf/settings_local.py of both the
> original site and the new blank site (with the same name).
>
> To my surprise either key gives me:
>
> Something broke! (Error 500)
> It appears something broke when you tried to go to here. This is either a
> bug in Review Board or a server configuration error. Please report this to
> your administrator.
> ERROR:root:Could not load siteconfig: Site matching query does not exist.
>
> Is there any way around this (e.g. recreate the key)?
> Could it be something else?
>
> Regards,
> Adam
>
>

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CALC-DAFGG_mP-p_P2n77DE4X96TUMCnui2%2BrTZawEZhpad4vYA%40mail.gmail.com.

migrating 3.0.18 between servers

[Adam Weremczuk]

Hi all,

Following my previous struggle I've decided to simplify things and set up
an almost identical destination server:

Source:

Debian 9.13
MySQL 5.7.31
Python 2.7.13
ReviewBoard 3.0.18

Destination:

Debian 9.13
MySQL 5.7.34
Python 2.7.13
ReviewBoard 3.0.18

Same steps as before:
- install and configure everything on destination the same way (users,
names, even passwords) + create a blank site with the same name
- migrate the database and entire site directory /var/www/mysite

I have tried SECRET_KEY from conf/settings_local.py of both the
original site and the new blank site (with the same name).

To my surprise either key gives me:

Something broke! (Error 500)
It appears something broke when you tried to go to here. This is either a
bug in Review Board or a server configuration error. Please report this to
your administrator.
ERROR:root:Could not load siteconfig: Site matching query does not exist.

Is there any way around this (e.g. recreate the key)?
Could it be something else?

Regards,
Adam

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CALC-DAFX3GvbSb7_zr2veLziqQnVMSZWvxboSU_xq_jdxoSpaA%40mail.gmail.com.

Re: migrating from 3.0.18 to 4.0.12

[Adam Weremczuk]

 reviews_statusupdate |
| scmtools_repository  |
| scmtools_repository_review_groups|
| scmtools_repository_users|
| scmtools_tool|
| site_localsite   |
| site_localsite_admins|
| site_localsite_users |
| siteconfig_siteconfiguration |
| webapi_webapitoken   |
+--+
82 rows in set (0.00 sec)

Regards,
Adam

On Mon, 3 Apr 2023 at 00:47, David Trowbridge  wrote:

> It sounds like perhaps you imported the data from a 3.0.18 database into
> the database schema of 4.0.2
>
> You'll want to drop the database entirely, import the dump, then run the
> rb-site upgrade command.
>
> On Sun, Apr 2, 2023 at 1:11 PM Adam Weremczuk 
> wrote:
>
>> Hello,
>>
>> I have a production server happily running:
>>
>> Debian 9.13
>> MySQL 5.7.31
>> Python 2.7.13
>> ReviewBoard 3.0.18
>>
>> I have set up a new machine:
>>
>> Debian 9.13
>> MySQL 5.7.34
>> Python 2.7.13
>> ReviewBoard 4.0.12
>>
>> and repeated the initial set up steps. The new site is blank, i.e. has no
>> users' data.
>>
>> Then I moved the db across as well as the entire /var/www/rb.example.com
>> directory.
>>
>> Now when I try an upgrade I get:
>>
>> rb-site upgrade /var/www/rb.example.com
>>
>> Traceback (most recent call last):
>>   File "/usr/local/bin/rb-site", line 8, in 
>> sys.exit(main())
>>   File
>> "/usr/local/lib/python2.7/dist-packages/reviewboard/cmdline/rbsite.py",
>> line 2995, in main
>> command.run(site, options)
>>   File
>> "/usr/local/lib/python2.7/dist-packages/reviewboard/cmdline/rbsite.py",
>> line 2503, in run
>> siteconfig = SiteConfiguration.objects.get_current()
>>   File
>> "/usr/local/lib/python2.7/dist-packages/djblets/siteconfig/managers.py",
>> line 42, in get_current
>> return self.get_for_site_id(Site.objects.get_current().pk)
>>   File
>> "/usr/local/lib/python2.7/dist-packages/django/contrib/sites/models.py",
>> line 63, in get_current
>> return self._get_site_by_id(site_id)
>>   File
>> "/usr/local/lib/python2.7/dist-packages/django/contrib/sites/models.py",
>> line 35, in _get_site_by_id
>> site = self.get(pk=site_id)
>>   File
>> "/usr/local/lib/python2.7/dist-packages/django/db/models/manager.py", line
>> 85, in manager_method
>> return getattr(self.get_queryset(), name)(*args, **kwargs)
>>   File
>> "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py", line
>> 380, in get
>> self.model._meta.object_name
>> django.contrib.sites.models.DoesNotExist: Site matching query does not
>> exist.
>>
>> Please advise.
>>
>> Regards,
>> Adam
>>
>> --
>> 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
>> "Review Board Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to reviewboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/reviewboard/CALC-DAHCBhJttHmOHVE4abUbjg3x7i81a8JP9QQ%2B_3kr74FLOA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/reviewboard/CALC-DAHCBhJttHmOHVE4abUbjg3x7i81a8JP9QQ%2B_3kr74FLOA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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
> "Review Board Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/reviewboard/CAFS3VNUNrmPpBsenQAe%3DduUU%2B1vPtDAkwpcv_jiBsU1LAY5rCA%40mail.gmail.com
> <https://groups

migrating from 3.0.18 to 4.0.12

[Adam Weremczuk]

Hello,

I have a production server happily running:

Debian 9.13
MySQL 5.7.31
Python 2.7.13
ReviewBoard 3.0.18

I have set up a new machine:

Debian 9.13
MySQL 5.7.34
Python 2.7.13
ReviewBoard 4.0.12

and repeated the initial set up steps. The new site is blank, i.e. has no
users' data.

Then I moved the db across as well as the entire /var/www/rb.example.com
directory.

Now when I try an upgrade I get:

rb-site upgrade /var/www/rb.example.com

Traceback (most recent call last):
  File "/usr/local/bin/rb-site", line 8, in 
sys.exit(main())
  File
"/usr/local/lib/python2.7/dist-packages/reviewboard/cmdline/rbsite.py",
line 2995, in main
command.run(site, options)
  File
"/usr/local/lib/python2.7/dist-packages/reviewboard/cmdline/rbsite.py",
line 2503, in run
siteconfig = SiteConfiguration.objects.get_current()
  File
"/usr/local/lib/python2.7/dist-packages/djblets/siteconfig/managers.py",
line 42, in get_current
return self.get_for_site_id(Site.objects.get_current().pk)
  File
"/usr/local/lib/python2.7/dist-packages/django/contrib/sites/models.py",
line 63, in get_current
return self._get_site_by_id(site_id)
  File
"/usr/local/lib/python2.7/dist-packages/django/contrib/sites/models.py",
line 35, in _get_site_by_id
site = self.get(pk=site_id)
  File
"/usr/local/lib/python2.7/dist-packages/django/db/models/manager.py", line
85, in manager_method
return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/django/db/models/query.py",
line 380, in get
self.model._meta.object_name
django.contrib.sites.models.DoesNotExist: Site matching query does not
exist.

Please advise.

Regards,
Adam

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CALC-DAHCBhJttHmOHVE4abUbjg3x7i81a8JP9QQ%2B_3kr74FLOA%40mail.gmail.com.

Re: site migration

[Adam Weremczuk]

o.example.com/htdocs"

# Error handlers
ErrorDocument 500 /errordocs/500.html

WSGIPassAuthorization On
WSGIScriptAlias "/" "/var/www/rebo.example.com/htdocs/reviewboard.wsgi/"


AllowOverride All
Options -Indexes +FollowSymLinks
Allow from all


# Prevent the server from processing or allowing the rendering of
# certain file types.

SetHandler None
Options None

AddType text/plain .html .htm .shtml .php .php3 .php4 .php5 .phps .asp
AddType text/plain .pl .py .fcgi .cgi .phtml .phtm .pht .jsp .sh .rb


php_flag engine off


# Force all uploaded media files to download.

Header set Content-Disposition "attachment"



# Alias static media requests to filesystem
Alias /media "/var/www/rebo.example.com/htdocs/media"
Alias /static "/var/www/rebo.example.com/htdocs/static"
Alias /errordocs "/var/www/rebo.example.com/htdocs/errordocs"
Alias /favicon.ico "/var/www/
rebo.example.com/htdocs/static/rb/images/favicon.png"

SSLEngine on
SSLOptions +StrictRequire
SSLCipherSuite HIGH:MEDIUM
SSLCertificateKeyFile /etc/ssl/rebo/rebo.key
SSLCertificateFile /etc/ssl/rebo/rebo.crt
SSLCertificateChainFile /etc/ssl/rebo/cacerts.pem


---

Does ReviewBoard support https?
Does it support migration from http to https?
Does it support migration from one site name (subdomain in my case) to
another?
What am I missing and why I'm seeing these errors?

Regards,
Adam


On Tue, 28 Jul 2020 at 17:40, Paul Mansfield 
wrote:

>
> AIUI, it's all in the database.
> https://groups.google.com/g/reviewboard/c/KHjIWCU_YJo
>
> well, apart from people's avatars, so I would back up htdocs/media/
>
>
> On Tue, 28 Jul 2020 at 17:16, Adam Weremczuk  wrote:
>
>> Hi Paul,
>>
>> Thanks for the hint, I'll bear it in mind.
>>
>> What I'm after really is a site migration procedure applicable to my
>> environment.
>>
>> If there is no official documentation in place maybe somebody could at
>> least provide a list of steps?
>>
>> Regards,
>> Adam
>>
>>
>> On Tue, 28 Jul 2020 at 17:04, Paul Mansfield <
>> paul.mansfi...@agileanalog.com> wrote:
>>
>>> did you restore your SECRET_KEY?
>>>
>>> check your reviewboard settings_local.py file
>>>
>>> mine is in /var/www/reviewboard/conf/settings_local.py because that's
>>> the directory for my virtual http server
>>>
>>> in there you'll find this:
>>> # Unique secret key. Don't share this with anybody.
>>> SECRET_KEY = 'xxx'
>>>
>>> you need to make a note/copy of that key from your live RB instance, and
>>> if you restore it from a backup, put that key into the new instance.
>>>
>>>
>>>
>>>
>>> On Tue, 28 Jul 2020 at 15:58, Adam Weremczuk 
>>> wrote:
>>>
>>>> Hi all,
>>>>
>>>> Today I've attempted a migration from:
>>>>
>>>> Debian 9.3
>>>> Apache 2.4.25
>>>> MySQL 5.7.30
>>>> ReviewBoard 3.0.17
>>>>
>>>> to:
>>>>
>>>> Debian 9.13
>>>> Apache 2.4.25
>>>> MySQL 5.7.31
>>>> ReviewBoard 3.0.18
>>>>
>>>> Rather small differences and I didn't expect much trouble.
>>>>
>>>> I started with migrating database (mysqldump) which resulted in the
>>>> following error:
>>>>
>>>>
>>>>
>>>>
>>>> *Something broke! (Error 500)It appears something broke when you tried
>>>> to go to here. This is either a bug in Review Board or a server
>>>> configuration error. Please report this to your administrator.[Tue Jul 28
>>>> 13:05:08.361856 2020] [wsgi:error] [pid 1650:tid 140483573556992] [client
>>>> 10.200.20.2:53391 <http://10.200.20.2:53391>] ERROR:root:Could not load
>>>> siteconfig: Site matching query does not exist.*
>>>>
>>>> When I dropped the database and restored the original the error didn't
>>>> go away which I found really strange. In order to get a fully functional
>>>> vanilla RB 3.0.18 back on the destination I had to restore the entire
>>>> container from a pre-db-fiddling backup.
>>>>
>>>> By looking at the content of mysqldump it doesn't look like db
>>>> migration should be necessary anyway. The differences between a vanilla and
>>>> data populated dump where down to:
>>>>
>>>> *ENGINE=InnoDB AUTO_INC

Re: site migration

[Adam Weremczuk]

Hi Paul,

Thanks for the hint, I'll bear it in mind.

What I'm after really is a site migration procedure applicable to my
environment.

If there is no official documentation in place maybe somebody could at
least provide a list of steps?

Regards,
Adam


On Tue, 28 Jul 2020 at 17:04, Paul Mansfield 
wrote:

> did you restore your SECRET_KEY?
>
> check your reviewboard settings_local.py file
>
> mine is in /var/www/reviewboard/conf/settings_local.py because that's the
> directory for my virtual http server
>
> in there you'll find this:
> # Unique secret key. Don't share this with anybody.
> SECRET_KEY = 'xxx'
>
> you need to make a note/copy of that key from your live RB instance, and
> if you restore it from a backup, put that key into the new instance.
>
>
>
>
> On Tue, 28 Jul 2020 at 15:58, Adam Weremczuk  wrote:
>
>> Hi all,
>>
>> Today I've attempted a migration from:
>>
>> Debian 9.3
>> Apache 2.4.25
>> MySQL 5.7.30
>> ReviewBoard 3.0.17
>>
>> to:
>>
>> Debian 9.13
>> Apache 2.4.25
>> MySQL 5.7.31
>> ReviewBoard 3.0.18
>>
>> Rather small differences and I didn't expect much trouble.
>>
>> I started with migrating database (mysqldump) which resulted in the
>> following error:
>>
>>
>>
>>
>> *Something broke! (Error 500)It appears something broke when you tried to
>> go to here. This is either a bug in Review Board or a server configuration
>> error. Please report this to your administrator.[Tue Jul 28 13:05:08.361856
>> 2020] [wsgi:error] [pid 1650:tid 140483573556992] [client 10.200.20.2:53391
>> <http://10.200.20.2:53391>] ERROR:root:Could not load siteconfig: Site
>> matching query does not exist.*
>>
>> When I dropped the database and restored the original the error didn't go
>> away which I found really strange. In order to get a fully functional
>> vanilla RB 3.0.18 back on the destination I had to restore the entire
>> container from a pre-db-fiddling backup.
>>
>> By looking at the content of mysqldump it doesn't look like db
>> migration should be necessary anyway. The differences between a vanilla and
>> data populated dump where down to:
>>
>> *ENGINE=InnoDB AUTO_INCREMENT=20 DEFAULT CHARSET=utf8;*
>>
>> vs
>>
>> *ENGINE=InnoDB DEFAULT CHARSET=utf8;*
>>
>> Is it ok to just copy "repository-clones", "data" and "conf" directories
>> over?
>>
>> Is what I'm trying to achieve documented somewhere step by step in
>> details?
>>
>> Please advise.
>>
>> Regards,
>> Adam
>>
>> --
>> 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
>> "Review Board Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to reviewboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/reviewboard/CALC-DAHJf%3DF1nzFF-TwhugqA1Dgj4azZ8F83jLNBofjBZbXFsw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/reviewboard/CALC-DAHJf%3DF1nzFF-TwhugqA1Dgj4azZ8F83jLNBofjBZbXFsw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>
>
> --
> P Mansfield, Senior DevOps Engineer, Agile Analog Ltd
> GPG fingerprint: 8BC9D73EE3D4669C1C138ABD41D5B0C9030D4AE6
>
> --
> 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
> "Review Board Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/reviewboard/CAMukpcDhwVvxF3kXmFF1VnMbW-ud3DDJmAWkuzyHATXHabnS3Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/reviewboard/CAMukpcDhwVvxF3kXmFF1VnMbW-ud3DDJmAWkuzyHATXHabnS3Q%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CALC-DAHeTAo1A4xRLN65TOojQrcgCn6k%3D%2B5PVpu4jHNHsiJwpg%40mail.gmail.com.

site migration

[Adam Weremczuk]

Hi all,

Today I've attempted a migration from:

Debian 9.3
Apache 2.4.25
MySQL 5.7.30
ReviewBoard 3.0.17

to:

Debian 9.13
Apache 2.4.25
MySQL 5.7.31
ReviewBoard 3.0.18

Rather small differences and I didn't expect much trouble.

I started with migrating database (mysqldump) which resulted in the
following error:




*Something broke! (Error 500)It appears something broke when you tried to
go to here. This is either a bug in Review Board or a server configuration
error. Please report this to your administrator.[Tue Jul 28 13:05:08.361856
2020] [wsgi:error] [pid 1650:tid 140483573556992] [client 10.200.20.2:53391
] ERROR:root:Could not load siteconfig: Site
matching query does not exist.*

When I dropped the database and restored the original the error didn't go
away which I found really strange. In order to get a fully functional
vanilla RB 3.0.18 back on the destination I had to restore the entire
container from a pre-db-fiddling backup.

By looking at the content of mysqldump it doesn't look like db
migration should be necessary anyway. The differences between a vanilla and
data populated dump where down to:

*ENGINE=InnoDB AUTO_INCREMENT=20 DEFAULT CHARSET=utf8;*

vs

*ENGINE=InnoDB DEFAULT CHARSET=utf8;*

Is it ok to just copy "repository-clones", "data" and "conf" directories
over?

Is what I'm trying to achieve documented somewhere step by step in details?

Please advise.

Regards,
Adam

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CALC-DAHJf%3DF1nzFF-TwhugqA1Dgj4azZ8F83jLNBofjBZbXFsw%40mail.gmail.com.

Re: oauthlib installation error

[Adam Weremczuk]

For a fresh installation it's generally sufficient to run:

sudo pip install oauthlib==1.0.1

before running:

sudo pip install --proxy 192.168.8.1:3128 ReviewBoard


On Thu, 23 Jul 2020 at 12:54, Adam Weremczuk  wrote:

> Hi Christian,
>
> FYI - without downgrading oauthlib installer reports issues:
>
> sudo rb-site install /var/www/site.example.com
>
> Unable to load SCMTool svn = reviewboard.scmtools.svn:SVNTool: (oauthlib
> 3.1.0 (/usr/local/lib/python2.7/dist-packages),
> Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
> Unable to load SCMTool git = reviewboard.scmtools.git:GitTool: (oauthlib
> 3.1.0 (/usr/local/lib/python2.7/dist-packages),
> Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
> Unable to load SCMTool bzr = reviewboard.scmtools.bzr:BZRTool: (oauthlib
> 3.1.0 (/usr/local/lib/python2.7/dist-packages),
> Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
> Unable to load SCMTool cvs = reviewboard.scmtools.cvs:CVSTool: (oauthlib
> 3.1.0 (/usr/local/lib/python2.7/dist-packages),
> Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
> Unable to load SCMTool perforce =
> reviewboard.scmtools.perforce:PerforceTool: (oauthlib 3.1.0
> (/usr/local/lib/python2.7/dist-packages),
> Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
> Unable to load SCMTool plastic = reviewboard.scmtools.plastic:PlasticTool:
> (oauthlib 3.1.0 (/usr/local/lib/python2.7/dist-packages),
> Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
> Unable to load SCMTool clearcase =
> reviewboard.scmtools.clearcase:ClearCaseTool: (oauthlib 3.1.0
> (/usr/local/lib/python2.7/dist-packages),
> Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
> Unable to load SCMTool hg = reviewboard.scmtools.hg:HgTool: (oauthlib
> 3.1.0 (/usr/local/lib/python2.7/dist-packages),
> Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
>
> We want git integration to work nicely so I'm going to take a step back
> and try downgrading oauthlib before rerunning.
>
> I'm assuming it's enough to "sudo rm -fr /var/www/site.example.com" + recreate
> the database as everything the installer has done will be contained in
> these two places, right?
>
> Regards,
> Adam
>
> On Wed, 22 Jul 2020 at 20:27, Christian Hammond 
> wrote:
>
>> Hi Adam,
>>
>> Hopefully not, but if so, you can force a downgrade of oauthlib to 1.0.1.
>> I’ll look into what we might be able to do about this on our end.
>>
>> If it is a problem, it will manifest as your Authentication Backends or
>> repository type options being limited to a couple of hard-codes types. It’s
>> not a great indicator, but the problem comes from deep in the Python
>> packaging and registrations layers. We’re working toward improving this.
>>
>> Christian
>>
>>
>> On Wed, Jul 22, 2020 at 10:33 Adam Weremczuk 
>> wrote:
>>
>>> Hi all,
>>>
>>> On Debian 10 "sudo pip install ReviewBoard" produces:
>>>
>>> ERROR: django-oauth-toolkit 0.9.0 has requirement oauthlib==1.0.1, but
>>> you'll have oauthlib 3.1.0 which is incompatible.
>>>
>>> but then appears to happily continue:
>>>
>>> Installing collected packages: django-braces, Pillow, pillowfight,
>>> futures, django-pipeline, feedparser, publicsuffix, python-dateutil, pytz,
>>> Django, dnspython, Djblets, oauthlib, urllib3, certifi, chardet, idna,
>>> requests, requests-oauthlib, markdown, django-haystack, django-evolution,
>>> docutils, Whoosh, asana, PyYAML, rbintegrations, django-multiselectfield,
>>> django-oauth-toolkit, pycparser, cffi, pynacl, bcrypt, paramiko,
>>> python-memcached, django-cors-headers, mimeparse, Pygments,
>>> pymdown-extensions, ReviewBoard
>>> Successfully installed Django-1.6.11 Djblets-1.0.13 Pillow-6.2.2
>>> PyYAML-5.3.1 Pygments-2.5.2 ReviewBoard-3.0.18 Whoosh-2.7.4 asana-0.10.0
>>> bcrypt-3.1.7 certifi-2020.6.20 cffi-1.14.0 chardet-3.0.4
>>> django-braces-1.13.0 django-cors-headers-1.1.0 django-evolution-0.7.8
>>> django-haystack-2.4.1 django-multiselectfield-0.1.12
>>> django-oauth-toolkit-0.9.0 django-pipeline-1.6.14 dnspython-1.16.0
>>> docutils-0.16 feedparser-5.2.1 futures-3.3.0 idna-2.10 markdown-2.6.11
>>> mimeparse-0.1.3 oauthlib-3.1.0 paramiko-2.7.1 pillowfight-0.3
>>> publicsuffix-1.1.1 pycparser-2.20 pymdown-extensions-3.5 pynacl-1.4.0
>>> python-dateutil-2.8.1 python-memcached-1.59 pytz-2020.1
>>> rbintegrations-1.0.1 requests-2.24.0 requests-oauthlib-1.0.0 urllib3-1.25.10

4.0 release

[Adam Weremczuk]

Hi all,

Any idea how soon it's likely to be released?

More like a month or a year?

Is version 3 approaching end of life together with Python 2.7?

DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020.
Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0
will drop support for Python 2.7 in January 2021. More details about Python
2 support in pip, can be found at
https://pip.pypa.io/en/latest/development/release-process/#python-2-support

Regards,
Adam

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CALC-DAH_D7SRro9wn7JnQ%2Bj3zLiwC-0ZomJ78Vp27bPp8FmAYw%40mail.gmail.com.

Re: oauthlib installation error

[Adam Weremczuk]

Hi Christian,

FYI - without downgrading oauthlib installer reports issues:

sudo rb-site install /var/www/site.example.com

Unable to load SCMTool svn = reviewboard.scmtools.svn:SVNTool: (oauthlib
3.1.0 (/usr/local/lib/python2.7/dist-packages),
Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
Unable to load SCMTool git = reviewboard.scmtools.git:GitTool: (oauthlib
3.1.0 (/usr/local/lib/python2.7/dist-packages),
Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
Unable to load SCMTool bzr = reviewboard.scmtools.bzr:BZRTool: (oauthlib
3.1.0 (/usr/local/lib/python2.7/dist-packages),
Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
Unable to load SCMTool cvs = reviewboard.scmtools.cvs:CVSTool: (oauthlib
3.1.0 (/usr/local/lib/python2.7/dist-packages),
Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
Unable to load SCMTool perforce =
reviewboard.scmtools.perforce:PerforceTool: (oauthlib 3.1.0
(/usr/local/lib/python2.7/dist-packages),
Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
Unable to load SCMTool plastic = reviewboard.scmtools.plastic:PlasticTool:
(oauthlib 3.1.0 (/usr/local/lib/python2.7/dist-packages),
Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
Unable to load SCMTool clearcase =
reviewboard.scmtools.clearcase:ClearCaseTool: (oauthlib 3.1.0
(/usr/local/lib/python2.7/dist-packages),
Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))
Unable to load SCMTool hg = reviewboard.scmtools.hg:HgTool: (oauthlib 3.1.0
(/usr/local/lib/python2.7/dist-packages),
Requirement.parse('oauthlib==1.0.1'), set(['django-oauth-toolkit']))

We want git integration to work nicely so I'm going to take a step back and
try downgrading oauthlib before rerunning.

I'm assuming it's enough to "sudo rm -fr /var/www/site.example.com" + recreate
the database as everything the installer has done will be contained in
these two places, right?

Regards,
Adam

On Wed, 22 Jul 2020 at 20:27, Christian Hammond 
wrote:

> Hi Adam,
>
> Hopefully not, but if so, you can force a downgrade of oauthlib to 1.0.1.
> I’ll look into what we might be able to do about this on our end.
>
> If it is a problem, it will manifest as your Authentication Backends or
> repository type options being limited to a couple of hard-codes types. It’s
> not a great indicator, but the problem comes from deep in the Python
> packaging and registrations layers. We’re working toward improving this.
>
> Christian
>
>
> On Wed, Jul 22, 2020 at 10:33 Adam Weremczuk  wrote:
>
>> Hi all,
>>
>> On Debian 10 "sudo pip install ReviewBoard" produces:
>>
>> ERROR: django-oauth-toolkit 0.9.0 has requirement oauthlib==1.0.1, but
>> you'll have oauthlib 3.1.0 which is incompatible.
>>
>> but then appears to happily continue:
>>
>> Installing collected packages: django-braces, Pillow, pillowfight,
>> futures, django-pipeline, feedparser, publicsuffix, python-dateutil, pytz,
>> Django, dnspython, Djblets, oauthlib, urllib3, certifi, chardet, idna,
>> requests, requests-oauthlib, markdown, django-haystack, django-evolution,
>> docutils, Whoosh, asana, PyYAML, rbintegrations, django-multiselectfield,
>> django-oauth-toolkit, pycparser, cffi, pynacl, bcrypt, paramiko,
>> python-memcached, django-cors-headers, mimeparse, Pygments,
>> pymdown-extensions, ReviewBoard
>> Successfully installed Django-1.6.11 Djblets-1.0.13 Pillow-6.2.2
>> PyYAML-5.3.1 Pygments-2.5.2 ReviewBoard-3.0.18 Whoosh-2.7.4 asana-0.10.0
>> bcrypt-3.1.7 certifi-2020.6.20 cffi-1.14.0 chardet-3.0.4
>> django-braces-1.13.0 django-cors-headers-1.1.0 django-evolution-0.7.8
>> django-haystack-2.4.1 django-multiselectfield-0.1.12
>> django-oauth-toolkit-0.9.0 django-pipeline-1.6.14 dnspython-1.16.0
>> docutils-0.16 feedparser-5.2.1 futures-3.3.0 idna-2.10 markdown-2.6.11
>> mimeparse-0.1.3 oauthlib-3.1.0 paramiko-2.7.1 pillowfight-0.3
>> publicsuffix-1.1.1 pycparser-2.20 pymdown-extensions-3.5 pynacl-1.4.0
>> python-dateutil-2.8.1 python-memcached-1.59 pytz-2020.1
>> rbintegrations-1.0.1 requests-2.24.0 requests-oauthlib-1.0.0 urllib3-1.25.10
>>
>> I didn't get this error when I ran in on Debian 9 a few months ago.
>>
>> Do I have anything to worry about?
>>
>> Thanks,
>> Adam
>>
>> --
>> 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
>> "Review Board Community" group.
&g

oauthlib installation error

[Adam Weremczuk]

Hi all,

On Debian 10 "sudo pip install ReviewBoard" produces:

ERROR: django-oauth-toolkit 0.9.0 has requirement oauthlib==1.0.1, but
you'll have oauthlib 3.1.0 which is incompatible.

but then appears to happily continue:

Installing collected packages: django-braces, Pillow, pillowfight, futures,
django-pipeline, feedparser, publicsuffix, python-dateutil, pytz, Django,
dnspython, Djblets, oauthlib, urllib3, certifi, chardet, idna, requests,
requests-oauthlib, markdown, django-haystack, django-evolution, docutils,
Whoosh, asana, PyYAML, rbintegrations, django-multiselectfield,
django-oauth-toolkit, pycparser, cffi, pynacl, bcrypt, paramiko,
python-memcached, django-cors-headers, mimeparse, Pygments,
pymdown-extensions, ReviewBoard
Successfully installed Django-1.6.11 Djblets-1.0.13 Pillow-6.2.2
PyYAML-5.3.1 Pygments-2.5.2 ReviewBoard-3.0.18 Whoosh-2.7.4 asana-0.10.0
bcrypt-3.1.7 certifi-2020.6.20 cffi-1.14.0 chardet-3.0.4
django-braces-1.13.0 django-cors-headers-1.1.0 django-evolution-0.7.8
django-haystack-2.4.1 django-multiselectfield-0.1.12
django-oauth-toolkit-0.9.0 django-pipeline-1.6.14 dnspython-1.16.0
docutils-0.16 feedparser-5.2.1 futures-3.3.0 idna-2.10 markdown-2.6.11
mimeparse-0.1.3 oauthlib-3.1.0 paramiko-2.7.1 pillowfight-0.3
publicsuffix-1.1.1 pycparser-2.20 pymdown-extensions-3.5 pynacl-1.4.0
python-dateutil-2.8.1 python-memcached-1.59 pytz-2020.1
rbintegrations-1.0.1 requests-2.24.0 requests-oauthlib-1.0.0 urllib3-1.25.10

I didn't get this error when I ran in on Debian 9 a few months ago.

Do I have anything to worry about?

Thanks,
Adam

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CALC-DAHTCZ7DyCsajEKVcUxWC9_HXgPNmcEFgZGb6exqh2OQuA%40mail.gmail.com.

NIS authentication

[Adam Weremczuk]

Hi all,

Is it supposed to be working?

The settings page only allows "E-Mail Domain".

No matter what I provide when I attempt to log in I always get:

AttributeError at /account/login/ 'module' object has no attribute 'error'
 
 Request Method: POST 
 Request URL: http://rb-test.matrixscience.co.uk/account/login/ 
 Django Version: 1.6.11 
 Exception Type: AttributeError 
 Exception Value: 'module' object has no attribute 'error'
 
 Exception Location: /usr/local/lib/python2.7/dist-packages/reviewboard/
accounts/backends/nis.py in authenticate, line 40 
 Python Executable: /usr/bin/python 
 Python Version: 2.7.13 
 Python Path: ['/var/www/rb-test.domain.co.uk/conf',
 '/usr/lib/python2.7',
 '/usr/lib/python2.7/plat-x86_64-linux-gnu',
 '/usr/lib/python2.7/lib-tk',
 '/usr/lib/python2.7/lib-old',
 '/usr/lib/python2.7/lib-dynload',
 '/usr/local/lib/python2.7/dist-packages',
 '/usr/lib/python2.7/dist-packages']


Thanks,
Adam

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/68c5ca8d-f8cd-46b5-a45c-c41ef8fffb43%40googlegroups.com.

Re: LDAP authentication error

[Adam Weremczuk]

>
> ldbmodify -H /var/lib/samba/private/sam.ldb dummy2.ldif -U admin 
>

My bad editing post. I actually executed -U dummy2 and it got updated 
successfully and as intended. 

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/bd4e944c-f3f5-4b9e-9e3c-f548c578ca98%40googlegroups.com.

Re: LDAP authentication error

[Adam Weremczuk]

One problem was my LDAP connection settings.

This is almost working for me (thanks to Paul Mansfield):

-> Authentication Method: LDAP
-> LDAP Server: ldap://192.168.x.x:389
-> Review Board LDAP Bind Account: cn=auth,cn=Users,dc=domain,dc=co,dc=uk
-> Review Board LDAP Bind Password: 
-> LDAP Base DN: cn=Users,dc=domain,dc=co,dc=uk
-> Username Attribute: uid
-> Given Name Attribute: givenName
-> Surname Attribute: sn
-> Full Name Attribute: cn
-> E-Mail LDAP Attribute: mail
-> E-Mail Domain: (blank)
-> Custom LDAP User Search Filter: (blank)

Now I have a weird problem with about half of users being able to log in:

2020-05-26 11:32:07,623 - DEBUG -  - root - Attempting to authenticate user 
DN "CN=dummy1,CN=Users,DC=domain,DC=co,DC=uk" (username dummy1) in LDAP

and half unable:

2020-05-26 11:40:57,671 - ERROR -  - root - Unexpected error authenticating 
user "dummy2" in LDAP: 'NoneType' object has no attribute 'decode'
Traceback (most recent call last):
  File 
"/usr/local/lib/python2.7/dist-packages/reviewboard/accounts/backends/ldap.py"
, line 146, in authenticate
userdn.decode('utf-8'), username)
AttributeError: 'NoneType' object has no attribute 'decode'

After ruling out the obvious such as AD groups membership and primary 
groups I compared ldapsearch dumps:

ldapsearch -D 'ad...@domain.co.uk' -b 'cn=Users,dc=domain,dc=co,dc=uk' -H 
ldap://192.168.x.x -W sAMAccountName=dummy

I've noticed that all of those who cannot log in are missing msSFU30Name 
and msDS-SupportedEncryptionTypes attributes.

I've added them to match settings for the successful users as below:

dummy2.ldif

dn: CN=dummy2,CN=Users,DC=domain,DC=co,DC=uk
changetype: modify
add: msSFU30Name
msSFU30Name: dummy2
add: msDS-SupportedEncryptionTypes
msDS-SupportedEncryptionTypes: 0

ldbmodify -H /var/lib/samba/private/sam.ldb dummy2.ldif -U admin
Modified 1 records successfully

Unfortunately it didn't help and I really don't get why.
TBH I haven't been able to find any failed login attempts logged on the 
samba4 LDAP/DC server.

Any ideas?

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/f3533015-6f9d-4596-912c-28502ec69381%40googlegroups.com.

Re: LDAP authentication error

[Adam Weremczuk]

The LDAP server listens on both 389 / 636 and I can telnet to either port 
from Review Board client fine.

A logging in attempt generates traffic with 13 packets being exchanged:

RB - Review Board client
LD - LDAP server
[ ] - flag


   1. RB -> LD   [S]
   2. LD -> RB   [S.]
   3. RB -> LD   [.]
   4. RB -> LD   [P.]
   5. LD -> RB   [.]
   6. LD -> RB   [P.]
   7. RB -> LD   [.]
   8. RB -> LD   [P.]
   9. LD -> RB   [P.]
   10. RB -> LD   [P.]
   11. RB -> LD   [F.]
   12. LD -> RB   [F.]
   13. RB -> LD   [.]

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/f48bd2ed-31b2-44d8-a72e-2263cd0c1932%40googlegroups.com.

Re: LDAP authentication error

[Adam Weremczuk]

pip2 install python-ldap
Requirement already satisfied: python-ldap in
/usr/local/lib/python2.7/dist-packages
Requirement already satisfied: pyasn1>=0.3.7 in
/usr/local/lib/python2.7/dist-packages (from python-ldap)
Requirement already satisfied: pyasn1-modules>=0.1.5 in
/usr/local/lib/python2.7/dist-packages (from python-ldap)

Is my version (3.2.0) known to be problematic and are you suggesting 2.4.15
?

>

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CALC-DAHM5VA7wzupBU3bTQTC4VZvrCfMjksFmLDK1eVMroxphQ%40mail.gmail.com.

Re: LDAP authentication error

[Adam Weremczuk]

On Thu, 21 May 2020 at 12:06, Paul Mansfield 
wrote:

>
> do you have python (2.x) ldap module installed?
>
>
pip2 list | egrep ldap
DEPRECATION: The default format will switch to columns in the future. You
can use --format=(legacy|columns) (or define a format=(legacy|columns) in
your pip.conf under the [list] section) to disable this warning.
python-ldap (3.2.0)

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CALC-DAGXdmn_g-noPJnh1BZHBHDwZMdsRscLATdhYZkCDzyy7w%40mail.gmail.com.

LDAP authentication error

[Adam Weremczuk]

Hi all,



Review Board 3.0.17



My LDAP settings:

-> Authentication Method: LDAP
-> LDAP Server: ldap://192.168.x.x:389
-> Review Board LDAP Bind Account: a...@domain.co.uk
-> Review Board LDAP Bind Password: 
-> LDAP Base DN: cn=Users,dc=domain,dc=co,dc=uk
-> Username Attribute: sAMAccountName
-> Given Name Attribute: givenName
-> Surname Attribute: sn
-> Full Name Attribute: displayName
-> E-Mail LDAP Attribute: mail
-> E-Mail Domain: (blank)
-> Custom LDAP User Search Filter: sAMAccountName=%s



My ldapsearch results:

ldapsearch -D 'du...@domain.co.uk' -b 'cn=Users,dc=domain,dc=co,dc=uk' -H 
ldap://192.168.x.x -W sAMAccountName=dummy
Enter LDAP Password:
# extended LDIF
#
# LDAPv3
# base  with scope subtree
# filter: sAMAccountName=dummy
# requesting: ALL
#

# dummy, Users, domain.co.uk
dn: CN=dummy,CN=Users,DC=domain,DC=co,DC=uk
objectClass: top
objectClass: person
objectClass: organizationalPerson
objectClass: user
sn: Account
givenName: Dummy
instanceType: 4
whenCreated: 20180313125318.0Z
displayName: Dummy Account
uSNCreated: 2511997
objectGUID:: Y5A3vaWhyuKF9j3q/Ek+9w==
badPwdCount: 0
codePage: 0
countryCode: 0
badPasswordTime: 0
lastLogoff: 0
lastLogon: 0
objectSid:: AQUAAAUVyHdPCeZosyKsV0w3FAUAAA==
accountExpires: 9223372036854775807
logonCount: 0
sAMAccountName: dummy
sAMAccountType: 805306368
userPrincipalName: du...@domain.co.uk
objectCategory: CN=Person,CN=Schema,CN=Configuration,DC=domain,DC=co,DC
 =uk
userAccountControl: 66048
cn: dummy
name: dummy
memberOf: CN=Domain Users,CN=Users,DC=domain,DC=co,DC=uk
memberOf: CN=Remote Desktop Users,CN=Builtin,DC=domain,DC=co,DC=uk
memberOf: CN=RDP Domain Users,CN=Users,DC=domain,DC=co,DC=uk
primaryGroupID: 2354
msSFU30NisDomain: example_domain
uidNumber: 5652
loginShell: /bin/bash
unixHomeDirectory: /home/dummy
gidNumber: 4700
msSFU30Name: dummy
uid: dummy
mail: du...@domain.com
pwdLastSet: 13217705164000
whenChanged: 20191108164604.0Z
uSNChanged: 3800280
distinguishedName: CN=dummy,CN=Users,DC=domain,DC=co,DC=uk

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1



On login attempt Review Board error log produces: 

2020-05-21 10:43:09,771 - INFO -  - root - Reloading logging settings
2020-05-21 10:43:09,772 - DEBUG -  - root - Logging to 
/var/log/reviewboard/reviewboard.log with a minimum level of DEBUG
2020-05-21 10:43:09,826 - WARNING -  - root - Error authenticating user 
"dummy" in LDAP: {'info': u'acl_read: Error retrieving instanceType for 
base. at ../source4/dsdb/samdb/ldb_modules/acl_read.c:356', 'desc': u'No 
such object'}
2020-05-21 10:43:09,827 - ERROR -  - root - Unexpected error authenticating 
user "dummy" in LDAP: 'NoneType' object has no attribute 'decode'
Traceback (most recent call last):
  File 
"/usr/local/lib/python2.7/dist-packages/reviewboard/accounts/backends/ldap.py", 
line 146, in authenticate
userdn.decode('utf-8'), username)
AttributeError: 'NoneType' object has no attribute 'decode'



Is it related to DB backend being set up as MySQL 5.7 with utf8 or 
something else?

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/4711e7ae-60ab-42fd-8b55-2b708bb0d62c%40googlegroups.com.

Re: utf8 colation error

[Adam Weremczuk]

Hi Christian,

Thank you for a detailed and thorough reply.

Since it's a fresh installation I've opted for mysql-server 5.7.30-1debian9
and utf8.

Would expect any issues with it?

Thanks,
Adam


On Mon, 18 May 2020 at 04:39, Christian Hammond 
wrote:

> Hi Adam,
>
> Yeah... Here's the situation with MySQL/MariaDB and "utf8".
>
> When MySQL introduced utf8 charset, they went with a sort of "compressed"
> version of UTF-8 that excluded bits for some character ranges (I am super
> simplifying this). Emojis and some other character ranges didn't exist at
> the time, and now cannot be represented by their "utf8".
>
> utf8mb4 is the "real" UTF-8 charset type. However, it's not a drop-in
> replacement. It affects key lengths, amongst other things, and is
> incompatible with, well, many things.
>
> There *is* a way to get true UTF-8 support. It requires utf8mb4, and a
> handful of global settings applied to the server to enable large keys and a
> different InnoDB file format. It then requires a special command to be set
> at the beginning of each MySQL/MariaDB session to opt into some better
> support.
>
> Basically, it's invasive and not something that we can currently tell
> people to enable, or it'll cause new problems. It also requires full table
> rebuilds. The instructions also depend on the version of MySQL/MariaDB.
>
> We plan to bake in some level of support for it in Review Board in the
> future, but Django doesn't natively support it, and it'll require a bunch
> of special logic to rebuild data.
>
> I can't currently provide the settings you may need, because many of them
> are dependent on the version of MySQL/MariaDB you're using, and I haven't
> verified them lately (just working off internal notes). It boils down to:
>
> 1) Using utf8mb4 charsets for all databases, tables, and
> connections/sessions
> 2) Using utf8mb4_bin collation for all the above
> 3) Enabling innodb_large_prefix and innodb_per_table (might depend on the
> versions of MySQL/MariaDB)
> 4) Enabling innodb_file_format=barracuda (not needed on modern versions)
>
> This is not an exhaustive step-by-step.
>
> PostgreSQL will do UTF-8 by default, fwiw.
>
> Hoping to revisit this support in MySQL/MariaDB after RB4 wraps up. Should
> be easier now that MySQL/MariaDB have made progress in this area, and I
> need to update my knowledge of what that progress looks like.
>
> Christian
>
>
> On Fri, May 15, 2020 at 5:31 AM Adam Weremczuk 
> wrote:
>
>> I don't think utf8mb4 was a good idea and I believe it's now leading to:
>>
>> sudo rb-site install /var/www/mysite
>> (...)
>> * Installing the site...
>> (...)
>> Creating table scmtools_repository
>>
>> [!] There was an error synchronizing the database. Make sure the
>> database is created and has the appropriate permissions, and then
>> continue.
>> [!] Details: (1071, 'Specified key was too long; max key length is 767
>> bytes')
>>
>> Press Enter to continue
>>
>>
>>
>> On Thursday, 14 May 2020 16:01:35 UTC+1, Adam Weremczuk wrote:
>>>
>>> Hi all,
>>>
>>> Following installation guide for MySQL I've added to /etc/mysql/my.cnf
>>>
>>> [client]
>>> default-character-set=utf8
>>>
>>> [mysqld]
>>> character-set-server=utf8
>>>
>>> MariaDB fails to start:
>>>
>>> May 14 14:01:41 gittest systemd[1]: Starting MariaDB 10.1.44 database
>>> server...
>>> May 14 14:01:41 gittest mysqld[10318]: 2020-05-14 14:01:41
>>> 139687784537472 [Note] /usr/sbin/mysqld (mysqld 10.1.44-MariaDB-0+deb9u1)
>>> starting as process 10318 ...
>>> May 14 14:01:41 gittest mysqld[10318]: 2020-05-14 14:01:41
>>> 139687784537472 [ERROR] COLLATION 'utf8mb4_general_ci' is not valid for
>>> CHARACTER SET 'utf8'
>>> May 14 14:01:41 gittest mysqld[10318]: 2020-05-14 14:01:41
>>> 139687784537472 [ERROR] Aborting
>>> May 14 14:01:41 gittest systemd[1]: mariadb.service: Main process
>>> exited, code=exited, status=1/FAILURE
>>> May 14 14:01:41 gittest systemd[1]: Failed to start MariaDB 10.1.44
>>> database server.
>>>
>>> When I comment out these 2 addition it starts fine and I can retrieve
>>> the following:
>>>
>>> MariaDB [(none)]> SHOW COLLATION LIKE 'utf8%';
>>>
>>> +--+-+-+-+--+-+
>>> | Collation| Charset | Id  | Default | Compiled |
>>> Sortlen |
>>>
>>> +

Re: error installing mysqlclient

[Adam Weremczuk]

Hi Christian,

I've figured this out myself.

"libmariadbclient-dev" appears to be working for MariaDB and
"libmysqlclient-dev" for MySQL

Thanks,
Adam

On Mon, 18 May 2020 at 04:42, Christian Hammond 
wrote:

> Hi Adam,
>
> Try installing the mariadb-devel package from yum and then re-installing
> the mysqlclient Python package.
>
> The pymysql package is not supported by Django (at least not the version
> used by Review Board).
>
> I'll see about updating the docs for MariaDB.
>
> Christian
>
> On Thu, May 14, 2020 at 8:12 AM Adam Weremczuk 
> wrote:
>
>> I've tried "sudo pip install pymysql" instead which installed fine.
>>
>> Now when running "rb-site install" I'm not presented with MySQL / MariaDB
>> option at all:
>>
>> * What database type will you be using?
>>
>>
>> You can type either the name or the number from the list below.
>>
>>
>> (1) sqlite3 (not supported for production use)
>>
>>
>> Database Type:
>>
>>
>> I'm not sure if it's related to mysqlclient or the other issue I've had:
>> https://groups.google.com/d/msg/reviewboard/rm3UK8n5gbE/d_EOTcr8CQAJ
>>
>> --
>> 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
>> "Review Board Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to reviewboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/reviewboard/12dd45b1-b9a0-4162-b623-d9d17b82fb7d%40googlegroups.com
>> <https://groups.google.com/d/msgid/reviewboard/12dd45b1-b9a0-4162-b623-d9d17b82fb7d%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> --
> Christian Hammond
> President/CEO of Beanbag <https://www.beanbaginc.com/>
> Makers of Review Board <https://www.reviewboard.org/>
>
> --
> 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
> "Review Board Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/reviewboard/CAE7Vndnm6kz-66Lc3hNZMj63HoenEnnUiDnL5Xpe_Xd1X_1-4Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/reviewboard/CAE7Vndnm6kz-66Lc3hNZMj63HoenEnnUiDnL5Xpe_Xd1X_1-4Q%40mail.gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/CALC-DAEh0q8yLArD2QwFSP5QwJ3TLn6EF4GzLyXji4Xx-7w0Jw%40mail.gmail.com.

Re: utf8 colation error

[Adam Weremczuk]

I don't think utf8mb4 was a good idea and I believe it's now leading to:

sudo rb-site install /var/www/mysite
(...)
* Installing the site...
(...)
Creating table scmtools_repository

[!] There was an error synchronizing the database. Make sure the
database is created and has the appropriate permissions, and then
continue.
[!] Details: (1071, 'Specified key was too long; max key length is 767
bytes')

Press Enter to continue



On Thursday, 14 May 2020 16:01:35 UTC+1, Adam Weremczuk wrote:
>
> Hi all,
>
> Following installation guide for MySQL I've added to /etc/mysql/my.cnf
>
> [client]
> default-character-set=utf8
>
> [mysqld]
> character-set-server=utf8
>
> MariaDB fails to start:
>
> May 14 14:01:41 gittest systemd[1]: Starting MariaDB 10.1.44 database 
> server...
> May 14 14:01:41 gittest mysqld[10318]: 2020-05-14 14:01:41 139687784537472 
> [Note] /usr/sbin/mysqld (mysqld 10.1.44-MariaDB-0+deb9u1) starting as 
> process 10318 ...
> May 14 14:01:41 gittest mysqld[10318]: 2020-05-14 14:01:41 139687784537472 
> [ERROR] COLLATION 'utf8mb4_general_ci' is not valid for CHARACTER SET 'utf8'
> May 14 14:01:41 gittest mysqld[10318]: 2020-05-14 14:01:41 139687784537472 
> [ERROR] Aborting
> May 14 14:01:41 gittest systemd[1]: mariadb.service: Main process exited, 
> code=exited, status=1/FAILURE
> May 14 14:01:41 gittest systemd[1]: Failed to start MariaDB 10.1.44 
> database server.
>
> When I comment out these 2 addition it starts fine and I can retrieve the 
> following:
>
> MariaDB [(none)]> SHOW COLLATION LIKE 'utf8%';
>
> +--+-+-+-+--+-+
> | Collation| Charset | Id  | Default | Compiled | 
> Sortlen |
>
> +--+-+-+-+--+-+
> | utf8_general_ci  | utf8|  33 | Yes | Yes  |  
>  1 |
> | utf8_bin | utf8|  83 | | Yes  |  
>  1 |
> | utf8_unicode_ci  | utf8| 192 | | Yes  |  
>  8 |
> | utf8_icelandic_ci| utf8| 193 | | Yes  |  
>  8 |
> | utf8_latvian_ci  | utf8| 194 | | Yes  |  
>  8 |
> | utf8_romanian_ci | utf8| 195 | | Yes  |  
>  8 |
> | utf8_slovenian_ci| utf8| 196 | | Yes  |  
>  8 |
> | utf8_polish_ci   | utf8| 197 | | Yes  |  
>  8 |
> | utf8_estonian_ci | utf8| 198 | | Yes  |  
>  8 |
> | utf8_spanish_ci  | utf8| 199 | | Yes  |  
>  8 |
> | utf8_swedish_ci  | utf8| 200 | | Yes  |  
>  8 |
> | utf8_turkish_ci  | utf8| 201 | | Yes  |  
>  8 |
> | utf8_czech_ci| utf8| 202 | | Yes  |  
>  8 |
> | utf8_danish_ci   | utf8| 203 | | Yes  |  
>  8 |
> | utf8_lithuanian_ci   | utf8| 204 | | Yes  |  
>  8 |
> | utf8_slovak_ci   | utf8| 205 | | Yes  |  
>  8 |
> | utf8_spanish2_ci | utf8| 206 | | Yes  |  
>  8 |
> | utf8_roman_ci| utf8| 207 | | Yes  |  
>  8 |
> | utf8_persian_ci  | utf8| 208 | | Yes  |  
>  8 |
> | utf8_esperanto_ci| utf8| 209 | | Yes  |  
>  8 |
> | utf8_hungarian_ci| utf8| 210 | | Yes  |  
>  8 |
> | utf8_sinhala_ci  | utf8| 211 | | Yes  |  
>  8 |
> | utf8_german2_ci  | utf8| 212 | | Yes  |  
>  8 |
> | utf8_croatian_mysql561_ci| utf8| 213 | | Yes  |  
>  8 |
> | utf8_unicode_520_ci  | utf8| 214 | | Yes  |  
>  8 |
> | utf8_vietnamese_ci   | utf8| 215 | | Yes  |  
>  8 |
> | utf8_general_mysql500_ci | utf8| 223 | | Yes  |  
>  1 |
> | utf8_croatian_ci | utf8| 576 | | Yes  |  
>  8 |
> | utf8_myanmar_ci  | utf8| 577 | | Yes  |  
>  8 |
> | utf8_thai_520_w2 | utf8| 578 | | Yes  |  
>  4 |
> | utf8mb4_general_ci   | utf8mb4 |  45 | Yes | Yes  |  
>  1 |
> | utf8mb4_bin  | utf8mb4 |  46 | | Yes  |  
>  1 |
> | utf8mb4_unicode_ci   | utf8mb4 | 224 | | Yes  |  
>  8 |
> | utf8mb4_icelandic_ci | utf8mb4 | 2

Re: error installing mysqlclient

[Adam Weremczuk]

I've tried "sudo pip install pymysql" instead which installed fine.

Now when running "rb-site install" I'm not presented with MySQL / MariaDB 
option at all:

* What database type will you be using?


You can type either the name or the number from the list below.


(1) sqlite3 (not supported for production use)


Database Type:


I'm not sure if it's related to mysqlclient or the other issue I've 
had: https://groups.google.com/d/msg/reviewboard/rm3UK8n5gbE/d_EOTcr8CQAJ 

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/12dd45b1-b9a0-4162-b623-d9d17b82fb7d%40googlegroups.com.

utf8 colation error

[Adam Weremczuk]

Hi all,

Following installation guide for MySQL I've added to /etc/mysql/my.cnf

[client]
default-character-set=utf8

[mysqld]
character-set-server=utf8

MariaDB fails to start:

May 14 14:01:41 gittest systemd[1]: Starting MariaDB 10.1.44 database 
server...
May 14 14:01:41 gittest mysqld[10318]: 2020-05-14 14:01:41 139687784537472 
[Note] /usr/sbin/mysqld (mysqld 10.1.44-MariaDB-0+deb9u1) starting as 
process 10318 ...
May 14 14:01:41 gittest mysqld[10318]: 2020-05-14 14:01:41 139687784537472 
[ERROR] COLLATION 'utf8mb4_general_ci' is not valid for CHARACTER SET 'utf8'
May 14 14:01:41 gittest mysqld[10318]: 2020-05-14 14:01:41 139687784537472 
[ERROR] Aborting
May 14 14:01:41 gittest systemd[1]: mariadb.service: Main process exited, 
code=exited, status=1/FAILURE
May 14 14:01:41 gittest systemd[1]: Failed to start MariaDB 10.1.44 
database server.

When I comment out these 2 addition it starts fine and I can retrieve the 
following:

MariaDB [(none)]> SHOW COLLATION LIKE 'utf8%';
+--+-+-+-+--+-+
| Collation| Charset | Id  | Default | Compiled | 
Sortlen |
+--+-+-+-+--+-+
| utf8_general_ci  | utf8|  33 | Yes | Yes  |  
 1 |
| utf8_bin | utf8|  83 | | Yes  |  
 1 |
| utf8_unicode_ci  | utf8| 192 | | Yes  |  
 8 |
| utf8_icelandic_ci| utf8| 193 | | Yes  |  
 8 |
| utf8_latvian_ci  | utf8| 194 | | Yes  |  
 8 |
| utf8_romanian_ci | utf8| 195 | | Yes  |  
 8 |
| utf8_slovenian_ci| utf8| 196 | | Yes  |  
 8 |
| utf8_polish_ci   | utf8| 197 | | Yes  |  
 8 |
| utf8_estonian_ci | utf8| 198 | | Yes  |  
 8 |
| utf8_spanish_ci  | utf8| 199 | | Yes  |  
 8 |
| utf8_swedish_ci  | utf8| 200 | | Yes  |  
 8 |
| utf8_turkish_ci  | utf8| 201 | | Yes  |  
 8 |
| utf8_czech_ci| utf8| 202 | | Yes  |  
 8 |
| utf8_danish_ci   | utf8| 203 | | Yes  |  
 8 |
| utf8_lithuanian_ci   | utf8| 204 | | Yes  |  
 8 |
| utf8_slovak_ci   | utf8| 205 | | Yes  |  
 8 |
| utf8_spanish2_ci | utf8| 206 | | Yes  |  
 8 |
| utf8_roman_ci| utf8| 207 | | Yes  |  
 8 |
| utf8_persian_ci  | utf8| 208 | | Yes  |  
 8 |
| utf8_esperanto_ci| utf8| 209 | | Yes  |  
 8 |
| utf8_hungarian_ci| utf8| 210 | | Yes  |  
 8 |
| utf8_sinhala_ci  | utf8| 211 | | Yes  |  
 8 |
| utf8_german2_ci  | utf8| 212 | | Yes  |  
 8 |
| utf8_croatian_mysql561_ci| utf8| 213 | | Yes  |  
 8 |
| utf8_unicode_520_ci  | utf8| 214 | | Yes  |  
 8 |
| utf8_vietnamese_ci   | utf8| 215 | | Yes  |  
 8 |
| utf8_general_mysql500_ci | utf8| 223 | | Yes  |  
 1 |
| utf8_croatian_ci | utf8| 576 | | Yes  |  
 8 |
| utf8_myanmar_ci  | utf8| 577 | | Yes  |  
 8 |
| utf8_thai_520_w2 | utf8| 578 | | Yes  |  
 4 |
| utf8mb4_general_ci   | utf8mb4 |  45 | Yes | Yes  |  
 1 |
| utf8mb4_bin  | utf8mb4 |  46 | | Yes  |  
 1 |
| utf8mb4_unicode_ci   | utf8mb4 | 224 | | Yes  |  
 8 |
| utf8mb4_icelandic_ci | utf8mb4 | 225 | | Yes  |  
 8 |
| utf8mb4_latvian_ci   | utf8mb4 | 226 | | Yes  |  
 8 |
| utf8mb4_romanian_ci  | utf8mb4 | 227 | | Yes  |  
 8 |
| utf8mb4_slovenian_ci | utf8mb4 | 228 | | Yes  |  
 8 |
| utf8mb4_polish_ci| utf8mb4 | 229 | | Yes  |  
 8 |
| utf8mb4_estonian_ci  | utf8mb4 | 230 | | Yes  |  
 8 |
| utf8mb4_spanish_ci   | utf8mb4 | 231 | | Yes  |  
 8 |
| utf8mb4_swedish_ci   | utf8mb4 | 232 | | Yes  |  
 8 |
| utf8mb4_turkish_ci   | utf8mb4 | 233 | | Yes  |  
 8 |
| utf8mb4_czech_ci | utf8mb4 | 234 | | Yes  |  
 8 |
| utf8mb4_danish_ci| utf8mb4 | 235 | | Yes  |  
 8 |
| utf8mb4_lithuanian_ci| utf8mb4 | 236 | | Yes  |  
 8 |
| utf8mb4_slovak_ci| utf8mb4 | 237 | | Yes  |  
 8 |
| utf8mb4_spanish2_ci  | 

error installing mysqlclient

[Adam Weremczuk]

Hi all,

I have been trying to install on Debian 9 following: 
https://www.reviewboard.org/docs/manual/3.0/admin/installation/linux/

Everything was going fine until:

 sudo pip install -U mysqlclient
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. 
Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 
will drop support for Python 2.7 in January 2021. More details about Python 
2 support in pip, can be found at 
https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Collecting mysqlclient
  Using cached mysqlclient-1.4.6.tar.gz (85 kB)
ERROR: Command errored out with exit status 1:
 command: /usr/bin/python -c 'import sys, setuptools, tokenize; 
sys.argv[0] = '"'"'/tmp/pip-install-yERS_t/mysqlclient/setup.py'"'"'; 
__file__='"'"'/tmp/pip-install-yERS_t/mysqlclient/setup.py'"'"';f=getattr(tokenize,
 
'"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', 
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' 
egg_info --egg-base /tmp/pip-pip-egg-info-f9sP8G
 cwd: /tmp/pip-install-yERS_t/mysqlclient/
Complete output (12 lines):
sh: 1: mysql_config: not found
sh: 1: mariadb_config: not found
sh: 1: mysql_config: not found
Traceback (most recent call last):
  File "", line 1, in 
  File "/tmp/pip-install-yERS_t/mysqlclient/setup.py", line 16, in 

metadata, options = get_config()
  File "setup_posix.py", line 61, in get_config
libs = mysql_config("libs")
  File "setup_posix.py", line 29, in mysql_config
raise EnvironmentError("%s not found" % (_mysql_config_path,))
EnvironmentError: mysql_config not found

ERROR: Command errored out with exit status 1: python setup.py egg_info 
Check the logs for full command output.

Mysql-server (mariadb-server) is already installed.
Installing mysql-client doesn't make this error go away.

Any idea?

Cheers,
Adam

-- 
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 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/reviewboard/998b8834-daf2-40ed-8ad3-690fcfca3da9%40googlegroups.com.