similar to: beta9 (auth) killed with signal 11 - backtrace

I have just upgraded from courier to dovecot and things seem to be working okay (after a few problems getting shared folders working correctly). I notice the following error message in my logs:- Jun 23 11:17:32 calzone dovecot: child 1258 (auth) killed with signal 11 I am using the beta9 ebuild that is available from gentoo portage. I have followed the steps to try to get a core dump but it

Hi there, I've been seeing this for quite a while now, but only today finally got off my lazy you-know-what and did a backtrace. Here's the requested info as per http://dovecot.org/bugreport.html: * Dovecot version [root at airframe]:~# dovecot --version 1.0.3 * Operating system or Linux distribution name Slackware 10.2, both kernel 2.6.21.3 and dovecot self-compiled * CPU

Hello, after upgrade from beta8 to beta9 deliver process crashes with segfault. Deleting old maildirs does not help. Here is backtrace: Program received signal SIGSEGV, Segmentation fault. 0x0808e36d in mail_cache_field_get_decision (cache=0x8114da0, field_idx=128) at mail-cache-lookup.c:301 301 i_assert(field_idx < cache->fields_count); (gdb) bt #0 0x0808e36d in

http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta9.tar.gz http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta9.tar.gz.sig Some changes since beta8: - This release should work perfectly with NFS attribute cache enabled. - Fixes to handling what should be written to cache file and when - Some index handling optimizations - IMAP LIST: dbox and cydir can now return children state Beta9 will

In a 1.2 release of asterisk, I've had no problem connecting to a Broadvoice SIP peer, to allow routing outgoing calls from Asterisk to Broadvoice. Now, with the same SIP configuration, I cannot establish the peer. I've enclosed a SIP log in the hope that someone can help me analyze this failure. I'd guess the issue is NAT related and wondering if someone can spot a problem in the

Hallo, I am playing arround with dovecot I hat version 1.0.beta7 running fine. After installing beta9 there is a problem with default_mail_env setting. I have all users in ldap. there is an attribute "mailMessageStore" which contains a relative path to users maildir mailMessageStore: sca/ my mailer completes this relative pathinformation to /var/mail/sca/ therefor I setup

Hello All, Upgraded a test machine this morning from beta9 to rc1 and lost access to messages and folders. an strace on the imap process shows it accessing the home directory, but not the mail directory. The two queries that I use are: password_query = SELECT email,crypt as password FROM users WHERE email = '%u' user_query = SELECT homedir AS home, maildir AS mail, 1000 AS uid, 1000

I'm trying to get IMAPS working with dovecot-1.0.beta9. I'm building it on a Solaris 10 box, with openssl-0.9.8b installed. Here is the results of my ./configure: Install prefix ...................... : /usr/local/dovecot-1.0.beta9 File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method ..... : none Building with SSL

I've had this working for over a month now with no problems. Then I suffered a power outage today, and now dovecot/auth dies as soon as I start dovecot. I've spent the past three hours searching google, but can't find even a hint at what's wrong with my server. As far as I can tell, this is the only thing that has failed after bringing the server back up when power was restored.

Trying to track down a dovecot issue .... The error message is: dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11 (core not dumped - set service auth-worker { drop_priv_before_exec=yes }) The setup is dovecot 2.2.29.1 with passwd and mysql auth db's and a very basic config. both authentications work ... the symptom is that after a connection

Trying to track down a dovecot issue .... The error message is: dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11 (core not dumped - set service auth-worker { drop_priv_before_exec=yes }) The setup is dovecot 2.2.29.1 with passwd and mysql auth db's and a very basic config. both authentications work ... the symptom is that after a connection

Hello everyone! I've just switched from Asterisk 1.6.0-beta9 to 1.6.0.1 and my mISDN is not working. Here's what happens, if I try to call the line: bach >> P[ 1] --> !! lib: No free channel! P[ 1] --> we have already send Release_complete I haven't changed the configuration fles. Should I change something there? If you need more info, just tell me and I'll

Hi, I've been using Dovecot successfully for a while and I've recently encountered an issue : I got to work today and half the emails, were deleted... and after careful investigation : - On Monday it seems, the emails magically vanished .. (what I've been told) - My backup from Tuesday morning at 3am, indicates that all the files (mailbox) are intact but the subscription file is

Still Trying to track down a dovecot issue .... The error message is: dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11 (core not dumped - set service auth-worker { drop_priv_before_exec=yes }) The setup is dovecot 2.2.29.1 with passwd and mysql auth db's and a very basic config. both authentications work ... the symptom is that after a

Is is possible for you to try https://github.com/dovecot/core/commit/3c5101ffdd2a8115e03ed7180d53578765dea4c9.patch Aki > On 28 February 2019 18:03 Patrik via dovecot <dovecot at dovecot.org> wrote: > > > This bug report is similar to this issue: > https://www.dovecot.org/list/dovecot/2017-May/108116.html (https://www.dovecot.org/list/dovecot/2017-May/108116.html) >

The Asterisk.org development team has released Asterisk versions 1.4.20-rc3 and 1.6.0-beta9. These releases are intended to encourage community testing to improve the quality of the upcoming 1.4.20 and 1.6.0 releases. The testing process has proven extremely useful and we would like to thank everyone who has participated. Please help continue the effort. Any issues with test releases

The Asterisk.org development team has released Asterisk versions 1.4.20-rc3 and 1.6.0-beta9. These releases are intended to encourage community testing to improve the quality of the upcoming 1.4.20 and 1.6.0 releases. The testing process has proven extremely useful and we would like to thank everyone who has participated. Please help continue the effort. Any issues with test releases

Hi, Auth always crash (segfault) using vpopmail backend. Any idea ? vpopmail 5.5.0 os: ubuntu 10.04 on rackspace cloud # dovecot -n dovecot -n # 2.0.1: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.35.1-rscloud x86_64 Ubuntu 10.04.1 LTS auth_debug = yes auth_mechanisms = plain login cram-md5 auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no first_valid_uid =

Running rc24 and with one user in particular they are getting "(auth) killed with signal 11" when trying to pop email. IMAP works. What causes this? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://dovecot.org/pipermail/dovecot/attachments/20070224/195f61be/attachment-0002.html>

Found this today multiple times for the same user: Aug 16 16:59:38 postamt dovecot: IMAP(username): file strfuncs.c: line 165 (p_strndup): assertion failed: (max_chars != (size_t)-1) Aug 16 16:59:38 postamt dovecot: IMAP(username): Raw backtrace: imap [0x80c6d53] -> imap(i_fatal+0) [0x80c6795] -> imap(p_strndup+0x38) [0x80d8316] -> imap(t_strndup+0x22) [0x80d86d7] ->