similar to: Imaptest stalls when removing msgs argument

FWIIW I had this message still in drafts /usr/bin/imaptest - append=100,0 logout=0 host=xxx port=143 user=xxx pass=xxx seed=100 secs=1 clients=1 mbox=64kb.mbox box=inbox/test msgs=100000 And inbox/test does not exist, results in: Fatal: master: service(imap): child 20282 killed with signal 11 (core dumped)

I have been testing with imaptest and getting 'stalls', I tried even building from source and static. Even running it on the same host. Anyone knows what I could doing wrong? [@~]# ./imaptest - append=100,0 logout=0 host=192.168.10.44 port=143 user=test2 pass=xxxxxxxx seed=100 secs=240 clients=1 mbox=64kb.mbox box=INBOX/test Logi Sele Appe 100% 100% 100% 1 1 5 1/ 1 0

Yes dovecot is showing the inserted messages until the stall. Looks like it is an issue with imap test because I am able to empty the mailbox again via thunderbird. I am comparing write tests to different backends. -----Original Message----- From: Daniel Miller [mailto:dmiller at amfes.com] Sent: dinsdag 17 september 2019 22:06 To: Marc Roos; dovecot Subject: Re: Imaptest stall On 9/17/2019

If you're just speed testing for writing probably sdbox or maildir would be the fastest. Daniel On 9/17/2019 1:09 PM, Marc Roos via dovecot wrote: > > Yes dovecot is showing the inserted messages until the stall. Looks like > it is an issue with imap test because I am able to empty the mailbox > again via thunderbird. I am comparing write tests to different backends. > >

On 9/17/2019 12:58 AM, Marc Roos via dovecot wrote: > > I have been testing with imaptest and getting 'stalls', I tried even > building from source and static. Even running it on the same host. > Anyone knows what I could doing wrong? > > [@~]# ./imaptest - append=100,0 logout=0 host=192.168.10.44 port=143 > user=test2 pass=xxxxxxxx seed=100 secs=240 clients=1

http://hg.dovecot.org/dovecot-dbox-redesign/ Looks like multi-dbox scales pretty nicely. Even after 100k messages the peak saved msgs/sec is the same as the initial saved msgs/sec, even if the average slows down somewhat. I tested this by first deleting mailbox, then running "imaptest" for a second to get saving to start writing several fields to dovecot.index.cache file. Then ran

I just changed Dovecot v1.1 code to work much more nicely when appending new messages to large mailboxes. Dovecot hg (cydir format, fsync_disable=yes): ./imaptest secs=1 ./imaptest - append=100,0 logout=0 msgs=10000000 clients=1 seed=1 secs=300 Logi Sele Appe 100% 100% 100% 1 1 2322 1/ 1 0 0 1998 1/ 1 0 0 2293 1/ 1 0 0 2009 1/ 1 0 0 1789 1/ 1 0

Hi I'am doing some tests with nginx proxy -> dovecot using imaptest: imaptest user=user host=host pass=pass msgs=50 clients=100 Logi List Stat Sele Fetc Fet2 Stor Dele Expu Appe Logo 100% 50% 50% 100% 100% 100% 50% 100% 100% 100% 100% 30% 5% 41 19 10 36 24 39 9 13 11 8 12 100/100 10 12 11 17 24 31 3

I get lots of these (in error log): dovecot: Apr 28 14:50:03 Error: IMAP(jenslt): Corrupted index cache file /home0/jenslt/.imap/INBOX/dovecot.index.cache: record points outside file And some of these: dovecot: Apr 28 14:50:03 Error: IMAP(jenslt): Corrupted index cache file /home0/jenslt/.imap/INBOX/dovecot.index.cache: field index too large (2037149797 >= 19) Should I worry or not?

I thought I'd try benchmarking with dbmail (v2.2.4) to see how much slower a SQL backend could actually be. Skip to bottom for the conclusions. Originally I ran the tests with the databases being in XFS filesystem. MySQL's performance was horrible. It went 3-7x faster with ext3. MySQL 5.0.30 backend (innodb): ./imaptest clients=1 - append=100 seed=1 secs=30 msgs=1000000 logout=0

