<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 24, 2011, at 7:04 PM, Darren Nickerson wrote:</div><blockquote type="cite"><div><font class="Apple-style-span" color="#000000"><br></font>That FD is a network connection to our database server:<br><br>[root@rt4 Plack-0.9970]# ls -l /proc/30310/fd/1<br>lrwx------. 1 root root 64 Feb 24 17:44 /proc/30310/fd/1 -> socket:[281592]<br>[root@rt4 Plack-0.9970]# netstat -antep | grep 281592<br>tcp 0 5 10.0.12.149:49410 10.0.11.100:3306 ESTABLISHED 48 281592 30310/httpd <br><br>The database server has no record of that tcp connection any longer, and mysqladmin processlist shows all threads sleeping.</div></blockquote><br></div><div>*bump* any thoughts on this?</div><div><br></div><div>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 ...</div><div><br></div><div>-d</div><div><br></div><br></body></html>