ISPConfig and Percona DB

Discussion in 'General' started by FatJay, Dec 8, 2015.

  1. FatJay

    FatJay New Member

    Hi Guys

    Just to say what a wonderful product, All the features one would need and it just works well.

    Senorio i am building and would like to know if it will fail or work

    Built already....

    ISPConfig main Server: Apache , MySQL , Bind , Dovecot , Mailman , as per Perfect install on Debian
    ISPConfig NS server 1 : Debian , MySQL , Bind
    ISPConfig Web Server 1 : Debian , MySQL, PureFTP , Apache
    ISPCOnfig Web Server 2 : Debian , MySQL, PureFTP , Apache
    ISPConfig Web Server 3 : Debian , MySQL , PureFTP, Apache
    ISPConfig Web Server 4 : Debian , MySQL , PureFTP, Apache

    Now the catch system

    ISPConfig DB Server : Debian , Percona

    The Percona is not to be used for ISPConfig, but for another system that will run on the 4 Web servers.

    If i add this Second last ISPConfig DB server will it create a problem on the main setup of MySQL?

    Also can i migrate from MySQL to MariaDB on ISPConfig?

    The last server to be added will be

    ISPConfig FTP Sync Server: Debian , MySQL , Puteftp, CSYNC or maybe RSYNC

  2. florian030

    florian030 Well-Known Member HowtoForge Supporter

    I think you can install ispconfig even if you percona instead of mysql. It makes no difference if you use maria or mysq.
  3. FatJay

    FatJay New Member

    Thank you
    will try the setup shortly and post my feedback
  4. FatJay

    FatJay New Member

    So far it works like a dream

    Thank you for your support
  5. iszabi

    iszabi New Member

    Hi FatJay and florian03 !
    We are using more servers with Percona MySQL and ispConfig in multiservers.
    Note: If you are using percona mySQL, you can change lib mysqli to mysqlnd,
    if loaded in PHP Cli, the ispconfig install and update processes stopped, so this error has been occured:
    PHP Fatal error: Class 'mysqli' not found in /usr/local/ispconfig/server/lib/classes/ on line 31

    The soultion today is to change mysqlnd to mysqli under ispconfig before install/update, and after chage to mysqlnd and
    correct mysql.sock path in my.conf, too.
    I think in the next ispConfig version will be resolved this little bug.

    I hope helped you, and have a good work.

Share This Page