I am also testing rbox plugin ;) So I would like just the imaptest tool to work. No one else ever run into this? I saw something similar on the mailing list a long time ago. -----Original Message----- From: Daniel Miller via dovecot [mailto:dovecot at dovecot.org] To: dovecot at dovecot.org Subject: Re: Imaptest stall If you're just speed testing for writing probably sdbox or maildir

I cleaned up the lib-storage code a bit so that it's easier to write support for new mailbox formats. It could still use a bit of cleaning up. Anyway, I thought I'd try how easy it would be to implement Cyrus-like mail store which would consist of only Dovecot's index files and "<uid>." message files. Flags and everything else is kept only in Dovecot's index files

I hacked some command line options into imaptest. I dont think I broke it.. Place into dovecot-source root as usual and compile with: gcc imaptest.c -o imaptest -Wall -W -I. -Isrc/lib -DHAVE_CONFIG_H src/lib/liblib.a As per Timo's instructions. # imaptest -h imaptest [USER at IP:PORTNO] [pass=PASSWORD] [mbox=MBOX] [clients=CC] [msgs=NMSG] [use_authenticate] [PORTNO] USER = template for

Please, unsubscribe me. I really don't want to read this. 12.01.2019 22:47, Stephan Bosch ?????: > > Op 11/01/2019 om 15:13 schreef Marc Roos: >> imaptest host=mail04.local port=143 user=xxx pass=xxx mbox=test.mbox >> >> [Fri Jan 11 15:09:14 2019] imaptest[7634]: segfault at 1354ff0 ip >> 0000000001354ff0 sp 00007ffed5d8f558 error 15 >> [Fri Jan 11 15:09:22

> On 18 Sep 2019, at 0.29, Marc Roos via dovecot <dovecot at dovecot.org> wrote: > > I am also testing rbox plugin ;) So I would like just the imaptest tool > to work. No one else ever run into this? I saw something similar on the > mailing list a long time ago. Yes I saw this in my rbox testing long time ago. I thought that rbox was just not mature enough back then. But

Hi All, We're on migration stage to a new 2-node active/active cluster with shared iSCSI storage,? everything is ready, but we are in the process of I/O testing, before we going to in production. Cluster info: 2 nodes with CentOS 7.4 balancer ( keepalived + ldirectord ), 2 dovecot directors, 2 dovecot IMAP backends, 2 Postfix SMTP, gfs2 ( corosync + dlm ), LMTP between Postfix and Dovecot

While trying to use imaptest (-20100922, from http://dovecot.org/nightly/imaptest/imaptest-latest.tar.gz) with the included tests directory, it assert-crashes after a suspicious connect() failure: $ ./imaptest user=foo pass=bar host=localhost test=tests Error: connect() failed: No route to host Panic: file test-exec.c: line 903 (test_send_lstate_commands): assertion failed:

* Found my error. I moved the dovecot source code after compiling it. Didn?t realize there were embedded/absolute URLS within the dovecot source tree. All I needed to do was make clean && make dovecot, then imaptest compiled no problem. [Brad Hein] From: <Hein>, Local Administrator <Brad_Hein at cable.comcast.com<mailto:Brad_Hein at cable.comcast.com>> Date:

I spent the last 5 hours or so updating my imaptest tool. It's beginning to become almost like a real IMAP client. http://dovecot.org/tools/imaptest10.c contains a version that compiles against Dovecot v1.0 (instead of against CVS HEAD). imaptest is this tool that I've been using for a few years to do stress testing. It can create a lot of dummy IMAP client connections which execute some

http://www.imapwiki.org/ImapTest/ <http://www.imapwiki.org/ImapTest/> I am doing imap testing using imaptest scripts. But, i am unable to append message. APPEND INBOX "15-Jun-2015 05:30:05 -0700" "From:abc at gmail.com" "Subject: test. HI this is msg". This command i am using in my testing script. Command executed properly. But, it is not appending mail