From owner-freebsd-questions Mon Jul 19 13:41:22 1999 Delivered-To: freebsd-questions@freebsd.org Received: from hercules.crossthread.com (hercules.crossthread.com [139.142.137.200]) by hub.freebsd.org (Postfix) with ESMTP id 14B6E14D84; Mon, 19 Jul 1999 13:41:11 -0700 (PDT) (envelope-from timp@orion.ab.ca) Received: from cgytpushor (shl-host1.shl.ca [209.135.106.225]) by hercules.crossthread.com (8.9.3/8.9.3) with SMTP id OAA48755; Mon, 19 Jul 1999 14:41:07 -0600 (MDT) Message-ID: <006801bed227$664d92f0$9828f99f@shl.com> From: "Tim Pushor" To: , Subject: Out of buffer space - REVISITED Date: Mon, 19 Jul 1999 14:43:16 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Let me first apologize for this long message. I realize that I was in panic mode earlier and did not furnish near enough information to draw any sort of conclusion. Here are the facts. I replaced two aging AIX boxes with FreeBSD (after MUCH convincing of our senior management). They trust my judgement, so let me proceed. Saturday I brought the new servers online and shut off the AIX boxes. Today, one of the servers fell over - it couldn't communicate with anything over the network. Ping'ing anything resulting in an 'out of buffer space' error message. Rebooting the server brought it back to life - for about 10 minutes. I have since discovered that I can simply do a ifconfig tl0 down, and an ifconfig tl0 up, and it will begin working again. Another interesting point is that the boxes are the exact same configuration, and the exact same kernel. They are primarily SMTP relay boxes for our company, and have equal MX preferences. They are running sendmail 8.9.3. One of the machines is also running named (stock from the FreeBSD 2.2.8 distribution - 4.9.4 ?? ). This is the machine that falls over. I have found that if I don't run sendmail on the machine that is running named, it stabilizes (so far anyway). A further complication is that I am 3000 miles away from this server :( But I do have access to the console remotely (Compaq Remote Insight). I *really* hope someone can help, as I have put myself out on a limb to get FreeBSD in active use here. Hardware: Compaq Proliant 1600 - PII 450 w/512 MB RAM Integrated ThunderLAN 10/100 NIC running at 10M Integrated NCR SCSI adapter 4G Wide SCSI drive Software: FreeBSD 2.2.8-RELEASE Integrated BIND (4.9.4??) sendmail 8.9.3 Integrated xntpd running Integrated inetd running Integrated cron running Integrated syslogd running System loads: Internal DNS for ~10,000 users on one box Inbound SMTP relays - when both are running they handle approximately 40 sendmail sessions consistently, concurrently - peaking at a maximum of 75. Syslog errors: Jul 19 12:48:26 dalubsmtp01 named[100]: sysquery: sendto([159.249.55.1].53): No buffer space available Jul 19 12:48:26 dalubsmtp01 named[100]: sysquery: sendto([159.249.127.1].53): No buffer space available Jul 19 12:48:26 dalubsmtp01 named[100]: sysquery: sendto([159.249.96.71].53): No buffer space available Kernel: fairly standard configuration - but configured with maxusers 256, which I believe automatically sets NMBCLUSTERS to 4608. Could this really be the problem? Kernel config file: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.77.2.28 1998/09/26 17:36:14 wpaul Exp $ machine "i386" cpu "I586_CPU" cpu "I686_CPU" ident SHLRELAY maxusers 256 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device options FAILSAFE #Be conservative options IPFIREWALL options "MAXMEM=(512*1024)" options INCLUDE_CONFIG_FILE config kernel root on wd0 controller isa0 #controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ncr0 controller scbus0 device sd0 device st0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Mandatory, don't remove device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device tl0 pseudo-device loop pseudo-device ether pseudo-device log pseudo-device vn 4 pseudo-device tun 4 pseudo-device pty 32 pseudo-device gzip # Exec gzipped a.out's pseudo-device bpfilter 4 # This provides support for System V shared memory. # options SYSVSHM options SYSVMSG options SYSVSEM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message