Re: [7.0.2] problems with spinlock under FreeBSD?

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [7.0.2] problems with spinlock under FreeBSD?
Date: 2000-08-24 12:40:21
Message-ID: Pine.BSF.4.21.0008240940100.801-200000@thelab.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Attached ...

On Thu, 24 Aug 2000, Tom Lane wrote:

> The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> > looking in /var/log/messages, I'm seeing the following just before the
> > crashes:
>
> > Aug 23 12:33:47 pgsql syslogd: /dev/console: Too many open files in system: Too many open files in system
> > Aug 23 12:33:47 pgsql syslogd: /var/run/utmp: Too many open files in system
> > Aug 23 12:33:47 pgsql /kernel: file: table is full
>
> That sure looks like you'd better tweak your kernel settings ... but
> offhand I don't see how it could lead to "stuck spinlock" errors.
> What do you get from gdb backtraces on the corefiles?
>
> regards, tom lane
>

Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org

Attachment Content-Type Size
gdb.out text/plain 5.5 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Vince Vielhaber 2000-08-24 13:33:51 Re: Some gripes about BugTool
Previous Message The Hermit Hacker 2000-08-24 12:32:07 Re: [7.0.2] problems with spinlock under FreeBSD?