It is strange that the structure of the table is not correct and the corresponding bucket are marked as skipped… I'm wondering if it comes from the generation/update of the appliance.

Could you please issue the following command and see if it changes things?

ALTER TABLE tracker_changeset_value_text ADD COLUMN body_format varchar(16) NOT NULL default 'text';

+----+-------------------------------------------------------------------------------------------------------------------+---------------------+---------------------+--------+
| id | script                                                                                                            | start_date          | end_date            | status |
+----+-------------------------------------------------------------------------------------------------------------------+---------------------+---------------------+--------+
| 37 | /usr/share/codendi/plugins/tracker/db/mysql/updates/2012/201206211511_add_body_format_column.php                  | 2013-10-03 15:42:08 | 2013-10-03 15:42:08 |      3 |
| 81 | /usr/share/codendi/plugins/tracker/db/mysql/updates/2013/201310301030_add_body_format_on_field_text_changeset.php | 2013-11-12 09:27:42 | 2013-11-12 09:27:42 |      3 |
+----+-------------------------------------------------------------------------------------------------------------------+---------------------+---------------------+--------+
2 rows in set (0.00 sec)

It seems that an upgrade has failed since you should have the following:

*************************** 1. row ***************************
       Table: tracker_changeset_value_text
Create Table: CREATE TABLE `tracker_changeset_value_text` (
  `changeset_value_id` int(11) NOT NULL,
  `value` text NOT NULL,
  `body_format` varchar(16) NOT NULL default 'text',
  PRIMARY KEY  (`changeset_value_id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8
1 row in set (0.00 sec)

What is the result of the following sql command?

SELECT * FROM forge_upgrade_bucket WHERE script LIKE '%body_format%';

First you need to know the codendiadm password to connect to the database. You should find it in /etc/codendi/conf/database.inc on your server, alongside the name of the database ($sys_dbpasswd and $sys_dbname).

Then issue the following command:

$> mysql -u codendiadm -p codendi

Where codendi is the name of the database (may be tuleap). Once connected to mysql (it will prompt the password), issue the command:

mysql> SHOW CREATE TABLE tracker_changeset_value_text \G

And copy-paste here the result.

Hi Laurent,

What is the result of the following sql command ?

SHOW CREATE TABLE tracker_changeset_value_text;