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\
>
>
>
# 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.
>
>
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
pr 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 work right migrating the
> database.
>
> David
>
> On Wed, Apr 5, 2023 at 4:55 AM Adam Werem
...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
> M
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
te:
> 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
Board 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
que 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
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
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 installe
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
s. 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 "s
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,
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:
>
> 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
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:
->
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 [.]
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
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
Hi all,
Review Board 3.0.17
My LDAP settings:
-> Authentication
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
om 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
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/
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
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]:
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
28 matches
Mail list logo
