similar to: IMAP crashes with signal 10 (SIGBUS)

Hi, I'm still running into consistent crashing when moving files between folders when dirsize quotas are enabled. This is running Dovecot1.0rc19. Please let me know if I'm posting this to the wrong list. Here is the gdb backtrace: #0 0x377fc in mbox_file_seek (mbox=0xc8560, view=0xc94c0, seq=1, deleted_r=0xffbef157) at mbox-file.c:167 167 if (data == NULL) { (gdb) bt

We've had another random imap process crash. This is with the original 1.2.5 imap (I haven't applied the patch for two processes creating an index simultaneously): > Oct 03 13:24:56 imap-login: Info: Login: user=<xxxxxxxx>, method=PLAIN, rip=134.225.1.46, lip=134.225.16.6 > Oct 03 13:25:59 IMAP 6067 xxxxxxxx 134.225.1.46 : Info: delete: uid=483, msgid=<xxxxxxxx> > Oct

http://dovecot.org/test/ Fixes: - Crashes in non-x86 64bit systems - Bugs in cache file header caching (you probably should delete all dovecot.index.cache files to be sure the bug won't haunt you in future) - FETCH ENVELOPE patch by Chris Wakelin (I'll try to figure out what to do with the list patch later) Known bugs left: - Thunderbird + maildir: moving lots of messages from

This is from the June 16 CVS, it also happens with June 15 but not with June 8. Basically, imap segfaults when opening my mbox. Some details are below: Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x08094e5c in message_parse_header_next (ctx=0x80c8e10, hdr_r=0xbffff64c) at message-parser.c:755 755 if (msg[0] ==

Hi, Installed Dovecot 1.1.3 today and started receiving panic errors on a few of our users: dovecot: [ID 107833 mail.crit] Panic: IMAP(xx): file mail-index-transaction-view.c: line 204: unreached When I upgraded, I deleted all of our users index files so it started with a clean slate. We are running mbox format over NFS with fsquota plugin on Solaris 8. Here is output of dovecot -n:

I have some archived mails in compressed (by bzip2) mboxes and I would like to read them via imap Unfortunately it looks like dovecot crashes when tries to read them :( #v+ kjonca at alfa:~/Mail/Old/Junk%sudo /usr/sbin/dovecot -n [sudo] password for kjonca: # 1.2.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32.7+2 i686 Debian squeeze/sid log_path: /var/log/dovecot

Hi, I'm experiencing the following problem when runnig dovecot-1.0-test set up to authenticate users against openldap, while the corresponding setup with dovecot-0.99.11 works fine : . my platform : FreeBSD 5.3-RELEASE-p1 . dovecot version : dovecot-1.0-test57 . openldap version : openldap-2.1.27 - Description : When I talk IMAP to the dovecot server, I can connect on port 143 and

Hi, Here is the backtrace. -- Nico Que de tout inconnu le sage se m?fie. -+- Jean de La Fontaine (1621-1695), Le Renard, le Loup et le Cheval (Fables XII.17) -+- -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: Dovecot-1.0-test57-backtrace URL:

http://dovecot.org/test/ Two important fixes: - Fixes the recently reported dovecot-auth crashes with unexpected client input - Fixes mbox corruption in some not-so-common cases. Hopefully this is the last one. I added more asserts anyway which try to catch similiar mistakes and avoid losing data. Others: - Added oe-ns-eoh workaround for pop3. Fixes outlook/netscape problems with buggy

We upgraded from 1.0-beta7 to 1.0-rc17 on Tuesday evening and looking at today's logs, just four imap processes out of 90,000+ died. I managed to get core files (the server is running Solaris 8 on Sparc, and Dovecot was compiled with gcc 3.3.2). I hope they're useful! (I should also say that performance between the two versions is roughly similar according to Solaris' process

I just tried upgrading one of our mail cluster servers to test60 from test57. We have dovecot connecting to 3 different MySQL tables in 3 sql conf files. The error seems to stem from this: Jan 13 14:57:59 svr21 dovecot: auth(sql8): file auth-client-connection.c: line 31 (auth_client_send): assertion failed: (conn->refcount > 1) After this the auth process gets killed with signal 6.

http://bugs.freedesktop.org/show_bug.cgi?id=11492 riccardo at datahost.it changed: What |Removed |Added ---------------------------------------------------------------------------- QAContact|eric at anholt.net |swfdec at lists.freedesktop.org Status|NEEDINFO |NEW AssignedTo|eric at anholt.net

Does FreeBSD have fallocate(2) or equivalent? On Mon, Oct 30, 2017 at 4:32 PM, Ed Maste <emaste at freebsd.org> wrote: > On 23 October 2017 at 18:49, Rui Ueyama via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > >> > >> BTW, posix_fallocate() might provide better portability and decrease the > >> likelihood of falling back on ftruncate(). > >

One of my servers has recently started giving an error every time I run "aide --check". I ran it manually twice today with the same results. The second time, I added the -V flag, but that didn't give me anything useful. The system is currently running CentOS 5.3. Nothing on the system has changed recently (that I am aware of). The Aide database hasn't been updated in a few

Hi there, I run tinc with not ConnectTo, (and it can't tcp-connect to the relevant other tincd, because that tincd is behind a firewall --> that tincd usualy connects to my tincd). If I start that tincd alone (not connected at all) and do a ping some_other_ip, it gets a SIGBUS in route.c:207 in the function route_ipv4_unreachable at the line: hdr->ip_v = 4; This seems to be an

-------- Original Message -------- Subject: smbstatus getting a SIGBUS error Date: Thu, 08 Jun 2000 13:52:13 +0700 From: Arnold Troeger <stssart@bkk.unocal.com> To: samba-bugs@samba.org CC: arnold.troeger@bkk.unocal.com I'm running Samba 2.0.7 and have been having a few problems with it. Just to keep things focused, I'll stick with smbstatus as this one has been the longest lasting

But that would disable mmap IO on systems that don't support fallocate. I'm not sure if OpenBSD people are for example happy about that. On Mon, Oct 30, 2017 at 2:03 PM, Rafael Avila de Espindola < rafael.espindola at gmail.com> wrote: > Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> writes: > > > If your system does not support fallocate(2), we use

Somemore information regarding the smbstatus error. The sigbus error is occuring where I noted below. I now have data values to go along with the location. The SIGBUS generating bit is "entry_scanner_p->e.pid" which looks to be in an unaccessable area of memory. Looking back through the code, I find a couple of bizarities. For example file_scanner_p->num_share_mode_entries

Hi Folks, I'm trying to run samba on Solaris 9. It works OK when I don't compile in kerberos and ldap, but when with those two compiled in, smbd seems to freeze (nmbd and winbindd are OK). After a bit of investigation I notice something strange in truss: ... /1@1: -> libldap-2.3:ldap_free_urldesc(0x30dfe8, 0x32e048, 0x32dfb8, 0x3 /1@1: ->

On Mon, Oct 23, 2017 at 3:40 PM, Brian Cain <brian.cain at gmail.com> wrote: > > > On Mon, Oct 23, 2017 at 5:21 PM, Rui Ueyama via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> If your system does not support fallocate(2), we use ftruncate(2) to >> create an output file. fallocate(2) succeeds even if your disk have less >> space than the