| Summary: | FreeBSD 4.1.1 - Kernel problems | ||
|---|---|---|---|
| Product: | Base System | Reporter: | jfa <jfa> |
| Component: | kern | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
jfa
2000-11-14 20:30:01 UTC
On Tue, Nov 14, 2000 at 12:28:26PM -0800, jfa@mail.sonet.pt wrote: > >Description: > The Kernel of FreeBSD 4.1.1, is to use swap, where the free server has memory, and passed one week, the server crash for: > > zeus /kernel: swap_pager_getswapspace: failed > zeus /kernel: pid 89825 (BitchX-1.0c17), uid 1029, was killed: out of swap space > zeus /kernel: pid 95115 (cron), uid 0, was killed: out of swap space These messages occur when you run out of swap space. Usually it kills the largest running process, so I'm slightly suprised that cron got killed. Can you watch for either lots of small processes building up, or one or two large processes? David. All my servers who are with FreeBSD 4.1.1, they are to occupy Swap, and they have free memory sufficiently. The ones that they are with FreeBSD 4.0 are not to use none swap! -- Best Regards, Jorge Filipe Andrade ___________________________ SONET - Serviços Internet, Lda http://www.sonet.pt ----- Original Message ----- From: "David Malone" <dwmalone@maths.tcd.ie> To: <jfa@mail.sonet.pt> Cc: <freebsd-gnats-submit@FreeBSD.org> Sent: Tuesday, November 14, 2000 8:37 PM Subject: Re: kern/22847: FreeBSD 4.1.1 - Kernel problems > On Tue, Nov 14, 2000 at 12:28:26PM -0800, jfa@mail.sonet.pt wrote: > > > >Description: > > The Kernel of FreeBSD 4.1.1, is to use swap, where the free server has memory, and passed one week, the server crash for: > > > > zeus /kernel: swap_pager_getswapspace: failed > > zeus /kernel: pid 89825 (BitchX-1.0c17), uid 1029, was killed: out of swap space > > zeus /kernel: pid 95115 (cron), uid 0, was killed: out of swap space > > These messages occur when you run out of swap space. Usually it kills > the largest running process, so I'm slightly suprised that cron got > killed. Can you watch for either lots of small processes building up, > or one or two large processes? > > David. > Fix: The fix of this problem, as available here: http://www.freebsd.org/cgi/query-pr.cgi?pr=19714 -- Best Regards, Jorge Filipe Andrade ___________________________ SONET - Serviços Internet, Lda http://www.sonet.pt State Changed From-To: open->closed Submitter found solution in PR 19714. |