Subject: The mailing list for listmasters using Sympa
List archive
Re: [sympa-users] db upgrade problem: 6.1.23 to 6.2.13
- From: Amos <address@concealed>
- To: David Verdin <address@concealed>
- Cc: "address@concealed >> address@concealed" <address@concealed>
- Subject: Re: [sympa-users] db upgrade problem: 6.1.23 to 6.2.13
- Date: Fri, 26 Feb 2016 14:49:48 -0600
OK, so it turned out that the error message was misleading. The account I was using to access the db didn't have sufficient perms to be able to add tables, and instead of the error message containing "db_host", it used the local hostname, so I got confused by that.
The db restrictions have been lifted, but now I encounter another problem (going to 6.2.14 since just released):
notice Sympa::DatabaseDriver::MySQL::update_field() ALTER TABLE exclusion_table CHANGE robot_exclusion robot_exclusion varchar(80) err main::#798 > Sympa::Upgrade::upgrade#118 > Sympa::DatabaseManager::probe_db#214 > Sympa::DatabaseManager::_check_primary_key#479 > Sympa::DatabaseDriver::MySQL::set_primary_key#368 > Sympa::Database::do_query#277 Unable to execute SQL statement "ALTER TABLE exclusion_table ADD PRIMARY KEY (user_exclusion,robot_exclusion,family_exclusion,list_exclusion)": (22004) Invalid use of NULL value err main::#798 > Sympa::Upgrade::upgrade#118 > Sympa::DatabaseManager::probe_db#214 > Sympa::DatabaseManager::_check_primary_key#479 > Sympa::DatabaseDriver::MySQL::set_primary_key#374 Could not set fields user_exclusion,robot_exclusion,family_exclusion,list_exclusion as primary key for table exclusion_table in database ais_sympa err main::#798 > Sympa::Upgrade::upgrade#118 > Sympa::DatabaseManager::probe_db#223 Unable to check the validity of primary key for table exclusion_table. Aborting err main::#798 > Sympa::Upgrade::upgrade#119 Database ais_sympa defined in sympa.conf has not the right structure or is unreachable. verify db_xxx parameters in sympa.conf err main::#801 Migration from 6.1.23 to 6.2.14 failed
On Wed, Feb 24, 2016 at 4:14 AM, David Verdin <address@concealed> wrote:
Hi Amos,
Check that your sympa.conf file is correct.
Over migration from 6.1 to 6.2, main config files are merged into sympa.conf and sympa.conf can be moved.
Also check in this file that the db name is correct. I don't know how it could have changed but it looks like Sympa is not finding it.
Regards,
David
Le 24/02/2016 03:04, Amos (via sympa-users Mailing List) a écrit :
Trying to upgrade test instance of Sympa. The db is on another box, and has worked fine in the past. However, the upgrade script doesn't seem to know the db is on another box because it is attempting to upgrade the db on the same box, but blows up because it doesn't exist.
err main::#798 > Sympa::Upgrade::upgrade#119 > Sympa::DatabaseManager::probe_db#156 > Sympa::DatabaseDriver::MySQL::add_table#177 > Sympa::Database::do_query#277 Unable to execute SQL statement "CREATE TABLE notification_table (temporary INT) DEFAULT CHARACTER SET utf8": (42000) CREATE command denied to user 'ais_sympa_app'@'aisdsympa01.x.edu' for table 'notification_table'
it instead should be looking at the db entry on the config file, and connect to that host.
Amos
--
A bug in Sympa? Quick! To the bug tracker!
David Verdin
Études et projets applicatifs
Tél : +33 2 23 23 69 71
Fax : +33 2 23 23 71 21
www.renater.fr
RENATER
263 Avenue du Gal Leclerc
35042 Rennes Cedex
-
[sympa-users] db upgrade problem: 6.1.23 to 6.2.13,
Amos, 02/24/2016
-
Re: [sympa-users] db upgrade problem: 6.1.23 to 6.2.13,
David Verdin, 02/24/2016
- Re: [sympa-users] db upgrade problem: 6.1.23 to 6.2.13, Amos, 02/26/2016
-
Re: [sympa-users] db upgrade problem: 6.1.23 to 6.2.13,
David Verdin, 02/24/2016
Archive powered by MHonArc 2.6.19+.