similar to: Unrecognized event: kevent

Displaying 20 results from an estimated 700 matches similar to: "Unrecognized event: kevent"

2006 Aug 16
9
BSD people, please test kqueue changes
I rewrote much of the kqueue code since the old code didn't handle properly the case when both input and output I/O handlers were added to the same file descriptor with different callbacks. This is done commonly in Dovecot, so I'm wondering why more people didn't complain about problems with it.. :) I don't anyway have access to any BSDs so the code is completely untested. Please
2006 Mar 11
2
dovecot-1.0b3 kevent error/warning message
i use openbsd/i386, dovecot-1.0b3, i see some kevent error/warning message in maillog like this: -------------------------------------------------------- imap(username): kevent(1) in io_loop_handle_add() failed: Bad file descriptor imap(username): kevent(1) in io_loop_handle_remove failed: Bad file descriptor --------------------------------------------------------
2006 May 09
2
Fix for the kevent "Unrecognized event" problem.
The attached patch should fix the problem with dying imap on "Unrecognized event". The problem is that when we register a handle for IO_ERROR only, we still can get readable/writable event without EV_EOF being set. This case was not handled. -- Vaclav Haisman -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: io-kq.diff URL:
2006 Apr 14
2
dovecot error: unrecognized event
I'm setting up a new server with dovecot 1.0b7. Whenever I try to connect with a mua (thunderbird or outlook) I get this error in the log: kernel: pid 53279 (pop3), uid 15008: exited on signal 6 Apr 14 10:52:54 dovecot: POP3(williams): Unrecognized event: kevent {.ident = 2, .filter = 0xfffffffe, .flags = 0x0001, .fflags = 0x00000000, .data = 0x00004000} Apr 14 10:52:54 dovecot: child 53279
2018 Feb 13
1
dovecot: master: Panic: kevent() failed: Invalid argument
Hello I've been seeing these panics with dovecot 2.2.31 (and older versions) under FreeBSD about once every 2-3 months or so.? I know it's been discussed here in the list, but I didn't see a definitive fix.? If it's been fixed, please ignore this post (sorry!). I finally managed to observe the bug on a server that has the patch that prints out the kevent() timespec values and
2008 Aug 16
1
dovecot bug - kevent(EV_DELETE, 9)
Sorry for my english. FreeBSD 7.0-STABLE dovecot-1.1.2_1 (from ports with LDAP) AD LDAP ?? Win 2003 SP2 (work via GK) CPU 2xIntel XEON NFS not used LDAP part of dovecot.conf (if you need all file, l'll send it): auth default { mechanisms = plain login passdb ldap { args = /usr/local/etc/dovecot-ldap.conf } userdb ldap { args =
2011 May 04
2
Dovecot stops with "Fatal: kevent(): Invalid argument"
# 2.0.11: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.2-STABLE amd64 Dovecot stops with the following logged: - master: Fatal: kevent(): Invalid argument I have found that a diff was created for "src/lib/ioloop-kqueue.c" for a similar issue: http://dovecot.org/pipermail/dovecot/2010-November/054855.html I have patched my system with this and haven't seen the problem
2006 Apr 11
1
kevent error (cvs version april-11), can't to login
after upgrade to cvs version(april-11), i can't to login my dovecot imap server the maillog error like this: ---------------------------------------------------------- Unrecognized event: kevent {.ident = 2, .filter = 0xfffffffe, .flags = 0x 0001, .fflags = 0x00000000, .data = 0x00004000} ---------------------------------------------------------- april-5 cvs version work fine i use
2006 May 08
1
kevent error (1.0.b7) - Is this a FreeBSD-only problem?
Hello everyone, The problem below has been reported, but I did not see any response! <cut> | | I'm also seeing this bug while testing the forthcoming 1.0.b7 FreeBSD | | port under 6.1-PRERELEASE: | | | | Info: imap-login: Login: user=<wibble>, method=PLAIN, rip=10.0.0.2, | | lip=10.0.0.2, TLS | | dovecot: Error: IMAP(isometry): Unrecognized event: kevent {.ident = | |
2006 Jan 17
1
1.0 beta1 -- kevent() for notify failed: Invalid argument
after upgrade to 1.0 beta1 i see the warning/error message in mail log like this: kevent() for notify failed: invalid argument I/O leak: 0x1c05b6cc (5) is it normal?
2010 Nov 14
1
Dovecot occasionally stops with Fatal: kevent(): Invalid argument
Hi, FreeBSD/amd64 8-STABLE, Dovecot 2.0.6, stops in random times with: Nov 14 18:42:14 be dovecot: master: Fatal: kevent(): Invalid argument Any ideas? Thanks,
2003 Aug 19
1
kqueue freezing 5.1R on kevent call
Hi, The sample program given below freezes my 5.1R installation. This program is from a bug report - kern/54331. That bug report (http://lists.freebsd.org/pipermail/freebsd-bugs/2003-July/001608.html) is for the shutdown function call, whereas my machine basically just freezes up and reboots on kevent itself. I am also noticing this problem with another program i wrote (but too long to include
2017 Jun 09
2
Dovecot stops with "Fatal: kevent(): Invalid argument"
On 05/21/2011 17:54, Timo Sirainen wrote: > On 21.5.2011, at 2.51, Henrik Larsson wrote: > >> >>>> That patch doesn't fix anything. It only changes the error message to be more informative so I could figure out what is causing it. If you haven't seen any more errors, it's just a coincidence. >>> >>> I have for some reason not seen the error
2014 Feb 24
0
Dovecot stopped with "master: Fatal: kevent(): Invalid argument"
Hi, after more than 20 days uptime, Dovecot stopped with the following logged in /var/log/messages: - master: Fatal: kevent(): Invalid argument dovecot -n: # 2.2.10: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 9.2-RELEASE-p3 amd64 auth_default_realm = xxx.com.ua auth_mechanisms = plain login default_client_limit = 3000 dict { quotadict =
2008 Sep 26
4
Quota exceeded message
I just realized that "quota" word probably doesn't mean much to many non-native english speakers. Do even non-technical native speakers understand what "Quota exceeded" really means? It's sent by quota plugin, currently in two different situations: 1) To the user doing the operation via IMAP COPY/APPEND. 2) More importantly: If deliver rejects the mail, it's
2005 Dec 14
2
Patch: ioloop using kqueue/kevent for FreeBSD
Hi, I would like to submit the attached patch. It implements IO loop using FreeBSD's kqueue/kevent syscalls. It is based on snapshot of CVS HEAD as of 2005-12-12. I could only give it limited testing on FreeBSD 5.4 but it works fine so far. Vaclav Haisman -------------- next part -------------- diff -rN -u old-dovecot-cvs/autogen.sh new-dovecot-cvs/autogen.sh ---
2003 Oct 27
1
Difficulties with R.oo (static fields, etc.)
I would like to use R.oo and tcltk to implement a Turtle World. I have encountered many problems because: 1) I am not sure how to implement static fields with R.oo 2) I am not sure how to implement a constructor that would call a function only for the first instance of a class (i.e., to initialize value of static fields only once) 3) I am not sure how to remove/delete cleanly existing
2006 Mar 03
1
convert tool
Trying out the new convert tool, to migrate from mbox to maildir. Using this syntax ( both inbox and folders are in user's home dir, in mbox format ) ./convert-tool pinetest/export/home2/pinetest \ mbox:/export/home2/pinetest/:INBOX=/export/home2/pinetest/mbox \ maildir:/export/home2/pinetest/Maildir/ I get this error. "Error: Mailbox conversion: Couldn't create mailbox home/Trash
2006 Apr 17
1
INBOX as mbox, other mailboxes as maildir
All, I'm trying to teach dovecot to use the mbox format for /var/mail/%u and maildir for /home/%u/Mail/ but I'm having quite a hard time. This is Dovecot v1.0.beta3 under OpenBSD 3.9 on sparc64. I've been fiddling with default_mail_env and also tried separate namespaces, but all to no avail. Here's some of the things I tried : default_mail_env =
2003 Oct 14
1
"Turtle world" graphics in R
I would greatly appreciate some idea about the best approach to make a graphical interface of for a turtle world in R. In the turtle environment, the user controls movements of a turtle through the command line (e.g. forward(10), turn(5), etc.). The turtle should be displayed in the new position and heading after each command. Also, the turtle's path and, possibly, objects (squares,