Bug 65214

Summary: Courierlogger coredumps causes courier-imap to fail to respond
Product: Ports & Packages Reporter: John O'Brien <john>
Component: Individual Port(s)Assignee: Oliver Lehmann <oliver>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description John O'Brien 2004-04-05 16:20:21 UTC 
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.
Comment 1 Mark Linimon freebsd_committer freebsd_triage 2004-04-05 17:53:41 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->oliver

Over to maintainer of mail/courier-imap.
Comment 2 Oliver Lehmann freebsd_committer freebsd_triage 2004-04-05 18:24:02 UTC 
Hi,

I can't reproduce it here with FreeBSD 5.2.1 on alpha and FreeBSD 4.9 on
i386.

i=0 ; while [ $i -lt 3000 ] ; do i=$(( $i + 1 )) ; (telnet 127.0.0.1 143
&) ; done

and still working...

How did you compile the port? (What options...)

-- 
 Oliver Lehmann
  http://www.pofo.de/
  http://wishlist.ans-netz.de/
Comment 3 Oliver Lehmann freebsd_committer freebsd_triage 2004-04-05 20:49:01 UTC 
John O'Brien wrote:

> Hey.. the build options are below:
> 
> portinstall courier-imap
> tweek# cat pkgtools.conf | grep courier
>         'mail/courier-imap' => 'WITH_VPOPMAIL=yes',
> ---------------------------------
> 
> I don't think that pounding on 127./143 is going to have the same
> effect.. It appears to go down when regular users are using it through
> either the external IP or squirrelmail accesseing it locally...
> There are imapd.core in some of the user's Maildir folders...
> Other than that? I can't really explain it.. I've had to go back to a
> 2.2.1 source build, as I was having to restart the service every 2
> minutes.
> 
> Anything I can do to help, let me know.

Hm... I'm still not able to reproduce it....


$ i=0 ; while [ $i -lt 100 ] ; do i=$(( $i + 1 )) ; ( perl test.pl & ) ;
done > lala
$ cat test.pl
#!/usr/bin/perl

use IO::Socket;

$Server   = "dill";
$Password = "test";
$Login    = "test\@salatschuessel.net";

sub action {
        $imap=$_[0];
        $action=$_[1];
        print $imap "x ".$action."\n";
        do {
                $responseLine = <$imap>;
                print "$responseLine";
        } until($responseLine =~/^x /);
}

$imap = new IO::Socket::INET( PeerAddr => $Server, PeerPort => 143 ) || 
        die "Cannot connect to $Server via IMAP\n";
$imap->autoflush(1);
$responseLine = <$imap>;
print $responseLine;

action($imap, "LOGIN $Login $Password");
action($imap, "SELECT INBOX");
action($imap, "LOGOUT");
$ grep connect lala
$ 

each connect succeeds On 4.9 (without VPOPMAIL support) and 5.2.1 (with
vpopmail support)

Can you debug the .core file with gdb?

-- 
 Oliver Lehmann
  http://www.pofo.de/
  http://wishlist.ans-netz.de/
Comment 4 Oliver Lehmann freebsd_committer freebsd_triage 2004-04-19 15:36:12 UTC 
State Changed
From-To: open->feedback

Some new informations about that issue? I'm still not able reproducing it here
Comment 5 Oliver Lehmann freebsd_committer freebsd_triage 2004-05-18 18:17:04 UTC 
State Changed
From-To: feedback->closed

Feedback-timeout