From owner-freebsd-isp@FreeBSD.ORG Wed Sep 17 08:44:42 2003 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97A8616A4B3 for ; Wed, 17 Sep 2003 08:44:42 -0700 (PDT) Received: from Shenton.org (23.ebbed1.client.atlantech.net [209.190.235.35]) by mx1.FreeBSD.org (Postfix) with SMTP id 09EB443FE1 for ; Wed, 17 Sep 2003 08:44:41 -0700 (PDT) (envelope-from chris@Shenton.Org) Received: (qmail 36304 invoked by uid 1001); 17 Sep 2003 15:46:05 -0000 To: vchkpw@inter7.com References: <86isnuj2gg.fsf@PECTOPAH.shenton.org> From: Chris Shenton Date: Wed, 17 Sep 2003 11:46:05 -0400 In-Reply-To: <86isnuj2gg.fsf@PECTOPAH.shenton.org> (Chris Shenton's message of "Sun, 14 Sep 2003 20:54:39 -0400") Message-ID: <86brtjo1tu.fsf@PECTOPAH.shenton.org> User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-isp@freebsd.org Subject: Re: [SOLVED] vpopmail POP: "ERR aac, chiled crashed" after reboot, core dumped X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2003 15:44:42 -0000 Chris Shenton writes: > The machine was recently rebooted and vpopmail's POP now crashes upon > successful authentication (names changed for privacy, sorry): > > chris@PECTOPAH<104> telnet foo.example.net pop3 > +OK <32620.1063584541@foo.example.net> > user chris@email.zz > +OK > pass MyPass > -ERR aack, child crashed I rebuilt the OS, rebuilt the kernel, rebuilt vpopmail (same version) -- to no affect. I was able to get it working again with a relatively minor fix. I'm documenting it here in case it helps anyone else. In /usr/local/vpopmail/etc/ there are files: open-smtp, open-smtp.lock, and tcp.smtp. I removed the lock file and renamed the other two to get them out of the way: -rw-r--r-- 1 root vchkpw 1874 Sep 17 08:11 open-smtp -rw-r--r-- 1 root vchkpw 302746 Sep 13 10:00 open-smtp.HIDE -rw-r--r-- 1 root vchkpw 0 Sep 17 07:55 open-smtp.lock -rw-r--r-- 1 vpopmail vchkpw 4015 Sep 17 08:11 tcp.smtp.cdb -rw-r--r-- 1 vpopmail vchkpw 2112 Sep 17 07:59 tcp.smtp.cdb.HIDE I was then able to POP in sucessfully. Is there some way I should have been able to detect this problem? Perhaps cranking up a debug flag and examining logs? I don't know the code enough to know which binaries use these, but it looks like they all use open-smtp. Any clues for future similar problems would be appreciated. If crash-related damage caused this, is it something that's worked-around in modern versions of vpopmail? Thanks.