> -----Original Message-----
> From: Cindy [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 28, 2001 5:49 PM
> To: MySQL List
> Subject: Re: Error on new connection socket: Invalid argument
>
>
>
> "Jeff Hinds" writes:
> >I have an application that is developed in perl using dbi and
> mysql that has
> >been working well for some time now. However, I have received emails and
> >phone calls asking if the server is down. I look at the service and the
> >system is up however, the mysql error log reports the following message:
> >
> > Error on new connection socket: Invalid argument
> >
> >Once I stop and restart the mysqld process all is well again.
> But I need to
> >prevent the error from happening over and over. I could not
> find any mention
> >of the message above in the documentation. Has anyone run into
> this problem
> >and found out what is causing it, and how to correct it?
>
> Sometimes the file /tmp/mysql.sock is removed by a cron job clearing
> out /tmp. In which case you may want to redefine
> socket=/usr/local/mysql/mysql.sock or whatever to avoid that problem.
>
Okay . . . This has been done. The mysql.sock file is in a dedicated area
for MySQL on our system. We have been looking for problems with applications
that may be terminating before close any connection it may have open. A
short term fix of increasing the Max Connections has been considered, but we
want to make this a final option. What else could be causing this problem?
Thanks in advance.
Jeff Hinds
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
