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.
<br><br>Thanks again.<br>Steve.<br><br><br><div><span class="gmail_quote">On 3/12/07, <b class="gmail_sendername"><a href="mailto:jmoseley@pgtv.com">jmoseley@pgtv.com</a></b> <<a href="mailto:jmoseley@pgtv.com">jmoseley@pgtv.com
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">OK. But obviously one or more of the patches you applied broke something -
<br>I would take a look at each patch that was installed and compare them<br>against the dependency requirements for RT. Then only back out of those<br>patches. Backing out of Sun supplied patches (which I assume these are) is
<br>fairly straightforward and shouldn't cause a problem - why would backing<br>out of a few patches on a central staff server be problematic? But it's<br>not my system to run...<br><br>If you are going to test on a different box, I would highly recommend not
<br>using Solaris, but instead go with a Linux distribution to take advantage<br>of central package management - Redhat, Fedora, Gentoo, etc. It makes<br>installing software, applying updates, etc, much more simpler.<br>
<br><br>James Moseley<br><br><br><br><br><br> "Steve Holmes"<br> <<a href="mailto:sholmes42@mac.co">sholmes42@mac.co</a><br> m> To
<br> Sent by: "<a href="mailto:jmoseley@pgtv.com">jmoseley@pgtv.com</a>"<br> <a href="mailto:sholmes42@gmail.c">sholmes42@gmail.c</a> <<a href="mailto:jmoseley@pgtv.com">
jmoseley@pgtv.com</a>><br> om cc<br> "RT Users"<br> <<a href="mailto:rt-users@lists.bestpractical.com">
rt-users@lists.bestpractical.com</a>>,<br> 03/12/2007 04:12 <a href="mailto:rt-users-bounces@lists.bestpractica">rt-users-bounces@lists.bestpractica</a><br> PM <a href="http://l.com">
l.com</a><br> Subject<br> Re: [rt-users] Can't create new<br> tickets, new problem
<br><br><br><br><br><br><br><br><br><br><br>Sorry, but we don't use sun's apache nor sun's perl. Unfortunately this RT<br>server is on one of the central staff servers so backing out patches would<br>be a very problematic. I might test an RT install on a different box, just
<br>to see if it makes a difference.<br><br>Thanks anyway,<br>Steve.<br><br><br>On 3/12/07, <a href="mailto:jmoseley@pgtv.com">jmoseley@pgtv.com</a> <<a href="mailto:jmoseley@pgtv.com">jmoseley@pgtv.com</a> > wrote:
<br> Again, I would back out of all Sun patches that anything to do with<br> apache<br> or perl, then see if things work - the problems did not start happening<br> until you applied those patches... It also appears you are using Sun's
<br> perl and apache that came with Solaris 10 (or you managed to get from<br> Sun)?<br> If so, I would stronly recommend not using their packages and recompile<br> perl and apache (and other associated modules) from scratch.
<br><br><br> James Moseley<br><br><br> James, thanks for your replies.<br><br> All:<br><br> [As a reminder I'm on Solaris 10, mysql 5.0.22, RT was 3.6.1, but is now<br> 3.6.3]<br><br> I've been snooping around and can't find anything wrong which might cause
<br> this. (I've googled, and searched the archives and the wiki.) I've<br> checked<br> the rt3 database. Unless RT is doing something funny, the db is ok. I.e.<br> it<br> DOES support transactions (except for the sessions table which is a
<br> MyISAM<br> table) It DOES NOT get errors in mysql when I do a start transaction nor<br> when I do a set autocommitt = 0;<br><br><br> The errors I get in the RT logs are:<br><br> Mar 12 10:46:12 localhost RT: Transaction not committed. Usually
<br> indicates<br> a software fault. Data loss may have occurred<br> (/opt/rt3/lib/RT/Interface/Web/Handler.pm:194)\n<br><br> It is of mild curiosity that these errors are occuring on a timed basis<br> rather than on a usage basis.
I.e. no one is actually using RT right now,<br> except when I'm testing it.<br><br> What I did this morning:<br><br> I upgraded RT to 3.6.3, I re-installed DBD::mysql on the RT server, I've<br> restarted apache. and I'm still getting this error. I can see tickets in
<br> RT, I just can't create new tickets or update existing ones.<br><br> Here is the raw error as displayed in the browser from trying to create<br> just one ticket (sorry for the wrap, some of these lines are VERY long):
<br><br><br></blockquote></div><br><br clear="all"><br>-- <br>I believe I found the missing link between animal and civilized man. It is<br>us. -Konrad Lorenz, ethologist, Nobel laureate (1903-1989)<br><br>We in America do not have government by the majority. We have government by
<br>the majority who participate. -Thomas Jefferson, third US president,<br>architect and author (1743-1826)