similar to: Real-time sync using dsync

Displaying 20 results from an estimated 10000 matches similar to: "Real-time sync using dsync"

2014 Apr 16
1
dsync replication does not replicate new subfolders
Hello, Although this issue has been raised in another thread: https://www.mail-archive.com/dovecot at dovecot.org/msg57281.html I decided I should create a new one dedicated on it because that thread includes other issues as well, and the issue in question still remains unresolved although it is an important one (and I am hoping to attract Timo's attention on it, too ;-) ). The
2014 Mar 28
2
dsync replication questions
I am running two servers with Dovecot v2.2.12 on CentOS x86_64 (5.10 and 6.5 respectively) and users are virtual over ldap. I have setup our main internal server (vmail.example.com) with dsync replication according to the first part of http://wiki2.dovecot.org/Replication. The second one (vmail1.example.com) will be the failover server which we want to be a real-time mirror (but can be
2013 Apr 19
2
Dovecot Failover
Hello, Assuming we have two (low traffic) servers (on different data centers) replicated using dsync, what is the best way to automatically direct users to the main server when it is up and to the redundant one when the main server is down? Using DNS? I've seen that DNS-based failover has generally issues (for example:
2014 Mar 30
1
pop3 mailbox mirroring issues using dsync
Hello, I have setup v2.2.12 to mirror mailboxes between our main mail server (vmail.example.com) and a failover server (vmail1.example.com). The problem I have is the behavior of mailboxes used on the main server (*vmail*) over POP3. I have setup an IMAP account on the failover server (*vmail1*) on such a mailbox: the mailbox is used on vmail using POP3 and the same is monitored on vmail1
2017 May 05
4
CentOS 7 cloned VM cannot boot
On 5/5/2017 8:29 ??, Nikolaos Milas wrote: > I am very puzzled with "unknown filesystem". After more googling, I found this bug report with a very recent fix: https://bugzilla.redhat.com/show_bug.cgi?id=1399487 It seems to me that this may be relevant in our case. If so, may it be that this fix has not been rolled out to CentOS repos yet? What is your opinion and your
2014 Jan 07
2
Forward http traffic
Hello, On CentOS 6.5 x86_64 I have (/etc/sysconfig/iptables): *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] :RH-Firewall-1-INPUT - [0:0] -A INPUT -j RH-Firewall-1-INPUT -A FORWARD -j RH-Firewall-1-INPUT -A RH-Firewall-1-INPUT -i lo -j ACCEPT -A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT -A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT -A
2015 Aug 22
4
PROXY protocol
Op 8/21/2015 om 1:31 PM schreef Nikolaos Milas: > On 20/8/2015 11:09 ??, Nikolaos Milas wrote: > >> As soon as I manage to re-build Dovecot with the latest snapshot, >> I'll test it! > > Hello, > > I've built dovecot with a today snapshot from hg > (dovecot-2-2-9f815e781beb) and I am trying to enable haproxy. > > I configured as follows (lines added
2017 Jun 01
2
Urgent: Need to change the location of a directory tree
Hi, I am running CentOS 7 (fully updated) on a VM. This has a mounted nfs share (via fstab) (which mounts a remote storage system) on which we have created the home directories of 2 users Here are the home directories: /mynfsmount | |--/user1 |--/user1 We want to move this whole branch from the mounted NFS share to the local disk. What is the way to do so? Would it be enough to create a
2016 Jan 15
2
remote | local blocks in protocol settings
Hello, Where can I find detailed documentation on how "remote" & "local" blocks are used in protocol configuration to provide specific settings for particular IPs/Names? I've been searching around (wiki2, Google) but I found very few things. I also checked in the conf.d directory of the installation and couldn't find anything. One useful thread was here:
2011 Dec 15
1
DKIM Verification failures
Hi, -- This message refers to the maillist itself rather than to dovecot software -- I have noticed that when I post to this list (only), I get DKIM Verification failure reports from: root at moncton.sidefx.com (e.g. for my last post: "DKIM failure report for job 4D27B5DC4E on mail.sidefx.com") root at mail.rmacd.com (e.g. for my last post: "DKIM failure report for job
2017 May 04
4
CentOS 7 cloned VM cannot boot
On 4/5/2017 5:56 ??, Marcelo Roccasalva wrote: > dracut -f /boot/initramfs-<kernel_version>.img <kernel_version> I did: # dracut -f /boot/initramfs-3.10.0-514.10.2.el7.x86_64.img 3.10.0-514.10.2.el7.x86_64 and it ended without reporting any error. However, when I rebooted, nothing changed ("no such device: <UUID>. Entering rescue mode..."). Am I missing
2017 Aug 04
2
Problem switching from LDA to LMTP (with Postfix)
Hello, I am trying to switch from LDA to LMTP on a Postfix/Dovecot setup, but something is going wrong. I have followed the directions at: https://wiki.dovecot.org/HowTo/PostfixDovecotLMTP Here is a session from dovecot.log: Aug 4 12:19:42 vmail2 dovecot: lmtp(3152): Connect from local Aug 4 12:19:42 vmail2 dovecot: auth: ldap(imaptester at noa.gr): unknown user Aug 4 12:19:42 vmail2
2017 May 05
2
CentOS 7 cloned VM cannot boot
On 5/5/2017 1:19 ??, Gianluca Cecchi wrote: > Could you verify, if /dev/sda is your boot disk, with the command > > fdisk -l /dev/sda > ? It's /dev/vda in my case: # fdisk -l /dev/vda Disk /dev/vda: 21.5 GB, 21474836480 bytes, 41943040 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512
2017 Jan 04
3
Strange (?) device.map in CentOS 7 VM installations
On 01/04/2017 03:07 AM, Nikolaos Milas wrote: > Is it normal in CentOS 7 to have a device map with two entries esp. > when the (physical or virtual) hardware has only one hd ? I don't see that on VMs that I manage. Some of the physical machines that I manage do have duplicates in the device.map.
2015 Aug 25
2
PROXY protocol
On 22/8/2015 2:56 ??, Nikolaos Milas wrote: > Can we "stamp" log entries originating from different listeners with a > configurable label? Hello, I haven't received any reply on it. Is it possible or not? Thanks, Nick
2012 Dec 10
2
SOS: Production VM not starting!
I am using a VM with CentOS 5.8 x86_64 under KVM. I only have console access to the VM through a virtual console (web based). Tonight, after a routine "yum update", I did a "shutdown -r now" due to kernel update and the VM won't start. See console screenshot vm1.png: https://vmail.noa.gr/files/vm1.png There is an error (which I haven't seen before): type=1404
2011 Oct 28
6
dsync should sync sieve-dirs to!
Having dsync to make backups from existing mail-spaces, it would be nice to make dsync syncing the sieve-dirs too. -Otherweise backups aren't complete... Peer -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030 / 40 50 51 - 0 Fax: 030 / 40 50 51 - 19 Zwangsangaben lt. ?35a GmbHG: HRB 93818 B / Amtsgericht
2012 Jan 01
3
Dsync fails on second sync for folders with dot in the name
I'm in the processes of running our first dsync backup of all users (from maildir to mdbox on remote server), and one problem I'm hitting that dsync will work fine on first run for some users, and then reliably fail whenever I try a new run: $ sudo dsync -u janfrode at example.net backup ssh -q mailbackup at repo1.example.net dsync -u janfrode at example.net $ sudo dsync -u janfrode
2017 May 03
3
CentOS 7 cloned VM cannot boot
On 3/5/2017 10:41 ??, Marcelo Roccasalva wrote: > Does the UUID of root filesystem in /etc/fstab match the actual UUID > as reported by blkid? And remove/etc/lvm/cache/.cache if it exists Thank you Marcelo for replying, The directory /etc/lvm/cache/ is empty. And, yes, the UUID matches: # blkid /dev/vda1: UUID="297e2939-d6f5-431a-9813-9848368ee306" TYPE="xfs"
2017 May 05
3
CentOS 7 cloned VM cannot boot
On Fri, May 5, 2017 at 12:52 PM, Nikolaos Milas <nmilas at noa.gr> wrote: > On 5/5/2017 1:42 ??, Nikolaos Milas wrote: > > Hmm, it seems that the boot flag should be removed from /dev/vda2 >> partition? >> > > Actually, I tried this and left the boot flag only to /dev/vda1. I > rebooted and I am still getting the same error. :-( > > I was hoping we were