similar to: epoll_ctl: Operation not permitted

Working on setting up dovecot and having trouble logging in. I get an error in logs (below) indicating Operation not Permitted. auth_debug doesn't help. Ideas? # dovecot --version 1.1.7 # dovecot -n # 1.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.29-gentoo-r5 i686 Gentoo Base System release 1.12.11.1 listen: *,[::] ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file:

Hello, I'am following the beginning tutorial on the Wiki, but actually, I can't even start the server correctly so far. The imap-login child dies immediately. What I can guess from the log is that it tries some unpermietted operations on some files but I can't find out which files are concerned. Google is not my friend at all either on this matter. How can I know which files are

Hi, I'm not exactly sure that this is caused by wine. But maybe someone have already met this. I have wine 20050628 setup on Mandriva Linux 10.2. I am seeing the stream of epoll_ctl: Operation not permitted in the .xsession-errors It take about a day to fill a 10G partition I think it is connected with audio card, so I switched off the audio system in wine (I don't need it anyway),

Hi Timo, I'm playing with Dovecot v1.2.beta2 currently. When the dict process was started via deliver(?) and Dovecot is killed (kill $PID_OF_DOVECOT) after delivering only one message, it logs: Fatal: io_loop_handle_add: epoll_ctl(1, 10): Bad file descriptor If the dict process was not started or deliver has delivered more than one message, the error doesn't occur. I'm not using

Whenever dovecot is stopped while a dict process is running I see Fatal: io_loop_handle_add: epoll_ctl(1, 11): Bad file descriptor in the error log. The following patch fixes this for me. I'm sure there is a better way though. --- dovecot-1.2.beta4/src/master/dict-process.c.orig 2009-03-27 16:44:59.000000000 +0100 +++ dovecot-1.2.beta4/src/master/dict-process.c 2009-03-27

Hello, More problems (it seems that we won't be able to put our new servers in production). The problem now is that when we reach 1000 dovecot processes we have errors like: Jul 9 12:10:22 myotis31 dovecot: imap-login: Panic: epoll_ctl(add, 6) failed: Invalid argument Jul 9 12:10:22 myotis31 dovecot: imap-login: Fatal: master: service(imap-login): child 32251 killed with signal 6

I have been running Dovecot 1.2.5 since Sept 14. Beginning at about 03:28 on Sept 21 for no apparent (to me) reason and continuing through the present, I am seeing log messages like the following and am experiencing delays logging in. Sep 22 19:07:15 sbh16 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 See the end of the message for a possible delete of a closed fd from epoll() problem. Every now and then I get a Panic after a successfull LMTP delivery: 2014-11-12 13:25:31 lmtp(20890): Info: Connect from local 2014-11-12 13:25:32 lmtp(20890): Info: Disconnect from local: Connection closed (in reset) 2014-11-12 13:25:34 lmtp(20890): Info: Connect

Hi Manfred, I applied the patch and recompiled and reinstalled and I got the folowing warning during my first test call: Aug 19 12:26:51 WARNING[294927]: dsp.c:1234 __ast_dsp_silence: zero length packet It looks like that could be the problem... and the fix! I'll let you know if the problem reoccurs. Might it be an idea to submit the patch to the bugtracker? Thanks, Gary ----- Original

In data venerd? 7 settembre 2018 10:06:00 CEST, Sami Ketola ha scritto: > > On 7 Sep 2018, at 11.00, Simone Lazzaris <s.lazzaris at interactive.eu> > > wrote: > > > > > > The only suspect thing is this: > > > > Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host > > 192.168.1.142 > > vhost count changed from 100 to 0 >

I'm currently trying out 1.2.beta1 and get the following error in 'mail.err' log file as soon as I stop dovecot: Feb 11 20:28:30 server dovecot: Fatal: io_loop_handle_add: epoll_ctl(1, 11): Bad file descriptor Is that anything critical? Thanks, e-frog -------------------------------------------------------------------------------- >: dovecot -n # 1.2.beta1:

I?m trying backup a user?s IMAP folders from a system running dovecot 2.1.7. to a system running dovecot 2.3.19.1. After much perusing of the web and Dovecot documentation I tried this: 1) On the 2.1.7 host set up the doveadm server to listen on TCP port 2425 and defined a doveadm_password value 2) Issued the following command on the 2.13.19.1 system: doveadm -o

On 7.3.2019 23.37, A. Schulze via dovecot wrote: > > Am 07.03.19 um 17:33 schrieb Aki Tuomi via dovecot: > >>> test-http-client-errors.c:2989: Assert failed: FALSE >>> connection timed out ................................................. : FAILED > Hello Aki, > >> Are you running with valgrind or on really slow system? > I'm not aware my buildsystem

Some more information: the issue has just occurred, again on an instance without the "service_count = 0" configuration directive on pop3-login. I've observed that while the issue is occurring, the director process goes 100% CPU. I've straced the process. It is seemingly looping: ... ... epoll_ctl(13, EPOLL_CTL_ADD, 78, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP, {u32=149035320,

I occasionally get a fatal error unable to delete epoll event: Bad file descriptor I think the attached patch will fix it. The patch does two things: 1) changes the error we look for from ENOENT to EBADF. It is hard to reproduce this error, but if I change the epoll_ctl line to epoll_ctl(epfd, EPOLL_CTL_DEL, 666, ed->GetEpollEvent()); it does return -1 with errno = EBADF on my Linux 2.6.9

Hello, Currently working on migrating our existing directors from 2.1.13 to 2.2.10. In 2.2.10 when issuing the logout command on an unauthenticated connection, the connection is closed before the server sends the BYE line to the client. The new version works as expected with a non-secure connection. I will include the strace output from the imap-login process that shows the connection closing

Every few days I find that dovecot auth is using all my CPU. This is from dovecot 2.2.13, I've just upgraded to 2.2.18 strace -r -p 17956 output: Process 17956 attached 0.000000 lseek(19, 0, SEEK_CUR) = -1 ESPIPE (Illegal seek) 0.000057 getsockname(19, {sa_family=AF_LOCAL, NULL}, [2]) = 0 0.000043 epoll_ctl(15, EPOLL_CTL_ADD, 19, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP,

Occasionally, all of our directors get stuck in an endless loop. Likely triggered by some network event, but I haven't been able to isolate exactly what triggers it, and am unable to reproduce at the moment. When this happens, it makes the dovecot/director process on all directors unresponsive, making login impossible. Restarting dovecot "fixes" it. Here's the info collected

On 7 Sep 2018, at 19.43, Timo Sirainen <tss at iki.fi> wrote: > > On 7 Sep 2018, at 16.50, Simone Lazzaris <s.lazzaris at interactive.eu <mailto:s.lazzaris at interactive.eu>> wrote: >> >> Some more information: the issue has just occurred, again on an instance without the "service_count = 0" configuration directive on pop3-login. >> >>

Hi, I got this simple test Sieve config: ############################################# # Sieve Filter # Generated by Ingo (http://www.horde.org/apps/ingo/) (11/01/2019, 10:46:06 PM) # Forwards if true { redirect "krustev at krustev.net"; } # Forward Keep Action if true { keep; stop; } ############################################# Which used to work fine with: # 2.2.27