Date: Mon, 5 Feb 2001 18:43:08 -0800 (PST) From: Dan Phoenix <dphoenix@bravenet.com> To: Matt Dillon <dillon@earth.backplane.com> Cc: Alfred Perlstein <bright@wintelcom.net>, Jos Backus <josb@cncdsl.com>, freebsd-hackers@FreeBSD.ORG Subject: Re: qmail IO problems Message-ID: <Pine.BSO.4.21.0102051837080.16117-200000@gandalf.bravenet.com> In-Reply-To: <200102060231.f162VL557466@earth.backplane.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
Nope I have not tweaked any kernel variables other thatn the ones i tried
temporarily and put back to normal afterwards.
Ok i will recompile the kernel with 256 maxuser setting and recompile
included is dmesg.boot from one of the machines.....not sure if that helps
as much as info i found in dmesg...as this is just hardware info.
Anyways here it is....should be back in a couple hours after basketball
game to recompile the kernels on those 2 boxes 2 new settings.
Thx for help as of this point.
On Mon, 5 Feb 2001, Matt Dillon wrote:
> Date: Mon, 5 Feb 2001 18:31:21 -0800 (PST)
> From: Matt Dillon <dillon@earth.backplane.com>
> To: Dan Phoenix <dphoenix@bravenet.com>
> Cc: Alfred Perlstein <bright@wintelcom.net>, Jos Backus <josb@cncdsl.com>,
> freebsd-hackers@FreeBSD.ORG
> Subject: Re: qmail IO problems
>
> :ok of those commands some interesting info was from dmesg...
> :on one machine i had
> :file: table is full
> :file: table is full
> :file: table is full
> :file: table is full
> :file: table is full
> :file: table is full
> :file: table is full
> :file: table is full
> :file: table is full
> :file: table is full
> :file: table is full
> :file: table is full
> :file: table is full
> :
> :from dmesg
> :
> :on the other machine
> :looutput: mbuf allocation failed
> :nfs server 172.16.0.101:/bravenet1/home: not responding
> :looutput: mbuf allocation failed
> :looutput: mbuf allocation failed
> :looutput: mbuf allocation failed
> :nfs server 172.16.0.101:/bravenet1/home: is alive again
> :looutput: mbuf allocation failed
> :looutput: mbuf allocation failed
> :
> :i doubt that mbuf allocation failed was from the nfs server timeout that
> :one time....but cannot be certain......this help you at all?
>
> This sheds a considerable amount of light on the problems...
> methinks you may have a low 'maxusers' setting in the kernel
> config. Read on.
>
> I still need the complete 'dmesg' output, or if it all scrolled off
> due to the above errors, cat the '/var/run/dmesg.boot' file.
>
> You had systat -vm 1 output in the earlier emails, but not
> 'vmstat 1' output for 20 seconds. That isn't as big a deal with
> all the other info we have now, but still useful.
>
>
> :[root@arwen qmail-1.03]# pstat -s
> :Device 1K-blocks Used Avail Capacity Type
> :/dev/ad0s1b 1048448 0 1048448 0% Interleaved
> :[root@arwen qmail-1.03]#
> :
> :[root@elrond dphoenix]# pstat -s
> :Device 1K-blocks Used Avail Capacity Type
> :/dev/ad0s1b 528696 2032 526664 0% Interleaved
> :[root@elrond dphoenix]#
>
> This indicates that you are not swapping or paging significantly,
> which is good. We can cross that off the list of possible problems.
>
> :ps axlww
> :
> :included is ps.txt.....
> :2 perl scripts running only on that machine at moment yet qmail queue keep
> :getting larger....seems to be getting abit better but not that great
> :either.
> :
> : (ps output not included in reply)
>
> The ps output indicates that you are running a relatively light process
> load. The prime suspects are thus the file table and mbuf errors.
>
> These errors normally occur when you configure a much too low
> 'maxusers' setting in the kernel config. Since you didn't provide
> the complete dmesg output (cat /var/run/dmesg.boot), I can't tell
> but I am guessing that you are either using the GENERIC kernel
> directly, or you created a custom kernel but didn't tune the
> 'maxusers' entry.
>
> For a machine doing the work this machine is doing, I recommend
> a maxusers setting in the kernel config of 256. You need to rebuild
> your kernel in that case. Have you ever built a kernel before?
> I think all you may need to do is up 'maxusers' in the kernel
> config and perhaps mess around with the number of mbuf clusters,
> but I suspect increasing maxusers will do the trick. These
> changes require recompiling the kernel.
>
> Also, to make sure... you haven't tweaked any other sysctl's, have
> you?
>
> -Matt
>
[-- Attachment #2 --]
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.2-STABLE #0: Fri Feb 2 14:43:07 PST 2001
droot@arwen.bravenet.com:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (498.75-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x672 Stepping = 2
Features=0x383fbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory = 268369920 (262080K bytes)
avail memory = 256974848 (250952K bytes)
Preloaded elf kernel "kernel" at 0xc043f000.
Pentium Pro MTRR support enabled
md0: Malloc disk
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Intel 82443BX host to PCI bridge (AGP disabled)> on motherboard
pci0: <PCI bus> on pcib0
sym0: <875> port 0x1400-0x14ff mem 0xfa200000-0xfa200fff,0xfa204000-0xfa2040ff irq 11 at device 13.0 on pci0
sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
sym1: <875> port 0x1800-0x18ff mem 0xfa201000-0xfa201fff,0xfa204400-0xfa2044ff irq 11 at device 13.1 on pci0
sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0x1060-0x107f mem 0xfa000000-0xfa0fffff,0xfa205000-0xfa205fff irq 10 at device 15.0 on pci0
fxp0: Ethernet address 00:90:27:73:c0:c0
fxp1: <Intel Pro 10/100B/100+ Ethernet> port 0x1080-0x10bf mem 0xfa100000-0xfa1fffff,0xfa202000-0xfa202fff irq 10 at device 16.0 on pci0
fxp1: Ethernet address 00:90:27:af:30:13
isab0: <Intel 82371AB PCI to ISA bridge> at device 18.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel PIIX4 ATA33 controller> port 0x1050-0x105f at device 18.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
uhci0: <Intel 82371AB/EB (PIIX4) USB controller> irq 11 at device 18.2 on pci0
uhci0: Could not map ports
device_probe_and_attach: uhci0 attach returned 6
chip1: <Intel 82371AB Power management controller> port 0x1040-0x104f at device 18.3 on pci0
pci0: <Cirrus Logic GD5480 SVGA controller> at 20.0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/8 bytes threshold
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ad0: 6149MB <QUANTUM FIREBALL CX6.4A> [13328/15/63] at ata0-master UDMA33
acd0: CDROM <IDE/ATAPI CD-ROM 40X> at ata1-master using PIO4
Waiting 15 seconds for SCSI devices to settle
Mounting root from ufs:/dev/ad0s1a
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSO.4.21.0102051837080.16117-200000>