Author: jstephens
Date: 2006-05-15 03:10:40 +0200 (Mon, 15 May 2006)
New Revision: 2092
Log:
Updated gone-away in view of some user comments.
Modified:
trunk/refman-4.1/problems.xml
trunk/refman-5.0/problems.xml
trunk/refman-5.1/problems.xml
Modified: trunk/refman-4.1/problems.xml
===================================================================
--- trunk/refman-4.1/problems.xml 2006-05-14 08:27:08 UTC (rev 2091)
+++ trunk/refman-4.1/problems.xml 2006-05-15 01:10:40 UTC (rev 2092)
@@ -1021,6 +1021,14 @@
should be corrected.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ A client application running on a different host does not
+ have the necessary privileges to connect to the MySQL server
+ from that host.
+ </para>
+ </listitem>
<listitem>
<para>
@@ -1045,14 +1053,14 @@
<listitem>
<para>
- You are using a windows client and the server had dropped
+ You are using a Windows client and the server had dropped
the connection (probably because
<literal>wait_timeout</literal> expired) before the command
was issued.
</para>
<para>
- The problem on windows is that in some cases MySQL doesn't
+ The problem on Windows is that in some cases MySQL doesn't
get an error from the OS when writing to the TCP/IP
connection to the server, but instead gets the error when
trying to read the answer from connection.
@@ -1105,11 +1113,37 @@
<listitem>
<para>
+ It is also possible to see this error if hostname lookups
+ fail (for example, if the DNS server on which your server or
+ network relies goes down). This is because MySQL is
+ dependent on the host system for name resolution, but has no
+ way of knowing whether it is working — from MySQL's
+ point of view the problem is indistinguishable from any
+ other network timeout.
+ </para>
+
+ <para>
You may also see the <literal>MySQL server has gone
away</literal> error if MySQL is started with the
<option>--skip-networking</option> option.
</para>
+
+ <para>
+ Another networking issue that can cause this error occurs if
+ if the MySQL port (default 3306) is blocked by your
+ firewall, thus preventing any connections at all to the
+ MySQL server.
+ </para>
</listitem>
+
+ <listitem>
+ <para>
+ You can also encounter this error with applications that
+ fork child processes, all of which try to use the same
+ connection to the MySQL server. This can be avoided by
+ using a separate connection for each child process.
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-5.0/problems.xml
===================================================================
--- trunk/refman-5.0/problems.xml 2006-05-14 08:27:08 UTC (rev 2091)
+++ trunk/refman-5.0/problems.xml 2006-05-15 01:10:40 UTC (rev 2092)
@@ -1021,6 +1021,14 @@
should be corrected.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ A client application running on a different host does not
+ have the necessary privileges to connect to the MySQL server
+ from that host.
+ </para>
+ </listitem>
<listitem>
<para>
@@ -1045,14 +1053,14 @@
<listitem>
<para>
- You are using a windows client and the server had dropped
+ You are using a Windows client and the server had dropped
the connection (probably because
<literal>wait_timeout</literal> expired) before the command
was issued.
</para>
<para>
- The problem on windows is that in some cases MySQL doesn't
+ The problem on Windows is that in some cases MySQL doesn't
get an error from the OS when writing to the TCP/IP
connection to the server, but instead gets the error when
trying to read the answer from connection.
@@ -1106,11 +1114,37 @@
<listitem>
<para>
+ It is also possible to see this error if hostname lookups
+ fail (for example, if the DNS server on which your server or
+ network relies goes down). This is because MySQL is
+ dependent on the host system for name resolution, but has no
+ way of knowing whether it is working — from MySQL's
+ point of view the problem is indistinguishable from any
+ other network timeout.
+ </para>
+
+ <para>
You may also see the <literal>MySQL server has gone
away</literal> error if MySQL is started with the
<option>--skip-networking</option> option.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ You can also encounter this error with applications that
+ fork child processes, all of which try to use the same
+ connection to the MySQL server. This can be avoided by
+ using a separate connection for each child process.
+ </para>
+
+ <para>
+ Another networking issue that can cause this error occurs if
+ if the MySQL port (default 3306) is blocked by your
+ firewall, thus preventing any connections at all to the
+ MySQL server.
+ </para>
+ </listitem>
<listitem>
<para>
Modified: trunk/refman-5.1/problems.xml
===================================================================
--- trunk/refman-5.1/problems.xml 2006-05-14 08:27:08 UTC (rev 2091)
+++ trunk/refman-5.1/problems.xml 2006-05-15 01:10:40 UTC (rev 2092)
@@ -1021,6 +1021,14 @@
should be corrected.
</para>
</listitem>
+
+ <listitem>
+ <para>
+ A client application running on a different host does not
+ have the necessary privileges to connect to the MySQL server
+ from that host.
+ </para>
+ </listitem>
<listitem>
<para>
@@ -1045,14 +1053,14 @@
<listitem>
<para>
- You are using a windows client and the server had dropped
+ You are using a Windows client and the server had dropped
the connection (probably because
<literal>wait_timeout</literal> expired) before the command
was issued.
</para>
<para>
- The problem on windows is that in some cases MySQL doesn't
+ The problem on Windows is that in some cases MySQL doesn't
get an error from the OS when writing to the TCP/IP
connection to the server, but instead gets the error when
trying to read the answer from connection.
@@ -1106,11 +1114,37 @@
<listitem>
<para>
+ It is also possible to see this error if hostname lookups
+ fail (for example, if the DNS server on which your server or
+ network relies goes down). This is because MySQL is
+ dependent on the host system for name resolution, but has no
+ way of knowing whether it is working — from MySQL's
+ point of view the problem is indistinguishable from any
+ other network timeout.
+ </para>
+
+ <para>
You may also see the <literal>MySQL server has gone
away</literal> error if MySQL is started with the
<option>--skip-networking</option> option.
</para>
+
+ <para>
+ Another networking issue that can cause this error occurs if
+ if the MySQL port (default 3306) is blocked by your
+ firewall, thus preventing any connections at all to the
+ MySQL server.
+ </para>
</listitem>
+
+ <listitem>
+ <para>
+ You can also encounter this error with applications that
+ fork child processes, all of which try to use the same
+ connection to the MySQL server. This can be avoided by
+ using a separate connection for each child process.
+ </para>
+ </listitem>
<listitem>
<para>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2092 - in trunk: refman-4.1 refman-5.0 refman-5.1 | jon | 15 May |
