UPP (Operation not supported)
263563 write(201401333]>, "* BYE Logging out\r\n? OK Logout
c"..., 43) = -1 EPIPE (Broken pipe)
263563 --- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=263563,
si_uid=994} ---
263563 epoll_ctl(14, EPOLL_CTL_DEL,
201401333]>, 0x7ffcd4f4f2e0)
Hello,
I have a new director ring I am setting up on centos 7 with dovecot
2.3.1. I haven't been able to replecate this in testing, but as soon as
I start pushing production traffic to the new ring I see dozens of these in the
logs:
Apr 18 00:34:00 d.director.imapd.sonic.net kernel: imap-login[16
p = 0x0, canceltype = 982799555}}}
not_first_call =
#21 0x5615cfbe850a in _start ()
No symbol table info available.
(gdb)
Quoting Aki Tuomi (2018-04-23 23:55:24)
>
>
> On 24.04.2018 00:40, Grant Keller wrote:
> > Hello,
> >
> > I have a new director ring I a
max_userip_connections = 20
mail_plugins = zlib mwi_update mail_log notify imap_zlib
}
protocol pop3 {
mail_plugins = zlib lazy_expunge
pop3_fast_size_lookups = yes
pop3_uidl_format = %f
}
Grant Keller
System Operations
grant.kel...@sonic.com
.
Quoting Grant Keller (2021-09-30 19:04:02)
> Hello,
>
> As stated in the subject we have been doing a pretty big version
> upgrade. Both new and old are on CentOS 7. For the second time, one of
> our upgraded servers have had the dovecot log process start consuming
> 100% cpu, an
): Disconnected: Connection closed (fd=11)
I don't see anything like a doveadm-postlogin service in the
documentation, so how would I go about making this work.
Grant Keller
System Operations
grant.kel...@sonic.com
We recently updated dovecot from 2.1.17 to 2.3.10. It used to be when we
encountered the following error:
Jan 6 15:29:20 d.imapd.sonic.net dovecot: imap(momomo):
session=aBd2O/LULMu4F6ia Error: Mailbox INBOX: UID=1:
read(/var/spool/mail/07/00/momomo/cur/1510707300.12345_0.a.spam,S=1234:2,)
fail
Hello,
Currently working on using the old-stats plugin in dovecot version
2.3.10.1. What file permissions are recommended for the old-stats-mail
and old-stats-user sockets? I was seeing a lack of data from the doveadm
oldstats dump command until I adjusted the default config to the
following:
ser
Recently we have been seeing a steady increase (nothing too crazy, just
more than usual) in "Deleting corrupted cache record" log errors. What
struck me as weird was that it would be for the same message over and
over, indicating that the deleted record was making it back into the
cache. Digging in
