Displaying 20 results from an estimated 3000 matches similar to: "stalling on LOGIN"
2007 Mar 20
5
Stalled imaptest10 process
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
in order to stress my Dovecot test installation a bit, I compiled
imaptest10.c.
Now and then I see:
Logi List Stat Sele Fetc Fet2 Copy Stor Dele Expu Appe Logo
100% 50% 50% 100% 100% 100% 33% 50% 100% 100% 100% 100%
30% 5% 5%
0 0 0 0 0 0 0 0 0 0 0 0 1/
2015 Jan 14
1
Questions regarding imaptest
Hi,
The measurements were created under the following conditions :
? operating system : Red Hat Enterprise Linux Server release 6.6 (Santiago)
kernel in version 2.6.32-504.el6.x86_64
? virtual server (VMware) with an Intel(R) Xeon(R) 4vCPU E5649 x 2,526 GHz
(2 cores per virtual socket) and 4 GB RAM
? 7,200 RPM SATA 1TB (FC SAN IBM System Storage N3400)
? all file systems had been formated in
2019 Sep 17
2
Imaptest stall
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
2019 Sep 17
3
Imaptest stall
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
2007 Mar 28
2
imaptest10 and stalled messages
Greetings -
I've now got as far as playing with the imaptest10 test utility to
see if I can stress-test our development server. imaptest10 is built
against dovecot-1.0rc28
It may just be that I'm excessively heavy handed, but when I let
imaptest10 rip with the command...
./imaptest10 user=test%03d host=testserver.imap.york.ac.uk clients=50
mbox=./dovecot.mbox msgs=1000 secs=30
2007 Nov 30
3
Zimbra benchmarking
Now that I have a working kvm setup, I thought I'd finally try how
Zimbra works. This is mainly some microbenchmarking, so it may not have
much to do with actual performance in real life.
Setup:
- 1GB memory given to kvm (from host's 2GB)
- Intel Core 2 6600 (kvm uses only one CPU)
- CentOS 5
- 15GB qcow2 image on XFS filesystem
- Zimbra 5.0 RC2 RHEL5 x86_64
- Dovecot latest hg,
2019 Jan 11
3
degfault imaptest
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 2019] imaptest[7635]: segfault at 2267ff0 ip
0000000002267ff0 sp 00007ffee5890308 error 15
[Fri Jan 11 15:10:47 2019] imaptest[7648]: segfault at 10e6ff0 ip
00000000010e6ff0 sp 00007ffedbb19f98
2019 Jan 12
1
degfault imaptest
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
2007 May 12
3
dbmail benchmarking
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
2011 Mar 25
1
imaptest assertion failure
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:
2014 Jun 26
1
Imaptest script testing
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
2008 Feb 19
3
compiling error imaptest.c
dovecot-1.1.beta16]# gcc imaptest.c -o imaptest -g -Wall -W -I.
-Isrc/lib-mail -Isrc/lib -Isrc/lib-imap -Isrc/lib-storage/index/mbox
-DHAVE_CONFIG_H src/lib-storage/index/mbox/mbox-from.o
src/lib-imap/libimap.a src/lib-mail/libmail.a src/lib/liblib.a
imaptest.c: In client_append function:
imaptest.c:1492: error: too many arguments for i_stream_create_limit
function
2019 Mar 31
1
CentOS Repository broken ?
Hello,
I download and install it manual, this working now?
waiting for next update to found out, yum is working correct again ;-)
Thanks for answers,
Am Sonntag, 31. M?rz 2019, 13:59:17 CEST schrieb Kostya Vasilyev via dovecot:
> On Sun, Mar 31, 2019, at 2:30 PM, G?nther J. Niederwimmer via dovecot wrote:
> > Hello,
> >
> > Am Samstag, 30. M?rz 2019, 21:36:12 CEST schrieb
2012 Mar 16
2
imaptest: performance testing
Dear Folks,
Using head of imaptest with dovecot 2.1, I am attempting to put a
heavy load on the server, with insufficient success.
I made 15000 user accounts, put them in to a file, one per line. Then
I ran imaptest with
./imaptest userfile=../../imap-test-userlist-15001.txt clients=15001
pass=SECRETPASSWORD
But CPU load is only reaching 20.
I put an mbox containing 67 messages into
2006 Apr 28
1
imaptest, with options!
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
2018 Jul 04
2
Benchmarks with imaptest
Hey guys,
Has anybody ever used imaptest to benchmark *ONLY* reads? I'm trying to run
a battery of tests in my new cluster and apparently no combination of
parameters works, because fetch instruction doesn't run. Below is the
command I'm using and its partial output
imaptest/src/imaptest host=$SERVER_IP port=143 user=teste%d at example%d.com
pass=$TEST_PASS users=10 domains=10
2019 Feb 22
2
new Centos server install yum dependancy error
> Am 22.02.2019 um 14:43 schrieb Voytek Eymont via dovecot <dovecot at dovecot.org>:
>
>
>
> On Sat, February 23, 2019 12:31 am, Gerald Galster via dovecot wrote:
>> Hello Voytek,
>>
>>
>> the *-devel packages include header files that are only needed if you
>> want to compile something, they are not needed for running a dovecot
>>
2010 Apr 07
2
ImapTest build problem
Hello.
My system is:
Debian Lenny 2.6.26-2-amd64
I try to build Imaptest and follow
http://www.imapwiki.org/ImapTest/Installation
But get this:
./configure --with-dovecot=../dovecot-2.0.beta4 && make
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking
2017 May 23
2
[imaptest] Explaining errors
Hi,
I'm an Apache James committer and we are curious to use imaptest in
order to validate our IMAP protocol implementation.
I'm using the nightlybuild : imaptest-20170506
I follow the examples given in the /T/ /est IMAP server compliancy/
examples https://imapwiki.org/ImapTest/Examples.
And I wanted to analyse the errors reported, here are some:
Error: user1 at james.org[11]: seq too
2019 Mar 29
5
CentOS Repository broken ?
Hello,
I have a CentOS 7 server with dovecot Repository enabled.
But it is not possible to Update with Yum Update
I have this Error?
The dovecot package is missing?
--> Transaktionspr?fung wird ausgef?hrt
---> Paket dovecot-imaptest.x86_64 2:2.3.5-1 markiert, um aktualisiert zu
werden
---> Paket dovecot-imaptest.x86_64 2:2.3.5.1-1 markiert, um eine
Aktualisierung zu werden
-->