Can't create new tickets, new problem

RT Users
1

My install of RT 3.6.1 (on Solaris 10, mysql 5.0.22) has been working very
nicely for several months. We only have about 80 tickets, but we have been
able to create tickets with no problems both in the web interface and via
email. That is, until today. Now I get:

error: Transactions not supported by database at
/opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm line 1668.
context: …
1664: sub begin_work { 1665: my $dbh = shift; 1666: return
$dbh->set_err(1, “Already in a transaction”) 1667: unless
$dbh->FETCH(‘AutoCommit’); 1668: $dbh->STORE(‘AutoCommit’, 0); # will
croak if driver doesn’t support it 1669: $dbh->STORE(‘BegunWork’, 1); #
trigger post commit/rollback action 1670: return 1; 1671: } 1672:

…
code stack: /opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm:1668
/opt/perlsite/lib/site_perl/5.8.7/DBIx/SearchBuilder/Handle.pm:720
/opt/rt3/lib/RT/Ticket_Overlay.pm:564
/opt/rt3/lib/RT/Interface/Web.pm:446
/opt/rt3/share/html/Ticket/Display.html:103
/opt/rt3/share/html/Ticket/Create.html:300
/opt/rt3/share/html/autohandler:279
when trying to create a ticket on the web. I get similar, but slightly
different errors from an email attempt. I’ve searched the archives and the
wiki but any mention of the keywords here are from 2002 or so.

I checked the rt3.Transactions table on the mysql server it it is INNODB.
Are there other tables to check?

I haven’t modified RT or the mysql server at all in many weeks. However,
Solaris patches were applied last night. Unfortunately, I can’t see anything
has changed in the RT or the mysql install. And SearchBuilder is up to date
according to CPAN.

Appreciate any ideas of where to look.

Thanks,
Steve Holmes

2

Which Solaris patches were installed? Have you tried backing out of them?

James Moseley

         "Steve Holmes"                                                
         <sholmes42@mac.co                                             
         m>                                                         To 
         Sent by:                  "RT Users"                          
         rt-users-bounces@         <rt-users@lists.bestpractical.com>  
         lists.bestpractic                                          cc 
         al.com                                                        
                                                               Subject 
                                   [rt-users] Can't create new         
         03/07/2007 02:15          tickets, new problem                
         PM

My install of RT 3.6.1 (on Solaris 10, mysql 5.0.22) has been working very
nicely for several months. We only have about 80 tickets, but we have been
able to create tickets with no problems both in the web interface and via
email. That is, until today. Now I get:

error: Transactions not supported by database at
/opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm line 1668.

context:

      ...                                                              
                                                                       
      1664:                                                            
                  sub begin_work {                                     
      1665:                                                            
                  my $dbh = shift;                                     
      1666:                                                            
                  return $dbh->set_err(1, "Already in a transaction")  
      1667:                                                            
                  unless $dbh->FETCH('AutoCommit');                    
      1668:                                                            
                  $dbh->STORE('AutoCommit', 0); # will croak if driver 
                  doesn't support it                                   
      1669:                                                            
                  $dbh->STORE('BegunWork', 1); # trigger post          
                  commit/rollback action                               
      1670:                                                            
                  return 1;                                            
      1671:                                                            
                  }                                                    
      1672:                                                            
                                                                       
      ...

code /opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm:1668
stack: /opt/perlsite/lib/site_perl/5.8.7
/DBIx/SearchBuilder/Handle.pm:720
/opt/rt3/lib/RT/Ticket_Overlay.pm:564
/opt/rt3/lib/RT/Interface/Web.pm:446
/opt/rt3/share/html/Ticket/Display.html:103
/opt/rt3/share/html/Ticket/Create.html:300
/opt/rt3/share/html/autohandler:279

when trying to create a ticket on the web. I get similar, but slightly
different errors from an email attempt. I’ve searched the archives and the
wiki but any mention of the keywords here are from 2002 or so.

I checked the rt3.Transactions table on the mysql server it it is INNODB.
Are there other tables to check?

I haven’t modified RT or the mysql server at all in many weeks. However,
Solaris patches were applied last night. Unfortunately, I can’t see
anything has changed in the RT or the mysql install. And SearchBuilder is
up to date according to CPAN.

Appreciate any ideas of where to look.

Thanks,
Steve Holmes
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

3

James,

It looks like 58 patches were applied on the RT server. I can list them for
you if you like. No we have not tried to back any of them out.

I’m not sure how to know which ones would be appropriate to backout. I’m
about to start reading all of the READMEs for the patches to see if I can
find anything that stands out.

Thanks,
SteveOn 3/7/07, jmoseley@pgtv.com jmoseley@pgtv.com wrote:

Which Solaris patches were installed? Have you tried backing out of them?

James Moseley

         "Steve Holmes"
         <sholmes42@mac.co
         m>                                                         To
         Sent by:                  "RT Users"
         rt-users-bounces@         <rt-users@lists.bestpractical.com>
         lists.bestpractic                                          cc
         al.com
                                                               Subject
                                   [rt-users] Can't create new
         03/07/2007 02:15          tickets, new problem
         PM

My install of RT 3.6.1 (on Solaris 10, mysql 5.0.22) has been working very
nicely for several months. We only have about 80 tickets, but we have been
able to create tickets with no problems both in the web interface and via
email. That is, until today. Now I get:

error: Transactions not supported by database at
/opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm line 1668.

context:

      ...

      1664:
                  sub begin_work {
      1665:
                  my $dbh = shift;
      1666:
                  return $dbh->set_err(1, "Already in a transaction")
      1667:
                  unless $dbh->FETCH('AutoCommit');
      1668:
                  $dbh->STORE('AutoCommit', 0); # will croak if driver
                  doesn't support it
      1669:
                  $dbh->STORE('BegunWork', 1); # trigger post
                  commit/rollback action
      1670:
                  return 1;
      1671:
                  }
      1672:

      ...

