ports/65214: Courierlogger coredumps causes courier-imap to fail to respond

John O'Brien john at boardom.ca
Mon Apr 5 15:20:21 UTC 2004


>Number:         65214
>Category:       ports
>Synopsis:       Courierlogger coredumps causes courier-imap to fail to respond
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Apr 05 08:20:21 PDT 2004
>Closed-Date:
>Last-Modified:
>Originator:     John O'Brien
>Release:        4.9-STABLE
>Organization:
>Environment:
FreeBSD tweek.boardom.ca 4.9-STABLE FreeBSD 4.9-STABLE #0: Fri Apr  2 23:33:50 EST 2004     root@:/usr/obj/usr/src/sys/GENERIC  i386

>Description:
I have recently installed courier-imap from ports. I have noticed that it has been failing to respond somewhat frequently.. 
When it fails, this is the response from port 143.

tweek# telnet 127.0.0.1 143
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.

The only relevant logs are in dmesg,

pid 3344 (courierlogger), uid 0: exited on signal 10 (core dumped)

Version installed:
courier-imap-3.0.3,1 IMAP (and POP3) server that provides access to Maildir mail

The only way to fix is to restart the imapd service.
>How-To-Repeat:
Manually killing courierlogger will reproduce the same problem.
I am unsure what it is exactly that is causing courierlogger to have the sig10.
>Fix:
      
>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list