[Koha] MySQL socket errors

[Robert Meltz]

Thanks Reed, could you please clarify a bit? Are you referring to the line in my.cnf that contains "bind-address" because if so, it is already set to 127.0.0.1. 

Best regards,
Robert Meltz
Field Service Engineer

770.458.8658 x108
404.642.9093 cell
rmeltz at insolnet.com
www.insolnet.com

Follow us on Twitter:  www.twitter.com/Insol_IT

At Insol: ownership and partnership know no bounds.  IT's personal.

-----Original Message-----
From: reedwade at gmail.com [mailto:reedwade at gmail.com] On Behalf Of Reed Wade
Sent: Friday, June 04, 2010 10:48 PM
To: Robert Meltz
Cc: koha at lists.katipo.co.nz
Subject: Re: [Koha] MySQL socket errors

Consider using the IP address (127.0.0.1) instead of localhost for the
db connection. This will cause mysql to connect via TCP instead of
using a named socket and may help -- assuming your database is
responsive otherwise.

(
Mysql's decision to trap the localhost name and act differently with
it instead of making that a separate option is insane but in
character.
)

-reed



On Sat, Jun 5, 2010 at 12:35 AM, Robert Meltz <RMeltz at insolnet.com> wrote:
> Good Morning,
>
> I am having problems with Koha returning the following error:
>
> Koha error
> The following fatal error has occurred:
>
> Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/perl/5.8/CGI/Carp.pm line 314.
> Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 30.
> BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 30.
> Compilation failed in require at /usr/share/koha/opac/cgi-bin/opac/opac-detail.pl line 25.
> BEGIN failed--compilation aborted at /usr/share/koha/opac/cgi-bin/opac/opac-detail.pl line 25.
>
>
> If I refresh the page it usually works, but this error appears more often than not since yesterday morning. I looked at some performance items suspecting that it may be related to slow response from the underlying system.
>
> top - 08:31:07 up 20:01,  1 user,  load average: 0.21, 0.24, 0.25
>
> # for i in a b; do hdparm -tT /dev/sd"$i"; done
>
> /dev/sda:
>  Timing cached reads:   2166 MB in  1.88 seconds = 1152.66 MB/sec
>  Timing buffered disk reads:   22 MB in  3.28 seconds =   6.71 MB/sec
>
> /dev/sdb:
>  Timing cached reads:   2530 MB in  1.87 seconds = 1355.50 MB/sec
>  Timing buffered disk reads:   34 MB in  3.32 seconds =  10.24 MB/sec
>
> # mount
> /dev/sda1 on / type ext3 (rw,relatime,errors=remount-ro)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> /sys on /sys type sysfs (rw,noexec,nosuid,nodev)
> varrun on /var/run type tmpfs (rw,noexec,nosuid,nodev,mode=0755)
> varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
> udev on /dev type tmpfs (rw,mode=0755)
> devshm on /dev/shm type tmpfs (rw)
> devpts on /dev/pts type devpts (rw,gid=5,mode=620)
> /dev/sdb1 on /var/lib type ext3 (rw,relatime,errors=remount-ro)
>
> It looks to me like the drives are slow. Not all that surprising considering that there are 6 virtual machines running off the same hyper-V host. What can I do to increase the performance under these conditions, or am I on the wrong track entirely?
>
> Best regards,
> Robert Meltz
> _______________________________________________
> Koha mailing list
> Koha at lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>