1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice

mchk still has error after first big fix

Discussion in 'Plesk for Linux - 8.x and Older' started by rvdmeer, Nov 6, 2005.

  1. rvdmeer

    rvdmeer Guest

    0
     
    Hi there,

    Oke, the last bug was an segmentation failed in mchk. After they fixed this i guess the programmer forgot to close the mysql connection to the PSA database.

    [root@vite plugins]# /usr/local/psa/admin/bin/mchk -v
    mchk: db_connect: failed to connect to database: Error: Too many connections
    mchk: db_connect: failed to connect to database: Error: Too many connections
    mchk: Unable to connect to the Plesk database
    mchk: Unable to connect to the Plesk database

    I guess more users are experiencing this... is there any news regarding this issue?

    Kind regards,
     
  2. mikk

    mikk Basic Pleskian

    23
    73%
    Joined:
    Jan 29, 2005
    Messages:
    83
    Likes Received:
    0
    This is easily fixed by increasing the max connections for mysql.

    Edit /etc/my.cnf and ensure you have a line like this - set XXXX accordingly.

    [mysqld]
    set-variable=max_connections=XXXX

    Then restart mysql
     
  3. rvdmeer

    rvdmeer Guest

    0
     
    Thanks for your reply but i know how to "solve" (work around) it.
    But i dont think thats the way how to solve the problem. The MAX in the config is set with a reason offcourse :)
     
  4. mikk

    mikk Basic Pleskian

    23
    73%
    Joined:
    Jan 29, 2005
    Messages:
    83
    Likes Received:
    0
    Personally never had a shared server where the "max" is enough :)

    But i guess it depends how many people you have active on the server.

    (wonder why they decided to add a max_connections variable to mysql if it wasnt too be used) :)
     
  5. rvdmeer

    rvdmeer Guest

    0
     
    As far as i can see the program is connecting to the SQL server and after that another session (socket) will be opened without closing the old.. thats the problem and that they should fix :)

    Did anyone already submit something regarding this?
     
Loading...