Date: Wed, 6 Oct 1999 05:29:59 -0700 (PDT) From: goodgene@nownuri.net To: freebsd-gnats-submit@freebsd.org Subject: kern/14162: sudden reboot problem ( maybe kernel panic) Message-ID: <19991006122959.1A60A14CC5@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 14162 >Category: kern >Synopsis: sudden reboot problem ( maybe kernel panic) >Confidential: no >Severity: critical >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Oct 6 05:30:01 PDT 1999 >Closed-Date: >Last-Modified: >Originator: jeon chan seok >Release: 3.2 >Organization: digito >Environment: FreeBSD dgl.softmessenger.com 3.2-RELEASE FreeBSD 3.2-RELEASE #0: Mon Oct 4 22:26:03 KST 1999 goodgene@dgl.softmessenger.com:/usr/src/sys/compile/RED+ i386 >Description: My company decide to introduce FreeBSD3.2 as gateway server for Instant Messaging Service. Because my tcp connections should be processed, I increased Maxuser to 300 and so did kernel compiling. And I changed some configurations like below. sysctl -w kern.ipc.somaxconn=1024 sysctl -w net.inet.ip.portrange.last=10000 sysctl -w net.inet.tcp.rfc1644=1 sysctl -w kern.maxprocperuid=1024 In this situation the performance was very good but our 2 FreeBSD3.2 server could last over 4 days. Suddenly the OS is rebooted. H/W specs are CPU Pen 2, RAM 128M, SCSI Adaptec UW 2940, BX tyan board. Is there any misconfiguration? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991006122959.1A60A14CC5>