Hi Michael,
Yesterday, I restarted the server and the mysql database.
And In the errorlog, I only have
050203 00:34:14 mysqld started
/u01/mysql/libexec/mysqld: ready for connections.
Version: '4.0.17-log' socket: '/tmp/mysql.sock' port: 3306
Also, I verified and my mysql user have access to write into my errorlog file
and in my directories.
David
David Marois
-----Message d'origine-----
De : Michael Dykman [mailto:[EMAIL PROTECTED]
Envoyé : 3 février, 2005 10:02
À : Marois, David
Cc : "MySQL List"
Objet : Re: help please : ERROR 2006: MySQL server has gone away
So far, you have only showed us the client-view of the problem.. look
in you data directories on the server machine... there is likely an
error file there which should give you some insight (unless permissions
for that directory are seriously messed up). IF there is no error file,
determine which user MySQL is running as (default: mysql) and confirm
that user has read/write permissions to that directory and
subdirectories.
There are a few misconfigurations which take MySQL a bit of time to fail
on.. I know I had similar results last summer doing a manual
source-install of MySQL 4.1 which was related to the data-directory
permissions.. Having sorted it out, the server has been extremely stable
under heavy load for several continuous months now.
- michael dykman
On Thu, 2005-02-03 at 08:38, Marois, David wrote:
> We still have the problem...
>
> In the error log, I have nothing about problem. I only have that:
> 050203 00:34:14 mysqld started
> /u01/mysql/libexec/mysqld: ready for connections.
> Version: '4.0.17-log' socket: '/tmp/mysql.sock' port: 3306
>
> If I do show variables, I have max_allowed_packet = 16776192
>
> IF I log into mysql with :mysql -uroot --max_allowed_packet=16M -p
>
> After I do:show databases; and I receive the answer.
> After I wait 30 sec and launch the command "show databases;" again and now I
> have the error:
>
> ERROR 2006: MySQL server has gone away
> No connection. Trying to reconnect...
>
>
> David
>
> ------------------------
>
> Hello.
>
> Does the problem remain? What is in the error log? Please, send
> us information about MySQL and operating system versions. There are
> two variables: max_allowed_packet - one has client, another has server.
> Run mysql with --max_allowed_packet=16M and mysqld with the same value.
> May be you have some ulimits which cause such behaviour?
>
>
> -----Message d'origine-----
> De : Marois, David
> Envoyé : 2 février, 2005 09:16
> À : 'mysql@lists.mysql.com'
> Objet : Re: help please : ERROR 2006: MySQL server has gone away
>
>
> And
>
> max_allowed_packet = 16776192
>
>
> David
>
>
> Hi,
> my interactive_timeout variable is
>
> interactive_timeout 3600
>
> Thanks !
>
> David
>
>
> Hello.
>
> I've asked you about interactive_timeout, not wait_timeout.
>
>
> Mark <[EMAIL PROTECTED]> wrote:
> >> -----Original Message-----
> >> From: Gleb Paharenko [mailto:[EMAIL PROTECTED]
> >
> >> Sent: woensdag 2 februari 2005 12:46
> >> To: [EMAIL PROTECTED]
> >> Subject: Re: help please : ERROR 2006: MySQL server has gone away
> >>
> >> Hello.
> >>
> >> What's the value of the interactive_timeout system variable? See:
> >> http://dev.mysql.com/doc/mysql/en/server-system-variables.html
> >> http://dev.mysql.com/doc/mysql/en/gone-away.html
> >
> > I believe he already answered that in part:
> >
> >> > Also, my variable wait_timeout = 3600.
> >
> > 1 hour, that is, instead of the default 8 (28800).
> >
> > - Mark
> >
> >
>
>
> David Marois
> <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]
>
--
- michael dykman
- [EMAIL PROTECTED]
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
