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

[Steve Holmes]

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):
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20070312/f6294801/attachment.htm>