[rt-devel] RT 4.2.7: SQL error on ticket traffic

Brian McNally bmcnally at uw.edu
Fri Sep 26 16:19:08 EDT 2014


Note that the statement works fine for me on one RT 4.2.7 instance and 
fails on the other. The difference in configuration is the original 
database I was migrating from (a 3.6.6 RT instance). The DB upgrade 
process for both was similar without any critical errors.

The only errors/warnings I saw during upgrade are listed below:

Processing 4.0.1
Now inserting database ACLs.
Now inserting data.
[1010] [Fri Sep 26 18:28:29 2014] [error]: Invalid right. Couldn't 
canonicalize right 'AdminAllPersonalGroups' 
(/data/tmp/rt-upgrade/rt-4.2.7/sbin/../lib/RT/ACE.pm:456)
[1010] [Fri Sep 26 18:28:29 2014] [error]: Invalid right. Couldn't 
canonicalize right 'AdminOwnPersonalGroups' 
(/data/tmp/rt-upgrade/rt-4.2.7/sbin/../lib/RT/ACE.pm:456)
[1010] [Fri Sep 26 18:28:29 2014] [error]: Invalid right. Couldn't 
canonicalize right 'DelegateRights' 
(/data/tmp/rt-upgrade/rt-4.2.7/sbin/../lib/RT/ACE.pm:456)
[1010] [Fri Sep 26 18:28:29 2014] [error]: Invalid right. Couldn't 
canonicalize right 'AdminAllPersonalGroups' 
(/data/tmp/rt-upgrade/rt-4.2.7/sbin/../lib/RT/ACE.pm:456)
[1010] [Fri Sep 26 18:28:29 2014] [error]: Invalid right. Couldn't 
canonicalize right 'AdminOwnPersonalGroups' 
(/data/tmp/rt-upgrade/rt-4.2.7/sbin/../lib/RT/ACE.pm:456)
[1010] [Fri Sep 26 18:28:30 2014] [error]: Invalid right. Couldn't 
canonicalize right 'DelegateRights' 
(/data/tmp/rt-upgrade/rt-4.2.7/sbin/../lib/RT/ACE.pm:456)
...
Processing 4.1.22
Now populating database schema.
Now inserting data.
[1010] [Fri Sep 26 18:29:42 2014] [info]: Going to delete all 
SMIMEKeyNotAfter attributes (./etc/upgrade/4.1.22/content:61)
Processing 4.1.23
Now inserting database indexes.
[1010] [Fri Sep 26 18:29:48 2014] [warning]: Records in Users table had 
non-unique values in Name column. Name has been changed for such 
records, and now matches '%-dup-%' (etc/upgrade/4.1.23/indexes:81)

Note that my other thread (about message encoding) is dealing with the 
RT 4.2.7 instance that does not suffer from this problem. At the moment 
the production instance that suffers from this problem is still version 
3.6.6 because this issue is a non-starter.

--
Brian McNally

On 09/26/2014 01:02 PM, Alex Vandiver wrote:
> On 09/25/2014 08:05 PM, Brian McNally wrote:
>> rt3_admin=# SELECT main.* FROM Scrips main JOIN ObjectScrips
>> ObjectScrips_1 ON ( ObjectScrips_1.Scrip = main.id ) JOIN
>> ScripConditions ScripConditions_2 ON ( ScripConditions_2.id =
>> main.ScripCondition ) WHERE (ObjectScrips_1.ObjectId = '3' OR
>> ObjectScrips_1.ObjectId = '0') AND (ObjectScrips_1.Stage =
>> 'TransactionCreate') AND (ScripConditions_2.ApplicableTransTypes LIKE
>> '%Create%' OR ScripConditions_2.ApplicableTransTypes LIKE '%Any%') AND
>> (main.Disabled = '0') GROUP BY main.id ORDER BY
>> MIN(ObjectScrips_1.SortOrder) ASC
>> rt3_admin-# ;
>> ERROR: column "main.description" must appear in the GROUP BY clause or
>> be used in an aggregate function
>> LINE 1: SELECT main.* FROM Scrips main JOIN ObjectScrips ObjectScrip...
>
> That statement works just fine for me on a clean RT 4.2.7 database with
> Pg 9.3.5.  I suspect something is odd with your Postgres database or
> configuration -- this is likely relevant to your other thread as well.
>
>> What's confusing is that I also upgraded another RT instance using the
>> same procedure and I do not have this same issue (the SQL query above
>> and ticket updates work fine).
>
> Compare your Pg configurations.
>   - Alex
>


More information about the rt-devel mailing list