Menu

error 2: PDO::__construct

Help
Lou Hurst
2010-01-02
2013-05-30
  • Lou Hurst

    Lou Hurst - 2010-01-02

    At your convenience folks!

    Running PGV 4.2.3 locally on a linux box with XAMPP 1.7.2

    Receive the following error in PGV:

    ERROR 2: PDO::__construct() :  Invalid argument (trying to connect via unix://)<br>
    0 Error occurred on in function __construct<br>
    1 called from line 115 of file class_pgv_db.php in function createInstance<br>
    2 called from line 276 of file session.php in function require_once<br>
    3 called from line 79 of file config.php in function require_once<br>
    4 called from line 42 of file install.php<br>
    Warning: PDO::__construct() :  Invalid argument (trying to connect via unix://) in /home/lou/public_html/pgv/includes/classes/class_pgv_db.php on line 115

    XAMPP specs:<br>
    PHP Version 5.3.0<br>
    mysqlnd 5.0.5-dev<br>
    PDO drivers mysql, pgsql, sqlite, sqlite2<br>
    pdo_mysql (enabled)  Client API version mysqlnd 5.0.5-dev

    Have downgraded to XAMPP 1.7.1 and all is well so just want to report this since from threads in Help & Open Discussion PGV 4.2.3 might now be happy with PHP 5.3 and MySQL 5.0.x.

    (and do I really have to hand-type an html br just to have a single space between lines or are they going to show up after I hit Add Topic?)

    Happy New Year

    Lou

     
  • Lou Hurst

    Lou Hurst - 2010-01-02

    Forgot to ask, does the workaround of editing the PHP 5.3 php.ini file I think it was to suppress error msgs still apply?

    Thanx

     
  • Lou Hurst

    Lou Hurst - 2010-01-02

    Just for fun, setup and did a fresh, brand-new out of the box install of PGV 4.2.3 and XAMPP 1.7.3, same error on initial login to PGV.

    Gonna go enjoy the 0 degree weather and snow of the great plains now.

    Lou

     
  • Greg Roach

    Greg Roach - 2010-01-02

    Did you keep your old php.ini file when you upgraded?

     
  • Lou Hurst

    Lou Hurst - 2010-01-02

    yes, have the old php.ini file, it's now the one back in use with 1.7.1.  LH

     
  • Anonymous

    Anonymous - 2010-01-02

    I suspect the upgrade from 1.7.2 to 1.7.3 didn't happen properly. This was a well reported error in 1.7.2.  The 1.7.3 release was the fix for it. I use it all the time, have done since it was released, and no problems.

     
  • Lou Hurst

    Lou Hurst - 2010-01-02

    Now that you mention it -

    When I got 1.7.3 installed, both via upgrade and as new install, after securing it (/opt/lampp/lampp security) MySQL showed as deactivated on the Lampp status page.  PGV didn't want to run with it "deactivated" (yet working) and fixed.

    I haven't looked anywhere else in my file system for other Lampp/Xampp files; as I recall it's a fairly well self-contained program isn't it?  LH

     
  • Lou Hurst

    Lou Hurst - 2010-01-02

    Oh and running it on a 64 big machine.  LH

     
  • Greg Roach

    Greg Roach - 2010-01-02

    IIRC, a configuration setting that controls how PHP talks to MySQL was changed in 1.7.2.  If you've retained your old php.ini, you'll have the "new" settings at the php end, and the "old" settings at the mysql end.

     
  • Lou Hurst

    Lou Hurst - 2010-01-02

    Sorry it looks like this is turning into a tech support thread for Xampp -

    So why would there be naughty behavior with a new install of 1.7.3?  Going back maybe to a question of does Lampp install files outside of /opt/lampp on a linux box that I'm missing?

     
  • Lou Hurst

    Lou Hurst - 2010-01-02

    Hey found something over at Xampp.

    -I saw the same problem and found a fix on the web so I'm sharing. The observed behavior for me on Ubuntu Karmic Koala is that MySQL and MySQLi calls will work fine but PDO fails with the error listed in the previous posting.

    Open up your php.ini file in the /opt/lampp/etc directory. You may need root privileges to edit the file on your distro.

    Look for the line titled pdo_mysql.default_socket. Add /opt/lampp/var/mysql/mysql.sock after the equal sign and save the file. Once I did this I was able to get PDO working properly.-

    Will try this and get back; I've got an identical (I think) situation.  LH

     
  • Lou Hurst

    Lou Hurst - 2010-01-02

    Ah Ha!  Happy Happy Joy Joy!  Telling the kid where to go for a default socket fixed it.  And without fixing the MySQL Deactivated (in Xampp status) problem yet.

    Lou

     

Log in to post a comment.