From owner-freebsd-ports@FreeBSD.ORG Thu Aug 25 03:04:09 2005 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1DD2A16A41F for ; Thu, 25 Aug 2005 03:04:09 +0000 (GMT) (envelope-from mworld@rom.no-ip.com) Received: from ip-3-52-145-203.ultraserve.net.au (ip-3-52-145-203.ultraserve.net.au [203.145.52.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id A92DE43D48 for ; Thu, 25 Aug 2005 03:04:05 +0000 (GMT) (envelope-from mworld@rom.no-ip.com) Received: (qmail 92935 invoked from network); 25 Aug 2005 03:04:03 -0000 Received: from amd64.twbc.net.au (HELO amd64) (192.168.0.195) by 0 with SMTP; 25 Aug 2005 03:04:03 -0000 Message-ID: <002a01c5a921$ae5295f0$c300a8c0@amd64> From: "mworld" To: Date: Thu, 25 Aug 2005 13:04:15 +1000 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: FreeBSD 4.11 + Apache 2.0.54 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Aug 2005 03:04:09 -0000 Hi. I have a server with FreeBSD 4.11 on it and Apache 2.0.54. SSL is = active. The Setup: There is another apache running on one ip ( with listen ip:80 and listen = ip:443 ) and the main apache is listening on 13 other ips. The = configuration has 296 vhosts most of them on one ip and some with static = ips for ssl. They all use Rotatelogs for one of their log files. The Problem: Adding just one more listen ip:80 to httpd.conf or one more vhost causes = apache to either 'bus error' or 'core dump'. I have tested this on my = local FreeBSD 5.4 and I cannot reproduce the error. My guess is there is = not enough resources somewhere for apache to start. Perhaps a socket = buffer or something ? Has anyone come across this kind of error or has = any advice on possible solutions ? Thanks. Regards, Otto.