similar to: How to detect out-of-sync condition

Thanks. I use dovecot's lda and dovecot's sieve filter. So it looks like I need to compare the index/mailbox mtimes as you suggest. What am I looking for? I see that the indexes are updated when I run the resync. I checked my mailbox (that was not resynced) and noticed that dovecot.index last update was 16 days ago. So am I resyncing if the gap is over x days? If so, is there a way to

Cliff Hayes <chayes at afo.net> writes: > I recently had a user whose mailbox had gone out of sync. > Webmail and client inbox totals had become vastly different and response > times had become unacceptable. > A doveadm force-resync fixed the problem nicely. > > This will no doubt happen again as we grow the service and I would like > to have some type of indication

What's the set of valid characters that can occur in an LLVM symbol name? The reason I ask is that my compiler is generating symbols based on method names. Some methods are operators, and I haven't got around to mangling the names yet. As a result it's producing symbols that look like _f_+ and _f_:=. LLVM seems to be coping fine with these so far and the IR output is quoting them,

Hello list, I recently had a user whose mailbox had gone out of sync. Webmail and client inbox totals had become vastly different and response times had become unacceptable. A doveadm force-resync fixed the problem nicely. This will no doubt happen again as we grow the service and I would like to have some type of indication at the server level so I can run a resync on a per-user basis as

Hi, im having this on my screen and dmesg im not sure if this is an error message. btw im using centos 4.4 with 2 x 200GB PATA drives. md: md0: sync done. RAID1 conf printout: --- wd:2 rd:2 disk 0, wo:0, o:1, dev:hda2 disk 1, wo:0, o:1, dev:hdc2 md: delaying resync of md5 until md3 has finished resync (they share one or more physical units) md: syncing RAID array md5 md: minimum _guaranteed_

Several companies have been interested in getting replication support for Dovecot. It looks like I could begin implementing it in a few months after some other changes. So here's how I'm planning on doing it: What needs to be replicated: - Saving new mails (IMAP, deliver) - Copying existing mails - Expunges - Flag and keyword changes - Mailbox creations, deletions and renames -

On Sep 11, 2010, at 11:03 AM, David Given wrote: > What's the set of valid characters that can occur in an LLVM symbol name? > > The reason I ask is that my compiler is generating symbols based on > method names. Some methods are operators, and I haven't got around to > mangling the names yet. As a result it's producing symbols that look > like _f_+ and _f_:=. >

On 02/23/11 02:46, Chris Lattner wrote: [...] > Remember that this isn't intended to be something users deal with, it's just an internal implementation detail of the compiler, debugger, nm implementation, etc. Can I put in a plea to have as much of LLVM as possible *not* require knowledge of a single, specific architecture to work? I have various things I would like to do that work on

I just added a new namespace-alias with alias_for. Apparently this causes all mailbox indexes to be resynced? Is this intentional and/or is there some way to avoid this? My NFS storage pretty much kills its elf when hundreds of thausands of users needs to resync indexes :) Thanks -- Tom

Hallo Simon, > Anyway, the splitting of large disks has additional advantages. Think of > what happens in case of a failure (power loss, kernel crash...). With the > disk as one large chunk, the whole disk has to be resynced on restart > while with smaller segments only those which are marked as dirty have to > be resynced. This can make a bit difference. I am not sure if this is

> Hallo Simon, > >> Anyway, the splitting of large disks has additional advantages. Think of >> what happens in case of a failure (power loss, kernel crash...). With >> the >> disk as one large chunk, the whole disk has to be resynced on restart >> while with smaller segments only those which are marked as dirty have to >> be resynced. This can make a bit

> On 01/11/2023 02:09 AM, Simon Matter wrote: >> What I usually do is this: "cut" the large disk into several pieces of >> equal size and create individual RAID1 arrays. Then add them as LVM PVs >> to >> one large VG. The advantage is that with one error on one disk, you wont >> lose redundancy on the whole RAID mirror but only on a partial segment.

I was using G729 with Asterisk 1.07. With the new ability to do packet loss correction with ILBC, I felt I'd give it a try. The new PLC does not work with G729. I don't use Speex because my softphone does not support it. This is a 1.5mb IP-VPN connection with prioritized QOS for port 4569 (IAX2). I've never really stressed the bandwidth. Typically, only 10-20 concurrent calls.

We have several CENTOS 4 and 5 servers. ALL CENTOS servers have NTP setup to sync time server. Several days ago due to power outage all servers are reboot. Due to DNS server did NOT up quickly, CENTOS servers start up and can NOT find time server. For CENTOS 5.X servers, it did quickly resync to time server after 30 minutes. For CENTOS 4.X servers, it have been 3 days still NOT sync to time

I have configured 2x 500G sata HDD as Software RAID1 with three partitions md0,md1 and md2 with md2 as 400+ gigs Now it is almost 36 hours the status is cat /proc/mdstat Personalities : [raid1] md0 : active raid1 hdb1[1] hda1[0] 104320 blocks [2/2] [UU] resync=DELAYED md1 : active raid1 hdb2[1] hda2[0] 4096448 blocks [2/2] [UU] resync=DELAYED md2 : active raid1

Hello, After some fiddling with the server now I have broken RAID1 with the "current" mirror on the disk with few unreadable sectors. If I try to re-add other disk to the mirror resync goes till those bad sectors and then starts from the beginning. And so on. Is it possible to somehow force resync to continue even after errors? Manual resync with dd would require a bit too long

Further investigations reveal: --- C:\WINDOWS\system32> w32tm /monitor GetDcList failed with error code: 0x800706BA. Exiting with error 0x800706BA --- error 0x800706BA indicates that the RPC server is unavailable. Any ideas? Thanks, Jonathan Kreider On Tue, Nov 6, 2018 at 5:48 PM Jonathan Kreider <jonathan.kreider at gmail.com> wrote: > > Thanks Robert & Marco. > >

Hello list, it seems that a sound file is not present on my system, although I have made a standard install... [Sep 22 12:28:51] WARNING[22117]: file.c:650 ast_openstream_full: File vm-INBOXs does not exist in any format [Sep 22 12:28:51] WARNING[22117]: file.c:953 ast_streamfile: Unable to open vm-INBOXs (format 0x8 (alaw)): No such file or directory I do not find this particular soundfile

Hello, Having a problem with software RAID that is driving me crazy. Here's the details: 1. CentOS 6.2 x86_64 install from the minimal iso (via pxeboot). 2. Reasonably good PC hardware (i.e. not budget, but not server grade either) with a pair of 1TB Western Digital SATA3 Drives. 3. Drives are plugged into the SATA3 ports on the mainboard (both drives and cables say they can do 6Gb/s). 4.

> I tried to look at a dovecot.index.log and it was unreadable in a text > editor. I didn't see anything in the wiki link about how to view the log. It's not supposed to be human readable -- the point of this exercise was to check whether your indices are really out of date. You can perhaps compare the mtime of the index files and the mailbox. If they're close or the same,