code /opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm:1668
stack: /opt/perlsite/lib/site_perl/5.8.7
/DBIx/SearchBuilder/Handle.pm:720
/opt/rt3/lib/RT/Ticket_Overlay.pm:564
/opt/rt3/lib/RT/Interface/Web.pm:446
/opt/rt3/share/html/Ticket/Display.html:103
/opt/rt3/share/html/Ticket/Create.html:300
/opt/rt3/share/html/autohandler:279

when trying to create a ticket on the web. I get similar, but slightly
different errors from an email attempt. I’ve searched the archives and the
wiki but any mention of the keywords here are from 2002 or so.

I checked the rt3.Transactions table on the mysql server it it is INNODB.
Are there other tables to check?

I haven’t modified RT or the mysql server at all in many weeks. However,
Solaris patches were applied last night. Unfortunately, I can’t see
anything has changed in the RT or the mysql install. And SearchBuilder is
up to date according to CPAN.

Appreciate any ideas of where to look.

Thanks,
Steve Holmes

The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

I believe I found the missing link between animal and civilized man. It is
us. -Konrad Lorenz, ethologist, Nobel laureate (1903-1989)

We in America do not have government by the majority. We have government by
the majority who participate. -Thomas Jefferson, third US president,
architect and author (1743-1826)

4

I would look for perl or apache patches. Were these simply Solaris OS
patches for security, or was this a jumbo patch which includes updates for
other installed software. Problem with new versions of Solaris is that
they come with Apache, Sendmail, Perl (I believe) - I wouldn’t install any
of that if possible…

James Moseley

         "Steve Holmes"                                                
         <sholmes42@mac.co                                             
         m>                                                         To 
         Sent by:                  "jmoseley@pgtv.com"                 
         sholmes42@gmail.c         <jmoseley@pgtv.com>                 
         om                                                         cc 
                                   "RT Users"                          
                                   <rt-users@lists.bestpractical.com>, 
         03/07/2007 02:46          rt-users-bounces@lists.bestpractica 
         PM                        l.com                               
                                                               Subject 
                                   Re: [rt-users] Can't create new     
                                   tickets, new problem

James,

It looks like 58 patches were applied on the RT server. I can list them for
you if you like. No we have not tried to back any of them out.

I’m not sure how to know which ones would be appropriate to backout. I’m
about to start reading all of the READMEs for the patches to see if I can
find anything that stands out.

Thanks,
SteveOn 3/7/07, jmoseley@pgtv.com <jmoseley@pgtv.com > wrote:
Which Solaris patches were installed? Have you tried backing out of
them?

James Moseley

           "Steve Holmes"
           <sholmes42@mac.co
           m>

To
Sent by: “RT Users”
rt-users-bounces@ rt-users@lists.bestpractical.com
lists.bestpractic
cc
al.com

Subject
[rt-users] Can’t create new
03/07/2007 02:15 tickets, new problem
PM

My install of RT 3.6.1 (on Solaris 10, mysql 5.0.22) has been working
very
nicely for several months. We only have about 80 tickets, but we have
been
able to create tickets with no problems both in the web interface and via
email. That is, until today. Now I get:

error: Transactions not supported by database at
/opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm line
1668.

context:

        ...

        1664:
                    sub begin_work {
        1665:
                    my $dbh = shift;
        1666:
                    return $dbh->set_err(1, "Already in a transaction")

        1667:
                    unless $dbh->FETCH('AutoCommit');
        1668:
                    $dbh->STORE('AutoCommit', 0); # will croak if

driver
doesn’t support it
1669:
$dbh->STORE(‘BegunWork’, 1); # trigger post
commit/rollback action
1670:
return 1;
1671:
}
1672:

        ...

code /opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm:1668
stack: /opt/perlsite/lib/site_perl/5.8.7
/DBIx/SearchBuilder/Handle.pm:720
/opt/rt3/lib/RT/Ticket_Overlay.pm:564
/opt/rt3/lib/RT/Interface/Web.pm:446
/opt/rt3/share/html/Ticket/Display.html:103
/opt/rt3/share/html/Ticket/Create.html:300
/opt/rt3/share/html/autohandler:279

when trying to create a ticket on the web. I get similar, but slightly
different errors from an email attempt. I’ve searched the archives and
the
wiki but any mention of the keywords here are from 2002 or so.

I checked the rt3.Transactions table on the mysql server it it is INNODB.
Are there other tables to check?

I haven’t modified RT or the mysql server at all in many weeks. However,
Solaris patches were applied last night. Unfortunately, I can’t see
anything has changed in the RT or the mysql install. And SearchBuilder is
up to date according to CPAN.

Appreciate any ideas of where to look.

Thanks,
Steve Holmes
The rt-users Archives

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

I believe I found the missing link between animal and civilized man. It is
us. -Konrad Lorenz, ethologist, Nobel laureate (1903-1989)

We in America do not have government by the majority. We have government by
the majority who participate. -Thomas Jefferson, third US president,
architect and author (1743-1826)

5

These were just simple patches which had not been applied and included all
the patches available. We don’t use Sun’s apache or perl and are careful not
to for this very reason. (Ditto sendmail, but that isn’t relevant to this
issue). The other possibility is that the server might not have been
rebooted, and therefore apache not restarted, since Christmas so some perl
modules might have changed in the mean time, but not been loaded since they
changed. I have to check that.

Thanks,
Steve.On 3/7/07, jmoseley@pgtv.com jmoseley@pgtv.com wrote:

I would look for perl or apache patches. Were these simply Solaris OS
patches for security, or was this a jumbo patch which includes updates for
other installed software. Problem with new versions of Solaris is that
they come with Apache, Sendmail, Perl (I believe) - I wouldn’t install any
of that if possible…

James Moseley

         "Steve Holmes"
         <sholmes42@mac.co
         m>                                                         To
         Sent by:                  "jmoseley@pgtv.com"
         sholmes42@gmail.c         <jmoseley@pgtv.com>
         om                                                         cc
                                   "RT Users"
                                   <rt-users@lists.bestpractical.com>,
         03/07/2007 02:46          rt-users-bounces@lists.bestpractica
         PM                        l.com
                                                               Subject
                                   Re: [rt-users] Can't create new
                                   tickets, new problem

