similar to: dsync crash

Displaying 20 results from an estimated 100 matches similar to: "dsync crash"

2014 Jan 13
0
dsync error: gz trailer has wrong CRC value
A few days ago by dovecot installation started behaving weirdly. First it was doveadm fts optimize which would fail (a thread running about that) and now it's dsync, which means my backups are not working. This all started a few days ago, which I find a little weird, because I haven't messed around with the dovecot setup in months. I've been searching the internet, but didn't find
2011 Dec 10
2
2.1.rc1 (8a63f621bd2e): SiS permission issue + crash
Since changeset 8a63f621bd2e I'm one step closer to the perfect working setup. I'm sharing one GID per domain, all it's alias names and accounts. So I can use: mail_attachment_dir = /srv/mail/.SiS/%{gid} In order to avoid permission trouble I've set fs ACL on the .SiS dir: ,--[ getfacl srv/mail/.SiS ]-- | # file: srv/mail/.SiS | # owner: root | # group: root | user::rwx |
2011 Jan 17
0
dsync crash
Hello! I'm converting mailboxes from maildirs to mdbox and dsync crashes on two of them /var/mail-nfs-1 - nfs mount /var/mail-nfs-indexes - local fs /usr/bin/dsync -f -u user at site.ru mirror mdbox:/var/mail-nfs-1/mail/site.ru/user/mail:INDEX=/var/mail-nfs-indexes/site.ru/user dsync(user at site.ru): Panic: file istream-limit.c: line 79 (i_stream_limit_seek): assertion failed: (v_offset
2010 Oct 22
3
Problems converting to maildir with dsync in 2.0.6
I'm trying to convert from an old Dovecot (1.0.15) and mbox to a new Dovecot and maildir. I'm running into several problems with dsync which are causing my mboxes not to convert. If I use LAYOUT=fs (as I'd prefer) I get an error because I have a mailbox called "subscriptions", and none of my messages convert. Is there a way to get dovecot to put its own metadata in
2013 Jul 04
2
Migrating domain using IMAPc
Hi list, I'm trying to do a domain migration using the imapc feature, but i'm having some problems and I really don't know what is happening. So if you guys could help me with a path to solve this, I will be glad. I'm using Dovecot 2.1.7 in a Debian Wheezy machine. The command I'm using is: dsync -Dv -o imapc_features=rfc822.size -o imapc_host=IP -o imapc_port=143 -o
2012 Jun 24
3
Mail migration to dovecot with doveadm backup
Hi, i try to migrate mails from a non dovecot imap server to a dovecot imap server with doveadm backup as described there: http://wiki2.dovecot.org/Migration/Dsync i first tried (local-mailbox port 18143 is the non dovecot imap server): /usr/bin/doveadm -o imapc_user=user at example.org -o imapc_password=imappw -o imapc_host=local-mailbox -o imapc_features=rfc822.size -o imapc_port=18143 -o
2012 Jun 15
3
doveadm backup panic
using latest auto build didn't help. this happens only with a specific account. # doveadm -o imapc_user=----- at domain.com -o imapc_password=---- backup -u =----- at domain.com -R imapc: dsync(---- at domain.com): Panic: pool_data_stack_realloc(): stack frame changed dsync(---- at domain.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x4209a) [0xb762b09a] ->
2013 Feb 21
1
Crash in dsync [dovecot 2.1.7]
Just taught i'd report this crash while running the ofllowing command: 19748 Aborted (core dumped) $DSYNC_BINARY -f -u document backup mdbox:$LOCAL_BACKUP_PATH/emails/document >> $LOG_FILE 2>&1 Here is the traceback I got: dsync(document): Error: Mailbox INBOX/Julie: Corrupted index, uidvalidity=0 dsync(document): Warning: mdbox
2010 Jul 24
1
Dsync error when working dir o-rwx
Hi, I dont know why dsync requires o+rx in working dir, at least it could give better error message when working dir has o-rwx. # cd # mkdir test # cd test # dsync -D -v -u 'info at example.org' -o 'mail_privileged_group=mail' -o 'mail_location=mbox:/email/info at example.org/mail:INBOX=/var/mail/info at example.org' mirror 'maildir:~/Maildir' dsync(info at
2019 Jul 04
2
solr vs fts
Hi I have a question about tunning dovecot-2.2.36.x Mail was stared in storage via nfs in MAILDIR via /home/us/username at domain.ltd/MAILDIR/ I use additionally local dovecot_indexes via SSD disk (/var/dovecot_indexes%h) A few clients have 25K and more e-mail I thinking about use solr like: ?fts = solr ?fts_solr = debug url=http://IP:8983/solr/ (solr in external machine) Does it make sense ?
2019 Nov 20
0
Error: Raw backtrace and index cache
Firstly, 2.2.13 is about 5 years old. So there's that. It would be helpful if you can reproduce this with 2.2.36. Also, you forgot to actually include in your log snippet the panic. So maybe few more lines before the Raw backtrace? Aki On 20.11.2019 10.54, Maciej Milaszewski IQ PL via dovecot wrote: > Hi > I have "problem" with dovect 2.2.13 from repo debian8 and I don't
2003 Nov 28
1
Hi bitrate tests
Maybe anyone can give me some links about testing results of mp3Lame and Vorbis on hi bitrate (192 or >)? Cos i can find only ~128 =[[ -=-=-=-=-=-=-=-=-=-=-=- SaSHa SHokovic E-mail: sh0ck@delfi.lt IRC: SH0x @ QuakeNet ICQ: 67504461 .+-j!i0+:)rhZm1hNrybXuz/-*arj) '+a{ +v&{ay,rR{.n+z,z{m^+-)emw
2019 Nov 20
0
Error: Raw backtrace and index cache
This is likely fixed in more recent version, can you try with 2.2.36? Aki On 20.11.2019 11.20, Maciej Milaszewski IQ PL wrote: > Hi > Thanx for replay. > > Log: > > http://paste.debian.net/1117077/ > > > On 20.11.2019 10:07, Aki Tuomi wrote: >> Firstly, 2.2.13 is about 5 years old. So there's that. It would be >> helpful if you can reproduce this with
2017 Jun 05
2
corrupted indexes rebuilding over and over
Hi, On saturday one of our dovecot machines had an OOPS, and we had to powercycle it. When it came up, it did a filesystem fsck (ext4) and fixed a couple things, but nothing in lost+found. Now, about 50 users have a problem where their indexes are corrupted. Dovecot tries to fix them, but for some reason it is failing. The users are seeing their mails duplicated and they cannot delete mails. I
2019 Nov 20
2
Error: Raw backtrace and index cache
Hi I have "problem" with dovect 2.2.13 from repo debian8 and I don't know how to solve it ... Server is a virtual (kvm) with debian 8.11 (postfix + dovecot from repo) and storage is mounting via nfs (I have use only one dovecot with external storage) All works fine but sometime ( after a few hours ) I have got a problem with dovecot cache (i use indexes) logs ->
2017 Jun 05
0
corrupted indexes rebuilding over and over
Hi, we had the same problem after a system failure. Our problem could be solved by rm /PATH/USER/mdbox/storage/dovecot.map.index* doveadm -D -v force-resync -u USER INBOX Best regards, Gordon On 05.06.2017 18:34, micah wrote: > > Hi, > > On saturday one of our dovecot machines had an OOPS, and we had to > powercycle it. When it came up, it did a filesystem fsck (ext4) and >
2019 Jul 04
0
solr vs fts
On 4.7.2019 12.14, Maciej Milaszewski IQ PL via dovecot wrote: > Hi > I have a question about tunning dovecot-2.2.36.x > > Mail was stared in storage via nfs in MAILDIR via > /home/us/username at domain.ltd/MAILDIR/ > I use additionally local dovecot_indexes via SSD disk > (/var/dovecot_indexes%h) > > A few clients have 25K and more e-mail > > I thinking about use
2010 Apr 03
1
dovecot 2 beta4 errors & core dumps
Hi, While running imaptest with "clients=50 seed=123 msgs=100000000 random secs=600", I got errors : "Error: user at domain.com[55]: Unexpected BYE: * BYE IMAP session state is inconsistent, please relogin.". dovecot.log : Apr 03 10:23:47 imap(user at domain.com): Panic: file index- transaction.c: line 145 (index_transaction_rollback): assertion failed:
2019 Nov 20
2
Error: Raw backtrace and index cache
Hi Thanx for replay. Log: http://paste.debian.net/1117077/ On 20.11.2019 10:07, Aki Tuomi wrote: > Firstly, 2.2.13 is about 5 years old. So there's that. It would be > helpful if you can reproduce this with 2.2.36. > > Also, you forgot to actually include in your log snippet the panic. So > maybe few more lines before the Raw backtrace? > > Aki > > On 20.11.2019
2013 Jul 17
1
pop3c migration?
Hi, I'm running dsync migrations using imapc and the source IMAP server is just too slow. It has taken 8 hours to migrate a mailbox with 47,000 messages. It seems most of the mailboxes are never accessed with IMAP, so it would be just as good to migrate them via POP3 which should work faster in my case. Is this actually meant to work? doveadm -D -o pop3c_user=xxxxxx at example.com -o