Heartbeat and ISpConfig 3 cluster

Discussion in 'Installation/Configuration' started by Captain, Nov 6, 2012.

  1. Captain

    Captain Member

  2. till

    till Super Moderator Staff Member ISPConfig Developer

    No, not automatically.

    Thats both possible.
     
  3. Captain

    Captain Member

    BIg thnks Till for your fast answer.

    Next week I will try to install and configure heartbeat with your Perfect cluster install.
    I will post about it.
     
  4. webguyz

    webguyz Member HowtoForge Supporter

    Looking forward to your results as I'm interested in trying this myself.
     
  5. Captain

    Captain Member

    Hello!

    Try to install cluster on virtual machines.

    Replications is Ok.
    I see on both server dbispconfig1 and dbispconfig2 DB.

    But when I try to install ISPConfig3 on srv2 have the error:

    Code:
    Unable to read server configuration from database.root@srv2:/tmp/ispconfig3_install/install
    
    How to solve it?

    Thank you.
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Which directories are mirrored by drbd and did you use different mysql users for the local ispconfig instances as described in the mirror guide?
     
  7. Captain

    Captain Member

    Thank you for fast answer Till!

    I use your perfect tutorial - cluster debian 6.0

    For file replication I use Unison - (/var/vmail and /var/www)

    on srv1 -
    dbispconfig1 - user ispconfig
    dbispconfig2 - user ispconfig2

    on srv2 -
    dbispconfig1 - user ispconfig
    dbispconfig2 - user ispconfig2
     
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    Are you are sure that you executed the install.php script and not the update.php script on srv2? The error message that you posted exists in the updater only, not the installersoit can not appear during installation.
     
  9. Captain

    Captain Member

    I reinstall ISPConfig on second server and now it works ok.

    Now I try to configurate heartbeat.

    Later I post about it.

    Thank you.
     
  10. Captain

    Captain Member

    I cofigured heartbeat wotk great.
    If need configuration steps I can post it.

    When I stop the master server. Slave goes on.

    After that I power on it (slave).

    Create new Client on srv1, but there are no replication now.
    on srv2 I did not see new client.

    in show slave status:

    Code:
    Error 'Table 'attempts_login' already exists' on query. Default database: 'dbispconfig2'. Query: 'CREATE TABLE `attempts_login` (
     `ip` varchar(39) NOT NULL,
     `times` int(11) DEFAULT NULL,
     `login_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP
    ) ENGINE=MyISAM DEFAULT CHARSET=utf8'
    
    
    How to solve it?
     
    Last edited: Nov 26, 2012
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    The above error is not related to creating a client in ispconfig. The query is from a ispconfig update were the ispconfig datannbase must have been updated or manually replaced before so that the updater could not recognize its structure due to a missing db version number in the server table of this server. So it is something related to your initial setup, maybe you installed ispconfig more then once on the server without removing it completely before.

    You can e.g. try to skip this replication step in mysql.
     
  12. Captain

    Captain Member

    Thank you for answer Till!

    I reinstall ISPConfig and re-replicate mysql.

    But question about mirroring, if I something create on slave server for expl. new mailbox. On should to be on master server too or mirroring goes only one direction?

    I am asking because I create one email on slave and now did not see it on master. If it is normal it is ok.

    But it is possible to create bi-direction mirroring?

    Thank you.
     
  13. till

    till Super Moderator Staff Member ISPConfig Developer

    The mirror guide installs a bidirectional mirroring. So it oes not matter if sou crate a mailbox on the master or the slave as the settings are applied on both servers automatically. At the end of the guide are instructions to copy the config.inc.php file from master to slave, this step is important ans has to be redone after an update to ensure that sou can use the ispconfig interface on the master and the slave.
     

Share This Page