From owner-freebsd-questions Fri Jul 26 12:00:58 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA16547 for questions-outgoing; Fri, 26 Jul 1996 12:00:58 -0700 (PDT) Received: from fw.tabula.com (fw.tabula.com [204.160.137.2]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA16539 for ; Fri, 26 Jul 1996 12:00:50 -0700 (PDT) Received: by fw.tabula.com (4.1/SMI-4.1) id AA28237; Fri, 26 Jul 96 12:00:49 PDT Received: from tab012.tabula.com(204.119.64.12) by fw.tabula.com via smap (V1.3) id sma028235; Fri Jul 26 12:00:14 1996 Received: by tabula.com (5.x/SMI-SVR4) id AA06100; Fri, 26 Jul 1996 11:58:38 -0700 Date: Fri, 26 Jul 1996 11:58:37 -0700 (PDT) From: Thor Clark To: Geoff Mohler Cc: questions@freebsd.org Subject: Re: Problem. In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Had a very similar problem - the machine didn't panic, it just stopped creating new processes. Processes currently running continued to run, and the machine responded to pings, but it would not create new processes for telnet, http, cron jobs, etc. (I eventually had to resort to the cron reboot...) It turned out to be a bug in 2.1 Release. I upgraded to 2.1.5 (took about 40 minutes), and have been up with no problems for a week. (I still see the 'rtq_reallyold' messages - they seem to happen in response to a particular type of load on the machine that often triggered the bug) Re update(if this is the same bug): make sure to back-up everything, particularly /etc. Though it is saved off to a tmp directory, I did lose some config files (sysconfig and a couple of others) along the way, and had to go to my backups. Thor Clark On Fri, 26 Jul 1996, Geoff Mohler wrote: > On Fri, 26 Jul 1996, Garrett Wollman wrote: > > > < said: > > > > > Can anyone tell me what this error means? > > > /kernel: in_rtqtimo: adjusted rtq_reallyold to 2400 > > > > It's not an error, just an informational message. The whole dynamic > > expiration thing needs re-working, but I don't hold out any hope that > > it will be soon. > > Why does this seem to co-ordinate wo closely with the machine halting? > > Currently, I have a cron that is booting the machine, every hour before > this 'timer' reaches bottom. And havent had a problem since. > > > Geoff Mohler > Operations Engineer > Charter Communications/ > Phoenix Data Net >