All;
I'm having some issues performing a site migration of RB 1.5.2 to 1.7.14
from an EOL server to a VM. Here are the steps I preformed:
1. Took SQL dump of reviewboard database and restored on new system
2. Took copy of application web root and copied to new system
3. Configured memcached on n
l cause of
> the problems.
>
> You also need to be sure your database is completely wiped before
> importing, so that there aren't any conflicts there.
>
> I don't remember which version of django-evolution we depended on back in
> 1.7.14, but make sure you have django
>
> Christian;
>
Good news! Turns out the dump has been truncated by the allowed_packet_size
for mysqldump (problem with the interface between the seat and keyboard).
The upgrade succeeded, however I had to alter the engine type of all the
tables from myisam to innodb.
Can you advise on updat
Your database dump appears incomplete. Try dumping with
--max_allowed_packet=512M (large packet to avoid truncation). Check your
1.5.X db and verify the table exists in production and in the backup. Also
verify all your tables are InnoDB instead of MYISAM, you can make manual
modification to th
Verify your static and media settings in your web server configuration.
You will probably have to post your apache vhost or lighthttp confg for
better help.
On Tuesday, March 18, 2014 6:07:16 AM UTC-7, shravanthi s wrote:
>
> Hi,
>
> We installed review board succesfully and created a site as we
e it couldn't
> access some table. So I temporarily overrode django's default database
> handler to use mysql + client configs in my.cnf (only a single site will
> reside on this VM) via django's conf/global_settings.py, I then ran
> './reviewboard/manage.py
March 19, 2014 3:11:13 AM UTC-7, Bhaskar Roy wrote:
>
> Hi Kevin,
>
> I did what you said but I am on same page.
>
> Can you please provide the procedure to do migration.
>
>
> regards
> bahskar
>
>
> On Wed, Mar 19, 2014 at 12:38 AM, Kevin Phillips <
&g
Christian;
Could he not just modify his settings_local.py to reflect to updates to the
file format. The specific errors are for CACHES and DATABASES which are
defined in that file. I understand Django-1.4 is not supposed to be
supported.
KP
On Thursday, August 30, 2012 4:25:36 PM UTC-7, Chris
mmond - chi...@chipx86.com
> Review Board - http://www.reviewboard.org
> Beanbag, Inc. - http://www.beanbaginc.com
>
>
> On Wed, Mar 19, 2014 at 3:20 PM, Kevin Phillips
>
> > wrote:
>
>> Christian;
>>
>> Could he not just modify his settings_local.py
x27;PASSWORD': 'password',
> 'HOST': 'localhost',
> },
> }
>
> # Unique secret key. Don't share this with anybody.
> SECRET_KEY = 'ic%zzz9a#p_m#1=lip_&5_1mkidljkgh89090t@s93fku#kdh@c'
>
> # Cache backend settin
;
> /Bhaskar
>
> On Sunday, 23 March 2014 02:19:22 UTC+5:30, Kevin Phillips wrote:
>>
>>
>> The devs changed the format to:
>> DATABASES = {
>> 'default' : {
>> 'ENGINE': 'django.db.backends,mysql',
>> 'NAM
11 matches
Mail list logo
