Sounds like the oom-killer is getting mysql. How much memory is on your db server? Is it configured in such a way that when the innodb pool is full it's not running out of memory? You shouldn't really have an issue with this unless you have a large amount of tickets. Might want to check some of your other logs and see what's occurring. Apache/mod_perl can be quite memory intensive at times depending how many children are setup, it will slowly grow.
Kobus Bensch - No Sig wrote: > Hi > > I am able to access the server, I am able to login, and in some cases > even able to brwose normally. > > The problem I then get is that when I try to create a ticket it thinks a > bit and then gives me this error. > > Due to this error the server creates massive logs, so much so that I > have to reboot the server and delete it as soon as it comes back. I > deleted a 81GB rt.log file. > > Further problems, but after tghis issue has been solved is after each > page i try to click on i have to login. > > Last error I sometimes just get blank pages. > > Thanks for the help > > Kobus > > Eli Altman wrote: > >> Please explain in detail what problem you are experiencing. Are you having >> problems installing RT and running it for the first time? Can you not >> access RT at all through a browser? >> >> >> -----Original Message----- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kobus Bensch >> Sent: Friday, October 24, 2008 12:38 PM >> To: RT Users >> Subject: [rt-users] DBD::mysql::st execute failed: MySQL server has gone >> away at >> >> Hi >> >> Please can someone help. >> >> Fresh install of os and rt and i get this error which ends of with the >> ticket email sent but no ticket created and my RT is currently not working. >> I have downloaded all the email archives and found other people with the >> same error but no real solution. >> >> Rt 3.8.1 on Centos 5.2 with php 5 perl 5.8.8 and mysql 5.0.45. >> >> Thanks for any help >> >> Kobus >> >> >> There is a lot more to this log entry, I just could not include it all here. >> HTML::Mason::Request::exec('RT::Interface::Web::Request=HASH(0x2b99543613e0)') >> called at /usr/lib/perl5/site_perl/5.8.8/HTML/Mason/ApacheHandler.pm >> line 168 >> >> HTML::Mason::Request::ApacheHandler::exec('RT::Interface::Web::Request=HASH(0x2b99543613e0)') >> called at /usr/lib/perl5/site_perl/5.8.8/HTML/Mason/ApacheHandler.pm >> line 825 >> >> HTML::Mason::ApacheHandler::handle_request('HTML::Mason::ApacheHandler=HASH(0x2b994c2469a0)', >> 'Apache2::RequestRec=SCALAR(0x2b995437e480)') called at >> /opt/rt3/bin/webmux.pl line 148 >> eval {...} called at /opt/rt3/bin/webmux.pl line 148 >> RT::Mason::handler('Apache2::RequestRec=SCALAR(0x2b995437e480)') >> called at -e line 0 >> eval {...} called at -e line 0 (/usr/lib/perl5/5.8.8/Carp.pm:272) >> [Thu Oct 23 22:30:23 2008] [warning]: DBD::mysql::st execute failed: >> MySQL server has gone away at >> /usr/lib/perl5/vendor_perl/5.8.8/Apache/Session/Store/DBI.pm line 67. >> (/usr/lib/perl5/vendor_perl/5.8.8/Apache/Session/Store/DBI.pm:67) >> [Thu Oct 23 22:30:23 2008] [warning]: DBD::mysql::st execute failed: >> MySQL server has gone away at >> /usr/lib/perl5/vendor_perl/5.8.8/Apache/Session/Lock/MySQL.pm line 71. >> (/usr/lib/perl5/vendor_perl/5.8.8/Apache/Session/Lock/MySQL.pm:71) >> >> >> >> > _______________________________________________ > 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 > > > _______________________________________________ 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