Page 3 of 3 FirstFirst 123
Results 21 to 28 of 28

Thread: Multi- server setup query

  1. #21
    Join Date
    Dec 2007
    Posts
    445
    Rep Power
    7

    Default

    Hi guys,

    To avoid above mentioned mysql replication issue, I am going to use source IP base sticky session on F5 load balancer. So i hope that can address this issue..

    Now I have started looking for how can I seperate LDAP configuration from Zimbra Single setup...But i couldnt find out any document or post regarding the same ...

    I want to sperate LDAP from single zimbra setup ...rest of the things ( MTA, Store ) will be on the same server..

    Please suggest ..or let me know any link where i can get details for the same...

    Thanks

  2. #22
    Join Date
    Dec 2007
    Posts
    445
    Rep Power
    7

    Default

    hi guys,

    Can anyone please tell is there any standard procedure to take LDAP out from single zimbra setup ?

    Thanks

  3. #23
    Join Date
    Nov 2007
    Location
    Santa Barbara, CA.
    Posts
    109
    Rep Power
    8

    Default

    Quote Originally Posted by chandu View Post
    hi guys,

    Can anyone please tell is there any standard procedure to take LDAP out from single zimbra setup ?

    Thanks
    We migrated from a single server installation to a multi server installation. I'm assuming you'd like to take the LDAP instance and move it to another zimbra server.

    We run NE, so we essentially ran a zimbra LDAP backup then copied that over to the new master zimbra server and ran zmrestore. After verifying the restore, we repointed the single zimbra server LDAP resources.


    To do this, we did:
    * zmlocalconfig -e ldap_url="ldap://new-ldap-master.example.com:389"

    sidenote:
    If you have an active LDAP slave server, then you can use that then the master:
    * zmlocalconfig -e ldap_url="ldap://new-ldap-slave.example.com:389 ldap://new-ldap-master.example.com:389"

    then disable the LDAP service:
    * zmprov ms `zmhostname` -zimbraServiceEnabled ldap


    It would be best to do a full zmcontrol stop / start at this point on the old server.


    It's been a few years since I actually did this, so I may be a little rusty on the process, but I can lab it up if you'd like.

    Good luck!

    --
    Jessie

  4. #24
    Join Date
    Dec 2007
    Posts
    445
    Rep Power
    7

    Default

    Hi Jessie,

    Thank u so much for reply ...

    I am using open source so have to find out the way to take it out. let me try something..will post soon..

  5. #25
    Join Date
    Sep 2008
    Location
    Latvia
    Posts
    165
    Rep Power
    7

    Default

    Hello, Chandu, sorry for dropping out of conversation, as my knowledge at this point for LDAP settings could not help anyway. As I've mentioned before, we use DRBD block device mirring, and do not have such issues. Although other consequences come in place - timeout in about 40 seconds to boot zimbra on other running server.

    Probably we'll try to implement LMStone sugestion mentioned in this thread.

    As far as your solution with sticky sessions on F5, I think, if you are happy with solution, that in such case no real load balancing between store servers could be done (more of the time, one store server will have more connections, than other), then it is OK. I recently switched off such solution for our web cluster (not ZCS, as it is not clustered for load balancing, but for failover), and it evened out load on servers. For MySQL - did you consider MySQL Proxy? Still, I think, it is in beta state, but there are many solutions which do work correctly.

  6. #26
    Join Date
    Dec 2007
    Posts
    445
    Rep Power
    7

    Default

    Sorry guys for delay in reply.

    Hey j2b, in F5 we can set retention period as per our setup requirement for sticky session.


    We successfully migrated our production dump in test environment and it worked as per our logic for existing users...
    I am enclosing by current setup configuration details with this thread for better understanding of my current setup status.

    We started tetsing to create new users and set huge mail communication to test load balancing.
    Now we are facing issue with error in logs and webmail .... account_id already exist , item already exist...

    I want to understand mailbox structure and found below very nice wiki page :

    Account mailbox database structure - Zimbra :: Wiki

    From this i got how mailbox id and group id are getting generated but want to understand below things :

    1. I am confuse regarding definition of mailbox_id, id and account_id. Is there any another link where I can get more clear picture.
    2. who is (ldap / mysql / zimbra code itself) generating these IDs? and which logic /algorithm it use for this creation ?
    3. In my setup I have shared store and index and mysql between both mail store ....is there any important thing I m missing to share between two mail store servers ?

    ################################################## ##

    I need to understand these details as I am getting below error message :

    I am getting below error message when I tried to send bulk mails through new email ids :




    2010-06-02 13:54:50,726 INFO [LmtpServer-276] [ip=1.1.1.2;] lmtp - Delivering message: size=1024 bytes, nrcpts=1, sender=user1@example.com, msgid=<20100602082437.9162334005@tcs-itontap.com>
    2010-06-02 13:54:50,727 INFO [LmtpServer-276] [name=user2@example.com;mid=5361;ip=1.1.1.2;] mailop - Adding Message: id=257, Message-ID=<20100602082437.9162334005@tcs-itontap.com>, parentId=-1, folderId=2, folderName=Inbox.
    2010-06-02 13:54:51,006 INFO [LmtpServer-276] [] ProtocolHandler - Handler exiting normally
    2010-06-02 13:54:52,957 INFO [ImapSSLServer-35434] [] imap - [1.1.1.4] connected
    2010-06-02 13:54:52,957 INFO [ImapSSLServer-35434] [ip=1.1.1.4;] ProtocolHandler - Exception occurred while handling connection
    javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:808)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.perform InitialHandshake(SSLSocketImpl.java:1112)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRe cord(SSLSocketImpl.java:623)
    at com.sun.net.ssl.internal.ssl.AppOutputStream.write (AppOutputStream.java:59)
    at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
    at com.zimbra.cs.imap.TcpImapHandler.sendLine(TcpImap Handler.java:239)
    at com.zimbra.cs.imap.ImapHandler.sendResponse(ImapHa ndler.java:3724)
    at com.zimbra.cs.imap.ImapHandler.sendUntagged(ImapHa ndler.java:3703)
    at com.zimbra.cs.imap.TcpImapHandler.setupConnection( TcpImapHandler.java:55)
    at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:130)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.io.EOFException: SSL peer shut down incorrectly
    at com.sun.net.ssl.internal.ssl.InputRecord.read(Inpu tRecord.java:333)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:789)
    ... 12 more
    2010-06-02 13:54:52,958 INFO [ImapSSLServer-35434] [] ProtocolHandler - Handler exiting normally
    2010-06-02 13:54:53,857 INFO [Pop3SSLServer-35425] [ip=1.1.1.4;] pop - connected
    2010-06-02 13:54:53,857 INFO [Pop3SSLServer-35425] [ip=1.1.1.4;] ProtocolHandler - Exception occurred while handling connection
    javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:808)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.perform InitialHandshake(SSLSocketImpl.java:1112)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRe cord(SSLSocketImpl.java:623)
    at com.sun.net.ssl.internal.ssl.AppOutputStream.write (AppOutputStream.java:59)
    at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
    at com.zimbra.cs.pop3.Pop3Handler.sendLine(Pop3Handle r.java:362)
    at com.zimbra.cs.pop3.Pop3Handler.sendResponse(Pop3Ha ndler.java:351)
    at com.zimbra.cs.pop3.Pop3Handler.sendOK(Pop3Handler. java:326)
    at com.zimbra.cs.pop3.Pop3Handler.startConnection(Pop 3Handler.java:117)
    at com.zimbra.cs.pop3.TcpPop3Handler.setupConnection( TcpPop3Handler.java:42)
    at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:130)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.io.EOFException: SSL peer shut down incorrectly
    at com.sun.net.ssl.internal.ssl.InputRecord.read(Inpu tRecord.java:333)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:789)

    ... 13 more
    2010-06-02 13:54:53,858 INFO [Pop3SSLServer-35425] [] ProtocolHandler - Handler exiting normally
    2010-06-02 13:54:54,620 INFO [ImapSSLServer-35435] [] imap - [1.1.1.4] connected
    2010-06-02 13:54:54,620 INFO [ImapSSLServer-35435] [ip=1.1.1.4;] ProtocolHandler - Exception occurred while handling connection
    javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:808)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.perform InitialHandshake(SSLSocketImpl.java:1112)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRe cord(SSLSocketImpl.java:623)
    at com.sun.net.ssl.internal.ssl.AppOutputStream.write (AppOutputStream.java:59)
    at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
    at com.zimbra.cs.imap.TcpImapHandler.sendLine(TcpImap Handler.java:239)
    at com.zimbra.cs.imap.ImapHandler.sendResponse(ImapHa ndler.java:3724)
    at com.zimbra.cs.imap.ImapHandler.sendUntagged(ImapHa ndler.java:3703)
    at com.zimbra.cs.imap.TcpImapHandler.setupConnection( TcpImapHandler.java:55)
    at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:130)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.io.EOFException: SSL peer shut down incorrectly
    at com.sun.net.ssl.internal.ssl.InputRecord.read(Inpu tRecord.java:333)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:789)
    ... 12 more
    2010-06-02 13:54:54,621 INFO [ImapSSLServer-35435] [] ProtocolHandler - Handler exiting normally
    2010-06-02 13:54:55,520 INFO [Pop3SSLServer-35426] [ip=1.1.1.4;] pop - connected
    2010-06-02 13:54:55,520 INFO [Pop3SSLServer-35426] [ip=1.1.1.4;] ProtocolHandler - Exception occurred while handling connection
    javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:808)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.perform InitialHandshake(SSLSocketImpl.java:1112)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRe cord(SSLSocketImpl.java:623)
    at com.sun.net.ssl.internal.ssl.AppOutputStream.write (AppOutputStream.java:59)
    at java.io.BufferedOutputStream.flushBuffer(BufferedO utputStream.java:65)
    at java.io.BufferedOutputStream.flush(BufferedOutputS tream.java:123)
    at com.zimbra.cs.pop3.Pop3Handler.sendLine(Pop3Handle r.java:362)
    at com.zimbra.cs.pop3.Pop3Handler.sendResponse(Pop3Ha ndler.java:351)
    at com.zimbra.cs.pop3.Pop3Handler.sendOK(Pop3Handler. java:326)
    at com.zimbra.cs.pop3.Pop3Handler.startConnection(Pop 3Handler.java:117)
    at com.zimbra.cs.pop3.TcpPop3Handler.setupConnection( TcpPop3Handler.java:42)
    at com.zimbra.cs.tcpserver.ProtocolHandler.run(Protoc olHandler.java:130)
    at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Wo rker.run(Unknown Source)
    at java.lang.Thread.run(Thread.java:619)
    Caused by: java.io.EOFException: SSL peer shut down incorrectly
    at com.sun.net.ssl.internal.ssl.InputRecord.read(Inpu tRecord.java:333)
    at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRec ord(SSLSocketImpl.java:789)
    ... 13 more
    2010-06-02 13:54:55,521 INFO [Pop3SSLServer-35426] [] ProtocolHandler - Handler exiting normally
    2010-06-02 13:54:57,957 INFO [ImapSSLServer-35436] [] imap - [1.1.1.4] connected


    Caused by: com.mysql.jdbc.exceptions.MySQLIntegrityConstraint ViolationException: Duplicate entry 'b6c115ea-aaba-400d-900e-c9f5510698d1' for key 2

    Query being executed when exception was thrown:

    INSERT INTO mailbox(account_id, id, group_id, index_volume_id, item_id_checkpoint, last_backup_at, comment) VALUES ('b6c115ea-aaba-400d-900e-c9f5510698d1', 5681, 81, 2, 255, null, 'user@example.com')
    at com.mysql.jdbc.SQLError.createSQLException(SQLErro r.java:931)
    at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.ja va:2985)
    at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:16 31)
    at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java :1723)
    at com.mysql.jdbc.Connection.execSQL(Connection.java: 3283)
    at com.mysql.jdbc.PreparedStatement.executeInternal(P reparedStatement.java:1332)
    at com.mysql.jdbc.PreparedStatement.executeUpdate(Pre paredStatement.java:1604)
    at com.mysql.jdbc.PreparedStatement.executeUpdate(Pre paredStatement.java:1519)
    at com.mysql.jdbc.PreparedStatement.executeUpdate(Pre paredStatement.java:1504)
    at com.zimbra.cs.db.DebugPreparedStatement.executeUpd ate(DebugPreparedStatement.java:173)
    at org.apache.commons.dbcp.DelegatingPreparedStatemen t.executeUpdate(DelegatingPreparedStatement.java:1 02)
    at com.zimbra.cs.db.DbMailbox.createMailbox(DbMailbox .java:253)
    ... 40 more
    2010-06-02 15:22:52,843 INFO [btpool0-9://localhost:8100/service/soap/AuthRequest] [oip=1.1.1.4;ua=zclient/6.0.6_GA_2324.RHEL5_64;] soap - AuthRequest
    2010-06-02 15:22:52,849 ERROR [btpool0-9://localhost:8100/service/soap/AuthRequest] [name=user@example.com;oip=1.1.1.4;ua=zclient/6.0.6_GA_2324.RHEL5_64;] mailbox - Error during mailbox creation
    com.zimbra.common.service.ServiceException: system failure: writing new mailbox row for account b6c115ea-aaba-400d-900e-c9f5510698d1
    ExceptionId:btpool0-9://localhost:8100/service/soap/AuthRequest:1275472372849:71d29b78d1587eb4
    Code:service.FAILURE


    ################################################## ##


    Please help..

    Thanks
    Attached Files Attached Files

  7. #27
    Join Date
    Dec 2007
    Posts
    445
    Rep Power
    7

    Default

    Hi guys,

    After some tetsing I found that, for existing production dump users there is no issue as both mail stores / mysql are aware about the all existing users and their respective IDs....

    But the issue is with newly created users...

    When I logged in to user1@example.com through F5 virtual IP..that request went to one of the mailstore ...and when sticky session retention period got over and the same user try to login again then request went to mailstore2 and it throw error that "b6c115ea-aaba-400d-900e-c9f5510698d1" is already exist and it stopped working there only ...

    Ya as per logic zimbra functionality is correct ....


    To fix this issue in my setup I need to understand how this FIRST login process happened ..who is generating the IDs for new users and who cross verify the existing user list ....

    Is there any way where we can ask mailstore to accept entry if it found the entry for first login ? ...i know this sound fishy and security risk ..but if we understand perfectly how it work then we can think about any other work around...

    Please suggest

  8. #28
    Join Date
    Dec 2007
    Posts
    445
    Rep Power
    7

    Default

    Hi Guys,

    As I told in my previous post that I am facing issue with only newly created email IDs and getting conflict due to duplicate entry.

    So for testing, I stopped service on 1st mailbox server and created user on another mailstore and logged in with same server and it work with usual way then I started service on first mailbox and now both servers are up and again tried to access this new user on both servers and it worked.

    It seems the information of newly created mailbox and first login is getting store somewhere in application memory ..i dont knw exactly ....is there any imporatnt thing I am missing here ? do i need to SHARE any other parameter between both mailbox servers ?


    Any idea, ...will RCS ( Redhat cluster suite) support zimbra active-active?

    Please suggest guys...

    thanks
    Last edited by chandu; 06-07-2010 at 06:58 AM.

Similar Threads

  1. dns in multi server
    By vikjava in forum Installation
    Replies: 17
    Last Post: 04-03-2009, 01:45 AM
  2. com_zimbra_asterisk on a multi server setup?
    By stephenwilley in forum Zimlets
    Replies: 0
    Last Post: 01-20-2009, 04:33 AM
  3. Error after installation
    By robsontuxlinux in forum Installation
    Replies: 13
    Last Post: 09-11-2008, 10:48 PM
  4. Moving from single to multi server
    By stephenwilley in forum Administrators
    Replies: 1
    Last Post: 06-11-2008, 10:52 AM
  5. Multi server install not working
    By Nassri in forum Installation
    Replies: 18
    Last Post: 08-17-2006, 10:23 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •