Re: Error: Raw backtrace and index cache
Hi
I have change now to dovecot-2.2.36.4 and problem seems not to occur
On 20.11.2019 13:48, Aki Tuomi via dovecot wrote:
> 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 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 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 -> http://paste.debian.net/1117072/
>>>>
>>>>
>>>> The store is mounted via nfs in /home/
>>>> index is local in /var/dovecot_indexes%h
>>>>
>>>> All go back to normal when i remove indexes like:
>>>> find /var/dovecot_indexes/home/ -name 'dovecot*' -type f -delete
>>>> but this is not good solution
>>>>
>>>> What am I doing wrong ?
>>>>
>>>>
>>>> For tunning nfs in 10-mail.conf:
>>>>
>>>> -
>>>> "mail_location = maildir:~/Maildir:INDEX=/var/dovecot_indexes%h
>>>>
>>>> namespace inbox {
>>>> inbox = yes
>>>> }
>>>>
>>>> mmap_disable = yes
>>>> dotlock_use_excl = no
>>>> mail_fsync = always
>>>>
>>>> mail_nfs_storage = no
>>>> mail_nfs_index = no
>>>>
>>>> lock_method = fcntl
>>>> mail_temp_dir = /tmp
>>>> mail_plugins = quota expire notify mail_log
>>>>
>>>> mailbox_idle_check_interval = 30 secs
>>>> mail_temp_scan_interval = 1w
>>>> maildir_very_dirty_syncs = no
>>>>
>>>> -
>>>>
>>>> doveconf -n
>>>>
>>>> # 2.2.13: /etc/dovecot/dovecot.conf
>>>> # OS: Linux 3.16.0-9-amd64 x86_64 Debian 8.11
>>>> auth_mechanisms = plain login
>>>> disable_plaintext_auth = no
>>>> dotlock_use_excl = no
>>>> lda_original_recipient_header = X-Original-To
>>>> log_path = /var/log/dovecot/dovecot.mail133
>>>> mail_fsync = always
>>>> mail_location = maildir:~/Maildir:INDEX=/var/dovecot_indexes%h
>>>> mail_plugins = quota expire notify mail_log
>>>> managesieve_notify_capability = mailto
>>>> managesieve_sieve_capability = fileinto reject envelope
>>>> encoded-character vacation subaddress comparator-i;ascii-numeric
>>>> relational regex imap4flags copy include variables body enotify
>>>> environment mailbox date index ihave duplicate mime foreverypart
>>>> extracttext
>>>> mmap_disable = yes
>>>> namespace inbox {
>>>> inbox = yes
>>>> location =
>>>> mailbox Drafts {
>>>> special_use = \Drafts
>>>> }
>>>> mailbox Junk {
>>>> special_use = \Junk
>>>> }
>>>> mailbox Sent {
>>>> special_use = \Sent
>>>> }
>>>> mailbox "Sent Messages" {
>>>> special_use = \Sent
>>>> }
>>>> mailbox Trash {
>>>> special_use = \Trash
>>>> }
>>>> prefix =
>>>> }
>>>> passdb {
>>>> driver = pam
>>>> }
>>>> passdb {
>>>> args = /etc/dovecot/dovecot-sql.conf
>>>> driver = sql
>>>> }
>>>> plugin {
>>>> mail_log_events = delete undelete expunge copy mailbox_delete
>>>> mailbox_rename
>>>> mail_log_fields = uid box msgid size
>>>> sieve = ~/dovecot.sieve
>>>> sieve_default = /var/lib/dove
Re: 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 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 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 -> http://paste.debian.net/1117072/
>>
>>
>> The store is mounted via nfs in /home/
>> index is local in /var/dovecot_indexes%h
>>
>> All go back to normal when i remove indexes like:
>> find /var/dovecot_indexes/home/ -name 'dovecot*' -type f -delete
>> but this is not good solution
>>
>> What am I doing wrong ?
>>
>>
>> For tunning nfs in 10-mail.conf:
>>
>> -
>> "mail_location = maildir:~/Maildir:INDEX=/var/dovecot_indexes%h
>>
>> namespace inbox {
>> inbox = yes
>> }
>>
>> mmap_disable = yes
>> dotlock_use_excl = no
>> mail_fsync = always
>>
>> mail_nfs_storage = no
>> mail_nfs_index = no
>>
>> lock_method = fcntl
>> mail_temp_dir = /tmp
>> mail_plugins = quota expire notify mail_log
>>
>> mailbox_idle_check_interval = 30 secs
>> mail_temp_scan_interval = 1w
>> maildir_very_dirty_syncs = no
>>
>> -
>>
>> doveconf -n
>>
>> # 2.2.13: /etc/dovecot/dovecot.conf
>> # OS: Linux 3.16.0-9-amd64 x86_64 Debian 8.11
>> auth_mechanisms = plain login
>> disable_plaintext_auth = no
>> dotlock_use_excl = no
>> lda_original_recipient_header = X-Original-To
>> log_path = /var/log/dovecot/dovecot.mail133
>> mail_fsync = always
>> mail_location = maildir:~/Maildir:INDEX=/var/dovecot_indexes%h
>> mail_plugins = quota expire notify mail_log
>> managesieve_notify_capability = mailto
>> managesieve_sieve_capability = fileinto reject envelope
>> encoded-character vacation subaddress comparator-i;ascii-numeric
>> relational regex imap4flags copy include variables body enotify
>> environment mailbox date index ihave duplicate mime foreverypart extracttext
>> mmap_disable = yes
>> namespace inbox {
>> inbox = yes
>> location =
>> mailbox Drafts {
>> special_use = \Drafts
>> }
>> mailbox Junk {
>> special_use = \Junk
>> }
>> mailbox Sent {
>> special_use = \Sent
>> }
>> mailbox "Sent Messages" {
>> special_use = \Sent
>> }
>> mailbox Trash {
>> special_use = \Trash
>> }
>> prefix =
>> }
>> passdb {
>> driver = pam
>> }
>> passdb {
>> args = /etc/dovecot/dovecot-sql.conf
>> driver = sql
>> }
>> plugin {
>> mail_log_events = delete undelete expunge copy mailbox_delete
>> mailbox_rename
>> mail_log_fields = uid box msgid size
>> sieve = ~/dovecot.sieve
>> sieve_default = /var/lib/dovecot/sieve/default.sieve
>> sieve_dir = %h/sieve
>> sieve_global_dir = /var/lib/dovecot/sieve/
>> }
>> protocols = " imap lmtp sieve pop3"
>> service auth {
>> unix_listener auth-master {
>> group = users
>> mode = 0666
>> user = virtual
>> }
>> unix_listener auth-userdb {
>> group = users
>> user = virtual
>> }
>> }
>> service lmtp {
>> inet_listener lmtp {
>> port = 24
>> }
>> unix_listener /var/spool/postfix/private/dovecot-lmtp {
>> group = postfix
>> mode = 0600
>> user = postfix
>> }
>> user = virtual
>> }
>> service managesieve-login {
>> inet_listener sieve {
>> address = 127.0.0.1 94.124.15.58
>> port = 4190
>> }
>> }
>> ssl_ca = /etc/postfix/ssl/mail.maximail.pl.pem
>> ssl_cert = > ssl_key = > ssl_protocols = !SSLv2 !SSLv3
>> userdb {
>> driver = passwd
>> }
>> userdb {
>> args = /etc/dovecot/dovecot-sql.conf
>> driver = sql
>> }
>> protocol lmtp {
>> info_log_path = /var/log/dovecot/dovecot.mali133
>> lmtp_save_to_detail_mailbox = yes
>> mail_plugins = quota sieve notify push_notification
>> }
>> protocol lda {
>> auth_socket_path = /var/run/dovecot/auth-master
>> lda_mailbox_autocreate = yes
>> log_path = /var/log/dovecot/dovecot-lda.mail133
>> mail_plugins = sieve
>> postmaster_address = root
>> }
>>
--
Maciej Miłaszewski
Starszy Administrator Systemowy
IQ PL Sp. z o.o.
Biuro Obsługi Klienta:
e-mail: b...@iq.pl
tel.: +48 58 326 09 90 - 94
fax: +48 58 326 09 99
Dział pomocy: https://www.iq.pl/pomoc
Informacja dotycząca przetwarzania danych osobowych: https://www.iq.pl/kontakt
IQ PL Sp. z o.o. z siedzibą w Gdańsku (80-298), ul. Geodetów 16, KRS
007725, Sąd rejestrowy: Sąd Rejonowy w Gdańsku VII Wydział KRS, kapitał
zakładowy: 140.000 PLN, NIP 5832736211, REGON 192478853
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 -> http://paste.debian.net/1117072/
The store is mounted via nfs in /home/
index is local in /var/dovecot_indexes%h
All go back to normal when i remove indexes like:
find /var/dovecot_indexes/home/ -name 'dovecot*' -type f -delete
but this is not good solution
What am I doing wrong ?
For tunning nfs in 10-mail.conf:
-
"mail_location = maildir:~/Maildir:INDEX=/var/dovecot_indexes%h
namespace inbox {
inbox = yes
}
mmap_disable = yes
dotlock_use_excl = no
mail_fsync = always
mail_nfs_storage = no
mail_nfs_index = no
lock_method = fcntl
mail_temp_dir = /tmp
mail_plugins = quota expire notify mail_log
mailbox_idle_check_interval = 30 secs
mail_temp_scan_interval = 1w
maildir_very_dirty_syncs = no
-
doveconf -n
# 2.2.13: /etc/dovecot/dovecot.conf
# OS: Linux 3.16.0-9-amd64 x86_64 Debian 8.11
auth_mechanisms = plain login
disable_plaintext_auth = no
dotlock_use_excl = no
lda_original_recipient_header = X-Original-To
log_path = /var/log/dovecot/dovecot.mail133
mail_fsync = always
mail_location = maildir:~/Maildir:INDEX=/var/dovecot_indexes%h
mail_plugins = quota expire notify mail_log
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date index ihave duplicate mime foreverypart extracttext
mmap_disable = yes
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
}
passdb {
driver = pam
}
passdb {
args = /etc/dovecot/dovecot-sql.conf
driver = sql
}
plugin {
mail_log_events = delete undelete expunge copy mailbox_delete
mailbox_rename
mail_log_fields = uid box msgid size
sieve = ~/dovecot.sieve
sieve_default = /var/lib/dovecot/sieve/default.sieve
sieve_dir = %h/sieve
sieve_global_dir = /var/lib/dovecot/sieve/
}
protocols = " imap lmtp sieve pop3"
service auth {
unix_listener auth-master {
group = users
mode = 0666
user = virtual
}
unix_listener auth-userdb {
group = users
user = virtual
}
}
service lmtp {
inet_listener lmtp {
port = 24
}
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
}
user = virtual
}
service managesieve-login {
inet_listener sieve {
address = 127.0.0.1 94.124.15.58
port = 4190
}
}
ssl_ca = /etc/postfix/ssl/mail.maximail.pl.pem
ssl_cert =
dovecot and ldap
Hi Sorry for my question... I use dovecot+ldap How realy works (in dovecot-2.2.x ) lists of LDAP hosts to use ? -- dovecot.conf hosts = ldap.domain.pl:389 ldap-slave.domain.pl:389 #uris = This is simpe HA ? I mean if ldap.domain.pl have problem another request go to ldap-slave.domain.pl ?
Re: Recent Dovecot on old operating system
Hi For test in my smal testing lab i downlod latest dovecot-2.2.36.4 and debian 7.x ./configure --prefix=/usr/local/dovecot-2.2.36.4 --sysconfdir=/etc --with-mysql --with-ssl=openssl --with-solr --with-storages=maildir,imapc and make working ok debian 7: dovecot-director debian 8: dovecot node and tested like debian 8: dovecot-director debian 7: dovecot node All works fine On 19.09.2019 12:28, Gerald via dovecot wrote: > Hi, > > sorry for the dumb question and please ignore this post if you think it's far > beyond; i know it's not the way to go, but for reasons ... > > Has anyone running a self compiled recent dovecot (2.2.36.4) on Debian-7 and > does it work? > Or thinks it should work. > > Surprisingly it actually compiles flawlessly on Debian-7, but i wonder wether > it will become a complete mess replacingthe existing dovecot (2.1.7) with the > new one, serving a few dozens users and any kind of mail clients. > > Libraries of the compiled Dovecot: > $ ldd ./src/master/.libs/dovecotlinux-vdso.so.1 => > (0x7ffeacfb1000) > libdovecot.so.0 => > /usr/local/00-DBAI/dovecot/lib/dovecot/libdovecot.so.0 (0x7f557b2a9000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f557af1c000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f557ad18000) > librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7f557ab1) > /lib64/ld-linux-x86-64.so.2 (0x7f557b5dc000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x7f557a8f4000) > > libc6 versions:Debian-7: 2.13-38Debian-9: 2.24-11 > > thanks so far, gerald > > > > >
Multiple certificate option SNI
Hi
I have some problem with SNI and dovecot 2.2.36.4
Server debian 9.x ad dovecot-2.2.36.4
default server ssl cert is a wildcard like *.domain.com (digicert)
ssl_ca = /var/control/cert.pem
ssl_cert = https://wiki.dovecot.org/SSL/DovecotConfiguration
like:
local_name imap.mail.test.domain.com {
ssl_cert =
Re: Multiple certificate option
Hi
This is for all dovecot version ?
On 10.09.2019 08:05, Greg Wildman via dovecot wrote:
> On Fri, 2019-09-06 at 17:25 -0700, remo--- via dovecot wrote:
>> What is the best way to adopt multiple certs?
> I have a setup that creates letsencrypt certs for each customer domain.
> To automate this I have the following at the end of conf.d/10-ssl.conf
>
> !include ssl.d/*.conf
>
> This includes any .conf file under conf.d/ssl.d
>
> Now it is a simple matter to add and remove certificates for each
> domain as the letsencrypt job runs. Each config file looks like this
>
> $cat ssl.d/somedomain_co_za.conf
> local_name imap.somedomain.co.za {
> ssl_cert =ssl_key = }
>
>
> YMMV.
>
--
Maciej Miłaszewski
Starszy Administrator Systemowy
IQ PL Sp. z o.o.
Biuro Obsługi Klienta:
e-mail: b...@iq.pl
tel.: +48 58 326 09 90 - 94
fax: +48 58 326 09 99
Dział pomocy: https://www.iq.pl/pomoc
Informacja dotycząca przetwarzania danych osobowych: https://www.iq.pl/kontakt
IQ PL Sp. z o.o. z siedzibą w Gdańsku (80-298), ul. Geodetów 16, KRS
007725, Sąd rejestrowy: Sąd Rejonowy w Gdańsku VII Wydział KRS, kapitał
zakładowy: 140.000 PLN, NIP 5832736211, REGON 192478853
signature.asc
Description: OpenPGP digital signature
solr
Hi I have set up SOLR in accordance with documentation and it runs well. I use solr like: ... fts = solr fts_solr = debug url=http://IP:8983/solr/ (solr in external machine) .. Is replication of this system really essential ?? Due to my tests, rollback of the solr server on external machine lasts less than minute and it is nearly non-visible from client side. On the other hand solr replication is quite complicated process and rollback or master-slave switch in this case is non-trivial task, that may have result in whole dataset inconsistency. Do you have any experience in such cases ? Maby load-balance in HAProxy colud do the thing ? Something like: . server search1 192.168.1.1:8983 check port 8983 inter 20s fastinter 2 server search2 192.168.1.2:8983 backup . Best Regards
Re: solr vs fts
>> 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 ? use dovecot_indexes and fts ? >> What is the difference in performance? >> > Hi! > > Dovecot indexes are not actually related to FTS that much. Using FTS > usually makes sense since it speeds up IMAP fulltext searches. > > Aki > Hi So you're advised to use a solr or something else?
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/usern...@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 ? use dovecot_indexes and fts ? What is the difference in performance?
Re: director in rings
48:06 2019] [] ? kmem_getpages+0x5b/0x110 [śro mar 6 08:48:06 2019] [] ? fallback_alloc+0x1cf/0x210 [śro mar 6 08:48:06 2019] [] ? tg3_alloc_rx_data+0x6d/0x260 [tg3] [śro mar 6 08:48:06 2019] [] ? __kmalloc+0x227/0x4e0 [śro mar 6 08:48:06 2019] [] ? tg3_alloc_rx_data+0x6d/0x260 [tg3] [śro mar 6 08:48:06 2019] [] ? tg3_alloc_rx_data+0x6d/0x260 [tg3] [śro mar 6 08:48:06 2019] [] ? tg3_poll_work+0x471/0xeb0 [tg3] [śro mar 6 08:48:06 2019] [] ? tg3_poll_msix+0x35/0x140 [tg3] [śro mar 6 08:48:06 2019] [] ? net_rx_action+0x129/0x250 [śro mar 6 08:48:06 2019] [] ? __do_softirq+0xf1/0x2d0 [śro mar 6 08:48:06 2019] [] ? irq_exit+0x95/0xa0 [śro mar 6 08:48:06 2019] [] ? do_IRQ+0x52/0xe0 [śro mar 6 08:48:06 2019] [] ? common_interrupt+0x81/0x81 [śro mar 6 08:48:06 2019] Mem-Info: [śro mar 6 08:48:06 2019] Node 0 DMA per-cpu: [śro mar 6 08:48:06 2019] CPU 0: hi: 0, btch: 1 usd: 0 [śro mar 6 08:48:06 2019] CPU 1: hi: 0, btch: 1 usd: 0 [śro mar 6 08:48:06 2019] CPU 2: hi: 0, btch: 1 usd: 0 [śro mar 6 08:48:06 2019] CPU 3: hi: 0, btch: 1 usd: 0 śro mar 6 08:48:06 2019] imap-login: page allocation failure: order:2, mode:0x204020 [śro mar 6 08:48:06 2019] CPU: 38 PID: 5656 Comm: imap-login Not tainted 3.16.0-5-amd64 #1 Debian 3.16.51-3+deb8u1 [śro mar 6 08:48:06 2019] Hardware name: Dell Inc. PowerEdge R620/01W23F, BIOS 2.6.1 02/12/2018 [śro mar 6 08:48:06 2019] 8151f937 00204020 88082fc63b98 [śro mar 6 08:48:06 2019] 81148d8f 818ea8b0 88080002 [śro mar 6 08:48:06 2019] 00012fffbe00 88082fffcc00 0046 0001 [śro mar 6 08:48:06 2019] Call Trace: [śro mar 6 08:48:06 2019] [] ? dump_stack+0x5d/0x78 [śro mar 6 08:48:06 2019] [] ? warn_alloc_failed+0xdf/0x130 [śro mar 6 08:48:06 2019] [] ? __alloc_pages_nodemask+0x8ef/0xb50 [śro mar 6 08:48:06 2019] [] ? kmem_getpages+0x5b/0x110 [śro mar 6 08:48:06 2019] [] ? fallback_alloc+0x1cf/0x210 [śro mar 6 08:48:06 2019] [] ? tg3_alloc_rx_data+0x6d/0x260 [tg3] [śro mar 6 08:48:06 2019] [] ? __kmalloc+0x227/0x4e0 [śro mar 6 08:48:06 2019] [] ? tg3_alloc_rx_data+0x6d/0x260 [tg3] [śro mar 6 08:48:06 2019] [] ? tg3_alloc_rx_data+0x6d/0x260 [tg3] [śro mar 6 08:48:06 2019] [] ? tg3_poll_work+0x471/0xeb0 [tg3] [śro mar 6 08:48:06 2019] [] ? tg3_poll_msix+0x35/0x140 [tg3] [śro mar 6 08:48:06 2019] [] ? net_rx_action+0x129/0x250 [śro mar 6 08:48:06 2019] [] ? run_rebalance_domains+0x3f/0x190 [śro mar 6 08:48:06 2019] [] ? __do_softirq+0xf1/0x2d0 [śro mar 6 08:48:06 2019] [] ? do_softirq_own_stack+0x1c/0x30 [śro mar 6 08:48:06 2019] [] ? do_softirq+0x4d/0x60 [śro mar 6 08:48:06 2019] [] ? __local_bh_enable_ip+0x84/0x90 [śro mar 6 08:48:06 2019] [] ? tcp_recvmsg+0x4c/0xc40 [śro mar 6 08:48:06 2019] [] ? set_next_entity+0x56/0x70 [śro mar 6 08:48:06 2019] [] ? pick_next_task_fair+0x6e1/0x820 [śro mar 6 08:48:06 2019] [] ? __switch_to+0x15c/0x5a0 [śro mar 6 08:48:06 2019] [] ? inet_recvmsg+0x6a/0x80 [śro mar 6 08:48:06 2019] [] ? sock_aio_read.part.7+0xfe/0x120 [śro mar 6 08:48:06 2019] [] ? do_sync_read+0x5c/0x90 [śro mar 6 08:48:06 2019] [] ? vfs_read+0x135/0x170 [śro mar 6 08:48:06 2019] [] ? SyS_read+0x42/0xa0 [śro mar 6 08:48:06 2019] [] ? system_call_fast_compare_end+0x10/0x15 now I changed memory and tunning min_free_kbytes in kernel My question is about soultions keeplive+haproxy 1)director1-ringdirector2 2)director3 - standalone as backup Options 1 and 2 have connect to 5 backend dovecot On 07.03.2019 08:43, Aki Tuomi via dovecot wrote: > On 6.3.2019 14.26, Maciej Milaszewski IQ PL via dovecot wrote: >> Hi >> Maby stupid question :) >> >> It possible to have 3 directors (frontend) >> but without rings ? >> >> All directors connect to this same dovecot (backend) - all backad have >> this same login_trusted_networks >> >> > Why would you even use a director then? > > Aki > -- Maciej Miłaszewski IQ PL Sp. z o.o. Starszy Administrator Systemowy Biuro Obsługi Klienta: e-mail: b...@iq.pl tel.: +48 58 326 09 90 - 94 fax: +48 58 326 09 99 Dział pomocy: https://www.iq.pl/pomoc Informacja dotycząca przetwarzania danych osobowych: https://www.iq.pl/kontakt Jakość gwarantuje: ISO 9001:2000 IQ PL Sp. z o.o. z siedzibą w Gdańsku (80-298), ul. Geodetów 16, KRS 007725, Sąd rejestrowy: Sąd Rejonowy w Gdańsku VII Wydział KRS, kapitał zakładowy: 140.000 PLN, NIP 5832736211, REGON 192478853
director in rings
Hi Maby stupid question :) It possible to have 3 directors (frontend) but without rings ? All directors connect to this same dovecot (backend) - all backad have this same login_trusted_networks -- Maciej Miłaszewski IQ PL Sp. z o.o. Starszy Administrator Systemowy
problem witht working director
Hi I have dovecot director with 2-3 ring and 4 dovecot My ring is : 10.0.100.2 9090 right never synced 8 37305225 39763861 0 723 2019-02-13 16:02:04 2019-02-13 16:02:04 10.0.100.3 9090 left never synced 8 57409664 8707830 0 737 2019-02-13 16:02:04 2019-02-13 16:02:04 10.0.100.4 9090 self never ring synced 1 - - - - - - 10.0.100.4 - This is my default server where clients connect - default direcor 2.2.36 10.0.100.3 - second direcot 2.2.36 10.0.100.2 - second director with older ver 2.2.18 Today I found the error in my default mailserver Feb 13 13:21:23 kernel: [24253349.641695] qmail-remote: page allocation failure: order:2, mode:0x204020 and problem with logging via imap and pop3 I try "doveadm director status" i get time out I try restart dovecot and get: Feb 13 13:21:03 thebe3 dovecot: master: Fatal: Dovecot is already running? Socket already exists: /var/run/dovecot/login/director before failure i found: "imap-login: Error: write(proxy-notify) failed: Resource temporarily unavailable" but my setting they seem correct https://paste.debian.net/1067596/ I moved IP (via keepalive) all to other director (secound servcer) And when I try "doveadm director status" i get time out https://paste.debian.net/1067601/ I do not understand why I had a problem with second server and restart dovecot in server2 restart solved the problem ?
alterstorage for archiv
Hi I have a testing lab with: debian10 + dovecot-2.2.33 (director) and one backaned with 2.2.33.2 mail_location = maildir:~/Maildir:INDEX=/var/dovecot_indexes%h All works fine but I thinking now about solutions to moved all messeges older by (14day) to my alter storage with poor disk to folder Archive like:/vmail/domain/user@domain/Maildir/ to: /otherstorage/vmail/domain/user@domain/ And i thinking about ( hmm mapping folder Archive) /vmail/domain/user@domain/Maildir/Archive/ mail_location = maildir:~/Maildir:INDEX=/var/dovecot_indexes%h:ALT:/otherstorage%h is that "solutions" Is good idea ? Or maby is another working solutions ? because: doveadm altmove not working with Maildir