James,

It looks like 58 patches were applied on the RT server. I can list them
for
you if you like. No we have not tried to back any of them out.

I’m not sure how to know which ones would be appropriate to backout. I’m
about to start reading all of the READMEs for the patches to see if I can
find anything that stands out.

Thanks,
Steve

On 3/7/07, jmoseley@pgtv.com <jmoseley@pgtv.com > wrote:
Which Solaris patches were installed? Have you tried backing out of
them?

James Moseley

           "Steve Holmes"
           <sholmes42@mac.co
           m>

To
Sent by: “RT Users”
rt-users-bounces@ <rt-users@lists.bestpractical.com

           lists.bestpractic

cc
al.com

Subject
[rt-users] Can’t create new
03/07/2007 02:15 tickets, new problem
PM

My install of RT 3.6.1 (on Solaris 10, mysql 5.0.22) has been working
very
nicely for several months. We only have about 80 tickets, but we have
been
able to create tickets with no problems both in the web interface and
via
email. That is, until today. Now I get:

error: Transactions not supported by database at
/opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm line
1668.

context:

        ...

        1664:
                    sub begin_work {
        1665:
                    my $dbh = shift;
        1666:
                    return $dbh->set_err(1, "Already in a

transaction")

        1667:
                    unless $dbh->FETCH('AutoCommit');
        1668:
                    $dbh->STORE('AutoCommit', 0); # will croak if

driver
doesn’t support it
1669:
$dbh->STORE(‘BegunWork’, 1); # trigger post
commit/rollback action
1670:
return 1;
1671:
}
1672:

        ...

code /opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm:1668
stack: /opt/perlsite/lib/site_perl/5.8.7
/DBIx/SearchBuilder/Handle.pm:720
/opt/rt3/lib/RT/Ticket_Overlay.pm:564
/opt/rt3/lib/RT/Interface/Web.pm:446
/opt/rt3/share/html/Ticket/Display.html:103
/opt/rt3/share/html/Ticket/Create.html:300
/opt/rt3/share/html/autohandler:279

when trying to create a ticket on the web. I get similar, but slightly
different errors from an email attempt. I’ve searched the archives and
the
wiki but any mention of the keywords here are from 2002 or so.

I checked the rt3.Transactions table on the mysql server it it is
INNODB.
Are there other tables to check?

I haven’t modified RT or the mysql server at all in many weeks. However,
Solaris patches were applied last night. Unfortunately, I can’t see
anything has changed in the RT or the mysql install. And SearchBuilder
is
up to date according to CPAN.

Appreciate any ideas of where to look.

Thanks,
Steve Holmes

6

Again, I would back out of all Sun patches that anything to do with apache
or perl, then see if things work - the problems did not start happening
until you applied those patches… It also appears you are using Sun’s
perl and apache that came with Solaris 10 (or you managed to get from Sun)?
If so, I would stronly recommend not using their packages and recompile
perl and apache (and other associated modules) from scratch.

James Moseley

         "Steve Holmes"                                                
         <sholmes42@mac.co                                             
         m>                                                         To 
         Sent by:                  "jmoseley@pgtv.com"                 
         sholmes42@gmail.c         <jmoseley@pgtv.com>                 
         om                                                         cc 
                                   "RT Users"                          
                                   <rt-users@lists.bestpractical.com>, 
         03/12/2007 02:24          rt-users-bounces@lists.bestpractica 
         PM                        l.com                               
                                                               Subject 
                                   Re: [rt-users] Can't create new     
                                   tickets, new problem

James, thanks for your replies.

All:

[As a reminder I’m on Solaris 10, mysql 5.0.22, RT was 3.6.1, but is now
3.6.3]

I’ve been snooping around and can’t find anything wrong which might cause
this. (I’ve googled, and searched the archives and the wiki.) I’ve checked
the rt3 database. Unless RT is doing something funny, the db is ok. I.e. it
DOES support transactions (except for the sessions table which is a MyISAM
table) It DOES NOT get errors in mysql when I do a start transaction nor
when I do a set autocommitt = 0;

The errors I get in the RT logs are:

Mar 12 10:46:12 localhost RT: Transaction not committed. Usually indicates
a software fault. Data loss may have occurred
(/opt/rt3/lib/RT/Interface/Web/Handler.pm:194)\n

It is of mild curiosity that these errors are occuring on a timed basis
rather than on a usage basis. I.e. no one is actually using RT right now,
except when I’m testing it.

What I did this morning:

I upgraded RT to 3.6.3, I re-installed DBD::mysql on the RT server, I’ve
restarted apache. and I’m still getting this error. I can see tickets in
RT, I just can’t create new tickets or update existing ones.

Here is the raw error as displayed in the browser from trying to create
just one ticket (sorry for the wrap, some of these lines are VERY long):

Transactions not supported by database at /opt/perlsite/lib/site_perl/5.8.7
/sun4-solaris/DBI.pm line 1668.

Trace begun at /opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Exceptions.pm
line 129
HTML::Mason::Exceptions::rethrow_exception(‘Transactions not supported by
database at /opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm line
1668.^J’) called at /opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm
line 1668

DBD::_::db::begin_work(‘DBI::db=HASH(0x1a2ae94)’) called at
/opt/perlsite/lib/site_perl/5.8.7/DBIx/SearchBuilder/Handle.pm line 720
DBIx::SearchBuilder::Handle::BeginTransaction(‘RT::Handle=HASH(0x10d3370)’)
called at /opt/rt3/lib/RT/Ticket_Overlay.pm line 563

RT::ticket::Create(‘RT::Ticket=HASH(0x1f82200)’, ‘DependsOn’,
‘ARRAY(0xabffe8)’, ‘TimeEstimated’, ‘’, ‘RefersTo’, ‘ARRAY(0xac0048)’,
‘ReferredToBy’, ‘ARRAY(0xac0060)’, ‘Status’, ‘open’, ‘Children’,
‘ARRAY(0xac0030)’, ‘Queue’, ‘Unix’, ‘AdminCc’, ‘ARRAY(0xabfaa8)’,
‘CustomField-2’, ‘ARRAY(0x1f89b8c)’, ‘MIMEObj’,
‘MIME::Entity=HASH(0x1f8250c)’, ‘Type’, ‘ticket’, ‘InitialPriority’, 1,
‘Starts’, ‘1970-01-01 00:00:00’, ‘TimeWorked’, ‘’, ‘Requestor’,
‘ARRAY(0xabfa00)’, ‘Cc’, ‘ARRAY(0xabfa54)’, ‘Subject’, ‘This is a test.
Please ignore’, ‘FinalPriority’, 10, ‘TimeLeft’, ‘’, ‘DependedOnBy’,
‘ARRAY(0xac0000)’, ‘Owner’, 22, ‘Parents’, ‘ARRAY(0xac0018)’,
‘CustomField-1’, ‘ARRAY(0x1f89bbc)’, ‘Due’, ‘2007-04-11 22:35:38’) called
at /opt/rt3/lib/RT/Interface/Web.pm line 446

HTML::Mason::Commands::CreateTicket(‘Attachments’, undef, ‘TimeEstimated’,
‘’, ‘Status’, ‘open’, ‘new-DependsOn’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values’, ‘’, ‘Queue’, ‘Unix’, ‘AdminCc’,
‘’, ‘Object-RT::Ticket–CustomField-2-Values’, ‘’, ‘Requestors’, ’

me@purdue.edu’, ‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’,
‘TimeWorked’, ‘’, ‘id’, ‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’,
‘’, ‘Subject’, ‘This is a test. Please ignore’, ‘new-RefersTo’, ‘’,
‘FinalPriority’, 10, ‘RefersTo-new’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’,
‘TimeLeft’, ‘’, ‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1,
‘DependsOn-new’, ‘’, ‘Owner’, 22, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’,
‘Content’, ‘Testing again.^M^J^M^J-- ^M^JSteve’, ‘Due’, ‘2007-04-11
18:35:38’, ‘TimeWorked-TimeUnits’, ‘minutes’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1) called at
/opt/rt3/share/html/Ticket/Display.html line 104

HTML::Mason::Commands::ANON(‘TimeEstimated’, ‘’, ‘Status’, ‘open’,
‘new-DependsOn’, ‘’, ‘Queue’, ‘Unix’,
‘Object-RT::Ticket–CustomField-1-Values’, ‘’, ‘AdminCc’, ‘’,
‘Object-RT::Ticket–CustomField-2-Values’, ‘’, ‘Requestors’, ’

me@purdue.edu’, ‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’,
‘TimeWorked’, ‘’, ‘id’, ‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’,
‘’, ‘Subject’, ‘This is a test. Please ignore’, ‘FinalPriority’, 10,
‘new-RefersTo’, ‘’, ‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1,
‘TimeLeft’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’, ‘RefersTo-new’, ‘’,
‘Owner’, 22, ‘DependsOn-new’, ‘’, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’,
‘Content’, ‘Testing again.^M^J^M^J-- ^M^JSteve’, ‘TimeWorked-TimeUnits’,
‘minutes’, ‘Due’, ‘2007-04-11 18:35:38’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1) called at
/opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Component.pm line 135

HTML::Mason::Component::run(‘HTML::Mason::Component::FileBased=HASH(0x1f81d8c)’,
‘TimeEstimated’, ‘’, ‘Status’, ‘open’, ‘new-DependsOn’, ‘’, ‘Queue’,
‘Unix’, ‘Object-RT::Ticket–CustomField-1-Values’, ‘’, ‘AdminCc’, ‘’,
‘Object-RT::Ticket–CustomField-2-Values’, ‘’, ‘Requestors’, ’

me@purdue.edu’, ‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’,
‘TimeWorked’, ‘’, ‘id’, ‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’,
‘’, ‘Subject’, ‘This is a test. Please ignore’, ‘FinalPriority’, 10,
‘new-RefersTo’, ‘’, ‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1,
‘TimeLeft’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’, ‘RefersTo-new’, ‘’,
‘Owner’, 22, ‘DependsOn-new’, ‘’, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’,
‘Content’, ‘Testing again.^M^J^M^J-- ^M^JSteve’, ‘TimeWorked-TimeUnits’,
‘minutes’, ‘Due’, ‘2007-04-11 18:35:38’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1) called at
/opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Request.pm line 1256

eval {…} at /opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Request.pm line
1246
HTML::Mason::Request::comp(undef, undef, ‘TimeEstimated’, ‘’, ‘Status’,
‘open’, ‘new-DependsOn’, ‘’, ‘Queue’, ‘Unix’,
‘Object-RT::Ticket–CustomField-1-Values’, ‘’, ‘AdminCc’, ‘’,
‘Object-RT::Ticket–CustomField-2-Values’, ‘’, ‘Requestors’, ’

me@purdue.edu’, ‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’,
‘TimeWorked’, ‘’, ‘id’, ‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’,
‘’, ‘Subject’, ‘This is a test. Please ignore’, ‘FinalPriority’, 10,
‘new-RefersTo’, ‘’, ‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1,
‘TimeLeft’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’, ‘RefersTo-new’, ‘’,
‘Owner’, 22, ‘DependsOn-new’, ‘’, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’,
‘Content’, ‘Testing again.^M^J^M^J-- ^M^JSteve’, ‘TimeWorked-TimeUnits’,
‘minutes’, ‘Due’, ‘2007-04-11 18:35:38’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1) called at
/opt/rt3/share/html/Ticket/Create.html line 301

HTML::Mason::Commands::ANON(‘TimeEstimated’, ‘’, ‘Status’, ‘open’,
‘new-DependsOn’, ‘’, ‘Object-RT::Ticket–CustomField-1-Values’, ‘’,
‘Queue’, ‘Unix’, ‘AdminCc’, ‘’, ‘Object-RT::Ticket–CustomField-2-Values’,
‘’, ‘Requestors’, ’

me@purdue.edu’, ‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’,
‘TimeWorked’, ‘’, ‘id’, ‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’,
‘’, ‘Subject’, ‘This is a test. Please ignore’, ‘new-RefersTo’, ‘’,
‘FinalPriority’, 10, ‘RefersTo-new’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’,
‘TimeLeft’, ‘’, ‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1,
‘DependsOn-new’, ‘’, ‘Owner’, 22, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’,
‘Content’, ‘Testing again.^M^J^M^J-- ^M^JSteve’, ‘Due’, ‘2007-04-11
18:35:38’, ‘TimeWorked-TimeUnits’, ‘minutes’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1, ‘TimeEstimated’, ‘’,
‘Status’, ‘open’, ‘new-DependsOn’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values’, ‘’, ‘Queue’, ‘Unix’, ‘AdminCc’,
‘’, ‘Requestors’, ’

me@purdue.edu’, ‘Object-RT::Ticket–CustomField-2-Values’, ‘’,
‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’, ‘TimeWorked’, ‘’, ‘id’,
‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’, ‘’, ‘Subject’, ‘This is
a test. Please ignore’, ‘new-RefersTo’, ‘’, ‘FinalPriority’, 10,
‘RefersTo-new’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’, ‘TimeLeft’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1, ‘DependsOn-new’, ‘’,
‘Owner’, 22, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’, ‘Content’, ‘Testing
again.^M^J^M^J-- ^M^JSteve’, ‘Due’, ‘2007-04-11 18:35:38’,
‘TimeWorked-TimeUnits’, ‘minutes’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1) called at
/opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Component.pm line 135

HTML::Mason::Component::run(‘HTML::Mason::Component::FileBased=HASH(0x1f57fe8)’,
‘TimeEstimated’, ‘’, ‘Status’, ‘open’, ‘new-DependsOn’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values’, ‘’, ‘Queue’, ‘Unix’, ‘AdminCc’,
‘’, ‘Object-RT::Ticket–CustomField-2-Values’, ‘’, ‘Requestors’, ’

me@purdue.edu’, ‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’,
‘TimeWorked’, ‘’, ‘id’, ‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’,
‘’, ‘Subject’, ‘This is a test. Please ignore’, ‘new-RefersTo’, ‘’,
‘FinalPriority’, 10, ‘RefersTo-new’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’,
‘TimeLeft’, ‘’, ‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1,
‘DependsOn-new’, ‘’, ‘Owner’, 22, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’,
‘Content’, ‘Testing again.^M^J^M^J-- ^M^JSteve’, ‘Due’, ‘2007-04-11
18:35:38’, ‘TimeWorked-TimeUnits’, ‘minutes’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1, ‘TimeEstimated’, ‘’,
‘Status’, ‘open’, ‘new-DependsOn’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values’, ‘’, ‘Queue’, ‘Unix’, ‘AdminCc’,
‘’, ‘Requestors’, ’

me@purdue.edu’, ‘Object-RT::Ticket–CustomField-2-Values’, ‘’,
‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’, ‘TimeWorked’, ‘’, ‘id’,
‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’, ‘’, ‘Subject’, ‘This is
a test. Please ignore’, ‘new-RefersTo’, ‘’, ‘FinalPriority’, 10,
‘RefersTo-new’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’, ‘TimeLeft’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1, ‘DependsOn-new’, ‘’,
‘Owner’, 22, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’, ‘Content’, ‘Testing
again.^M^J^M^J-- ^M^JSteve’, ‘Due’, ‘2007-04-11 18:35:38’,
‘TimeWorked-TimeUnits’, ‘minutes’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1) called at
/opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Request.pm line 1256

eval {…} at /opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Request.pm line
1246
HTML::Mason::Request::comp(undef, undef, undef, ‘TimeEstimated’, ‘’,
‘Status’, ‘open’, ‘new-DependsOn’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values’, ‘’, ‘Queue’, ‘Unix’, ‘AdminCc’,
‘’, ‘Object-RT::Ticket–CustomField-2-Values’, ‘’, ‘Requestors’, ’

me@purdue.edu’, ‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’,
‘TimeWorked’, ‘’, ‘id’, ‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’,
‘’, ‘Subject’, ‘This is a test. Please ignore’, ‘new-RefersTo’, ‘’,
‘FinalPriority’, 10, ‘RefersTo-new’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’,
‘TimeLeft’, ‘’, ‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1,
‘DependsOn-new’, ‘’, ‘Owner’, 22, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’,
‘Content’, ‘Testing again.^M^J^M^J-- ^M^JSteve’, ‘Due’, ‘2007-04-11
18:35:38’, ‘TimeWorked-TimeUnits’, ‘minutes’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1, ‘TimeEstimated’, ‘’,
‘Status’, ‘open’, ‘new-DependsOn’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values’, ‘’, ‘Queue’, ‘Unix’, ‘AdminCc’,
‘’, ‘Requestors’, ’

me@purdue.edu’, ‘Object-RT::Ticket–CustomField-2-Values’, ‘’,
‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’, ‘TimeWorked’, ‘’, ‘id’,
‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’, ‘’, ‘Subject’, ‘This is
a test. Please ignore’, ‘new-RefersTo’, ‘’, ‘FinalPriority’, 10,
‘RefersTo-new’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’, ‘TimeLeft’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1, ‘DependsOn-new’, ‘’,
‘Owner’, 22, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’, ‘Content’, ‘Testing
again.^M^J^M^J-- ^M^JSteve’, ‘Due’, ‘2007-04-11 18:35:38’,
‘TimeWorked-TimeUnits’, ‘minutes’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1) called at
/opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Request.pm line 915

HTML::Mason::Request::call_next(‘HTML::Mason::Request::ApacheHandler=HASH(0x1e60fb8)’,
‘TimeEstimated’, ‘’, ‘Status’, ‘open’, ‘new-DependsOn’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values’, ‘’, ‘Queue’, ‘Unix’, ‘AdminCc’,
‘’, ‘Requestors’, ’

me@purdue.edu’, ‘Object-RT::Ticket–CustomField-2-Values’, ‘’,
‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’, ‘TimeWorked’, ‘’, ‘id’,
‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’, ‘’, ‘Subject’, ‘This is
a test. Please ignore’, ‘new-RefersTo’, ‘’, ‘FinalPriority’, 10,
‘RefersTo-new’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’, ‘TimeLeft’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1, ‘DependsOn-new’, ‘’,
‘Owner’, 22, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’, ‘Content’, ‘Testing
again.^M^J^M^J-- ^M^JSteve’, ‘Due’, ‘2007-04-11 18:35:38’,
‘TimeWorked-TimeUnits’, ‘minutes’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1) called at
/opt/rt3/local/html/autohandler line 282

HTML::Mason::Commands::ANON(‘TimeEstimated’, ‘’, ‘Status’, ‘open’,
‘new-DependsOn’, ‘’, ‘Object-RT::Ticket–CustomField-1-Values’, ‘’,
‘Queue’, ‘Unix’, ‘AdminCc’, ‘’, ‘Object-RT::Ticket–CustomField-2-Values’,
‘’, ‘Requestors’, ’

me@purdue.edu’, ‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’,
‘TimeWorked’, ‘’, ‘id’, ‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’,
‘’, ‘Subject’, ‘This is a test. Please ignore’, ‘new-RefersTo’, ‘’,
‘FinalPriority’, 10, ‘RefersTo-new’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’,
‘TimeLeft’, ‘’, ‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1,
‘DependsOn-new’, ‘’, ‘Owner’, 22, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’,
‘Content’, ‘Testing again.^M^J^M^J-- ^M^JSteve’, ‘Due’, ‘2007-04-11
18:35:38’, ‘TimeWorked-TimeUnits’, ‘minutes’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1) called at
/opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Component.pm line 135

HTML::Mason::Component::run(‘HTML::Mason::Component::FileBased=HASH(0xaf54e0)’,
‘TimeEstimated’, ‘’, ‘Status’, ‘open’, ‘new-DependsOn’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values’, ‘’, ‘Queue’, ‘Unix’, ‘AdminCc’,
‘’, ‘Object-RT::Ticket–CustomField-2-Values’, ‘’, ‘Requestors’, ’

me@purdue.edu’, ‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’,
‘TimeWorked’, ‘’, ‘id’, ‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’,
‘’, ‘Subject’, ‘This is a test. Please ignore’, ‘new-RefersTo’, ‘’,
‘FinalPriority’, 10, ‘RefersTo-new’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’,
‘TimeLeft’, ‘’, ‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1,
‘DependsOn-new’, ‘’, ‘Owner’, 22, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’,
‘Content’, ‘Testing again.^M^J^M^J-- ^M^JSteve’, ‘Due’, ‘2007-04-11
18:35:38’, ‘TimeWorked-TimeUnits’, ‘minutes’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1) called at
/opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Request.pm line 1251

eval {…} at /opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Request.pm line
1246
HTML::Mason::Request::comp(undef, undef, undef, ‘TimeEstimated’, ‘’,
‘Status’, ‘open’, ‘new-DependsOn’, ‘’,
‘Object-RT::Ticket–CustomField-1-Values’, ‘’, ‘Queue’, ‘Unix’, ‘AdminCc’,
‘’, ‘Object-RT::Ticket–CustomField-2-Values’, ‘’, ‘Requestors’, ’

me@purdue.edu’, ‘InitialPriority’, 1, ‘Starts’, ‘’, ‘Attach’, ‘’,
‘TimeWorked’, ‘’, ‘id’, ‘new’, ‘TimeEstimated-TimeUnits’, ‘minutes’, ‘Cc’,
‘’, ‘Subject’, ‘This is a test. Please ignore’, ‘new-RefersTo’, ‘’,
‘FinalPriority’, 10, ‘RefersTo-new’, ‘’, ‘TimeLeft-TimeUnits’, ‘minutes’,
‘TimeLeft’, ‘’, ‘Object-RT::Ticket–CustomField-1-Values-Magic’, 1,
‘DependsOn-new’, ‘’, ‘Owner’, 22, ‘new-MemberOf’, ‘’, ‘MemberOf-new’, ‘’,
‘Content’, ‘Testing again.^M^J^M^J-- ^M^JSteve’, ‘Due’, ‘2007-04-11
18:35:38’, ‘TimeWorked-TimeUnits’, ‘minutes’,
‘Object-RT::Ticket–CustomField-2-Values-Magic’, 1) called at
/opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Request.pm line 460

eval {…} at /opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Request.pm line
460
eval {…} at /opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/Request.pm line
412
HTML::Mason::Request::exec(‘HTML::Mason::Request::ApacheHandler=HASH(0x1e60fb8)’)
called at /opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/ApacheHandler.pm
line 168

HTML::Mason::Request::ApacheHandler::exec(‘HTML::Mason::Request::ApacheHandler=HASH(0x1e60fb8)’)
called at /opt/perlsite/lib/site_perl/5.8.7/HTML/Mason/ApacheHandler.pm
line 826
HTML::Mason::ApacheHandler::handle_request(‘HTML::Mason::ApacheHandler=HASH(0x123ae50)’,
‘Apache2::RequestRec=SCALAR(0x1f20d70)’) called at /opt/rt3/bin/webmux.pl
line 123

eval {…} at /opt/rt3/bin/webmux.pl line 123
RT::Mason::handler(‘Apache2::RequestRec=SCALAR(0x1f20d70)’) called at -e
line 0
eval {…} at -e line 0

Any help would be greatly appreciated.
Thanks,
Steve Holmes

I would look for perl or apache patches. Were these simply Solaris OS
patches for security, or was this a jumbo patch which includes updates
for
other installed software. Problem with new versions of Solaris is that
they come with Apache, Sendmail, Perl (I believe) - I wouldn’t install
any
of that if possible…

James Moseley

           "Steve Holmes"
           < sholmes42@mac.co
           m>

To
Sent by: " jmoseley@pgtv.com"
sholmes42@gmail.c < jmoseley@pgtv.com>
om
cc
“RT Users”
<rt-users@lists.bestpractical.com

,
03/07/2007 02:46
rt-users-bounces@lists.bestpractica
PM l.com

Subject
Re: [rt-users] Can’t create new
tickets, new problem

James,

It looks like 58 patches were applied on the RT server. I can list them
for
you if you like. No we have not tried to back any of them out.

I’m not sure how to know which ones would be appropriate to backout. I’m
about to start reading all of the READMEs for the patches to see if I can
find anything that stands out.

Thanks,
SteveOn 3/7/07, jmoseley@pgtv.com < jmoseley@pgtv.com > wrote:
Which Solaris patches were installed? Have you tried backing out of
them?

James Moseley





             "Steve Holmes"
             < sholmes42@mac.co
             m>
To
             Sent by:                  "RT Users"
             rt-users-bounces@         <

rt-users@lists.bestpractical.com>
lists.bestpractic
cc
al.com

Subject
                                       [rt-users] Can't create new
             03/07/2007 02:15          tickets, new problem
             PM









My install of RT 3.6.1 (on Solaris 10, mysql 5.0.22) has been working
very
nicely for several months. We only have about 80 tickets, but we have
been
able to create tickets with no problems both in the web interface and

via
email. That is, until today. Now I get:

error:   Transactions not supported by database at
          /opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm line
1668.

context:

          ...

          1664:
                      sub begin_work {
          1665:
                      my $dbh = shift;
          1666:
                      return $dbh->set_err(1, "Already in a

transaction")

          1667:
                      unless $dbh->FETCH('AutoCommit');
          1668:
                      $dbh->STORE('AutoCommit', 0); # will croak if
driver
                      doesn't support it
          1669:
                      $dbh->STORE('BegunWork', 1); # trigger post
                      commit/rollback action
          1670:
                      return 1;
          1671:
                      }
          1672:

          ...



code     /opt/perlsite/lib/site_perl/5.8.7/sun4-solaris/DBI.pm:1668
stack:   /opt/perlsite/lib/site_perl/5.8.7
          /DBIx/SearchBuilder/Handle.pm:720
          /opt/rt3/lib/RT/Ticket_Overlay.pm:564
          /opt/rt3/lib/RT/Interface/Web.pm:446
          /opt/rt3/share/html/Ticket/Display.html:103
          /opt/rt3/share/html/Ticket/Create.html:300
          /opt/rt3/share/html/autohandler:279




when trying to create a ticket on the web. I get similar, but slightly
different errors from an email attempt. I've searched the archives and
the
wiki but any mention of the keywords here are from 2002 or so.

I checked the rt3.Transactions table on the mysql server it it is

INNODB.
Are there other tables to check?

I haven't modified RT or the mysql server at all in many weeks.

However,
Solaris patches were applied last night. Unfortunately, I can’t see
anything has changed in the RT or the mysql install. And SearchBuilder
is
up to date according to CPAN.

Appreciate any ideas of where to look.

Thanks,
Steve Holmes
7

Sorry, but we don’t use sun’s apache nor sun’s perl. Unfortunately this RT
server is on one of the central staff servers so backing out patches would
be a very problematic. I might test an RT install on a different box, just
to see if it makes a difference.

Thanks anyway,
Steve.On 3/12/07, jmoseley@pgtv.com jmoseley@pgtv.com wrote:

Again, I would back out of all Sun patches that anything to do with apache
or perl, then see if things work - the problems did not start happening
until you applied those patches… It also appears you are using Sun’s
perl and apache that came with Solaris 10 (or you managed to get from
Sun)?
If so, I would stronly recommend not using their packages and recompile
perl and apache (and other associated modules) from scratch.

James Moseley

James, thanks for your replies.

All:

[As a reminder I’m on Solaris 10, mysql 5.0.22, RT was 3.6.1, but is now
3.6.3]

I’ve been snooping around and can’t find anything wrong which might cause
this. (I’ve googled, and searched the archives and the wiki.) I’ve checked
the rt3 database. Unless RT is doing something funny, the db is ok. I.e.
it
DOES support transactions (except for the sessions table which is a MyISAM
table) It DOES NOT get errors in mysql when I do a start transaction nor
when I do a set autocommitt = 0;

The errors I get in the RT logs are:

Mar 12 10:46:12 localhost RT: Transaction not committed. Usually indicates
a software fault. Data loss may have occurred
(/opt/rt3/lib/RT/Interface/Web/Handler.pm:194)\n

It is of mild curiosity that these errors are occuring on a timed basis
rather than on a usage basis. I.e. no one is actually using RT right now,
except when I’m testing it.

What I did this morning:

I upgraded RT to 3.6.3, I re-installed DBD::mysql on the RT server, I’ve
restarted apache. and I’m still getting this error. I can see tickets in
RT, I just can’t create new tickets or update existing ones.

Here is the raw error as displayed in the browser from trying to create
just one ticket (sorry for the wrap, some of these lines are VERY long):

8

OK. But obviously one or more of the patches you applied broke something -
I would take a look at each patch that was installed and compare them
against the dependency requirements for RT. Then only back out of those
patches. Backing out of Sun supplied patches (which I assume these are) is
fairly straightforward and shouldn’t cause a problem - why would backing
out of a few patches on a central staff server be problematic? But it’s
not my system to run…

If you are going to test on a different box, I would highly recommend not
using Solaris, but instead go with a Linux distribution to take advantage
of central package management - Redhat, Fedora, Gentoo, etc. It makes
installing software, applying updates, etc, much more simpler.

James Moseley

         "Steve Holmes"                                                
         <sholmes42@mac.co                                             
         m>                                                         To 
         Sent by:                  "jmoseley@pgtv.com"                 
         sholmes42@gmail.c         <jmoseley@pgtv.com>                 
         om                                                         cc 
                                   "RT Users"                          
                                   <rt-users@lists.bestpractical.com>, 
         03/12/2007 04:12          rt-users-bounces@lists.bestpractica 
         PM                        l.com                               
                                                               Subject 
                                   Re: [rt-users] Can't create new     
                                   tickets, new problem

Sorry, but we don’t use sun’s apache nor sun’s perl. Unfortunately this RT
server is on one of the central staff servers so backing out patches would
be a very problematic. I might test an RT install on a different box, just
to see if it makes a difference.

Thanks anyway,
Steve.On 3/12/07, jmoseley@pgtv.com <jmoseley@pgtv.com > wrote:
Again, I would back out of all Sun patches that anything to do with
apache
or perl, then see if things work - the problems did not start happening
until you applied those patches… It also appears you are using Sun’s
perl and apache that came with Solaris 10 (or you managed to get from
Sun)?
If so, I would stronly recommend not using their packages and recompile
perl and apache (and other associated modules) from scratch.

James Moseley

James, thanks for your replies.

All:

[As a reminder I’m on Solaris 10, mysql 5.0.22, RT was 3.6.1, but is now
3.6.3]

I’ve been snooping around and can’t find anything wrong which might cause
this. (I’ve googled, and searched the archives and the wiki.) I’ve
checked
the rt3 database. Unless RT is doing something funny, the db is ok. I.e.
it
DOES support transactions (except for the sessions table which is a
MyISAM
table) It DOES NOT get errors in mysql when I do a start transaction nor
when I do a set autocommitt = 0;

The errors I get in the RT logs are:

Mar 12 10:46:12 localhost RT: Transaction not committed. Usually
indicates
a software fault. Data loss may have occurred
(/opt/rt3/lib/RT/Interface/Web/Handler.pm:194)\n

It is of mild curiosity that these errors are occuring on a timed basis
rather than on a usage basis. I.e. no one is actually using RT right now,
except when I’m testing it.

What I did this morning:

I upgraded RT to 3.6.3, I re-installed DBD::mysql on the RT server, I’ve
restarted apache. and I’m still getting this error. I can see tickets in
RT, I just can’t create new tickets or update existing ones.

Here is the raw error as displayed in the browser from trying to create
just one ticket (sorry for the wrap, some of these lines are VERY long):

9

Turns out it was a version mis-match between the mysql running on the
database server and the mysql running on the RT server. We had overlooked
the fact that the new version got started when the RT server host was
rebooted after the patches. The mysql server (a separate host) didn’t get
upgraded until yesterday. Not the right order of doing things, but it was
unintentional and taught us a valuable lesson.

Thanks again.
Steve.On 3/12/07, jmoseley@pgtv.com jmoseley@pgtv.com wrote:

OK. But obviously one or more of the patches you applied broke something

I would take a look at each patch that was installed and compare them
against the dependency requirements for RT. Then only back out of those
patches. Backing out of Sun supplied patches (which I assume these are)
is
fairly straightforward and shouldn’t cause a problem - why would backing
out of a few patches on a central staff server be problematic? But it’s
not my system to run…

If you are going to test on a different box, I would highly recommend not
using Solaris, but instead go with a Linux distribution to take advantage
of central package management - Redhat, Fedora, Gentoo, etc. It makes
installing software, applying updates, etc, much more simpler.

James Moseley

         "Steve Holmes"
         <sholmes42@mac.co
         m>                                                         To
         Sent by:                  "jmoseley@pgtv.com"
         sholmes42@gmail.c         <jmoseley@pgtv.com>
         om                                                         cc
                                   "RT Users"
                                   <rt-users@lists.bestpractical.com>,
         03/12/2007 04:12          rt-users-bounces@lists.bestpractica
         PM                        l.com
                                                               Subject
                                   Re: [rt-users] Can't create new
                                   tickets, new problem

Sorry, but we don’t use sun’s apache nor sun’s perl. Unfortunately this RT
server is on one of the central staff servers so backing out patches would
be a very problematic. I might test an RT install on a different box, just
to see if it makes a difference.

Thanks anyway,
Steve.

On 3/12/07, jmoseley@pgtv.com <jmoseley@pgtv.com > wrote:
Again, I would back out of all Sun patches that anything to do with
apache
or perl, then see if things work - the problems did not start happening
until you applied those patches… It also appears you are using Sun’s
perl and apache that came with Solaris 10 (or you managed to get from
Sun)?
If so, I would stronly recommend not using their packages and recompile
perl and apache (and other associated modules) from scratch.

James Moseley

James, thanks for your replies.

All:

[As a reminder I’m on Solaris 10, mysql 5.0.22, RT was 3.6.1, but is now
3.6.3]

I’ve been snooping around and can’t find anything wrong which might
cause
this. (I’ve googled, and searched the archives and the wiki.) I’ve
checked
the rt3 database. Unless RT is doing something funny, the db is ok. I.e.
it
DOES support transactions (except for the sessions table which is a
MyISAM
table) It DOES NOT get errors in mysql when I do a start transaction nor
when I do a set autocommitt = 0;

The errors I get in the RT logs are:

Mar 12 10:46:12 localhost RT: Transaction not committed. Usually
indicates
a software fault. Data loss may have occurred
(/opt/rt3/lib/RT/Interface/Web/Handler.pm:194)\n

It is of mild curiosity that these errors are occuring on a timed basis
rather than on a usage basis. I.e. no one is actually using RT right
now,
except when I’m testing it.

What I did this morning:

I upgraded RT to 3.6.3, I re-installed DBD::mysql on the RT server, I’ve
restarted apache. and I’m still getting this error. I can see tickets in
RT, I just can’t create new tickets or update existing ones.

Here is the raw error as displayed in the browser from trying to create
just one ticket (sorry for the wrap, some of these lines are VERY long):

I believe I found the missing link between animal and civilized man. It is
us. -Konrad Lorenz, ethologist, Nobel laureate (1903-1989)

We in America do not have government by the majority. We have government by
the majority who participate. -Thomas Jefferson, third US president,
architect and author (1743-1826)