murder problems (mupdate getting lost between frontends and mupdate
master)
Sergio Devojno Bruder
bruder at haxent.com.br
Thu Apr 15 12:34:47 EDT 2004
Our murder started to act a little strange some days ago:
Apr 15 13:17:43 frontend1 mupdate[21845]: successful mupdate connection to master
Apr 15 13:17:43 frontend1 mupdate[21845]: unready for connections
Apr 15 13:17:43 frontend1 mupdate[21845]: synchronizing mailbox list with master mupdate server
Apr 15 13:17:58 frontend1 mupdate[21845]: retrying connection to mupdate server in 22 seconds
Apr 15 13:18:20 frontend1 mupdate[21845]: successful mupdate connection to master
Apr 15 13:18:20 frontend1 mupdate[21845]: unready for connections
Apr 15 13:18:20 frontend1 mupdate[21845]: synchronizing mailbox list with master mupdate server
Apr 15 13:18:43 frontend1 mupdate[21845]: retrying connection to mupdate server in 27 seconds
Apr 15 13:19:10 frontend1 mupdate[21845]: successful mupdate connection to master
Apr 15 13:19:10 frontend1 mupdate[21845]: unready for connections
Apr 15 13:19:10 frontend1 mupdate[21845]: synchronizing mailbox list with master mupdate server
....
and so on. the mupdate slave in frontends is looping in connecting, syncing, loose connection, connect, sync, loose, and so on.
Someone already saw this pattern? we are using cyrus 2.2.3 with skiplist mailboxes.db.
--
Sergio Devojno Bruder <bruder at haxent.com.br>
http://haxent.com.br 41 362-5930, 41 9127-6620
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
More information about the Info-cyrus
mailing list