[rt-users] Testing 4.0.0rc5 - experiences upgrading from 3.6.4 on RHEL6

Darren Nickerson darren at dazza.org
Mon Feb 28 11:08:20 EST 2011


On Feb 24, 2011, at 7:04 PM, Darren Nickerson wrote:
> 
> That FD is a network connection to our database server:
> 
> [root at rt4 Plack-0.9970]# ls -l /proc/30310/fd/1
> lrwx------. 1 root root 64 Feb 24 17:44 /proc/30310/fd/1 -> socket:[281592]
> [root at rt4 Plack-0.9970]# netstat -antep | grep 281592
> tcp        0      5 10.0.12.149:49410           10.0.11.100:3306            ESTABLISHED 48         281592     30310/httpd     
> 
> The database server has no record of that tcp connection any longer, and mysqladmin processlist shows all threads sleeping.

*bump* any thoughts on this?

Should I be looking outiside of RT for a fix for this? Is this more likely to be a kernel/networking problem in RHEL6 or with mod_perl or the MySQL DBD/DBI stuff? Looks like RT is using persistent database connections, but that when the lockup occurs it's usually because apache is waiting to get data back from a MySQL socket that no longer exists on the database server ...

-d


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20110228/a96de2c5/attachment.htm>


More information about the rt-users mailing list