[rt-users] Can't create new tickets, new problem

[jmoseley at pgtv.com]

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 at mac.co                                             
             m>                                                         To 
             Sent by:                  "jmoseley at pgtv.com"                 
             sholmes42 at gmail.c         <jmoseley at pgtv.com>                 
             om                                                         cc 
                                       "RT Users"                          
                                       <rt-users at lists.bestpractical.com>, 
             03/12/2007 04:12          rt-users-bounces at 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 at pgtv.com <jmoseley at 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):