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, [EMAIL PROTECTED] <[EMAIL PROTECTED]> 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"
<[EMAIL PROTECTED]
m> To
Sent by: "[EMAIL PROTECTED]"
[EMAIL PROTECTED] <[EMAIL PROTECTED]>
om cc
"RT Users"
<[email protected]>,
03/07/2007 02:46 [EMAIL PROTECTED]
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, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:
Which Solaris patches were installed? Have you tried backing out of
them?
James Moseley
"Steve Holmes"
<[EMAIL PROTECTED]
m>
To
Sent by: "RT Users"
rt-users-bounces@ <[email protected]
>
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: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
