[rt-users] Upgrading 4.0.8 -> 4.2.0 breaking outgoing email

[Wright, Cory (CDC/OID/NCEZID) (CTR)]

Kevin



Version:

mysql  Ver 14.14 Distrib 5.1.69, for redhat-linux-gnu (x86_64) using readline 5.1



all data locations pointed to a 160GiB FusionIO.

and various mysql options:

max_allowed_packet             = 16M

max_connect_errors             = 1000000

skip_name_resolve

sql_mode                       = STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_AUTO_VALUE_ON_Z               ERO,NO_ENGINE_SUBSTITUTION,NO_ZERO_DATE,NO_ZERO_IN_DATE,ONLY_FULL_GROUP_BY

sysdate_is_now                 = 1

innodb                         = FORCE

#innodb_strict_mode             = 1



tmp_table_size                 = 32M

max_heap_table_size            = 32M

query_cache_type               = 0

query_cache_size               = 0

max_connections                = 500

thread_cache_size              = 50

open_files_limit               = 65535

table_definition_cache         = 1024

table_open_cache               = 2048



innodb_flush_method            = O_DIRECT

innodb_log_files_in_group      = 2

innodb_log_file_size           = 512M

innodb_flush_log_at_trx_commit = 1

innodb_file_per_table          = 1

innodb_buffer_pool_size        = 24G







-----Original Message-----
From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of Kevin Falcone
Sent: Wednesday, October 30, 2013 3:20 PM
To: rt-users at lists.bestpractical.com
Subject: Re: [rt-users] Upgrading 4.0.8 -> 4.2.0 breaking outgoing email



On Tue, Oct 29, 2013 at 09:32:20PM +0000, Wright, Cory (CDC/OID/NCIRD) (CTR) wrote:

>    After some further troubleshooting I have determined that email from the upgraded 4.2.0

>    instance is in fact working (testing with dashboard subs), but that no scrips execute.  The

>    bulk of errors in my debug log are:

>    [6973] [Tue Oct 29 21:24:15 2013] [warning]: DBD::mysql::st execute failed:

>    'rt_helpdesk_420.main.Name' isn't in GROUP BY at

>    /usr/local/share/perl5/DBIx/SearchBuilder/Handle.pm line 589. (/usr/local/share/perl5/

>    DBIx/SearchBuilder/Handle.pm:589)

>    [6973] [Tue Oct 29 21:24:15 2013] [warning]: RT::Handle=HASH(0x7fd5eea7f588) couldn't execute

>    the query 'SELECT main.* FROM CustomFields main JOIN ObjectCustomFields ObjectCustomFields_1

>    ON ( ObjectCustomFields

>    _1.CustomField = main.id )  WHERE (ObjectCustomFields_1.ObjectId = '1' OR

>    ObjectCustomFields_1.ObjectId = '0') AND (main.Disabled = '0') AND (main.LookupType =

>    'RT::Queue-RT::Ticket') AND (main.id = '0')  GROUP

>    BY main.id  ORDER BY MIN(ObjectCustomFields_1.SortOrder) ASC ' at

>    /usr/local/share/perl5/DBIx/SearchBuilder/Handle.pm line 602.

>

>    I am unable to determine the impact of these warnings or if they are the culprit.  Full log

>    can also be seen in previous communication.



These warnings are almost certainly a culprit.



What version of mysql and what non-standard options are you using?

On a stock 5.5.27 your query runs fine.



-kevin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20131030/c51923de/attachment.htm>