<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to 24: Sqlgrey becomes unresponsive if MySQL server is unavailable</title><link href="https://sourceforge.net/p/sqlgrey/bugs/24/" rel="alternate"/><link href="https://sourceforge.net/p/sqlgrey/bugs/24/feed.atom" rel="self"/><id>https://sourceforge.net/p/sqlgrey/bugs/24/</id><updated>2010-07-05T11:06:12Z</updated><subtitle>Recent changes to 24: Sqlgrey becomes unresponsive if MySQL server is unavailable</subtitle><entry><title>Sqlgrey becomes unresponsive if MySQL server is unavailable</title><link href="https://sourceforge.net/p/sqlgrey/bugs/24/" rel="alternate"/><published>2010-07-05T11:06:12Z</published><updated>2010-07-05T11:06:12Z</updated><author><name>rcb </name><uri>https://sourceforge.net/u/recobo/</uri></author><id>https://sourceforge.net7f2679a70bc0ec82e3993b577b2417ba4dd92a30</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Version: 1.8.0rc2-1&lt;/p&gt;
&lt;p&gt;Sqlgrey behaves normally when the mysql server is killed with e.g. /etc/init.d/mysql stop, postfix then continues to deliver e-mail normally&lt;br /&gt;
When the server becomes unavailable for other reasons, for example using 'iptables -A INPUT -p tcp --dport 3306 -j DROP', then two different things happen.&lt;br /&gt;
- Sqlgrey dies, resulting in 'warning: connect to 127.0.0.1:2501: Connection refused', which gives postfix configuration errors and 4.3.5 error messages to the clients.&lt;br /&gt;
- Sqlgrey  keeps waiting for the connection to timeout, this results in messages like 'dbaccess: can't connect to DB: Can't connect to MySQL server on '127.0.0.1' (110)'. The effect is the same, 4.3.5 error messages to the clients.&lt;/p&gt;
&lt;p&gt;This can be reproduced by firewalling MySQL using 'iptables -A INPUT -p tcp --dport 3306 -j DROP'&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>