From owner-freebsd-stable Fri Jan 23 07:45:14 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12449 for stable-outgoing; Fri, 23 Jan 1998 07:45:14 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from mail.kersur.net (root@mail.kersur.net [199.79.199.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12430 for ; Fri, 23 Jan 1998 07:45:01 -0800 (PST) (envelope-from dswartz@druber.com) Received: from manticore (manticore.druber.com [207.180.95.108]) by mail.kersur.net (8.8.8/8.8.8) with SMTP id KAA19996 for ; Fri, 23 Jan 1998 10:44:50 -0500 (EST) Message-Id: <3.0.2.32.19980123104447.00e635b0@mail.kersur.net> X-Sender: druber@mail.kersur.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.2 (32) Date: Fri, 23 Jan 1998 10:44:47 -0500 To: freebsd-stable@freebsd.org From: Dan Swartzendruber Subject: process hanging? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have been running INN 1.7.2 (the prepatched version inn-1.7.2.insync-1.1d). It had been running fine. The kernel is 2.2.5, running on a PII-300 with two adaptec UW controllers, using ccd0 for the news spool (multiple UW disks). The problem I am seeing is that for the last couple of days, the nightly expiration run is not completing. When I log in to the server and do 'ps axl', I see the primary expire process in state 'D', with wchan 'getblk'. This is during the building of the expire.rm file (the list of files to expire). It is not totally hung, since this file does grow (albeit glacially slowly). I can kill the process, and everything then finishes up fairly quickly. What is weird is that if I then re-run the expiration script manually, everything seems to work okay. Any ideas? --- Swartzendruber Consulting, Inc.