SQL Socket Error

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Alan Powell

    SQL Socket Error

    Hello all

    I am a newbie to Linux, Apache and mySQL etc. I am running a standard RH9
    build with yum updates. All appears to be working ok except one aspect.
    Simple database (indexed 2 table)activity works but on a more sophisticated
    existing database accessed through a perl script I get this error (taken
    from logs): -

    [Tue Apr 27 20:22:52 2004] [error] [client 192.168.0.12] [Tue Apr 27
    20:22:52 2004] lbf.cgi: DBI
    connect('userna me_disney:local host','username _lettuce',...) failed: Can't
    connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'
    (13) at /home/username/public_html/dating/cgi-bin/scripts/new_database.pl
    line 6, referer: http://www.awebsite.loc/

    I have checked that the daemon is up and all standard checks recommended
    from the mySQL site show the socket is connecting ok and for TCP/IP on port
    3306 etc....

    Any ideas please? Thanks in advance

    Alan



  • Alan Powell

    #2
    Re: SQL Socket Error

    By the way, my mysql.sock file is 0 bytes! Is this correct???

    "Alan Powell" <alan.powell@as sured-design.com> wrote in message
    news:cCKjc.1074 $28.365@fe07.us enetserver.com. ..[color=blue]
    > Hello all
    >
    > I am a newbie to Linux, Apache and mySQL etc. I am running a standard RH9
    > build with yum updates. All appears to be working ok except one aspect.
    > Simple database (indexed 2 table)activity works but on a more[/color]
    sophisticated[color=blue]
    > existing database accessed through a perl script I get this error (taken
    > from logs): -
    >
    > [Tue Apr 27 20:22:52 2004] [error] [client 192.168.0.12] [Tue Apr 27
    > 20:22:52 2004] lbf.cgi: DBI
    > connect('userna me_disney:local host','username _lettuce',...) failed: Can't
    > connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'
    > (13) at /home/username/public_html/dating/cgi-bin/scripts/new_database.pl
    > line 6, referer: http://www.awebsite.loc/
    >
    > I have checked that the daemon is up and all standard checks recommended
    > from the mySQL site show the socket is connecting ok and for TCP/IP on[/color]
    port[color=blue]
    > 3306 etc....
    >
    > Any ideas please? Thanks in advance
    >
    > Alan
    >
    >
    >[/color]



    Comment

    • Alan Powell

      #3
      Re: SQL Socket Error

      By the way, my mysql.sock file is 0 bytes! Is this correct???

      "Alan Powell" <alan.powell@as sured-design.com> wrote in message
      news:cCKjc.1074 $28.365@fe07.us enetserver.com. ..[color=blue]
      > Hello all
      >
      > I am a newbie to Linux, Apache and mySQL etc. I am running a standard RH9
      > build with yum updates. All appears to be working ok except one aspect.
      > Simple database (indexed 2 table)activity works but on a more[/color]
      sophisticated[color=blue]
      > existing database accessed through a perl script I get this error (taken
      > from logs): -
      >
      > [Tue Apr 27 20:22:52 2004] [error] [client 192.168.0.12] [Tue Apr 27
      > 20:22:52 2004] lbf.cgi: DBI
      > connect('userna me_disney:local host','username _lettuce',...) failed: Can't
      > connect to local MySQL server through socket '/var/lib/mysql/mysql.sock'
      > (13) at /home/username/public_html/dating/cgi-bin/scripts/new_database.pl
      > line 6, referer: http://www.awebsite.loc/
      >
      > I have checked that the daemon is up and all standard checks recommended
      > from the mySQL site show the socket is connecting ok and for TCP/IP on[/color]
      port[color=blue]
      > 3306 etc....
      >
      > Any ideas please? Thanks in advance
      >
      > Alan
      >
      >
      >[/color]



      Comment

      • Aggro

        #4
        Re: SQL Socket Error

        Alan Powell wrote:
        [color=blue]
        > By the way, my mysql.sock file is 0 bytes! Is this correct???[/color]

        Yes. Sometimes the only information file needs to provide is whether it
        exists or not. This is one of those cases.

        Comment

        • Aggro

          #5
          Re: SQL Socket Error

          Alan Powell wrote:
          [color=blue]
          > By the way, my mysql.sock file is 0 bytes! Is this correct???[/color]

          Yes. Sometimes the only information file needs to provide is whether it
          exists or not. This is one of those cases.

          Comment

          • Alan Powell

            #6
            Re: SQL Socket Error

            Thanks aggro

            I have now gotten my server running ok on sockets. I am using webmin to
            administer and after some experiments found that I need to set a password
            for each user for "localhost" as well as "all".

            Problem solved.

            "Aggro" <spammerdream@y ahoo.com> wrote in message
            news:NiSjc.608$ rd1.413@read3.i net.fi...[color=blue]
            > Alan Powell wrote:
            >[color=green]
            > > By the way, my mysql.sock file is 0 bytes! Is this correct???[/color]
            >
            > Yes. Sometimes the only information file needs to provide is whether it
            > exists or not. This is one of those cases.[/color]



            Comment

            • Alan Powell

              #7
              Re: SQL Socket Error

              Thanks aggro

              I have now gotten my server running ok on sockets. I am using webmin to
              administer and after some experiments found that I need to set a password
              for each user for "localhost" as well as "all".

              Problem solved.

              "Aggro" <spammerdream@y ahoo.com> wrote in message
              news:NiSjc.608$ rd1.413@read3.i net.fi...[color=blue]
              > Alan Powell wrote:
              >[color=green]
              > > By the way, my mysql.sock file is 0 bytes! Is this correct???[/color]
              >
              > Yes. Sometimes the only information file needs to provide is whether it
              > exists or not. This is one of those cases.[/color]



              Comment

              Working...