Displaying 3 results from an estimated 3 matches for "blade6".
Did you mean:
blades
2013 Dec 09
0
Gluster - replica - Unable to self-heal contents of '/' (possible split-brain)
Hello,
I''m trying to build a replica volume, on two servers.
The servers are: blade6 and blade7. (another blade1 in the peer, but with
no volumes)
The volume seems ok, but I cannot mount it from NFS.
Here are some logs:
[root@blade6 stor1]# df -h
/dev/mapper/gluster_stor1 882G 200M 837G 1% /gluster/stor1
[root@blade7 stor1]# df -h
/dev/mapper/gluster_fast...
2013 Aug 02
2
Maildir Synchronization warnings
...readdir()s, 0 rename()s to cur/, why=0x1)
Aug? 2 12:52:55 blade8 dovecot: imap(kavish.karkera at example.com): Warning: Maildir /mail/v3store/example.com/kavish.karkera at example.com/Maildir: Synchronization took 94 seconds (0 new msgs, 0 flag change attempts, 0 expunge attempts)
Aug? 2 12:53:54 blade6 dovecot: imap(kavish.karkera at example.com): Warning: Maildir: Scanning /mail/v3store/example.com/kavish.karkera at example.com/Maildir/cur took 154 seconds (43129 readdir()s, 0 rename()s to cur/, why=0x1)
Aug? 2 12:53:54 blade6 dovecot: imap(kavish.karkera at example.com): Warning: Maildir: Scann...
2012 Aug 21
1
Error: Couldn't open INBOX: Timeout while waiting for lock
Hi ,
My users are frequetly getting the below error,
Aug 21 00:04:18 blade6 dovecot: pop3-login: proxy(hgl_dipak): Login failed to 192.168.1.43:110: [IN-USE] Couldn't open INBOX: Timeout while waiting for lock.
We are proxing pop connections from one pop server (dovecot version 1.1.20) i.e 192.168.1.39 to the other pop Server (Dovecot version 2.0.16 ) i.e 192.168.1.4....